Public Compliance Surface
Compliance, status, and known limits.
This page exists so the build cannot quietly imply stronger enforcement, authority, or integration than it actually has. It shows what is live, what is preview-only, what is local-device state only, and what is still pending backend or charter enforcement. The Charter, truth labels, and known-gap register are now part of the visible organism.
Charter version
draft-1
Governing standard in public view
Build version
phase1-charter-c5
Front-end phase one organism
Shared state
wall.phase1.state.v1
Canonical preview store
Backend authority
Pending
No global authoritative ledger yet
Visible truth labels are part of the Charter. The Wall, Country Race, Badge, and Flame Carriers now carry public state labels so the build cannot quietly imply stronger authority than it actually has.
Current enforcement posture
This build is charter-aligned and partially charter-constrained at the front end. It is not yet fully charter-enforced at the backend, audit, or anti-fraud level.
- Truth labels: config-driven across the build
- Canonical state: live in the front end
- Global ledger: not yet live
- Fraud resistance: not yet globally enforced
- Referral verification: not yet globally authoritative
Threshold decision now governing IL / BS
250 validated submissions is the new minimum public signal threshold for a specific provider + service type + service territory case.
This means the case becomes visible, tracked, and cumulative on the Wall, but does not yet imply guilt, fraud, or formal response-window activation. Higher thresholds govern formal response and escalation.