Policy before reasoning
The local reference path applies an organisational rule before work continues. Production identity and deployment controls remain qualification dependencies.
Reference demonstration
See how an AI-assisted request is kept within bounds.
Choose a synthetic route and scenario to see how the interface represents redaction, policy, escalation and evidence. The sequence is illustrative and deterministic; it is not a live provider request or proof of deployment readiness.
Synaporia Guided Scenario
3. Security controls & simulation
Configure controls and click 'Run Synthetic Scenario' to trace the illustrative sequence...
DEMONSTRATION: safeguard outcomes are represented in this browser.
DEMONSTRATION: no external service or business system is contacted.
Illustrative Recourse Record
This panel demonstrates the fields a future controlled recourse record could expose. It does not use a tenant key, encrypt customer data or establish compliance with any legal regime.
No illustrative record. Run a high-risk scenario to populate this panel.
Synaporia Mobile
*144#
Synchronous USSD State Flow
This synthetic handset illustrates the repository's synchronous CON/END and session-fencing contract. It is not connected to a carrier gateway.
State: DIALIN_PENDING
What the demonstration represents
A target control path—with visible qualification boundaries.
The browser models authenticate → minimize → authorize → supervise → evidence. Individual controls have different maturity levels, and this page does not prove that an end-to-end production path has been deployed.
Evidence at every step
Local checks support review of a decision record. Independent production assurance, retention and export remain incomplete.
PII masked at the edge
Local examples can hide supported structured fields. Production privacy testing is incomplete, and no claim is made that every identifier can be detected.
Loop & cost guard
Resource-limit contracts and negative loop scenarios exist locally. Atomic provider cost reservation and billing reconciliation are not production-qualified.
Durable execution
Local tests cover repeated requests and uncertain results, but complete production recovery testing is still required.
Channel-aware design
Basic-mobile timing and session rules are locally tested. Live mobile and messaging connections are not deployed.