Mirrors / pub — Free Computation Foundation

Mirror policy

FCF preservation follows a simple rule: a URL is not a backup. A resource is considered preserved only when FCF controls a copy of the bytes and records an immutable identity such as a full Git commit or SHA-256 digest.

Current public state: the CENTL preservation, SHA-256 integrity, release-authentication, no-network rebuild, and OCI recovery-capsule tooling are implemented in the canonical source tree. The actual FCF preservation store and public artifact mirror are still being provisioned. This page will not label bytes as mirrored until those copies exist and pass the defined audit gates.

Browse: Index of /pub

CENTL preservation set

Resource class	Public status	Identity / recovery contract
CENTL source	Canonical repository available	Exact Git commit + deterministic source SHA256SUMS receipt
CENTL native releases	Available from GitHub Releases	Archive SHA-256; signed release SHA256SUMS supported for FCF-authenticated releases
Build/toolchain sources	Preservation tooling implemented; FCF store provisioning pending	Immutable archive SHA-256 or full Git commit
CENTL-SCi model weights	Preservation-by-content-hash implemented; not served by this Pages site	Exact GGUF SHA-256 + provenance
Development caches/environments	Snapshot tooling implemented; FCF store provisioning pending	opam/Julia snapshot manifests + source commit
Linux recovery capsule	OCI build/save/run tooling implemented; first preserved capsule pending	Saved OCI archive SHA-256 + no-network recovery test

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 implementation and operational boundaries are documented in the supply-chain preservation guide, integrity and authentication guide, and release-signing guide.

Planned public hierarchy

/pub/
  centl/
    releases/
    source/
    toolchain/
    models/
    manifests/
    keys/
  SHA256SUMS

The exact backing store may move as FCF infrastructure grows. Public URLs are a distribution layer; 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 and OpenBSD signify for authenticated FCF release checksum manifests. No custom hash or signature algorithm is introduced.

Canonical source

Until an item is explicitly marked mirrored here, use the CENTL repository and official releases as the distribution source.