Authority Preservation Substrate
The substrate layer that preserves who had the right to act — across humans, autonomous agents, and multi-party workflows.
Authority precedes computation. H33-74 preserves what happened. H33-Root preserves who had the right to make it happen.
H33-74 (Evidence Root) See the Architecture →Most systems can reconstruct what happened. Some can prove what decision was made. Few can answer the question that matters most when an autonomous system acts on your behalf: "Did this actor have the authority to act?"
H33-Root is the substrate that preserves authority across a delegation chain — from the human who granted permission, through every intermediate agent, to the action that ultimately executed. Without it, evidence trails are missing their first and most important link.
Click a scenario. H33-Root checks every link in the delegation chain before the action ships. Either the chain is complete — or the action is rejected and the rejection itself becomes signed evidence.
CFO delegated scope=contracts ≤$15M to controller. Controller delegated scope=vendor-onboarding to AP automation. AP automation delegated scope=$10M tier to vendor-onboarding agent. Every link is signed, time-bounded, and scope-checked. Action executes. The evidence bundle ships with the full authority tree attached — verifiable years later by an external auditor with no H33 contact required.
Both outcomes produce a portable artifact. The "allowed" bundle proves the action happened with valid authority. The "blocked" bundle proves the system didn’t act and exactly why — equally valuable evidence.
H33-Root is not an AI feature. It is the substrate layer that sits beneath every workflow where someone needs to prove later who was permitted to act.
Encryption, evaluation, and attestation are all downstream of the question: was this actor permitted to do this in the first place. H33-Root sits above the lifecycle, not inside it.
H33-Root is a Core Infrastructure substrate. It applies to humans, agents, multi-agent chains, and cross-company workflows equally. Positioning it as "AI governance" misses 80% of the use cases.
Every H33-74 attestation can carry an H33-Root authority binding. Verification recovers both: what happened (Evidence Root) and who was permitted (Authority Root). Independent verifiers check both without contacting H33.
An H33-Root authority chain remains verifiable even if H33 disappears, the original software is replaced, or the organization that granted authority no longer exists. The chain is the asset.
H33-Root and H33-74 are the two foundational substrates of the H33 machine. Everything in tiers above eventually consumes one or both.