Who
Pages are published under one organizational standard: Compute Statecraft. The method is public so the rules do not change from page to page.
Methodology
Authority comes from visible method, not confident prose.
Every Map is built to separate confirmed facts from synthesis and scenarios. The template is deliberately constrained so readers can audit what changed, what is sourced, and where uncertainty remains.
How
Sources are classified, claims get provenance labels, narratives are forced into supports and contradictions, and changes are logged instead of hidden.
Why
The objective is faster orientation for researchers, operators, and policy readers who need the evidence chain, not a confidence performance.
1
Capture the claim
A candidate claim enters the system only when it can be attached to a source, actor, policy action, market signal, or observable event.
2
Classify the evidence
Sources are grouped as primary, secondary, or social. Primary material carries the most weight; social material is usually treated as an object of analysis.
3
Assign provenance
SOURCED means direct support. INFERRED means synthesis from listed sources. SPECULATIVE means a forward-looking hypothesis that must not be read as confirmed.
4
Map the narratives
Each narrative gets support, contradiction, context, weak points, and trajectory. This keeps disagreement structured instead of rhetorical.
5
Update the record
New source material should update the canonical Map and changelog before creating another thin page on the same story.
Before publication
- Confirm the page belongs inside the declared coverage boundary.
- Prefer primary documents before leaning on analysis or commentary.
- Keep inference explicit and connected to listed citations.
- Update an existing Map when the story already has a canonical page.
Automation rule
Automation may help with collection, formatting, or drafting, but it does not override provenance. If a claim cannot be tied to a cited source or justified inference, it does not belong on the page.
Material use of automation should be disclosed in the product context that matters, and automation itself is never treated as evidence.
Mandate class
A mandate-class claim is tied directly to policy text, filings, official releases, legislative drafts, transcripts, or other primary material that creates a real obligation or public position.
Projection class
A projection-class claim explains likely consequences, bargaining leverage, or capability effects. It remains downstream from the verified legal or technical record.
Publication gate
- Blocked slugs such as `test`, `clone`, `sample`, `demo`, `tmp`, and `draft` are rejected.
- Indexable canonical Maps need at least two sources and at least one primary source.
- Indexable Dossiers need at least two receipts, at least one primary receipt, and at least one public position.
- Duplicate canonical titles are rejected so a story arc resolves into one authoritative page.
- When a story already has a canonical Map, updates belong in that page and its changelog first.
Translatory brief standard
Compute Statecraft should be legible to both compliance counsel and systems operators. A translatory brief therefore has to show the clause, the control surface, and the proof path together.
Mandate to mechanism
State the exact clause, draft, filing, or official mandate that creates the obligation.
Describe the silicon, firmware, platform, cloud, or network surface where the obligation is enforced.
List the telemetry, attestation, procurement, or inspection path that would prove the control is real.
Policy to failure mode
Name the enforcement trigger, threshold, or prohibited condition in legal language.
Map that trigger to the system component that can throttle, deny, log, or disable behavior.
Explain what would falsify the implementation claim or reveal a compliance gap.
Operator implications
Identify which operator, vendor, or jurisdiction is bound by the obligation.
Translate the obligation into operational burdens such as monitoring, capacity planning, key management, or hardware replacement.
Show which records, audit artifacts, or public statements would confirm those burdens in practice.
Correction and update rule
When a source contradicts a claim, the preferred path is to update the existing Map, change the provenance label if needed, and record the change in the changelog. Silent rewrites weaken trust, so visible revision history is part of the product.