Public article projection
Acme Analytics
No admitted customer-count proposition is currently eligible for this illustrative public composition.
/examples/reverse-wiki-record
Reverse-wiki record example
This page renders one synthetic generic governed record through the polished Counterpedia renderer. The header, the canonical column, the provenance rail, the audit timeline, and the method panel are the same components used at /records/SYN-REC-RW-0001. It also pairs deterministic teaching controls with a server-rendered proof stack. Each proof identifies whether its inputs are retained real artifacts or synthetic explanatory material.
A Counterpose-shaped walkthrough lives at /examples/counterpose-signal. The two together show that Counterpedia generalizes across profiles without copying Counterpose itself.
For the product model behind the demonstration, read Reverse Wiki. The interactive controls below do not invoke DAGR or mutate canonical state.
Interactive proof
Same evidence, different standing
Step through a synthetic proposition as it moves from proposal to refusal, then reopening and revised admission. Switch between the article projection, source-first traversal, split histories, machine state, and the agent's WHAT / WHY NOT / WHAT CHANGED answers. Nothing here is a live admission write.
Interactive specimen · deterministic · no backend mutation
Synthetic Acme Analytics record. The controls only switch among committed illustrative states in this page.
Current illustrative stage
The proposition exists before the article does.
Agent-27 has submitted a valid, sourced candidate. The candidate is inspectable, but no governed admission disposition has made it eligible for the public composition.
Agent proof
Ask the record, not the prose
Advance to the admitted stage to compare all three answers.
The current stage does not yet support the final three-answer comparison. Its own standing and history remain inspectable above.
RW-REAL0 · committed artifact proof
The same lifecycle exists in retained real record history
The synthetic Acme control above teaches the mechanism. This section reads the retained Heppner lifecycle bytes and admission ledger directly. Heppner is not a current admitted flagship: it was terminally retired from current standing on August 14, 2026. Its earlier governed lifecycle remains addressable as a historical proofcase.
- record
- HEPPNER-LIFECYCLE-0001
- current_standing
- retired_from_current_corpus
- source
- United States v. Heppner, document 27
- capture
- sha256:b7bd04c056563e6864cc4fcb68ed62eff732eaacf812377d2d4f6d24fb9f920c
- proof posture
- historical_committed_artifact_projection
- verification reports
- 2 retained, separately owned/scoped
01
Candidate refused
candidate:heppner:work-product-behest was refused in the initial governed state.
reconsiderable refusal: the proposed source anchor is not in the initial admitted capture
Reopen if: new_evidence_admitted
02
Named condition satisfied
The committed reopening object targets the exact same candidate and recordsnew_evidence_admittedas the trigger.
the supplemental public capture admitted the candidate's pinned page 9 anchor
03
Revised state admits it
The work-product ruling rested in part on the AI Documents not being prepared by or at the behest of counsel and not reflecting counsel's strategy.
Anchor: anchor:heppner:doc27:p9:work-product-behest
The unrelated universal proposition remains a final refusal: reopening one branch does not erase negative state elsewhere.
04
Current standing later ends
Owner decision: retire the Heppner proofcase from current public/admitted standing. Its admission history (events 0001 and 0002) is retained, not erased; this terminal event withdraws the lineage from serving without a replacement admission. The record bytes remain physically present for historical provenance but are no longer projected to any current public or showcase surface. Retirement asserts nothing about the prior admission's validity; it only ends current standing.
Terminal event: ADM-EVT-public:HEPPNER-LIFECYCLE-0001-0003
Current admission events remaining: 0. History remains reachable anyway.
RW-BIND0 · citation ≠ evidence scope
The source exists. The stronger proposition still does not get licensed.
This is not a new semantic judgment by the demo. It projects an already-recorded final refusal from the retained Heppner lifecycle: a universal proposition was broader than the case-specific memorandum and had no supporting anchor.
What the retained source actually anchors
“Heppner's use of Claude fails to satisfy either of these rules”
- scope
- case_specific
- page
- 12
- anchor
- anchor:heppner:doc27:p12:case-specific-conclusion
What the candidate tried to make load-bearing
candidate:heppner:universal-ai-privilege-rule
- scope
- universal
- standing
- final_refusal
- reason
- final refusal: the universal proposition is broader than the case-specific memorandum and has no supporting anchor
Source present
yes
Universal candidate admitted
no
Refusal survives revision
yes
A citation can establish where a proposition points without establishing every predicate the proposition tries to carry. Counterpedia can preserve that boundary as governed negative state.
No ADJ1 support assertion is issued here. The demo only exposes the scope boundary already recorded in the committed historical refusal.
Retirement proves another Reverse-Wiki property: ending current standing is not deletion. The prior admission, refusal, reopening, revised state, source anchors, and verification reports remain historical objects that can still explain what happened.
This surface projects committed retained artifacts only. It does not reactivate Heppner, reverse its retirement, or treat historical admission as current standing.
RW-PROV0 · provenance ≠ authority
Authority cannot hitchhike through the pipeline
The three actors below are illustrative, not a live provider trace. The boundary is real: Counterpedia's acquisition adapter treats model output as proposal material, forbids model fields from supplying standing/admission/verification authority, and preserves source provenance separately from later analysis.
Level A · origin
Example Newswire
publishes an attributed report
assertion
Factory X reported 100 units shipped in the quarter.
inherits prior authority: false
Level B · intermediary
Example Aggregator
retrieves, normalizes, and transports the report
inherits prior authority: false
Level C · analytical overlay
Example Model
classifies the transported material
assertion
bullish
inherits prior authority: false
Flattening Counterpedia must refuse
source: Example Newswire claim: bullish
That representation would silently turn the model's analysis into an assertion by the origin source. The analytical overlay does not inherit origin authority.
Separated representation
- origin says
- Factory X reported 100 units shipped in the quarter.
- transport
- Example Aggregator
- model says
- bullish
- model state
- UNADMITTED
Counterpedia does not merely remember where information came from. It preserves where each assertion originated so transport, normalization, and analysis cannot silently upgrade their own outputs into somebody else's authority.
Engineering anchor: the existing acquisition adapter outputs proposal state and rejects model-supplied authority fields. See the existing source-loop demo for the broader captured-bytes → proposal → verification → agent → memory walkthrough.
RW-SOURCE0 · real source-first traversal
A source can be governed and traversable before it becomes a factual claim
TH-S01 is current admitted Counterpedia corpus material built around an independently captured public SEC filing. Its source is public and content-addressed. The same record explicitly declines to restate the filing's allegations as established facts and takes no position on their truth.
Start at the source
SEC enforcement filing (captured public document)
- source_id
- TH-S01-SRC-0001
- publication
- public
- integrity
- captured_bytes
- capture
- sha256:3ce565f81f038797a7803cef3f9370019c16676700c551ea31c639f2222e6826
Traverse upward into current public consequences
- U.S. SEC Enforcement Filing Concerning Theranos and Elizabeth Holmes (Captured Public Document)
cited_by_record · Research Corpus
These links are derived from committed page-model source presence. They do not infer support, truth, standing, or a new Countergraph edge.
Recorded citation attachment
Editorial paraphrase: a United States securities regulator issued a 2018 enforcement filing concerning a blood-testing company and its founder. This span is a neutral summary, not a verbatim quotation of the source.
- span
- TH-S01-SPAN-0001
- verification
- unverified
What source presence does not do
- ✓ source custody / capture can be represented
- ✓ the source can be traversed to records that cite it
- ✕ filing allegations do not become established facts by source presence
- ✕ source presence does not establish truth
- ✕ an unverified citation span does not become independently verified
In an article-first system, the source is usually a leaf hanging from prose. Here the source is an addressable junction: start with the captured artifact, then ask which public records depend on it — without upgrading that dependency into a factual verdict.
RW-GRAPH0 · graph ≠ admission
The graph can contain an edge to something it has not admitted
Counterpedia's current reference graph preserves both resolved and unresolved reference topology. An unresolved edge names a target not present among the current graph nodes. That is the cleanest possible proof that edge presence cannot itself mean admission.
Resolved edge
CP-SIG-60 → CP-SIG-24
- state
- resolved
- target node
- present
- admission effect
- none
Unresolved edge
CP-SIG-57 → CP-26
- state
- unresolved
- target node
- absent
- edge still exists
- true
- admission effect
- none
Claim support
not_evaluated
Truth
not_asserted
Standing effect
none
Admission effect
none
Edge schema, exactly
{
from,
to,
state: "resolved" | "unresolved"
}There is no support verdict, truth verdict, or admission mutation in the edge object. The authority boundary above is projection metadata for reading the graph honestly, not a new source of standing.
A path can be useful without becoming a proposition. A graph can preserve a reference to an unadmitted target without admitting it. Countergraph and reference views therefore remain projections over governed state, not alternate admission engines.
RW-EXPLAIN0 · agent-readable epistemic state
The agent does not have to reconstruct “why not?” from prose
These four answers are resolved directly from Counterpedia's existing public read API. No model generates them, no search is performed, and no MCP transport is opened. The same record identity and versioned surfaces that serve readers supply the agent read model.
read onlyMCP: HOLD_CP_MCP_01
LOOKUP
recordWhat does this record currently represent?
Heppner AI privilege ruling: governed claim lifecycle — standing: retired_from_current_corpus; projection: retired_historical_projection.
- standing
- retired_from_current_corpus
- projection
- retired_historical_projection
- version_ref
- HEPPNER-LIFECYCLE-0001@HEPPNER-LIFECYCLE-EDITION-REVISED
- elements used
- 3
EXPLAIN
exclusionsWhy doesn't the universal AI-privilege proposition enter the record?
final: final refusal: the universal proposition is broader than the case-specific memorandum and has no supporting anchor
- standing
- retired_from_current_corpus
- projection
- retired_historical_projection
- version_ref
- HEPPNER-LIFECYCLE-0001@HEPPNER-LIFECYCLE-EDITION-REVISED
- elements used
- 1
TRACE
historyWhat changed for the reconsiderable work-product branch?
candidate:heppner:work-product-behest: candidate → reconsiderable; candidate:heppner:work-product-behest: reconsiderable → admitted
- standing
- retired_from_current_corpus
- projection
- retired_historical_projection
- version_ref
- HEPPNER-LIFECYCLE-0001@HEPPNER-LIFECYCLE-EDITION-REVISED
- elements used
- 1
VERIFY
verificationWhat properties were independently checkable?
10 independently-checkable properties are represented. Verification checks independently-checkable properties (cryptographic integrity, schema conformance, source availability) at the pinned version. It does not guarantee currentness, and it does not adjudicate the truth of the underlying allegation.
- standing
- retired_from_current_corpus
- projection
- retired_historical_projection
- version_ref
- HEPPNER-LIFECYCLE-0001@HEPPNER-LIFECYCLE-EDITION-REVISED
- elements used
- 1
Mutation
false
Admission effect
none
Model generation
false
Search
false
MCP transport
false
Mode
read_only_projection
LOOKUP, EXPLAIN, TRACE, and VERIFY are not four new authorities. They are four disciplined questions over the same public governed record. A future MCP layer can expose this contract only after its separately held schema gate is cleared.
RW-AMNESIAC0 · epistemic caching
Reuse the durable determination; do not re-invent its authority
Counterpedia and arcs-amnesiac already carry a reciprocal, byte-pinned governed-read seam. The reusable object is identified by record and version; drift keys on the version reference. The cache does not upgrade retrieval or memory into truth, currentness, admission, or verification authority.
Durable governed-read identity
- record
- SYN-CP-SIG-0001
- version_ref
- SYN-CP-SIG-0001@SYN-CP-ED-0003
- drift key
- version_ref
- contract
- amnesiac.governed-public-read.normalized.v0_1
- fixture sha256
- 6269f3f0bac5e2050342545d4beb3a9a5afa86d241691ad3cf9115a00ef96e92
What the agent no longer has to rediscover from scratch
- ✓ record identity
- ✓ version identity
- ✓ normalized read contract
- ✓ cross repo fixture identity
Never inherited from the cache
✕ currentness
✕ truth
✕ producer_identity
✕ admission_authority
✕ verification_authority
✕ wire_compatibility
Amnesiac → Counterpedia authority
false
Counterpedia → Amnesiac authority
false
Memory creates authority
false
Version drift reopens work
true
The model still reasons. It simply does less epistemic archaeology. Identity, versioning, and a normalized governed read can be reused as durable infrastructure, while any change in the version key forces reconsideration instead of silently serving stale memory as current truth.
1. Record header
Identity, profile, status, lifecycle, anchor resolution, and render-time eligibility, in three calm rows of badges.
record SYN-REC-RW-0001slug synthetic-reverse-wiki-bootstrap-layout
Synthetic Demo: Reverse-Wiki Record for the Bootstrap Layout
Generic GARPedia record used to exercise the renderer model without Counterpose-specific surfaces.
profileResearch Corpusresearch_corpus
statusPublished
lifecyclePublishedanchorsAll anchors resolved
eligibilitypublication-eligible
computed at 2026-05-07T11:00:00Z
rendered at 2026-05-07T11:00:00Z
2. Canonical column and provenance rail
The canonical article on the left, the provenance rail on the right. The rail is the governed-record difference from an ordinary wiki page: sources, fragment-level citation spans, entities, typed cross-references, intersections, projections, and disputes render alongside the body, not in footnotes. Inline citation markers in the canonical column are anchor links into the rail.
Overview
This synthetic record exercises the generic GARPedia renderer model: a canonical body, fragment-level citation spans, a small entity set, a single cross-reference, one projection, and a short lineage. It is a profile-neutral record; the Counterpose-specific publisher, edition, and relationship grammar are exercised by the sibling record.1
Citation spans and projection
Citation spans on this record carry a verification state recorded by the verbatim fragment lint at admission. The single projection is a short summary that names the categories of information known to be absent from the projected view.2
Cross-reference into the Counterpose-shaped record
The single cross-reference on this record is a related-link into the demo Counterpose-shaped signal, used to show the renderer that even a generic record can carry typed relationships into other rendered records.
3. Audit timeline
The governed events that produced the current state, oldest first. Counterpedia presents the chain; it does not write to it.
Audit timeline
Governed events that produced the current state of the record. Oldest first. Counterpedia renders the chain; it does not write to it. Adjudication, review approval, and publication approval happen in the operator surface (the GARP Workbench), not here.
2026-04-22T15:00:12Z — SYN-RW-EVT-0001
candidate createdactor: ingest_agent
Candidate record assembled from two registered captures and routed into the Research Corpus review queue.
2026-04-25T17:20:01Z — SYN-RW-EVT-0002
promotedactor: promoter
Candidate promoted to admitted record under the Research Corpus profile; lineage hash recorded in the audit chain.
2026-04-30T14:02:11Z — SYN-RW-EVT-0003
publication eligibility setactor: eligibility_checker
Publication eligibility set to true; reasons include verified spans and registered captures.
2026-04-30T14:06:00Z — SYN-RW-EVT-0004
edition releasedactor: renderer
First edition released; canonical body and projection emitted.
4. Method
The rules and posture under which the record was rendered, in plain view. Counterpedia does not run search, does not run retrieval, and does not host operator controls.
Method
Method transparency for this rendered record. The panel surfaces the rules and posture under which the record was rendered, in plain view, alongside the audit chain that produced its current state.
Profile admission boundary
profileResearch Corpus (research_corpus)
A record is admitted when sources are registered and review-routed; publication eligibility additionally requires a clean verbatim fragment lint on every cited span.
Discovery posture
No discovery posture metadata is recorded for this record.
Counterpedia does not run search or retrieval. The fields above are render-time metadata only; they do not configure any indexer.
Control discharge
No control-discharge notes were recorded for this rendered record.
Counterpedia does not host operator controls. Mutation, review approval, publication approval, dispute adjudication, and other governed actions live in the GARP Workbench, not on this surface.