Cubie-tf architecture

Resource library map

A reader-friendly map of the monorepo, the public Cloudflare library, and the scope boundaries behind the headline claims. Use this page to pick the right entry point before downloading evidence or citing a claim.

Open claims registry Try API workbench Machine catalog Repo source

Start here Library data plane Claim boundaries Repo layout Containers & dependencies Why it matters ← Resource library

Start here

Browse library Find an artifact

Start from the collection browser when you know the family, date, or object prefix.

Claims registry Check a headline

Use this for public statements. It carries the source evidence and the caveats.

Agent index Automate lookup

Agents should start with /llms.txt and /api/catalog instead of scraping pages.

Workbench Inspect APIs

Try list, catalog, search, ask, object, capabilities, and OpenAPI routes in place.

Live resource-library data plane

collections

Proofs, archives, logs, evidence packs, learning packs, and whitepapers.

grounded claims

Each headline claim has status, scope, evidence, reproduce steps, and known gaps.

machine catalog

Live /api/catalog backed by D1, with R2-listing fallback if D1 is unavailable.

answer surface

Workers AI answers from source excerpts; ranked-search fallback remains available.

PublishSmall repo locator manifests point at public R2 object keys.

CatalogD1 indexes exact keys, sizes, hashes, source refs, and collection metadata.

BrowseHumans use cards and filters; agents use /llms.txt and /api/catalog.

Answer/api/ask answers from retrieved sources with ranked-search fallback.

Claim boundaries

These cards mirror the grounded claims registry: live artifacts are cited directly, and scoped claims carry the limitation in the same place as the metric.

Proof corpusScoped

Mixed Coq, Lean, and Verus snapshot. Cite manifest-scoped checks, not blanket closure.

TEP replayScoped

V8.1 reports 96.745% on the complete recovered replay; the 100/100/100 peak remains a same-trace control, not held-out validation.

Agentic wastePublic data

Public JSON reproduction pack and REPRODUCE.md are available from the claim page.

EU AI ActScaffold

Rust crates compile and generate mappings, but the conformity pack is not fully populated.

Core Cubie runtime ← cubie-mathEU AI Act layer ← cubie-euControl plane / TrustFortress ← tf-rusty + trustfortressProof kernels triple-kernelApps & UI surfacesSupport / infra shared bolt-on feature-gated / optional module foundation depended on by everything

Repository layout — the four layers + proof kernels

Proof kernels

triple-kernel

Coq + Lean4 + Verus proof corpus with manifest-scoped closure evidence.

coq

Coq corpus; zero-axiom claims are scoped to checked manifest subsets.

coq/ →lib

lean

Lean 4 corpus; use manifest and local checks before closure claims.

lean/ →lib

verus

Verus specs; verification is scoped to the checked files and gates.

verus/ →lib

Core Cubie runtime

← cubie-math

no_std bare-metal geometric trust runtime + admit pipeline + FFI.

cubie-corefoundation

Foundation: ternary cells, 54-cell topology, Belnap, geometry. 40 crates depend on it.

cubie-core/

cubie-platform

Admit pipeline (L0–L5), cycle bounds, PCIe, trust_fabric, SemanticAuth consumer.

cubie-platform/

cubie-control

Control-path crypto (HMAC/SHA-256, P-384 attestation).

cubie-control/

cubie-ffibolt-on

C ABI / Python ctypes bridge (CubeObjectV1 192B).

cubie-ffi/

cubie-qecbolt-on

Quantum-error-correction stabilizer helpers.

cubie-qec/

bare-metal

no_std targets: riscv32imc / x86_64-none / aarch64-none.

bare-metal/

cubie-projector

Recursive face/topology projector (HTTP /compile/recursive).

cubie-projector/

cubie-tepbolt-on

Tennessee-Eastman detector; public metrics are calibration/proxy scoped.

cubie-tep/

cubie-tdx-shimbolt-on

Intel TDX guest/host shim; standalone, not yet admit-wired.

cubie-tdx-shim/

EU AI Act layer

← cubie-eu

Articles 9/10/11/13/14/15 + Annex IV conformity, ledger, attestation.

