1. Purpose
The Wall exists to provide a public instrument through which people can register demand for CTMP deployment by geography, surface pricing deltas against published benchmark estimates under declared assumptions, aggregate submissions into defined procedural consequences, and submit infrastructure designs for qualified public evaluation under published rules.
2. Scope
This Charter governs all public and operational components materially affecting Wall behavior, including public interfaces, client code, build and release pipelines, deployment configuration, data schemas, validation logic, anti-abuse systems, ranking and tally logic, methodology documents, moderation and quarantine tools, admin surfaces, status pages, dispute handling, and third-party services used by any of the above.
No component may escape Charter scope merely because it is internal, temporary, experimental, or administrative if it can influence public outputs or participant treatment.
3. Constitutional order of precedence
- Charter integrity
- Participant safety and privacy
- Correctness
- Public honesty and labeling
- Stability and survivability
- Auditability
- Scalability
- Usability
- Polish
- Novelty
Nothing lower may override anything higher.
4. The six hard constraints
No identity capture
No accounts, no unnecessary personal information, no hidden profiling, no silent conversion of anti-abuse signals into identity records.
No monetization surfaces
No advertising, dark patterns, commercial upsells, pay-to-amplify mechanics, or extractive attention loops inside core public utility functions.
Every public output must be auditable
Every visible tally, ranking, threshold, score, or status must have a traceable source class, formula basis, methodology version, and time basis.
Deterministic logic
Same materially identical input, same output, for everyone, under the same methodology version.
Built to survive
The architecture prefers static-first, edge-first, failure-visible design. If degraded, the system must say so.
The Charter overrides everything
If old behavior conflicts with the Charter, the Charter wins.
5. Truthfulness and public state labels
Every public feature and output must be labeled honestly where relevant. Required label classes include:
- Verified
- Modeled
- Scenario
- Strategic Vision
- Live
- Preview
- Simulated
- Local-device state only
- Partially integrated
- Degraded
- Disputed
- Corrected
- Archived
6. Inputs, validation, and anti-abuse
Raw public submissions are not public facts. All public inputs must pass schema validation, integrity checks, abuse screening, classification, and permitted-use routing. Suspicious or malformed inputs must be quarantined away from public outputs until resolved or expired under published rules.
Anti-abuse controls may include rate limiting, challenge mechanisms, anomaly detection, replay protection, and integrity scoring, but they may not be used as a pretext for identity capture or hidden discrimination.
7. Audit trail and retention
Material events must generate append-only audit records, including methodology changes, output corrections, disputes, exception grants and expiries, releases, emergency rollbacks, dependency substitutions, and data reclassifications. Publicly relevant audit history must remain inspectable.
8. Exceptions and amendments
Exceptions are allowed only when they are specific, scoped, reasoned, time-bounded, publicly recorded, and automatically expiring. Expired exceptions revert automatically. No exception may authorize identity monetization, suppress truthful state labels, or erase audit history.
Amendments require a public process, version history, rationale, and effect date. Foundational clauses such as No Identity Capture, No Monetization Surfaces, Auditable Outputs, Truthful State Labeling, Audit Trail Preservation, and Charter Supremacy are subject to the highest amendment burden.
9. Function-specific constitutional rules
One-Click Mandate
The public must be able to tell what counts, what is provisional, what is local-only, and what is globally authoritative. No tally may imply global authority unless the architecture truly provides it.
Integrity Ledger / Bill Scrubber
Pricing deltas are not findings of guilt. Public outputs must distinguish user-reported prices, benchmark estimates, validation status, provider responses, disputes, and corrections. 250 validated submissions is the minimum public signal threshold for a provider + service type + service territory case; higher thresholds govern formal response and escalation.
Agency layer
Any procedural consequence must be published in advance, timestamped, visible, and reversible only under published correction rules.
Vertical Challenge
Evaluation, reviewer qualification, conflict rules, scoring, disputes, and implementation oversight require a dedicated annex before the function may claim merit-based winner selection.
10. Operator powers and limits
No single operator may silently alter methodology, erase audit history, relabel outputs, grant indefinite exceptions, change thresholds retroactively, or suppress valid public outputs without record. Privileged actions must leave a trace.
11. Enforcement standard
A rule is not enforced because it is stated. A rule is enforced when violation is blocked, recorded, or both. Therefore every Charter obligation must eventually be mapped into one or more of the following:
- build-time block
- release-time block
- runtime guard
- audit log requirement
- public labeling requirement
- exception process
- rollback trigger
This page is part of that visible compliance surface. It states the constitutional order now, and the build must progressively move from declared doctrine to enforced mechanism across The Wall, the Country Race, the Badge, Flame Carriers, and the coming IL / BS functions.