Skip to content

Latest commit

 

History

History
26 lines (21 loc) · 1.6 KB

File metadata and controls

26 lines (21 loc) · 1.6 KB

Phase 1 Supervisory Sandbox Engagement Framework (2026–2028)

1. Objective

To establish a transparent, high-frequency engagement model between the institution and the regulator during the Supervisory Control Plane (SCP) Phase 1 sandbox.

2. Roles and Contact Points

  • Institution Lead: Chief AI Safety Officer (ASO).
  • Technical Lead: SCP Platform Architect.
  • Regulator Lead: Supervisory Sandbox Office Manager.
  • Verification Lead: Regulator Technical Auditor (Verifier Node Operator).

3. Reporting Cadence

  • Daily DevSecOps Reports: Automated summaries of G-SRI, attestation health, and proof pipeline status.
  • Weekly Summaries: Human-in-the-loop review of the week's transitions and any policy exceptions.
  • Monthly Metrics: Deep dive into systemic resilience, control effectiveness, and roadmap progress.
  • Quarterly Roadmap Reviews: Strategic alignment on sandbox exit criteria and upcoming feature rollout.

4. Regulator Query Triage and Escalation

  • Level 1 (Standard): Technical queries regarding specific logs or proofs. Response time: 24 hours.
  • Level 2 (Urgent): Queries regarding G-SRI threshold breaches or containment events. Response time: 4 hours.
  • Level 3 (Crisis): Escalation to ASO and Board Risk Committee. Linked to GSM "QUARANTINE" state. Response time: 1 hour.

5. Observation Windows and Drills

Regulators are invited to observe "Red Dawn" chaos engineering drills and "Rogue-Yield" simulations.

  • Schedule: Monthly scheduled drills; quarterly unannounced "Surprise Drills".
  • Evidence: Signed drill reports and replayable incident timelines.