DEMONSTRATION ENVIRONMENTLAKEVIEW GENERAL HOSPITALSYNTHETIC DATA ONLYNOT FOR PHIFictional hospital · real Nexus governance logic
Alice · the authority layer inside Nexus
Policies
A policy in Alice is a rule that runs on every decision, not a document in a binder. Approved policies come from the organization; two more are derived from signals — an intelligence event and a readiness gap — and are labelled by source and status.
approved · v1.0approved policy
Data Sovereignty Policy
DEMO-POL-001 · owner Privacy Officer
Scope: All AI requests touching PHI or regulated data
PHI and regulated data may only be processed by sovereign models inside hospital-controlled infrastructure; never over an external network.
Nothing an agent produces is published or sent outside the boundary without a named human's approval (the Alice kernel's no_external_publish restriction).
Scope: AI-involved incidents at a prescribed hospital
Derived from the Intelligence Terminal item on O. Reg. 51/26: AI-involved security events are reported on the regulation's timelines. Draft pending Security Committee approval; applied as REVIEW only.
Autonomy Cap for Unverified Inventory (GOV-04 gap)
DEMO-POL-006 · owner AI Governance Lead
Scope: Agents whose host system was discovered rather than approved
Derived from the readiness assessment's critical blocker GOV-04 (shadow AI present): agents attached to a discovered system are capped at Level 1 and every non-public request is reviewed until the inventory is verified.
DRAFT POLICIESA draft policy is applied as REVIEW only — it can hold a request for a human but never block or allow on its own until approved.
Alice on this site runs over the synthetic Lakeview General Hospital environment. Verdicts, checks, and receipts are computed by the Nexus decision engine on synthetic requests; nothing here is a customer, a patient, or a production deployment. Signed-in organizations see their own agents, decisions, and receipts.