# 🚀 T81 Foundation — Beginner Onboarding Q&A

[t81dev]

Welcome. If you're new to T81, start here.

This thread answers common entry questions and helps you orient yourself before diving into specs or code.

---

🔹 What is T81 Foundation in simple terms?

T81 is an experimental computing stack built around:

• A ternary (base-3) numeric foundation
• A custom instruction set (TISC)
• A deterministic virtual machine
• A policy enforcement layer (Axion)

The long-term goal is reproducible, auditable execution — especially for AI and scientific workloads.

---

🔹 Do I need to understand ternary logic to contribute?

No — but it helps.

You can contribute in areas like:

• Documentation
• Testing
• Tooling
• CLI improvements
• CI workflows
• Performance benchmarking

Ternary internals matter most if you're modifying arithmetic, ISA behavior, or VM execution.

---

🔹 How do I build the project?

From the repository root:

cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --parallel

Then run:

./build/t81 --help

If it builds and runs, you're ready to explore.

---

🔹 What should I read first?

Recommended order:

1. README.md (high-level overview)
2. Canonical Architecture document
3. TISC ISA spec
4. VM implementation (src/vm)
5. Axion policy layer (src/axion)

You don’t need to absorb everything at once.

---

🔹 What makes this project different?

Most systems treat determinism as optional.

T81 treats it as foundational.

That affects:

• Instruction design
• Runtime behavior
• Policy enforcement
• Roadmap decisions

The architecture is intentionally strict.

---

🔹 I don’t understand everything. Is that expected?

Yes.

This is a layered system:

• Surface layer: CLI + language
• Mid layer: ISA + VM
• Deep layer: arithmetic encoding + determinism mechanics
• Governance layer: Axion

You can enter at any layer.

---

🔹 What are good first contributions?

Beginner-friendly areas:

• Clarify confusing documentation
• Improve code comments
• Add unit tests
• Refactor small utilities
• Improve CLI UX consistency
• Expand usage examples

If you’re unsure, ask here first.

---

🔹 How do I propose changes?

Before coding:

1. Ask in Discussions.
2. Reference the spec.
3. Explain architectural impact.
4. Explain determinism implications.

Changes that affect execution semantics require careful review.

---

🔹 Is this trying to replace existing systems?

No.

This is exploratory architecture work — pushing on deterministic execution, governance-aware computation, and ternary-native modeling.

It’s a research-grade ecosystem.

---

🔹 Where can I ask beginner questions?

Right here in this thread.

If something seems obvious but unclear — ask.

Clear questions help improve documentation for everyone.