Check provenance
A value should carry its source and retrieval context. Different systems may use different definitions or reporting periods.
INSIGHTS / EVIDENCE BEFORE CONFIDENCE
A fluent explanation can hide stale sources or a reporting mismatch. An evidence-led workflow asks what data was used, whether the scope matches, which checks passed, and what remains unresolved.
02 / THE OPERATING CONTRACT
A value should carry its source and retrieval context. Different systems may use different definitions or reporting periods.
Matching values can strengthen support, but shared upstream errors can still exist. Disagreement should be visible and investigated.
Explain the reporting scope, exclusions, and calculation method. Keep assumptions separate from observed facts.
When a reviewer resolves a conflict, record the choice and its basis. The new result should carry that decision forward.
03 / CONNECTED BY DESIGN
Inspect the sequence.
Each stage has a defined responsibility.
Select a node to inspect its role in the workflow.
Define the source of truth, permitted actions, accountable owner, and acceptance criteria. Scope matters more than an open-ended instruction.
Check the outcome, capture unresolved exceptions, and preserve the relevant policy and evidence. A task is complete only within its defined boundary.
04 / A CONCRETE EXAMPLE
If one source includes a different reporting period, the contradiction is about scope rather than arithmetic. Choosing the larger or more recent value without investigating would hide the actual issue.
Use explicit acceptance checks for authoritative source, reporting period, freshness, arithmetic, and unresolved exceptions.
05 / QUESTIONS & BOUNDARIES
Architecture descriptions show intended system behavior. Validate implementation, integration, data handling, and operational controls before relying on a production workflow.
No. The interface uses qualitative confidence states to communicate evidential support and uncertainty.
No. It shows sources, calculations, checks, assumptions, and concise decision factors.
Identity, context, policy, evaluation, verification, execution, and audit form one operating model. Explore the related components below to see their responsibilities.
06 / CONTINUE THE EXPLORATION