cubie-eu-articles

Article 9/13/14/15 obligation predicates.

crates/cubie-eu-articles/

cubie-eu-annex-iv

Annex IV technical-documentation generator.

crates/cubie-eu-annex-iv/

cubie-eu-attest

Conformity attestation + assurance.

crates/cubie-eu-attest/

cubie-eu-ledger

Dual ledger / consent hierarchy.

crates/cubie-eu-ledger/

cubie-eu-tdxbolt-on

TDX host-side attestation scaffolding; lab validation deferred.

crates/cubie-eu-tdx-host/

Control plane / TrustFortress

← tf-rusty + trustfortress

Attestation, audit, governance, identity, MCP, edge control.

tf-attestation

Runtime attestation service.

controlplane/tf-attestation/

tf-audit

Merkle-chained audit trail.

controlplane/tf-audit/

tf-governance

Policy governance + drift denial.

controlplane/tf-governance/

tf-identity

Workload identity seams.

controlplane/tf-identity/

tf-mcpbolt-on

MCP transport / tool surface.

controlplane/tf-mcp/

tf-edgebolt-on

Edge control node.

controlplane/tf-edge/

Apps & UI

surfaces

TrustFortress app, dashboards, MCP surfaces, demos.

trustfortress

TrustFortress app: confidant-server, gauntlet, MCP.

apps/trustfortress/

cubie-dashboard

Trust dashboard UI.

cubie-dashboard/

resource-library

This library Worker (R2 archive + this map).

apps/resource-library/

Support / infra

shared

Datasets, benches, eBPF dataplane, manifold, tooling, docs.

ebpf-dataplanebolt-on

eBPF dataplane hooks.

ebpf-dataplane/

core-manifold

Shared manifold / tf-core theorems.

core-manifold/

dataset-runnerbolt-on

Offline dataset scoring (never gates prod).

dataset-runner/

cubie-tools

CUB allocator, corpus metrics, wiring tools.

cubie-tools/

Containers, cuts & dependencies

Where the monorepo is cut (layer boundaries preserved from the frozen source repos), how the containers depend on each other, and which are bolt-on (feature-gated / optional). cubie-core is the foundation everything builds on.

everything→ depends on →cubie-core40 crates → the foundation

cubie-platform→ depends on →cubie-core + cubie-controladmit path over runtime + crypto

cubie-eu-*→ depends on →cubie-coreEU obligations over the runtime — CUT at crates/ (Annex IV traces layer names)

controlplane/tf-*→ depends on →cubie-platformcontrol plane over the admit platform — CUT at controlplane/

apps/trustfortress→ depends on →controlplane/tf-*app surfaces over control plane — CUT at apps/

verus specs→ depends on →cubie-core / cubie-platformin-crate proof-to-code bindings (ensures over real fns)

Docker deploy units: root Dockerfile(.server/.demo/.intel-profiler), apps/trustfortress-full/* (edge, local, mcp-proxy), apps/trustfortress/* (edge, local, compliance-dashboard). Bolt-on modules are feature-gated crates that attach without touching the core admit hot path.

Why it matters

headline claims with public status, evidence, reproduce steps, and gaps

verification kernels with scoped evidence: Coq · Lean 4 · Verus

EU AI Act

Articles 9/13/14/15 + Annex IV mapped through layer names

R2+D1

Large evidence stays out of Git, while the catalog remains machine readable

Manifest-scoped verification. The geometric trust runtime carries proof-to-code bindings in crate and evidence manifests. Use the linked manifests and local verifier commands before making blanket proof-closure claims.

TDX roadmap + patented IP. Intel TDX/SPDM/DOE shim code exists, but real hardware validation and admit-pipeline wiring remain deferred until lab evidence is published. Patents include US 11,956,363 B2 & US 12,073,439 B2; the runtime stays proprietary.

Historical archive. This resource library keeps bulky artifacts out of Git — proof artifacts, evidence packs, recovery bundles, datasets, transcripts — with SHA-256 locators committed in-repo for provenance.

Generated from the cubie-tf workspace manifest · served by the resource-library Worker · lib.trustfortress.ai