Relations

Record ↔ Record

Create or inspect the Record ↔ Record relationship with explicit endpoints, authority, scope, validity and lifecycle state.

Evidence-awareAuthority-awareLifecycle-aware

Purpose

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.

Operational flow

Record ↔ Record lifecycle.

Resolve both endpoints

Validate relation type

Confirm authority & scope

Create relation event

Track expiry/revocation

Object model

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

Operational state

Designed for progressive activation.

InterfacePrepared

BackendIntegration required

Audit trailDesigned

Status modelDefined

Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.

Related PAR domains