Relationship Layer
Express who or what is related to whom, under which role, authority, scope and period of validity.
One function. Explicit trust boundaries.
Relations convert isolated identifiers into a verifiable graph of roles, ownership, control, authority and record-to-record dependency.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Relations functions.
The domain is separated into explicit functions so status, authority, evidence and lifecycle transitions can be inspected independently.
Person ↔ Company
Create or inspect the Person ↔ Company relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →02Company ↔ Authority
Create or inspect the Company ↔ Authority relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →03Person ↔ Device
Create or inspect the Person ↔ Device relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →04Person ↔ Asset
Create or inspect the Person ↔ Asset relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →05Asset ↔ Owner
Create or inspect the Asset ↔ Owner relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →06Record ↔ Record
Create or inspect the Record ↔ Record relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →07Authority ↔ Record
Create or inspect the Authority ↔ Record relationship with explicit endpoints, authority, scope, validity and lifecycle state.
Explore →Relations lifecycle.
Resolve both endpoints
Validate relation type
Confirm authority & scope
Create relation event
Track expiry/revocation
Minimum verification context.
The exact schema can vary by object class and policy version, but the verification layer should be able to resolve these core dimensions.
- Relation ID
- Source entity
- Target entity
- Relation type
- Role / scope
- Authority
- Validity period
- Status
Designed for progressive activation.
Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.