Reference · connect · render · examine
Counterpedia can make public evidence legible, navigable, and reusable while keeping the issuing authority, provider identity, custody chain, and governed record visible.
Counterpedia role surface
Counterpedia can reference, connect, render, and help examine public evidence issued elsewhere without becoming the authority that issued the source, receipt, observation, assessment, or admission.
This page is one human-readable projection. The same public object should be usable by software or an independent verifier without depending on this interface.
Portable object · demonstration
Stable reference, machine projection, verification surface, and developer entry points are first-class exits from the website.
Authority map
Origin / issuer
Authority over the original act or source
Provider / repository
Makes a provider-native object addressable
Capture / operation
Binds custody, bytes, method, or receipt
Portable object
Carries exact identity and provenance across systems
Counterpedia
Public projection · renderer / connector
Independent verifier
Checks governed bindings without trusting this UI
No arrow above means “authority transfers.” It means the public projection preserves and exposes the relationship among separately governed objects.
Shared contract
Counterpedia can make public evidence legible, navigable, and reusable while keeping the issuing authority, provider identity, custody chain, and governed record visible.
Rendering does not make Counterpedia the source issuer, receipt issuer, assessor, verifier, admission authority, or owner of a provider-native identity.
Counterpedia renders evidence that is already public or that its holder chose to publish. Private institutional acts remain outside this public surface unless published.
Boundary proof 1 · structured dataset
Wikidata remains the provider of the structured record. Counterpedia exposes the QID, retained observation, carried references, and connected views without treating provider graph membership as admission or substantive truth.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
What this establishes
Provider identity, exact QID, carried statements/references, retained provenance, and explicit provider-native navigation.
What this does not establish
That Counterpedia admits the record, that a statement is true in the world, or that a carried reference has Counterpedia evidentiary standing.
Boundary proof 2 · regulatory system
CIK and accession values remain SEC-owned identifiers. A filing may expose the issuer record carried by its exact CIK, but the issuer view does not manufacture a reverse filing universe from an aggregate count.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
Explicit provider neighborhood
The filing itself carries CIK 0000320193, so the projection can expose exactly that SEC issuer record as navigation. No reverse edge is inferred.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
Provider neighborhood
Explicit provider-native record relationships carried by the producer.
carried cik issuer record
sec_edgar
Counterpedia does not infer reverse links, sibling records, same-subject identity, or completeness from these edges.
What this establishes
Exact SEC provider records, SEC-native identifiers and locators, and the filing-to-issuer edge explicitly carried by the filing's CIK.
What this does not establish
Counterpedia canonical identity, a complete issuer filing neighborhood, SEC endorsement of Counterpedia, or evidentiary standing.
Boundary proof 3 · repository / discovery
CourtListener is rendered as the repository/discovery provider. Explicit carried parent-context relations can be navigated without re-describing CourtListener as the court or treating repository identity as origin authority.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
Provider neighborhood
Explicit provider-native record relationships carried by the producer.
docket context
courtlistener
Counterpedia does not infer reverse links, sibling records, same-subject identity, or completeness from these edges.
What this establishes
CourtListener-native record identity, repository/discovery provenance, and the exact docket context explicitly carried by the provider material.
What this does not establish
Issuing-court identity, court-origin authority, uncarried sibling/reverse relations, or a legal holding.
Boundary proof 4 · governed association
This fixture carries an acquisition source/capture identity with an accepted committed Source Crosswalk. Counterpedia can therefore render the governed Source Record connection and downstream family/organization navigation.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
Governed Counterpedia connection
This connection exists only because the committed Source Crosswalk resolves the exact acquisition identity. Provider URL, title, digest, and label similarity are not association rules.
What this establishes
That an exact acquisition identity resolves through the existing accepted governed crosswalk to the displayed Source Record and its governed classifications.
What this does not establish
Equivalence based on URL, title, hostname, digest resemblance, or model inference; the UI cannot create the association by displaying it.
Boundary proof 5 · archive / custody
Archive semantics expose original resource, capture time, replay locator, retained digest, receipt reference, and explicitly carried adjacent captures. The archive remains a custody and replay layer rather than the origin publisher.
Source & provenance
Trace the provider record, Counterpedia custody, and any governed source association separately.
Origin
Counterpedia observation
How Counterpedia obtained it
Provider neighborhood
Explicit provider-native record relationships carried by the producer.
previous capture
internet_archive
wayback:20231201091500:https://example.org/report
carried by previous_capture_ref · wayback:20231201091500:https://example.org/report
next capture
internet_archive
wayback:20240302164500:https://example.org/report
carried by next_capture_ref · wayback:20240302164500:https://example.org/report
Counterpedia does not infer reverse links, sibling records, same-subject identity, or completeness from these edges.
What this establishes
Capture custody, timestamp, replay locator, retained digest/receipt reference, and the explicitly carried previous/next capture records.
What this does not establish
Original publisher identity, origin authority, substantive authenticity, or that adjacent captures form a complete version history.
Portability test
A successful public evidence surface does not trap the object in Counterpedia. The record should be inspectable here, consumable directly by software, and independently verifiable without treating this presentation as the authority.
Get the machine object
JSON projection · no HTML scraping required
Use the public layer directly
Developer interfaces and machine workflows
Inspect verification material
Receipts and governed bindings remain separate from verdicts
Bring your own evidence
Start from a claim and source rather than this demo
Counterpedia does not need to own the authority to make the evidence legible. It needs to preserve the boundary well enough that you can leave with the object intact.