GDPR Compliance Simulator
Execution-time admissibility against illustrative European enforcement patterns, plus a separate stateful trajectory that shows authority decay and a re-bonding checkpoint. Browser-only — payloads are not sent to BiDigest APIs or third-party models.
The production A · S · C · F IFQ engine and stateful trajectory methodology are patent pending. This UI is a client-side illustration only.
Three paths to start
For engineering and architecture reviewers: read the brief, run the browser simulator, then request a scoped assessment when you are ready to map domain, orchestration, and authority source. Deeper doctrine, roadmap tags, and operator handbooks are linked below—not required on first read.
- Step 1
1. Architecture brief (primary)
Payload shapes, control-flow diagram, wire-field glossary, and integration FAQ for verify → verdict → receipt_id.
- Step 2
2. This page — illustrative simulator only
Client-side panels only. Payloads are not sent to BiDigest APIs or third-party models from this UI.
Scroll down to run the panels on this page.
- Step 3
3. Scoped authorization assessment
Map your domain, orchestration path, and authority source before production verify traffic.
High-risk commit gate (illustrative Phase 2)
Browser-only storyboard for dual control at the commit boundary. Production on main still uses a single approver_id — see docs/internal/RISK_CONTEXT_TIER_ROADMAP.md.
HIGH-RISK COMMIT GATE
CRITICAL · HIGHL1 APPROVAL
Risk_Officer_Alpha
Execute (locked)
Demo: execute stays disabled until dual-control completes. Production requires approved row + execute secret; Phase 2 would add explicit multi-approval states — this UI does not call the API.
You are acting as the Accountable Executive (L2).
Stateful trajectory
Featured: Sovereign shadow citation breach (non-allow-listed URL with strong A/S/F). Alternatively, run the stepped decay from 0.98 to the 0.84 floor or a manual authority breach. Browser-only — no API calls; IFQ numbers are illustrative.
EXECUTION_BAR // authority_ttl = 1.00 (λ decay, threshold 0.2)
Start a synthetic trajectory to chain decision receipts. The execution bar reflects remaining authority (A0 → threshold).
BiDigest Gateway
Select a scenario to run a synthetic execution-boundary trace.
- Clause
- —
- Status
- IDLE
- Node
- BiDigest_GW_01
EXECUTION_BOUNDARY_v4.0.1 // —
Awaiting execution payload…
Target scenarios
Synthetic payloads only — no data is sent to BiDigest APIs. "Reset system" clears the terminal.
This simulator utilizes historical public data. To determine how foundational models will process your domain's proprietary Ground Truth, queue a live Forensic Audit.
Not legal advice. Scenarios are simplified for product education; always consult qualified counsel for compliance decisions.