resident-request.txt
Move a recurring family visit from Wednesday afternoon to Thursday morning for four weeks.
Interactive Arca walkthrough
See the evidence trail.
A controlled demonstration using fictional care-home records. No live customer data is processed.
01
Evidence received
Three records define the evidence boundary.
Arca starts with the exact records available to the workflow.
policy.md
The change is allowed when no documented care activity conflicts with the requested time.
staff-note.txt
No conflicting activity is recorded. Recommendation: approve the change for four weeks.
02
Provenance captured
The sources remain attached to the workflow.
Arca records which exact records formed the basis of the result.
resident-request.txt
policy.md
staff-note.txt
ARCA
Evidence state
Sources3
Policy version1.0
Evidence boundaryDefined
03
Decision reconstructed
The recorded result stays connected to its evidence.
Scheduling change
APPROVED
The requested Thursday morning visit can be scheduled for four weeks.
Policy rule 1
No conflicting activity
APPROVE
Notify family contact
Update internal schedule
04
Verification
Verification makes silent changes visible.
First verify the recorded state. Then simulate a change to one source.
Verification status
VERIFIED
The current evidence set matches the recorded state.
Source records3
Policy version1
Staff assessment1
Evidence setIntact
Changed source
staff-note.txt
“No conflicting care activity is recorded” becomes “A conflicting care activity is recorded”.
05
Reconstruction
Months later, the evidence trail is still understandable.
The organisation can see what information was used and how the recorded result was produced.
01
REQUEST
resident-request.txt
02
POLICY
policy.md · v1.0
03
STAFF NOTE
staff-note.txt
04
RECORDED RESULT
Scheduling change approved
“If someone asks later why this action was taken, the organisation can reconstruct the evidence basis.”
This is an explanatory simulation of Arca’s evidence, provenance, verification and reconstruction concepts using fictional records. It is not a live customer workflow and does not validate medical, legal or policy correctness.