Start with the execution model, the foundational execution architecture: reusable VM/OS support, open-ended compatible network instances, explicit proof profiles and independently placed workers.
| specification | scope |
|---|---|
| release train | origin source pins, stack/product gates, platform receipts and owner promotion |
| execution model | normative architecture; implementation coverage is reported separately |
| native node adapter | durable acceptance, request retry, HTTP bounds and legacy import |
| genesis pipeline | burial snapshot → the chain.md §4 genesis file (tade) → block-0 state root; owners, balances, particles, links, passports and the decisions behind them; debug export |
| terms | shared vocabulary |
| types | data/type model |
| languages | language contracts |
| filenames | portable source-tree paths |
| vault composition | first storage/sync use case; secret custody, complete replicas and device-loss recovery |
| routing | the wire obeys the graph: greedy forwarding by locus over FOLLOW links, gravity-pressure fallback; radio stays transport, tru never dials |
| chain | the phase-1 root chain: hemera proof of work, ASERT, two neuron transaction kinds plus coinbase, bbg state root, genesis from the burial, heaviest chain with a reorg limit and sunset checkpoints, staked cyberlinks, scheduled forks for later rule sets |
| chain-economy | the focus economy in consensus from genesis: epochs of 240 blocks, the boundary block as beacon, positions with stake and valence (lock, unlock, payout), genesis weights, φ* over the staked graph, settlement of Δφ⁺ by one gradient solve recomputed on every node, the subsidy split between miners and the focus pool, attacks, vectors |
| chain-wire | the chain's network: cyber-radio topics and request streams, header-first sync, discovery through the graph, limits, the HTTP surface cyb and true-cyber use |
| chain-conformance | acceptance vectors: hemera anchors, compact target, ASERT, header and PoW, transactions, identities, state, consensus, genesis pipeline, wire |
| kadek composition | the media codec stack; pure-Rust video/audio decode and encode, containers, conformance |
Soft3 owns composition invariants. Trident, warriors, proof systems and node products own their specialized interfaces. Foundations explains the substrate; chains as plugins discusses protocol adapters over it.
report placement across the stack
Each repository keeps audits, implementation status reports, benchmark results
and release validation in its root audit/ directory, grouped by subsystem
when needed. specs/ and reference/ define contracts, invariants, formats and
acceptance criteria. Mixed documents keep their contract here and move observed
results into an audit report, linked from the relevant contract or index.
Reports retain their checked revisions, dates, evidence and limitations. Relocation updates relative links and graph paths together. A report's results describe the recorded check; a directory move does not revalidate them.