The Bazaar

FCF origins, CARAVAN provisioners, preserved bytes, and immutable identities.

Bazaar policy

The Bazaar is the public directory of places from which FCF material can be obtained. A stall in the Bazaar is a provisioner, not an authority: FCF origins and CARAVAN carriers may supply bytes, while immutable content identity and authenticated metadata determine which bytes CENTL trusts.

Current public state: CENTL preservation, SHA-256 integrity, release authentication, no-network rebuild, model provenance, CARAVAN Phase 1, and the fail-closed FCF Semantic Origin exporter are implemented in the canonical source tree. The dedicated FCF artifact/model origin and public CARAVAN carrier network are still being provisioned. This page will not claim those bytes are publicly supplied until they are actually reachable and pass their audit gates.

CARAVAN census

Active Camels ๐Ÿชโ€”
Lost Camels ๐Ÿชโ€”

Census not live yet

The public counter contains aggregate carrier counts only. It does not publish volunteer IP addresses, hostnames, usernames, email addresses, locations, or a per-node roster. Active and Lost are defined by authenticated heartbeat windows in the CARAVAN census contract.

Browse: Index of /pub

Provisioners

ProvisionerStatusRole
FCF source repositoryliveCanonical CENTL source and development history.
FCF release channellive through GitHub ReleasesCurrent release archives and adjacent integrity material.
FCF Semantic Originpublication contract implemented; origin provisioning pendingDirect content-addressed distribution of a redistribution-approved CENTL-SCi model.
CARAVAN provisionersPhase 1 laboratory; public rollout gatedAuthenticated replication and retrieval of public-approved artifacts without granting carriers authority.

CENTL preservation set

Resource classPublic statusIdentity / recovery contract
CENTL sourceCanonical repository availableExact Git commit + deterministic source SHA256SUMS receipt
CENTL native releasesAvailable from GitHub ReleasesArchive SHA-256; signed release SHA256SUMS supported for FCF-authenticated releases
Build/toolchain sourcesPreservation tooling implemented; FCF store provisioning pendingImmutable archive SHA-256 or full Git commit
CENTL-SCi model weightsPreservation and public-origin export tooling implemented; current Q4_K_M publication blocked pending exact quantized provenance and redistribution approvalExact GGUF SHA-256 + bound provenance + explicit public-approved state
Development caches/environmentsSnapshot tooling implemented; FCF store provisioning pendingopam/Julia snapshot manifests + source commit
Linux recovery capsuleOCI build/save/run tooling implemented; first preserved capsule pendingSaved OCI archive SHA-256 + no-network recovery test

Semantic route

local content-addressed model cache
        |
        v
FCF Semantic Origin
        |
        v
authenticated CARAVAN provisioners
        |
        v
same approved SHA-256 identity

The route can change without changing authority. CENTL-SCi and MIRAGE can run locally once the exact qualified bytes are present; no hosted inference API is part of the semantic trust path.

Implemented recovery path

source receipt + exact commit
        |
preserved dependency/model bytes
        |
SHA-256-protected OCI build capsule
        |
no-network rebuild + test + Nemo differential gate
        |
release SHA256SUMS
        |
FCF signify signature

The operational boundaries are documented in the semantic-origin contract, supply-chain preservation guide, integrity and authentication guide, manual CARAVAN joining guide, and release-signing guide.

Public hierarchy

/pub/
  centl/
    releases/
    source/
    toolchain/
    models/
      ACTIVE.json
      sha256/
    caravan/
      catalog-v1.json
      census-v1.json
    manifests/
    keys/
  SHA256SUMS

The exact backing store may move as FCF infrastructure grows. Public URLs are distribution routes; they are not the sole preservation copy or cryptographic identity.

Integrity and authentication

SHA-256 detects byte changes when the expected digest is trusted. It does not by itself prove who published that digest. CENTL therefore keeps integrity and authentication separate: standard SHA-256 for byte identity, OpenBSD signify for authenticated FCF release checksum manifests, and TUF-authenticated catalog metadata for CARAVAN distribution. No custom hash or signature algorithm is introduced.

Canonical source

Until an item is explicitly marked live in The Bazaar, use the CENTL repository and official releases for the currently published material.