This guide is the deterministic portal: it lays out the ledgered path from cloning the repo to shipping a change, complete with Axion policies, canonical builds, and reproducibility checkpoints.
-DT81_USE_CXX23=OFF).make.user.name/user.email; ensure your commits carry identity so the ledger stays auditable.| Area | Purpose |
|---|---|
include/t81/ |
Public headers (t81::v1) — add APIs that respect Axion and ternary invariants. |
src/ |
Implementation for compiler, VM, tools, and deterministic tooling with canonical builds. |
tests/cpp/ |
Regression proofs; every manifest change gets tests. |
docs/ |
Guides, portal narratives, and quickstarts (Doxygen output is generated under build/api). |
spec/ |
Normative constitution; updates require RFCs under spec/rfcs/. |
benchmarks/ |
Benchmark runners and report generation scripts that feed docs/reference/benchmarks.md. |
tools/, scripts/ |
Utility helpers used in reproducibility workflows (Axion trace capture, policy generation). |
Always refer to ../explanation/ARCHITECTURE.md and ../explanation/DESIGN.md before modifying cross-cutting subsystems.
git clone https://github.com/t81dev/t81-foundation.git
cd t81-foundation
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release # this config is the baseline manifest entry
cmake --build build --parallel
ctest --test-dir build --output-on-failure
cmake --build build --target docs # regenerates build/api/html
T81_BUILD_TESTS, T81_BUILD_BENCHMARKS, and T81_BUILD_EXAMPLES can be passed to cmake as ON/OFF to scope the build and keep the ledger concise.ctest --test-dir build -R <regexp> to rerun a subset (e.g., -R tensor) when verifying targeted invariants.build/api; open build/api/html/index.html locally after running the docs target to confirm the manifest matches the implementation.For migration-aligned runtime validation, run the canonical e2e bundle from
t81-examples:
scripts/run-canonical-runtime-demo.sh
Use t81-foundation/examples as reference and research demos; contract
promotion evidence should use the t81-examples runtime bundle.
The primary entrypoint is the t81 binary built under build/.
t81 compile <file.t81> [-o <file.tisc>]
t81 run <file.t81|.tisc>
t81 check <file.t81> (syntax + semantic validation)
t81 benchmark [benchmark flags]
t81 weights import <safetensors|gguf> [...]
Semantic errors reported by t81 compile now include a file:line:column snippet so you can locate the problem immediately.
t81 compile/run exercises the frontend→TISC→VM pipeline covered in ../explanation/ARCHITECTURE.md.t81 weights quantize … --to-gguf produces GGUF models for llama.cpp../build/t81 --help.tests/cpp/t81_tensor_* exercises tensors; fixes here have fast feedback loops.t81_tensor_matmul_test and confirm failure with ctest -R tensor_matmul.include/t81/types or core/types keeping RAII/no-exceptions rules.tests/cpp/.docs/how-to/tensor-guide.md or relevant doc to describe new behavior.cmake --build build --target t81_tensor_matmul_test plus ctest -R tensor_matmul and rerun cmake --build build --target docs.cmake caches stale options, delete build/ and re-configure.clang-tidy later if desired.ctest, run the executable directly (./build/t81_tensor_matmul_test) to see stdout.../../spec/t81lang-spec.md, ../../spec/tisc-spec.md, ../../spec/t81vm-spec.md, ../../spec/t81-data-types.md.../explanation/ARCHITECTURE.md, ../explanation/DESIGN.md, ../reference/system-status.md.../../CONTRIBUTING.md, ../../spec/rfcs/template.md.../guides/adding-a-language-feature.md.Keeping this guide up-to-date is critical: each release should confirm the commands still work and the CLI workflow matches ../../README.md.