Original Source
Example
Refurbishment 2018 Project Record
Provenance Through Context
The purpose of the Provenance Layer is to help users understand where information originally came from, how it entered the organisation, and what source record or evidence sits behind it.
Core question
Where did this come from?
Trust shows where information came from, how current it is, and how it connects. Governance shows where responsibility sits. Provenance shows the origin path.
Section 1 - Provenance
Where did this come from?
Provenance preserves the path back to the source.
Created By
Example
Maintenance Contractor
Created Date
Example
14 March 2018
Source Type
Example
Project File
Section 2 - Operational Memory
Why did this happen?
Operational Memory preserves the path back to the reason.
Why It Happened
Feed assembly failures causing downtime.
Outcome
Reliability improved following refurbishment.
Lessons Learned
Inspection intervals increased.
Superseded By
Maintenance Regime 2021
Worked example
Crusher / CR-01
Related context: Refurbishment 2018. The user can scan where the information came from, then immediately see why the change happened.
Provenance Context
- Original Source: Refurbishment 2018 Project Record
- Created By: Maintenance Contractor
- Created Date: 14 March 2018
- Source Type: Project file
Operational Memory
- Why It Happened: Feed assembly failures causing downtime.
- Outcome: Reliability improved following refurbishment.
- Lessons Learned: Inspection intervals increased.
- Superseded By: Maintenance Regime 2021.
Contextual Identity
Known As
Flint
Purpose
Show how the asset, project, location or operational item may be referenced in conversations, emails, reports and historic records.
Why This Matters
Historic maintenance records, project documents and operational conversations may refer to this asset as Flint rather than Crusher CR-01.
Example User Questions
- Why are people talking about Flint?
- Is Flint the same as CR-01?
- Why can't I find Flint in the asset register?
Contextual Identity helps users join operational conversations, emails, project records, maintenance history and asset registers without needing prior local knowledge.
Boundary
Provenance, Operational Memory and Contextual Identity should stay calm and lightweight. They show origin, reason and naming context without long document previews, evidence dumps or AI certainty language.
Connection to other layers
Companion concepts, scanned together.
Trust answers: Can I trust this?
Governance answers: Where does responsibility sit?
Provenance answers: Where did this come from?
Operational Memory answers: Why did this happen?
Provenance helps users understand where information came from. Operational Memory helps users understand why things changed. Contextual Identity helps users understand what something is known as. Together they help preserve the path back to understanding.