Participants
Who participates in the governed relationship.
GOVERNANCE & FEDERATION
Governance Without Universal Authority
CRU allows governed computational objects to cross boundaries without requiring participating domains to surrender control of their own governance.
01
Governance Is Bounded
An organization may establish governance over the resources, operations, relationships, and computational objects within its legitimate domain. A CRU can carry verifiable evidence of decisions made under that governance.
Portable governance does not mean universal authority.
02
The Governance Boundary
A CRU provides a computational boundary within which identity, state, evidence, provenance, and governing conditions can be evaluated coherently. But the CRU’s governance boundary does not eliminate the authority boundary of the receiving system.
The object carries its governance.
The receiving domain retains its authority.
03
Governed Result
Governance evaluates evidence and context under applicable policy.
Evidence + Context + Policy
Governance Evaluation
Governed Result
A Governed Result expresses an outcome under defined conditions and authority—not authorization everywhere.
04
Authority Context
Every Governed Result exists within an Authority Context: which authority produced it, for what purpose, under what governance, and within what boundary it applies.
A Governed Result can travel farther than the authority under which it was produced.
05
Verification Is Not Authorization
Domain B may verify Alice’s identity, state, provenance, and assertions from Domain A. That establishes authenticity. It does not require Domain B to grant Alice authority.
AUTHENTICITY// DOES NOT IMPLY //ADMISSIBILITY// DOES NOT IMPLY //AUTHORITY
06
Asymmetric Federation
The source domain determines the semantics and context of what it presents. The receiving domain determines whether that information is admissible and what local effect it may have.
SOURCE DOMAIN
Governed Assertion / Result
Authority Context
DOMAIN BOUNDARY
RECEIVING DOMAIN
Verification
Admissibility
Local Governance → Local Effect
Both domains retain their own authority.
07
Bounded Cross-Domain Mapping
Where domains choose to federate, they can establish an agreed and bounded mapping. The mapping defines how legitimate evidence or authority from one context may be interpreted within another; it does not manufacture authority.
Domain A Qualification
Agreed Mapping
Domain B Interpretation
Local Governance
Local Capability
08
When Federation Is Not Enough
Sometimes organizations need more than recognition of one another’s assertions. They may need to govern a shared resource, mission, service, relationship, or process together. That requires explicit shared governance.
09
CRU Contract
A CRU Contract establishes a governed relationship among participating domains.
Delegated Authority
What authority is explicitly contributed.
Responsibilities
What each participant is accountable for.
Conditions
When the relationship applies.
Governance Rules
How shared decisions are evaluated.
Change & Revocation
How the relationship evolves or ends.
Shared authority must be explicit rather than assumed.
10
From Bilateral to Multiparty Governance
A governed relationship may involve two organizations—or many. The number of participants does not change the principle: each participates under explicit governance, limited to powers actually delegated.
Domain A
Domain B
Domain C
Domain D
11
Events Do Not Create Authority
CRU-TR can represent governed dependencies and event relationships.
Event
CRU-TR
Governance Evaluation
Governed Result
CRU-TR can initiate governance. It cannot manufacture authority.
12
Local Enforcement Remains Local
The receiving domain remains responsible for its own resources.
Source Assertion
Verification
Authority Context
Local Admissibility
Receiving-Domain Governance
Local Governed Result
Local Enforcement
PRINCIPLE
Governance Without Universal Authority
Verify what another domain presents. Understand the authority under which it was produced. Determine whether it is admissible locally. Apply local governance. Share governance explicitly when necessary.
CRU makes governance portable without making authority universal.
Use Cases
See how the same governed-object model responds when roles, missions, risks and domains change.
Explore Use Cases →