For developers

What this page is

A task-oriented reference for retrieving Counterpedia's public projection of governed records: which routes return what, how an agent can traverse the site without a browser, and what this site deliberately does not do. Counterpedia is read-only. Nothing reachable from this page performs admission, review, promotion, publication, revision, or custody actions.

Retrieve a public record

The records registry at /records lists every currently admitted record and links to each one. Every admitted record renders at its own /records/{recordId} route, statically generated at build time.

Example: /records/HEPPNER-LIFECYCLE-0001

Page-model JSON and the portable export bundle

Each record's rendered page model is also available as static JSON, and a separate portable export bundle carries a source-reference summary, receipt references, and cross-artifact traversal links for the same record. Both are static files served from this deployment; neither is produced by a live backend call.

Bundles are not uniform in standing. One committed bundle is a supported public projection the published client accepts; the rest are demonstration and historical fixtures. They stay reachable at their own URLs so past outputs remain inspectable, but they are refused by the client and the MCP adapter with a typed unsupported-format result, and no surface presents them as supported machine artifacts. The supported set is listed at /garpedia/export-bundles/supported-index.json.

• Page model: /garpedia/page-models/HEPPNER-LIFECYCLE-0001.json
• Portable export bundle: /garpedia/export-bundles/HEPPNER-LIFECYCLE-0001.json

Sources, history, refusals, and verification artifacts

/sources lists every registered source and the records that cite it. Each record's lifecycle history renders at /records/{recordId}/history. /refusals is the cross-record index of every refused, reconsiderable, FINAL, and unsupported candidate branch, each linking back to its record. Where a record carries a committed verification report, that report renders inside the record's own Verify tab; /verification-workbench indexes committed reports across records.

• Records registry
• Refusals index
• Sources registry
• Corpus decision index
• Verification workbench
• /records/HEPPNER-LIFECYCLE-0001/history

Agent-readable traversal

/llms.txt and /llms-full.txt list every current public route in plain-text, machine-readable form, generated from the same public surface registry that drives primary navigation, the Archive, and sitemap.xml. An agent can start from either file and reach every public record, source, and registry index without parsing HTML.

• /llms.txt
• /llms-full.txt
• /sitemap.xml

What an agent or developer may not do here

Counterpedia performs no admission, review, promotion, publication, revision, mutation, or custody action of any kind. There is no live verifier invocation, no MCP tool-call console, no free-text agent chat, no search, no accounts, and no credential flow anywhere on this site. Every route above returns a static or statically-generated response, and none of them accept a write.

Where DAGR MCP fits, and does not

DAGR MCP is a receipt-emitter and runtime binding that signs SRS receipts at a configured admission boundary. It is a separate, operator-side system that Counterpedia does not embed, call, or expose a console for. Counterpedia only ever renders records and receipts that already exist as static, committed artifacts.

Where ARCS Verify fits, and does not

ARCS Verify independently checks a signed receipt against a pinned SRS envelope schema and a named conformance profile. It verifies the structure, cryptographic properties, and profile conformance of a receipt; it does not certify the producing implementation and does not establish that the real-world event the receipt describes actually occurred. Counterpedia links to committed verification reports where one exists; it does not run ARCS Verify live and does not recompute a verdict.

The Counterpedia integration SDK

Four packages are implemented in this repository as private prerelease/internal packages, distinct from the GARP/Profile SDK substrate that binds a profile to a workbench and source registry: @garpedia/contracts (zero-network types, schemas, and validators), @garpedia/client (a universal read-only fetch/validate/cache client), @garpedia/graph (a deterministic, read-only reference-graph projection), and @garpedia/mcp (a thin, read-only MCP adapter over the same public artifacts — distinct from DAGR MCP; see above). Source and package-local documentation live under packages/ in this repository, and a discovery manifest is published at /.well-known/garpedia-discovery.json.

None of the four packages is published to npm. All remain private and versioned as internal prereleases, and there is no public install command yet. The supported portable-bundle family is garpedia.portable_export_bundle.v1.public_projection only; other committed bundles remain reachable but unsupported. This MCP adapter does not yet expose a discovery tool, even though client.getDiscovery() and the published manifest both exist.

Where GARP Ingest fits, and does not

GARP Ingest is the separate, upstream ingest/handoff producer that classifies and preserves inbound source material before any of it is a candidate for a governed record. Its own boundary holds three distinct, non-implying stages: OKF conformance != GARP intake acceptance != ARCS admission. Counterpedia adds a fourth link rather than assuming it: none of those three stages implies Counterpedia publication. Counterpedia's public artifacts and discovery manifest never advertise ingest-bundle or handoff artifacts — only already-admitted, already-rendered public records and their projections.

The six-role namespace map