TYRVAQ / CURRENT BRIEF
Human authority is a system requirement.
SPARTA is TYRVAQ’s proposed consent and governance layer across AEVION and connected ASSETs. This page explains the intended boundaries. Protected review and safety controls need implemented authorization and test evidence before they can be called operational.
Current architecture · 4 October 2026
The Continuity Kernel roots identity and continuity. GATE interprets intent. SPARTA independently compiles and enforces finite authority. The System Resource Fabric evaluates feasibility with zero policy authority. Destination controllers enforce physical limits, and independently attested outcomes establish what actually happened.
Consent + override
The user should be able to decline, stop, disconnect, or reduce capability without fighting the system.
Safety + privacy
Safety, privacy, power, thermal state, and approved purpose constrain what the system is allowed to do.
Identity + authorization
Private material should be delivered only after verified identity, agreement evidence, owner approval, and per-resource grants exist.
Recording boundary
For covered private reviews, recording is off by default. Any exception must be specific, explicit, and separately authorized.
The public bundle contains public material.
Confidential engineering should never be hidden inside public HTML, downloadable models, source maps, or client-side password checks. A private-review experience belongs behind authenticated delivery, not visual secrecy.
Not every artifact belongs in the same room.
The classification boundary comes before upload, not after something sensitive has already become public.
Concept story, approved renders, sanitized architecture, published policies, and material intentionally released to visitors.
Named materials disclosed to approved reviewers for a defined purpose under the applicable review process.
Secrets, provider credentials, unpublished implementation detail, sensitive source, and material not approved for disclosure.