CENTL manuals
| Document | Subject |
|---|---|
| CENTL-SCi | Scientific interpreter architecture and evidence boundary. |
| CENTL-MIRAGE | Local self-development architecture, provenance, candidate staging, and assurance boundaries. |
| CENTL CARAVAN | Content-addressed preservation and availability architecture. |
| CARAVAN Phase 1 | Bounded local laboratory implementation and validation boundary. |
| Installation | Native install, offline archives, and GNU/Linux release contract. |
| Syntax | CENTL language syntax. |
| Mathematics | Supported mathematical operations and boundaries. |
| Numerical contract | Exactness, approximation, and justified output. |
| Physics | Typed exact-first physics operations and limits. |
| Verification | Claim checking and evidence. |
| Machine protocol | Programmatic protocol surface. |
| MCP adapter | MCP integration. |
| Architecture | System design and implementation structure. |
| Repository map | Supported source-tree organization and active/historical boundaries. |
| Oasis release standard | Repeatable consolidation, hardening, and validation declaration. |
| v0.14.0 candidate notes | Current release boundary and Oasis qualification status. |
| Roadmap | Planned development. |
| Changelog | Release history. |
Preservation and trust
| Document | Subject |
|---|---|
| Supply-chain preservation | FCF-controlled dependency/model snapshots, mirror layout, OCI recovery capsule, and no-network rebuild process. |
| Integrity and authentication | Standard SHA-256 source/dependency/release verification and the separation between integrity and publisher authentication. |
| Release signing | OpenBSD signify release manifests, recoverable key custody, verification, and rotation. |
| Release verification keys | Public-key directory policy and practical recoverable signing-key operations. |
| Security policy | Supported versions, threat boundaries, reporting, and Oasis security gate. |
Development
Site policy
This index points at repository copies so documentation follows the canonical source revision. Public mirror status is intentionally conservative: implemented tooling and actually provisioned FCF-hosted bytes are reported separately.