CounterpediaExplore knowledge. Follow the sources.

/demos

Demonstrations

Counterpedia's canonical knowledge demonstration is the eight-scene network composition below. It follows one governed knowledge story across capture, discovery, source routing, authoring, evidence/query, governed traversal, independent verification, and continued validity without moving those owner systems' authority into the presentation layer.

The surface is fail-closed. When an owner-controlled artifact or binding is unavailable, the corresponding scene says so explicitly instead of filling the gap with fixture data or an inferred answer. When an immutable run pack is configured, its exact artifact bytes, digests, schema identities, and explicitly proven joins are checked before they render.

Product journey

Try Counterpedia end to end

One route map over product surfaces that already exist. Missing public actions stay visibly unavailable instead of becoming placeholder buttons or inferred capabilities.

authority movement 0
  1. 01

    Capture

    Open

    Inspect the live discovery/capture surface.

    Capture records exact bytes and provenance; capture is not admission or support.

    Open surface →
  2. 02

    Draft from source

    Not public

    Create a proposal from retained source material.

    The producer/reader proposal seams exist, but current main exposes no public Draft-from-source action. This journey will not invent one.

    No public route on current main
  3. 03

    Article

    Open

    Read the admitted NYT/OpenAI entry through the canonical article surface.

    The reader observes current standing; viewing the article moves no authority.

    Open surface →
  4. 04

    Source Footprint / Library

    In article

    Inspect the source treatments already composed into the admitted article.

    Observed reference, source candidate, captured source, and evaluated evidence remain distinct states.

    Open surface →
  5. 05

    Source Atlas

    Open

    Move from one entry's source surface into the dedicated cross-entry Source Atlas.

    /sources is the dedicated public Source Atlas (SOURCE-ATLAS-PUBLIC0 and later Atlas facet work): a cross-entry source directory with family and organization views. It is not a coverage, quality, or corroboration score.

    Open surface →
  6. 06

    Claims & provenance

    Open

    Inspect capture, proposal, decision, custody position, and current standing together.

    The Governance Trace composes already-governed records. It does not infer support or mint provenance, custody, standing, or authority.

    Open surface →
  7. 07

    Currentness

    Not public

    Run a dedicated reader-facing currentness check for this object.

    The network demo contains a changed-source STALE path, but currentness is not promoted here into a standalone public action or conflated with support or standing.

    No public route on current main
  8. 08

    Counterpedia Check

    Open

    Open the existing Check surface and inspect its bounded verification workflows.

    Check/verification does not create truth, authorization, admission, or standing.

    Open surface →
  9. 09

    Agent research

    Open

    Inspect the existing research/capture agent demonstration.

    Agent capability and proposal behavior do not imply permission or epistemic authority.

    Open surface →
  10. 10

    Network proof

    Open

    Follow the canonical eight-scene governed knowledge composition.

    Structural traversal, independent verification, and continued validity remain separate governed questions.

    Open surface →
  11. 11

    Integration registry

    Open

    Inspect who and what may participate through the pinned registry snapshot.

    Capability, runtime permission, explicit authority, provenance, distribution standing, and marketplace standing remain separate axes.

    Open surface →

Canonical knowledge demo

Follow the knowledge story end to end

8 scenes · read-only composition

/demos/network is the primary Counterpedia knowledge-demo front door. Each scene reads an owner-controlled seam or immutable artifact; the page does not re-author, re-admit, re-verify, mint identity, or infer a missing cross-system relationship. The immutable replay header distinguishes exact byte/digest bindings from mere same-run context.

Scenes 1–4

Capture → Discovery → Source routing → Authoring

Exact custody and proposal-only authoring remain distinct from admission or publication.

Scenes 5–8

Evidence/query → Governed read → Verify → Continued validity

Includes the real changed-source STALE path and its paired pre-mutation-refusal projection without turning currentness into admission or standing.

Open the knowledge demoInspect research/captureInspect live discovery/captureReplay Wikidata → Crossref

Source architecture

Compare provider provenance across systems

