Distribution index
| Name | Type | Location / state |
|---|---|---|
| CENTL source | developer/research distribution | github.com/chasebryan/centl |
| CENTL v0.14.0 | current Oasis release | latest release |
install | stable GNU/Linux installer | Oasis installer |
| FCF Semantic Origin | qualified semantic-artifact distribution | Publication tooling exists; individual artifacts remain subject to provenance and redistribution gates. |
| CARAVAN | authenticated artifact availability | Phase 1 local laboratory is established; later carrier enrollment/public-origin rollout remains gated. |
| Checksums and release authentication | integrity / identity | Published and validated according to the active release contract. |
Source checkout
git clone https://github.com/chasebryan/centl.git
cd centlThe default repository checkout is the comprehensive developer/research distribution. Stable product authority is the oasis branch.
Ordinary installation
curl -fsSLO https://raw.githubusercontent.com/chasebryan/centl/oasis/install
sh installCENTL v0.14.0 is the current published Oasis release. GNU/Linux x86_64 is its active stable native release boundary.
CARAVAN support
CARAVAN participation is a form of infrastructure contribution. Once qualified public enrollment is opened, volunteer carriers can contribute bounded storage, bandwidth, and availability to approved FCF artifacts without becoming content authorities. Current join tooling can be tested and prepared without silently enabling public network service.
Semantic publication
Semantic artifacts are not published merely because a model can run locally. A candidate must satisfy the applicable provenance, content-identity, licensing/redistribution, preservation, and publication gates before FCF or CARAVAN advertises it as an approved artifact. See the FCF Semantic Origin contract.
Hosting policy
FCF distinguishes an index from a provisioner. This page may point to canonical release objects, while The Bazaar records whether underlying bytes are actually preserved and publicly supplied under an FCF or CARAVAN distribution contract.
Large binary artifacts are not forced into the Pages Git repository. The static site remains the human-readable directory; large qualified artifacts belong in a dedicated FCF origin or other explicitly provisioned backing store.