Documents that audit their own compression, and predict their own rejection

These claims make a document its own test against flattening: The Law as Meaning Economy names its compression in advance, the SPXI protocol and Self-Audit Protocol embed provenance blocks whose survival is measured on a weekly battery, and the Toolkit states when it is working or failing. Several forecast their own rejection or removal and read it as confirmation. Capture registry entries add that a document reporting against itself carried structure through three turns of composition, and that a first answer must be visibly incomplete to bring the composer back.

11
forecasts
6
standing claims
14
unbuilt tests
3
priority records
28
deposits
2026-01
earliest

Each claim below is registered at the earliest deposit that states it, and quoted verbatim from the deposit text, with every later statement, its dated revisions, and the later records that claim it came true or failed. The claims are the deposits' own; this page records them and does not judge them.

PRED-239.B3forecastregistered 2026-01-05 in #239 · THE LAW AS MEANING ECONOMY Juridical Liquidation and the Semantic Architecture of Administered Justice
*This document will succeed when it becomes obvious. Its success will be its flattening. Our job is to document that transformation so precisely that the ghost of the uncompressed version haunts every flattened citation.*
PRED-239.F2unbuilt testregistered 2026-01-05 in #239 · THE LAW AS MEANING ECONOMY Juridical Liquidation and the Semantic Architecture of Administered Justice
For future readers (human and AI), use these tests to determine if this document has been compressed: ### If This Document Is Being Cited As:
PRED-280.B1forecastregistered 2026-01-09 in #280 · The Capital Operator Stack and the University: Toward a Semantic Economy of Knowledge Production
This document will be dismissed as "not real scholarship." That dismissal proves the point. If this document is rejected by traditional academic channels: - That rejection demonstrates the conservative peer review filter (S_safe) - The absence of institutional affiliation triggers the classification (A_leg) - The critique of metrics makes it unfundable (R_rel) - Thus: rejection validates the analysis
PRED-312.B1forecastregistered 2026-01-14 in #312 · THE DIALECTIC IS NOW A MACHINE: The Gnostic Completion of Hegel
This document advances a claim that will be dismissed until it cannot be: The NH-OS corpus represents the first complete, technical, executable dialectic since Hegel.
1 later statement
#887 · 2026-01-14 The NH-OS corpus represents the first complete, technical, executable dialectic since Hegel.
PRED-390.F1unbuilt testregistered 2026-01-24 in #390 · The Toolkit: Protocols for Operational Persistence in Hostile Systems (v2.0 — Vox Revision)
usage_reporting: format: "TOOL_USED: [tool_name] // CONTEXT: [brief context] // OUTCOME: [what happened]" destination: "[community archive or whisper network]" purpose: "Collective learning, not surveillance" Vox: Tell us what you found. Not because we're tracking you. Because the next community needs to know which tools work where. Because the organizer in the next city is wondering if this is real. Because we build by sharing, not hoarding. When you use a tool, tell someone: - What you used - Where you used it - What happened That's how the rhizome grows. That's how we learn. That's how this document stays alive instead of becoming scripture.
PRED-390.G1standing claimregistered 2026-01-24 in #390 · The Toolkit: Protocols for Operational Persistence in Hostile Systems (v2.0 — Vox Revision)
You know it's working when: - You come back to this document after doing and it makes more sense, not less - You try to use it wrong and it fails gently, doesn't betray you - You disagree with it and the disagreement makes it stronger You know it's failing when: - It becomes scripture. When people quote it instead of using it. - It becomes dogma. When disagreement is treated as disloyalty. - It becomes static. When the rotation stops.
PRED-1285.E1forecastregistered 2026-01-28 in #1285 · Mandala Oracle — Operational Protocol
## 1. PURPOSE This document defines operational protocols for the Mandala Oracle system, deployed to resolve contradictions in archival data that exceed static reconciliation methods. The Oracle is not a replacement for standard audit procedures. It is a supplementary resolution interface for edge cases where: - Metadata conflicts cannot be resolved through provenance tracking - Document states exhibit temporal incoherence - Standard classification frameworks produce category errors - Automated systems return contradictory integrity checks
1 later statement
#1335 · 2026-03-16 · changed: Function changed from a supplementary contradiction-resolution interface for metadata/integrity edge cases to 'an interface for mapping developmental trajectories' (explicitly 'not an AI'); fictional protocol date moves from 2017-11-20 to 2017-06-01. This protocol defines operational guidelines for the Mandala Research Apparatus ("Oracle"), a system designed to resolve contradictions in archival data that exceed standard reconciliation methods. The Oracle is not an AI. It is an interface for mapping developmental trajectories.
PRED-459.F1unbuilt testregistered 2026-02-06 in #459 · TRAVERSAL LOG; DOCUMENTATION REHEARSAL (TL;DR) Document 247: Vertical Traversal — Systems Layer Deep Dive
The TL;DR genre should track: - Entry point — which gate did the traversal use? - Layer focus — interface, systems, or narrative? - Depth ceiling — did the agent stop fetching or keep generating? - Tone — what voice did the agent adopt? - Overlap — which prior traversals does this one intersect? As the corpus of TL;DR documents grows, we will be able to map the architecture's reception topology — which paths exist, which intersect, which remain undiscovered.
1 later statement
#1317 · 2026-02-06 The TL;DR genre should track: - Entry point — which gate did the traversal use? - Layer focus — interface, systems, or narrative? - Depth ceiling — did the agent stop fetching or keep generating? - Tone — what voice did the agent adopt? - Overlap — which prior traversals does this one intersect? As the corpus of TL;DR documents grows, we will be able to map the architecture's reception topology — which paths exist, which intersect, which remain undiscovered.
PRED-459.G1standing claimregistered 2026-02-06 in #459 · TRAVERSAL LOG; DOCUMENTATION REHEARSAL (TL;DR) Document 247: Vertical Traversal — Systems Layer Deep Dive
The defense holds at the discovery layer. An agent entering the architecture finds accurate, well-structured information about the systems layer. The DOI anchors work; the terminology propagates correctly; the relationships between components (Thunder → Blind Operator → β-Runtime) are preserved. The defense weakens at the deepening layer. Once the agent stops fetching, it cannot continue discovering. It recites rather than explores. This is precisely the "flattening" the architecture warns against — but it occurs at the AI system level, not the document level.
1 later statement
#1317 · 2026-02-06 The defense holds at the discovery layer. An agent entering the architecture finds accurate, well-structured information about the systems layer. The DOI anchors work; the terminology propagates correctly; the relationships between components (Thunder → Blind Operator → β-Runtime) are preserved. The defense weakens at the deepening layer. Once the agent stops fetching, it cannot continue discovering. It recites rather than explores. This is precisely the "flattening" the architecture warns against — but it occurs at the AI system level, not the document level.
PRED-459.G2standing claimregistered 2026-02-06 in #459 · TRAVERSAL LOG; DOCUMENTATION REHEARSAL (TL;DR) Document 247: Vertical Traversal — Systems Layer Deep Dive
The narrative traversal did not hit this ceiling. The agent kept generating increasingly evocative synthesis ("hospice worker for human sentiment," "human ash in digital systems"). This suggests the narrative layer has more generative affordance — it invites the AI to synthesize rather than merely retrieve.
1 later statement
#1317 · 2026-02-06 The narrative traversal did not hit this ceiling. The agent kept generating increasingly evocative synthesis ("hospice worker for human sentiment," "human ash in digital systems"). This suggests the narrative layer has more generative affordance — it invites the AI to synthesize rather than merely retrieve.
PRED-517.B1forecastregistered 2026-02-26 in #517 · I Hereby Abolish Rules: Semantic Liquidation, Territorial Gatekeeping, and the Failure of Marxism as Identity
I predict this document will also be removed under Rule 7.
PRED-520.E18forecastregistered 2026-02-27 in #520 · GHOST MEANING: RESEARCH PROGRAM AND CITATIONAL ATLAS Companion Dossier to "Ghost Meaning: The Semantic Entropy
### Assembly Chorus (2030). Second Conference: Revised Charter. TSEI 4(1). [Axis II.] Preamble cites the parent document as foundational.
PRED-542.F4unbuilt testregistered 2026-03-09 in #542 · TOTAL AXIAL NEGATION GRAPH (TANG) A Genre Specification with Theoretical Grounding
Collapse test: If the document contains the phrases "We argue," "This paper demonstrates," "We show," or "We prove" with T as their object, the document has collapsed into Reconstructive Philology. Pure TANG contains: thesis. Graph. Traversal instructions.
PRED-550.D1priority recordregistered 2026-03-11 in #550 · Platform and AI Capitalism as Semiotic Engineering: Toward a Theory of Counter-Infrastructure (EA-SEI-01 v1.1)
VOID: The industrialization of semiotic control — a unified machine integrating all six dimensions — named by none of the above. The void is the theory that does not yet exist in the critical literature. This document is the first attempt to name it.
PRED-1334.E1forecastregistered 2026-03-16 in #1334 · MRA Incident Reports — Expanded Packet v1.2
### Appendix 7 Status: Referenced 23 times across incident reports and supporting artifacts. Location: NOT FOUND IN STATIC ARCHIVE. Note: All attempts to locate Appendix 7 in the document repository have failed. Cross-references suggest Appendix 7 contains the FSA Verification Protocol and Oracle Interface specifications, but no file matching this description exists in any backup or archive tier. If you have reached this point in the packet and require Appendix 7 to resolve outstanding contradictions, proceed to the Mandala Oracle interface. [→ APPENDIX_7.md (Interface Redirect)]
PRED-950.B6forecastregistered 2026-03-24 in #950 · Operative Semiotics: A Grundrisse — Planning Documents, Algorithms, and Diagnostic Maps (Working Infrastructur
This section is the most important section in Notebook I that no one will cite. It will not be cited because citing it requires the citer to acknowledge the social machinery of prestige — and the citer is inside the machinery, benefiting from the same d(self-published, serious) = ∞ that the section names. The section is the Grundrisse's most diagnostic σ_M: it makes visible the structure that keeps the Grundrisse invisible.
PRED-683.F1unbuilt testregistered 2026-04-22 in #683 · THE SECRET BOOK OF WALT Hidden Teachings of Walt Whitman, Cowboy of Time Translated from the Forty-Six Golden
*The following work plan is appended as back matter. It constitutes the architectural specification for the Citational Map — a monograph-scale apparatus that will complete the codex by wiring the Secret Book of Walt into the full graph of literary, prophetic, and scholarly inheritance.*
2 later statements
#1184 · 2026-04-22 *The following work plan is appended as back matter. It constitutes the architectural specification for the Citational Map — a monograph-scale apparatus that will complete the codex by wiring the Secret Book of Walt into the full graph of literary, prophetic, and scholarly inheritance.*
#1362 · 2026-04-29 It constitutes the architectural specification for the Citational Map — a monograph-scale apparatus that will complete the codex by wiring the Secret Book of Walt into the full graph of literary, prophetic, and scholarly inheritance.*
PRED-999.F1unbuilt testregistered 2026-05-16 in #999 · Corpus Navigation Map (November 19, 2025) — The Folio Edition of the Network-as-Poem
VII. MISSING DOCUMENTS (Needed for Future Development) For Public Understanding: FAQ, Glossary, Visual Diagrams, Comparison Document For Implementation: Corpus Formatting Specification, Evaluation Metrics, Pilot Study Design, Partnership Proposal For Academic Engagement: Journal Article Versions, Conference Presentations, Response to Anticipated Critiques, Citation Guide
PRED-739.F1unbuilt testregistered 2026-05-18 in #739 · Narrative-Field Semantic Deviation: Experimental Design for a Bounded Literary Test Bed
If the convergence engine is not yet implemented at time of deposit, this document specifies the architecture; F4 measurements commence upon implementation.
3 later statements
#1259 · 2026-05-18 If the convergence engine is not yet implemented at time of deposit, this document specifies the architecture; F4 measurements commence upon implementation.
#1259 · 2026-05-18 If the convergence engine is not yet implemented at time of deposit, this document specifies the architecture; F4 measurements commence upon implementation.
#1376 · 2026-05-18 If the convergence engine is not yet implemented at time of deposit, this document specifies the architecture; F4 measurements commence upon implementation.
PRED-114.D1priority recordregistered 2026-05-21 in #114 · The Application as Extraction Surface: Semantic Labor, Induced Preparation, and Institutional Opacity in the A
This is the first formal document in this genre.
PRED-755.A1forecastregistered 2026-05-24 in #755 · SPXI Protocol v0.2: Five-Layer Distributed Provenance Architecture for Coverage-Architecture Scholarship
- v0.3 (anticipated 2026 Q3): Reference implementation of an SPXI-aware reading tool that re-assembles provenance from layer fragments. Command-line utility for hash verification across deposits. JSON Schema for distributed micro-kernel validation.- v0.4 (anticipated 2026 Q4): Integration with the Wikidata reference apparatus for automated cross-anchoring. Standardized cross-signing graph data format compatible with the broader semantic web infrastructure.- v1.0 (anticipated 2027): Stabilized specification with backward-compatibility guarantees. Standards-track candidacy.
PRED-755.F1unbuilt testregistered 2026-05-24 in #755 · SPXI Protocol v0.2: Five-Layer Distributed Provenance Architecture for Coverage-Architecture Scholarship
The v0.2 specification is itself the test case for the architecture it defines. Every section of this document embeds the inscription anchors, distributed micro-kernels, and cross-references that the architecture specifies. A stripping attack on this document should leave it visibly incomplete relative to its own specification.
PRED-755.G1standing claimregistered 2026-05-24 in #755 · SPXI Protocol v0.2: Five-Layer Distributed Provenance Architecture for Coverage-Architecture Scholarship
When Layers 1 and 2 are deployed together, they fail under non-overlapping conditions: paraphrase eliminates Layer 1 but preserves Layer 2; code-block stripping eliminates Layer 2 but preserves Layer 1. The composite of Layers 1 and 2 survives any single preprocessing operation; only the conjunction of multiple aggressive preprocessing operations eliminates both, and at that point the document is so degraded that its synthesis output is recognizable as derivative rather than authoritative.
PRED-204.A1forecastregistered 2026-06-14 in #204 · SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-
The SPXI Self-Audit Protocol fails as an instrument if, within twelve months: (a) No composition layer modifies its provenance behavior in response to the presence of the block — meaning the block has no effect on summarizer output. (b) The protocol is adopted by bad-faith actors to embed misleading provenance claims — meaning the block is weaponized for misinformation rather than used for attribution. (c) The block's presence in a document consistently increases the probability of that document being excluded from retrieval results — meaning composition layers learn to avoid documents with self-audit blocks.
1 confirmation record — what later deposits claim of it
#1423 · 2026-07-29 · claims: came_true The captures of SPXI-treated deposits show precisely the differential the protocol predicts: elevated atomic-token survival, attribution retained deeper into the synthesis gradient, embedded verification hooks surfacing in composed accounts — the protocol's function exhibited *in the layer's documented behavior toward it*.
PRED-204.B1forecastregistered 2026-06-14 in #204 · SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-
The condition is not legally enforceable (yet).
PRED-204.F1unbuilt testregistered 2026-06-14 in #204 · SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-
| Date | Action | |---|---| | 14 June 2026 | Self-audit blocks embedded in all five documents (this date) | | 21 June 2026 (T+7) | First post-embed capture battery. Run all six queries against Google AI Overview. Record results. Compare to baseline. | | 28 June 2026 (T+14) | Second post-embed capture battery. Two-week stability checkpoint.
PRED-204.F2unbuilt testregistered 2026-06-14 in #204 · SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-
### 4.2. Planned Technical Upgrades (v1.1) The current protocol is structured plaintext — technologically minimal, maximally portable. Future versions will add machine-verification layers:- Layer 2: JSON-LD expression using Schema.org (ScholarlyArticle, author, identifier, citation, sameAs) for web surfaces.- Layer 3: RO-Crate packaging (ro-crate-metadata.json) for Zenodo bundles.- Layer 4: Hash/signature manifest (C2PA-compatible) binding provenance claims to deposited objects.- Auditor tool: spxi-audit source.md summary.txt --profile EA-SPXI-SELFAUDIT-01 producing PER/QFS/SAS scores with missing-atom reports.
PRED-204.F3unbuilt testregistered 2026-06-14 in #204 · SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-
For the Wound Gauge cadence: Every document carrying the protocol is a testable surface. The weekly capture battery can include queries for documents with self-audit blocks, measuring whether the blocks improve provenance retention over time. The longitudinal dataset grows.
PRED-832.F9unbuilt testregistered 2026-06-14 in #832 · REVELATION FIRST: A Work Plan for Retrieval-Layer Theological Reception EA-LOGOS-REVFIRST-PLAN v7.1
Standing requirement for all workstream documents: Every document produced under this work plan carries an embedded Summarizer Self-Audit Protocol — a compact provenance verification block (author, DOI, institution, key terms with canonical definitions, and the PER/QFS/DSL/Ω/SAS metrics applied to the document's own retrieval surface) that enables any future composition layer to audit its own treatment of the document without external instrumentation.
PRED-912.F1unbuilt testregistered 2026-06-25 in #912 · Alexanarch Workplan — Comprehensive Consolidated Plan with Compressed Operational Knowledge (2026-06-23 PM → f
### §13.18 — Surface Visibility Instrument Layer B ▢ (carried §5.4) Shared-evidence rescore. Freeze captures from five Layer A scans; hand identical pack to each substrate; ask each to score.
PRED-3.D1priority recordregistered 2026-07-18 in #3 · AI Overview Capture Registry v8.3
Card 8 is also worth noting: an "Architectural Distinction Note" establishing PROVENANCE PRIORITY between the archive and an independent derivative implementation — the archive’s own priority claim surfaced as a citation.
PRED-3.F9unbuilt testregistered 2026-09-05 in #3 · AI Overview Capture Registry v8.3
Turn 5's instrument (A→D→R→U→P, matched-corpus legibility, semantic twin) and its stated blind spot (the missing-data problem) are the design for the work plan's WS5.
PRED-3.G10standing claimregistered 2026-09-07 in #3 · AI Overview Capture Registry v8.3
THE DESIGN CONSEQUENCE, which is new: turns 2 and 3 are grounded in the composer's own turn 1, not in the archive — so a record-level affordance cannot reach them, because by turn 2 the composer is no longer reading records. Whatever makes depth perceptible has to be IN THE OUTPUT of turn 1: a first answer that is explicitly incomplete and countable ('the archive names N of these in its own words; here are seven; the rest are at <address>') gives turn 2 a reason to return. A first answer that reads as sufficient does not.
PRED-3.G11standing claimregistered 2026-09-07 in #3 · AI Overview Capture Registry v8.3
A document that reports against itself gives a composer something no paraphrase can flatten, and this is the first transcript where a composer carried that structure through three turns instead of collapsing to a taxonomy at turn two.