How CRU Works

Start with the object.

Conventional systems often distribute responsibility for an object across multiple services. One establishes identity. Another stores state. Another evaluates policy. Another determines permissions. Another records provenance.

CRU brings those concerns into a common governed representation.

The database, network, cloud, application, or execution environment can change without necessarily redefining the object itself.

Canonical Representation

Portability requires more than copying data. Two systems need a deterministic way to determine whether they are evaluating the same logical object and state.

The particular storage or transport mechanism does not define the CRU.

Evidence and Context

Identity alone rarely determines authority. A governance decision may depend upon the object’s current state together with applicable evidence and context.

Governance Evaluation

Governance gives those inputs meaning. This is broader than authentication. Authentication may establish identity. Governance determines what may occur under the current conditions.

Governed Result

A Governed Result expresses the outcome of a particular governance evaluation.

Not “Authorized Everywhere.”

Authorized Under These Conditions.

A Governed Result exists within an Authority Context that establishes the boundary within which the result has meaning.

From Governed Result to Capability

The capability is not arbitrary authority carried by an object. It is an operational expression of applicable governance.

Capability Leases

Not every capability should become a permanent entitlement. CRU can support capabilities bounded by purpose, scope, conditions, or time.

Just enough. Just in time.

Governed State Transitions

A proposed change does not have to become accepted state merely because someone attempted to modify the object.

The object persists while governance determines which state transitions become authoritative.

Event-Driven Governance

A qualification may expire. A mission condition may change. A device may become compromised. Another governed object may change state.

A trigger can initiate governance. It does not manufacture authority.

Disconnected Operation

Where the required CRU state, evidence, governing rules, and applicable capabilities are available locally, governance need not require continuous connectivity to a centralized service.

Disconnected does not mean uncontrolled operation.

Separation of Trust and Execution

The source of authority does not necessarily have to be the environment performing the action.

This separation allows governance to travel without requiring every participating system to become part of one centralized trust environment.

The CRU model.

Cryptography establishes evidence. Governance determines meaning. Governed results determine permitted effect within bounded authority.

CRU makes that relationship a property of the governed computational object rather than leaving it entirely implicit in the infrastructure surrounding it.