Roots for real organizations
Human, threshold-controlled, and enterprise roots represent different ways of controlling an identity. Their anchor records carry the commitments and policies needed to verify them.
Authority, anchored
Follow authority back to its roots.
GAL connects identity documents, organizational lineage, and revocation to a shared on-chain trust root.
Global Anchor LayerIllustrated study
Defined scope / checked / bounded
A permission is a condition, not a blank cheque.
Global Anchor Layer
01 / Built for a purpose
Who gave this agent permission?
A signature tells you which key signed. GAL helps answer the next question: where does that key’s authority come from? It anchors root identities and organizational commitments so applications can verify a chain of control.
Small commitments, portable documents
Full identity documents remain off-chain. GAL records the cryptographic commitments that let a resolver check the document it retrieved from a registry or other source.
Revocation comes first
A valid old signature should not rescue revoked authority. Resolution checks the subject and its ancestors so a revoked root can invalidate dependent authorization paths.
Membership you can prove
Organizational Merkle roots let members present inclusion proofs. A verifier checks membership against the anchored root instead of taking a directory’s answer on faith.
A changing organization, a traceable history
Sequence numbers, shard assignments, and topology records describe how anchored state evolves. Updates have an order that resolvers can inspect.
↳ Local policy example
Draw the boundary.
Give an agent room to act. Decide what it can do, set its budget, and send a task through your rules.
EXAMPLE / 00
Authorized space+
·
Permission + budget
✓ compute allowedand✓ 35 ≤ 60 credits
↳
Your rules. Its next move.
Run the task, then try turning off its permission or lowering the budget.
02 / From intent to outcomeA clear path through
A clear path through
global anchor layer.
- 01
Check revocation
Reject a revoked subject or ancestor before accepting its claimed authority.
- 02
Verify the root and document
Compare the retrieved document with its active anchor and cryptographic commitment.
- 03
Verify the relationship
Check parent signatures and any required organizational inclusion proof.
The details matterGood questions.
Good questions.
Clear answers.
Does GAL store every identity document?+
No. It stores anchors, commitments, and lifecycle records. Documents can be retrieved from compatible off-chain sources and checked against those anchors.
How is GAL different from a registry?+
A registry helps discover and retrieve a document. GAL provides the on-chain reference against which its authority and integrity can be verified.
Keep exploringOne capability.