Site Stewardship Principles governing The Wall and its supporting systems.
The Wall is governed by a public charter — the Site Stewardship Charter. The charter is the constitutional order for how the public instrument is allowed to behave, what it may not do, and how gaps must be honestly labeled until full enforcement exists. If existing behavior conflicts with the charter, the charter wins.
The charter governs The Wall, the Country Race, the Badge layer, Flame Carriers, the Integrity Ledger, the Bill Scrubber, and the Vertical Challenge. No component escapes charter scope merely because it is internal, temporary, experimental, or administrative, if it can influence public outputs or participant treatment.
The current charter version is draft-1. Its status is governing standard. The current build is front-end phase one with live backend enforcement for sign recording, referral crediting, and rate limiting.
The charter establishes a strict order of precedence. When priorities conflict, the higher-ranked principle always wins:
Nothing lower on this list may override anything higher. A usability improvement that compromises auditability is prohibited. A scalability optimization that weakens participant safety is prohibited. A novel feature that undermines public honesty is prohibited.
The charter imposes six constraints that cannot be overridden by any operational decision, exception, or amendment:
No accounts, no unnecessary personal information, no hidden profiling, no silent conversion of anti-abuse signals into identity records. The system is designed so that the operator cannot identify individual participants. Third-party infrastructure providers operate their own network layers, which are outside the operator's control — this limitation is disclosed as a known gap.
No advertising, no dark patterns, no commercial upsells, no pay-to-amplify mechanics, no extractive attention loops inside core public utility functions.
Every visible tally, ranking, threshold, score, or status must have a traceable source class, formula basis, methodology version, and time basis. If a number appears publicly, someone must be able to trace where it came from.
The same materially identical input produces the same output, for everyone, under the same methodology version. The system does not produce different results for different people under the same conditions.
The architecture prefers static-first, edge-first, failure-visible design. If the system is degraded, the charter requires that it say so.
If old behavior conflicts with the charter, the charter wins. No legacy code, no prior decision, no operational convenience overrides a charter obligation.
The charter requires that every public feature and output be labeled honestly. The system uses a set of required label classes to indicate the operational status of every surface:
The core principle: no feature may imply stronger operational reality than it currently possesses. If a count is local-only, it must say so. If a methodology is not yet fully enforced, it must say so. These labels are visible across The Wall, the Country Race, the Badge, and Flame Carriers.
The charter permits exceptions, but only under strict conditions. Every exception must be 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 — no identity capture, no monetization surfaces, auditable outputs, truthful state labeling, audit trail preservation, and charter supremacy — carry the highest amendment burden.
The charter distinguishes between stated rules and enforced rules. A rule is not enforced because it is written. A rule is enforced when violation is blocked, recorded, or both.
Every charter obligation must eventually be mapped into one or more enforcement mechanisms: build-time blocks, release-time blocks, runtime guards, audit log requirements, public labeling requirements, exception processes, or rollback triggers.
Any rule not yet mechanized is labeled as a governing standard pending full enforcement implementation. This is not an aspiration. It is a disclosure. The charter tells you which rules are currently enforced and which are currently stated but not yet mechanically blocked. The compliance surface shows this status for every feature.
To read the full charter with all eleven sections, see Site Stewardship Charter.
To see the current enforcement posture, feature states, and known gaps, see Compliance Surface.
To understand how the audit and methodology systems work, see Audit and Methodology.
To understand what The Wall is, see What Is The Wall?.