ARCHITECTURE
The system, page by page.
Every concept in tebako has exactly one page here — from the wire format to the trust model, from the VFS to the trace toolkit.
The model
02
Overview
What tebako is and what it does — the one-page picture.
03
Concepts
The wire format, the trailer, slot records, flags, and format IDs.
04
Anatomy
What is inside a running tebako process, exit codes included.
05
Building blocks
The nine parts of the system, one page each.
06
Contract model
The edges, the evolution law, and the non-goals.
Runtimes
Loading and dispatch
10
Dispatch
How a command name becomes the right payload, version, and runtime.
11
Driver contract
The wire format the bootstrap uses to hand off to the runtime.
12
Composition
The dependency grammar: requires, needs, mounts, resolution.
13
The store
The ~/.tebako directory: runtimes, payloads, shims, registries, trust.
14
VFS model
The userland virtual filesystem: mount table, longest-prefix dispatch, pluggable backends.
15
Image formats
The format axis: limnifs, dwarfs, squashfs, zip — and auto-detection.
The host boundary
Trust
Observability
The project
22
Repositories
The repo map: who owns what, and the product crate map.
23
Comparisons
How tebako compares to version managers, containers, and language packagers.
24
Contributors
The engineering order, contract suites, and the SSOT ownership table.
25
Migration (v1→v2)
What changed between the v1 and v2 architectures.
26
v1→v2 flag map
The flag-by-flag migration guide for the tebako CLI.