The authority-preserving surface shows how Counterpedia presents external evidence without absorbing the authority of the systems that issued, hosted, captured, or governed it. The demo compares Wikidata, SEC EDGAR, CourtListener, governed Source Record bridges, and archive custody while keeping provider identity, custody, documentary identity, and Counterpedia's public role separate.

See how Counterpedia renders public evidence without inheriting source, provider, custody, or admission authorityInspect the Wikidata template

Focused proof

Can you actually defend this connection?

The NYT/OpenAI Countergraph proof remains available as a focused inspector, not the overall knowledge-demo front door. A structural policy can find a one-hop projects_as route while a supported_by-only policy returns NO_DEFENSIBLE_PATH and keeps the rejected structural route inspectable.

Open the connection proofSee the Agent boundary

Program map

Planned demonstrations

The cards below are planning metadata, separate from the canonical /demos/network implementation. Their appearance here does not mean an underlying record exists, has been admitted, or can be checked yet.

  • Utility / executable knowledgePLANNED · not yet admitted

    USB-C / Thunderbolt compatibility

    Planned demonstration of a deterministic compatibility answer derived from governed device and specification inputs, with the exact rule edition and input versions shown next to the result rather than a bare yes/no.

    Capability: Compute / DERIVE · Maturity: R0 · Next: Source capture and a governed compute record.

  • Utility / executable knowledgePLANNED · not yet admitted

    Warbling Vireo classification

    Planned demonstration of how a taxonomic classification reprojects across governed editions, showing the prior and current authority and the resulting projection delta instead of a single flat label.

    Capability: Reproject / VERSION · Maturity: R0 · Next: Governed edition records for the classifying authority.

  • Utility / executable knowledgePLANNED · not yet admitted

    NYC curb-rule applicability

    Planned demonstration of how a governed rule's applicability changes with public-safe contextual variables (place, time, vehicle class), showing the projected result and the inputs it depends on.

    Capability: Context / APPLY · Maturity: R0 · Next: A governed rule record plus a context-projection surface.

  • Contested recordPLANNED · not yet admitted

    Theranos

    Planned contested-record demonstration: current standing, typed unknowns, and an explicit “why not” surface distinguishing allegations from established findings — with refusals and typed absence kept visible rather than hidden.

    Capability: Record / Why not? · Maturity: R0 · Next: Source capture and an adjudication record.

  • Contested recordPLANNED · not yet admitted

    MH370

    Planned bounded-unknown demonstration: what the governed record establishes and — as first-class content — what it does not, carrying typed unknowns and reopening conditions instead of speculation.

    Capability: Record / Why not? · Maturity: R0 · Next: Source capture and a bounded-record composition.

  • TrajectoryPLANNED · not yet admitted

    Spot Bitcoin ETP

    Planned trajectory demonstration of how institutional and regulatory posture changed across editions over time, rendered as governed history and supersession rather than a single present-tense verdict.

    Capability: History / Reproject · Maturity: R0 · Next: A pre-capture research record; nothing served publicly.

  • Utility / executable knowledgePLANNED · not yet admitted

    Election-information routing

    Planned demonstration of epistemic routing under stakes: whether a question is answered from the record, routed to retrieval, deferred, or refused — with the routing basis shown.

    Capability: Route · Maturity: R0 · Next: A governed routing-policy record.

  • ReconciliationPLANNED · not yet admitted

    The Join

    Planned reconciliation demonstration of where two governed views align, diverge, or fail to align at all (a seam) — reported without fabricating consensus, and distinguishing a value disagreement from an unmapped coordinate.

    Capability: Compare / Reconcile · Maturity: R0 · Next: Two governed views and a reconciliation projection.

How to read demo status

Canonical composition

The eight-scene surface exists; each scene still reports its own bound, unavailable, replay, or refusal state honestly.

Immutable replay

Configured run-pack bytes and digests are checked before rendering; same-run context is not promoted into a causal or identity join.

Admitted

A separate governed record-lifecycle property. Demonstration and projection do not create admission or standing.