Source Trust
Context Sources
- Historic Site Note
- Contractor Observation
- Planning Condition
- Project Record
The purpose of the Trust Layer is to help users understand why information can be trusted.
Trust Layer concept
Hold does not create trust by scoring information. It helps users see where information came from, whether it is current, and why related records or aliases are connected.
Reusable Trust Cards
These cards are intended to be embedded later across Logistics, Estates, Aggregates, Signal and Governance pages without creating a separate trust dashboard.
Context Sources
Review Status
Related Context
Why it matters
A major refurbishment programme completed in 2018 changed the crusher feed assembly and created maintenance references still connected to the current asset record.
Action
Design principle
The role of the Trust Layer is to make provenance, currency and operational relationships visible when they matter.
It should remain calm, lightweight and close to the operational record being viewed.
Where a Related Context item points to a supporting record, document, project note or historic reference, Hold should be able to bring the supporting evidence forward when context matters.
Hold should try to answer the next obvious question, not every possible question. The Trust Layer should show not only that two things are connected, but why that connection matters.
Keep this calm and lightweight: small explanatory text, short "Why it matters" notes and optional source-record actions. No long document previews, no AI certainty language and no heavy dashboard treatment.
Signal notices something. Trust shows where the information came from. Reasoning explains the current situation. Operational Memory explains what happened before. Contextual Identity helps preserve what something was known as.
Governance shows where responsibility sits when context needs review, change or escalation.
Provenance shows the path back to the original source record or supporting evidence.