Multi-System Reconciliation
What is decision lineage and why does it matter?
Last reviewed
Direct answer
Decision lineage is the record of how a governing number came to be: which sources supplied evidence, what disagreement existed, which authority decided, what was determined, and which reports, recommendations and actions then used it. It matters because it lets an operator explain, defend, audit or reverse any decision built on that number.
Videos that answer this question
Watch: Coherence before Intelligence · 9:24
Watch: Why SeniorCRE · 2:09
Watch: Can You Trust the Operating Picture of Your Enterprise? · 1:39
Watch: Can You Defend Every Number? · 1:37
Watch: You Run the Community. You Deserve Information You Can Trust. · 2:43
Watch: How Do You Scale Operating Consistency? · 1:48
Watch: The Information Behind Every Care Decision · 1:21
Watch: SeniorCRE Architecture of Coherence — Full Film · 3:45
Watch: SeniorCRE Clinical Record · 8:18
Watch: Senior Care Tech Paradigm · 8:30
Watch: RIDEA Governance Gap · 7:15
Watch: The Blind Spot: Connecting Capital to Care · 5:11
Watch: Truth before Intelligence · 10:50
Watch: Governing SI Truth · 7:34
Watch: The Architecture of Operational Truth · 7:45
Watch: The Monday Morning Number · 9:14
Watch: Governance Before SI · 10:54
Watch: The Illusion of Identical Returns · 4:56
Watch: The Institutional Operator · 5:31
Watch: The Operator Authority Chain · 6:50
Watch: SeniorCRE for REITs · 1:30
Watch: The Evidence · 1:36
Watch: The SeniorCRE Platform · 1:36
Watch: Workforce Intelligence Explainer · 7:20
Why this happens
Data lineage shows where values came from. Decision lineage also shows who decided and why.
When SI and automation act on operating data, decision lineage is what connects each action back to human authority.
Hypothetical example: an integration copies a stale value
Payroll
Team member: active
The termination has not yet been processed.
HR system (copied from payroll)
Team member: active
The integration copies the value as-is.
Scheduling
Team member: terminated
The manager removed them from the schedule.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Two systems agree because one copied the other. Agreement produced by copying is not verification.
The governance question
A conventional technology sequence is integrate, normalize, analyze, automate. A governing sequence is Evidence, Disagreement, Authority, Operator-Controlled Operating Record, Intelligence, Execution. SeniorCRE Intelligence works downstream of operator authority. The difference is that disagreement is surfaced and decided by the operator rather than resolved invisibly by software.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Detect disagreements instead of letting the last write win.
- Route conflicts to the person with authority to decide.
- Distinguish rule-based resolution from human determinations.
- Record every reconciliation decision with its lineage.
- Standardize reconciliation rules across the organization.
SeniorCRE perspective
SeniorCRE’s architecture treats integration as a source of evidence and reconciliation as a governed act. Software can apply rules the operator has approved; anything outside those rules goes to a named person, and the decision is recorded. Unified data is not governed truth. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
