What we will show
Turn interview notes, system inventories and sample exports into a reviewable system map; ingest and reconcile versioned records; and produce an evidence-linked report under explicit privacy and disclosure rules.
Demonstrators
Scenarios that make the architecture answerable.
The demonstrations are not showcases with hidden decisions. They are repeatable experiments designed to expose ownership, uncertainty, policy, failure and human authority.
Demonstrator 01
Charity systems discovery and reporting
A synthetic mental-health charity has a patchwork of CRM, case-management, spreadsheet and manual reporting processes. Staff spend scarce time finding and reconciling information.
What must remain visible
- gaps, conflicts and unknowns;
- the provenance of every reported result;
- the rule or transformation applied;
- human correction and approval; and
- duplicate, malicious and out-of-order inputs.
Demonstrator 02
Care disruption and rebooking
A consultant or specialist becomes unavailable, creating a time-sensitive coordination problem across synthetic appointments, capacity, priorities, approvals and communications.
What we will show
Receive a disruption, identify affected work, propose policy-constrained options, require meaningful approval and track actions, notifications, refusals and unresolved cases.
What must remain visible
- independent component ownership;
- versioned and explainable constraints;
- human approval of consequential action;
- safe handling of partial failure; and
- cases beyond the scenario's authority.
- Disruption
A service publishes a change in availability. - Impact
Scheduling identifies affected synthetic work. - Options
Capacity and policy constrain the response. - Authority
A person approves, changes, defers or rejects.