The Hub now distinguishes who produced an object, who owns it, who holds it, who may act on it and what use is permitted.
The optional evidence_governance envelope adds authority, validation, interoperability and lifecycle controls without deleting, renaming or restructuring existing Hub objects. In the protected Evidence Explorer, the envelope is now stored as a revision-controlled companion profile linked to the existing evidence ID.
Profiles now attach to existing evidence without overwriting it.
An authorised reviewer can initialise a held profile from recorded evidence, edit controlled fields with field-specific guidance, record a bounded human review and inspect immutable revision history. Guidance never inserts or infers operational facts. Revision locking prevents one reviewer from silently overwriting another reviewer’s newer changes.
1
Select evidence
Open an existing spatial-calibration record in the protected Evidence Explorer.
2
Initialise safely
Recorded values are copied with durable references; unsupported values remain unconfirmed.
3
Review under identity
The authenticated reviewer records scope, purpose, uncertainty, exceptions and reliance posture.
4
Preserve history
Every revision receives a hash, actor, timestamp and change summary.
P0 enforcement: conditional or permitted reliance is rejected while any Authority or Validation field remains unconfirmed. The evidence producer cannot record the bounded reliance action.
Four control families
Twenty-two fields, one bounded envelope.
When the optional envelope is used, every field must carry a controlled status. A blank cell is not an acceptable substitute for uncertainty.
P05 fields
Authority
Separates producer, owner, custodian, legal authority and usage rights.
producer
owner
custodian
legal_authority
usage_rights
P07 fields
Validation
Records the bounded human review and the purpose for which reliance may or may not occur.
reviewer
protocol
review_scope
accepted_purpose
uncertainty
exceptions
reliance_status
P15 fields
Interoperability
Makes mappings and exports versioned and testable without implying external conformity.
external_standard
schema_version
mapping
export_profile
interoperability_test
P15 fields
Lifecycle
Names the steward and preserves the route from update through supersession, retirement and history.
data_steward
update_trigger
supersession
retirement
change_history
Backward-compatible adoption
Legacy objects remain valid.
1
Existing object
The object remains unchanged when no evidence-governance envelope is present.
2
Profile when touched
Add the optional envelope only when the record is reviewed, exported or materially updated.
3
Confirm from evidence
Populate a value only when a source reference supports it.
4
Expose uncertainty
Record unconfirmed with a note when evidence is absent.
Controlled QA
Rwanda note and synthetic transaction.
The same 22-field profile is applied to one existing opportunity note and one synthetic transaction. The Rwanda record deliberately remains held where authority and permitted use are not evidenced.
Loading controlled test records…
Extension boundary
Sector-specific data does not reshape the core.
LCI process context and functional-unit data are available only through the inactive TV-EG-EXT-LCI-0.1 reference profile. Activating or extending that profile would require separate governance review and would still not establish conformity with an external method or standard.
Completing these fields does not make an object accurate, admissible, certified, investment-ready or fit for institutional reliance. A named human reviewer and the receiving institution retain those decisions under their own authority.
