Immutable, hash-verified artifacts • Pre-side-effect policy enforcement • Bit-exact reproducibility • Ternary-native execution
| English | 简体中文 | Español | Русский | Português |
T81 is a substrate for producing canonical decision objects with identity from governed AI tasks.
Instead of interpreting AI output, T81 consumes durable decision bundles that provide complete provenance, deterministic replayability, and cross-system portability.
Policies are evaluated deterministically and enforced before execution or materialization begins. Governance does not rely on runtime heuristics, anomaly scoring, or after-the-fact monitoring. T81 can be adopted incrementally via CanonFS + policy enforcement without requiring full stack adoption.
T81 prioritizes decision integrity over raw throughput. Bundle creation and consumption are optimized for deterministic verification, not maximum inference speed.
The system’s advantages come from identity and provenance guarantees, not from emulated ternary arithmetic performance.
When performance matters more than decision integrity, other runtimes may be better suited. When guarantees matter more than speed, T81 provides verifiable, replayable, policy-bound decisions.
T81 also has in-progress ternary hardware directions, but the usable form today is the decision substrate.
If you want the clearest contributor-facing surfaces in the repo today, start here:
.v1 versioning boundary:
AI_OS_OBJECT_BUNDLE_VERSIONING_BOUNDARY.mdThese are narrower and more buildable than the repo’s longer-horizon OS and hardware directions.
If you want the shortest practical “how do I actually use this today?” guide, start here:
| Subsystem | Role | Maturity |
|---|---|---|
| TISC ISA | Frozen ternary instruction set (v1.9.0) | Frozen |
| T81VM | Deterministic interpreter with Axion hooks | Stable |
| Axion | Governance kernel mediating dispatch | Stable |
| CanonFS | Immutable, hash-verified storage backend | Stable |
| T81Lang | High-level language frontend for ternary logic | Stable |
The Deterministic Core Profile (DCP) (TISC ISA, core VM, and data types) is a Verified Deterministic Surface. Experimental areas (e.g., Cognitive Tiers, full Hanoi VM) sit outside the DCP.
T81 ties immutable inputs to deterministic outcomes through a policy-gated pipeline:
sequenceDiagram
participant Host
participant CFS as "CanonFS"
participant VM as "T81VM"
participant AX as "Axion"
Host->>CFS: Import model/code (canonfs import)
CFS-->>Host: CanonHash81
Host->>VM: Run with weights hash + policy
loop Instruction Cycle
VM->>AX: eval_axion_call(insn)
AX-->>VM: Verdict (Allow/Deny)
alt Allow
VM->>VM: Execute TISC Opcode
else Deny
VM->>VM: Trap (SecurityFault)
end
end
VM-->>Host: Deterministic Result + Audit Trace
This is part of the longer-term systems direction, not the main reason a new contributor should pick up T81 today.
Balanced ternary delivers structural advantages for verifiable inference:
See full benchmarks in benchmarks/results/.
This shows that an artifact can be stored immutably and execution can be denied before it runs.
Run this from the repo root after building:
tmp_root="$(mktemp -d)"
canon_root="$tmp_root/.t81_canonfs"
# 1. Import one artifact into CanonFS
./build/t81 canonfs import \
examples/storage-and-canonfs/canonfs-interchange/v1/model.t81w \
--canonfs-root "$canon_root" \
--json
canon_hash="<imported_objects[0] from step 1>"
# 2. Export the same artifact back out by CanonFS hash
./build/t81 canonfs export \
"$canon_hash" \
--canonfs-root "$canon_root" \
--out "$tmp_root/restored.t81w" \
--json
# 3. Try the same import under a checked-in denying policy
./build/t81 canonfs import \
examples/storage-and-canonfs/canonfs-interchange/v1/model.t81w \
--canonfs-root "$canon_root" \
--policy examples/storage-and-canonfs/canonfs-interchange/v1/policy-deny-all.apl \
--json
What you should see:
status: "ok"status: "ok"status: "error" with kind: "policy-failure" and reason: "policy_denied"See: examples/proofs/canonfs_policy_proof/
This shows:
docker run --rm -it ghcr.io/t81dev/t81-foundation demo
Runs hello-world → ternary demo → determinism check → interactive REPL.
git clone https://github.com/t81dev/t81-foundation.git
cd t81-foundation
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build
ctest --test-dir build --output-on-failure
Key CMake flags:
T81_STRICT_DETERMINISTIC_FLOAT=ON (default) — Enforces bit-exact float paths.T81_HYBRID_MLP=OFF — Keeps pure ternary invariants (requires Axion approval if enabled).pip install .
# Compile and run T81Lang
t81 code build examples/core-language/hello_world.t81 -o hello.tisc
t81 vm run hello.tisc
# CanonFS + policy-gated execution example
t81 canonfs import model.t81w --json
t81 code run inference.t81 --weights-model model.t81w --policy secure_model.apl --trace
Current admitted bounded AI OS-object family examples:
bash examples/ai-and-inference/model-load-canonfs/run_assess_fixed_host_action.sh
That example ends on a stored bundle object, not just an AI task result. The bundle is the top-level persisted object for the current assess-fixed chain and links:
Second admitted bounded composition using the same object model:
bash examples/ai-and-inference/model-load-canonfs/run_route_fixed_path_selection.sh
Third admitted bounded composition using the same object model:
bash examples/ai-and-inference/model-load-canonfs/run_classify_fixed_rule_selection.sh
Short explanation:
Current bounded composition catalog:
Maintainer-facing bounded family status:
Portable smoke path for the same chain:
./build/t81_ai_task_assess_fixed_composition_test ./build/t81The bounded family is now a protected subsystem. Treat these examples as the current admitted family:
assess-fixedroute-fixedclassify-fixedIf you want the bundle-first external-consumer path for that family, start with:
# Install deps (Ubuntu example)
sudo apt-get install -y qemu-system-arm qemu-efi-aarch64 mtools parted
git clone https://github.com/t81dev/t81-foundation.git && cd t81-foundation
./drivers/qemu/scripts/boot_demo.sh
At the t81> prompt: status, policy, help.
agent Inference {
behavior run(prompt: String) -> Tensor {
return Model.forward(prompt); // gated by Axion
}
}
# secure_model.apl
allow infer if model.hash in approved_models;
deny infer reason "unapproved-model";
As of March 2026, The T81 deterministic core (ISA, VM, data types) is stable and governed by a monthly C2 review cadence. Active risks, implementation matrix, and decision logs are tracked in docs/status/.
T81 prioritizes verifiability, determinism, and governance over broad compatibility. When decision integrity matters more than raw throughput, T81 provides verifiable, replayable, policy-bound decisions.
For deeper technical mapping (Natural Language Space → Code Entity Space), see the Project Overview in the DeepWiki.
T81 is being developed toward a computing model where cognition becomes a first-class software substrate. Rather than treating model weights as opaque blobs behind external runtimes, T81 treats them as governed software artifacts: provenance-bound, policy-mediated, and executable within bounded cognitive tiers.
The long-term goal is an operating environment where cognitive software can be stored, invoked, composed, and governed with the same rigor applied today to code, processes, and files.
Apache 2.0
Thanks for checking out T81. Early feedback, issues, and contributors are welcome!