Who owns this?
Show who owns the record, asset, process, location or operational decision.
Governance Through Context
Hold governance is not about adding another reporting layer. It is about helping people understand who owns information, who reviews it, who can approve change, and where responsibility sits.
Governance Layer concept
Governance should remain close to the operational record being viewed.
The purpose is not compliance reporting. The purpose is accountability visibility. Operational understanding helps people decide what to do next. Accountability trails show how the current understanding was reached, reviewed and carried forward.
Who reviews this?
Show who is responsible for reviewing whether information remains valid.
Who can change this?
Show approval state, change authority and where human review is required.
Governance Cards
Lightweight accountability context
These cards are intended to sit beside operational records, signals and review notes without becoming a heavy approval workflow.
Operational Owner
Purpose
Show who owns the record, asset, process, location or operational decision.
Example
Quarry Manager
Review Authority
Purpose
Show who is responsible for reviewing whether information remains valid.
Example
Engineering Lead
Approval Status
Purpose
Show whether the information is current, under review, superseded or awaiting approval.
Example
Current
Escalation Path
Purpose
Show who should be contacted if the issue requires operational action.
Example
Operations Manager
Site Director
Human Review Required
Purpose
Show where AI, Signal or historic context can assist understanding but cannot authorise action.
Example
Historic context identified. Current operational decision required.
Example operational record
Crusher / CR-01
A simple governance context pattern showing who owns the record, who reviews it, and when human review is required.
Governance Context
- Operational Owner: Quarry Manager
- Review Authority: Engineering Lead
- Approval Status: Current
- Escalation Path: Operations Manager
- Human Review Required: Yes, if historic restriction affects current access
Why this matters
The crusher record may include historic restrictions, maintenance references and local names. Governance context helps a user understand who is accountable before relying on that context for an operational decision.
Boundary
Governance can show responsibility and review routes. It should not imply that AI, Signal or historic context can approve current operational action.
Connection to Trust Layer
Trust shows evidence. Governance shows responsibility.
Trust shows where information came from, how current it is, and how it connects.
Governance shows where responsibility sits.
Provenance shows where the information originated.
Governance grows through visible accountability. It should remain calm, lightweight and close to the operational record being viewed.
Governance notes
July 2026 — Hold Content Use Policy introduced
Hold introduced a Content Use Policy early in the life of the project, distinguishing public human review and evaluation from AI model training or dataset use without permission.