/what-is-counterpedia
What is Counterpedia?
Position
Counterpedia is the public read surface for governed records produced under the Governed Analytical Records Protocol. It renders profile-eligible records for human readers and agents, exposes their admitted claims, their sources, what was refused and why, their lifecycle history, and a machine-readable projection of the same material, and explains the protocol model and the systems built on it. Counterpedia does not claim upstream custody, admission, verification, or certification authority over the material it renders — it presents projections of governed state that other, separately owned systems produce.
The public surface is organized around six canonical operations: search (declared but not yet hosted), read (retrieve a governed record's current projection), explain (the 'Why not?' surface for refused candidates and unresolved lifecycle values), sources (the source material the record declares), history (prior editions and governed lifecycle transitions), and verify (the record's declared verification posture, independently checkable). These six operations are the Counterpedia public facade; the underlying substrate identifiers and package names are unchanged.
Why this site exists separately
Most knowledge systems hide the moment information becomes durable: a document is saved without ceremony, a page is edited without notice, a model answer is cached and reappears as fact, and a claim is copied into a report and treated as canon by virtue of being typeset. Counterpedia explains the opposite pattern, in which knowledge enters through governed admission, source support, review, lineage, and publication boundaries that remain visible after the record exists. The site exists so a non-developer audience can understand the protocol without first parsing a schema or a repository.
The underlying stack
| Name | Role |
|---|---|
| GARP | Governed Analytical Records Protocol — the schema and object model |
| DAGR | Runtime boundary: projects calls into lifecycle decisions, emits signed SRS receipts |
| ARCS | Verification standard: independently recomputes receipt structure and crypto from bytes alone |
| Counterpedia | Public read surface: renders governed records for humans and agents across six operations |
| Counterpose | Publication platform built on the GARP model; Counterpose at counterpose.org is the editorial authority |
| garp.tools | Implementation references, schemas, validators, and SDK for developers and operators |
The six canonical operations
The public facade exposes exactly six named operations. counterpedia.read returns one governed record's current projection, its admitted projection, and the reader interpretation, kept distinct. counterpedia.explain returns the 'Why not?' surface: candidates the record evaluated and did not adopt, plus open disputes and unresolved lifecycle values. counterpedia.sources returns the source material the record declares, passed through without re-characterisation as proof of a claim. counterpedia.history returns prior editions and governed lifecycle transitions, kept distinct from the current projection. counterpedia.verify returns the record's declared verification posture — independently-checkable properties — and is not a verdict and not a verifier run.
counterpedia.search is declared as a surface operation but is not yet hosted. The SEARCH_NOT_YET_HOSTED flag is true; consumers can check it before calling. The operation will be added as a live capability in a subsequent release; today it raises an honest not-yet-hosted error rather than silently doing nothing.
What Counterpedia is not
Counterpedia is not a single encyclopedia or database, not a content management system, not an AI governance compliance product, and not a substitute for record custody at the ARCS layer. It is also not a publication platform, since Counterpose at counterpose.org plays that role, not an implementation portal, since garp.tools plays that role for developers and operators, and not a verifier — the independently-recomputed structural and cryptographic verdict on a receipt is produced by arcs-verify from the receipt bytes alone, importing no Counterpedia code.