CounterpediaExplore knowledge. Follow the sources.

Bounded legal-record investigation

CourtListener: recurse through a carried frontier

A CourtListener docket becomes a first-class starting point for a bounded investigation. The seed and its carried cohort are addressable, while the page keeps provider observation, structural traversal, Check, history, and forum challenge as separate planes.

Retained specimen: CourtListener docket 68117049 · The New York Times Company v. Microsoft Corporation

Common reader grammar

Try → Inspect → Machine → Continue

One trail, five surfaces, no hidden promotion between them.

  1. 01Try

    Counterpedia

    Open the exact carried docket

    Start with the exact CourtListener native id. Grammar-valid ids outside the pinned cohort remain absent rather than becoming invented observations.

    Open surface →

  2. 02Inspect

    Countergraph

    Open the structural inspector

    Inspect the read-only Countergraph surface. Adjacency is carried structure, not support, confidence, or authority.

    Open surface →

  3. 03Machine

    Check

    Open the machine-check front door

    Use Check for dimensioned machine findings. A Check receipt is not a verdict and does not promote a source into support.

    Open surface →

  4. 04Continue

    History

    Read retained history

    Continue to the history lens. It renders carried lifecycle or attempt history; it does not infer a prose edit log.

    Open surface →

  5. 05Continue

    Counterforum

    Continue into challenge and revision

    Counterforum is the challenge/research/revision surface. Its later synthesis does not change Counterpedia standing by itself.

    Inspect source ↗

Machine snapshot

What the page actually carries

Open capability ledger →
schema_version
counterpedia.proof-journey.v0.1
Capability
bounded-courtlistener-frontier
Provider
CourtListener
Seed docket
68117049 · 1:23-cv-11195
Seed case
The New York Times Company v. Microsoft Corporation
Seed locator
https://www.courtlistener.com/docket/68117049/the-new-york-times-company-v-microsoft-corporation/
Captured bytes
sha256:a72447287f7d79867b8670a2bf915279bc7ba13ed30673417c200b135a0ba49a
Cohort frontier
5 carried dockets · recursion bound = carried cohort only
Boundary
provider observation and adjacency ≠ support, authenticity, or standing

Exact source bindings

  • Pinned source: thelaplage/counterpedia@50d4634f1c08… · lib/counterpedia/providers/courtListenerCarriedEntries.ts

What this proves

  • • A real CourtListener docket can enter the common Counterpedia entry grammar only when it is present in the pinned capture cohort.
  • • A bounded provider frontier can be inspected without minting a second truth store or silently converting adjacency into support.

What this does not prove

  • • The carried cohort is not a claim that the matters are semantically related.
  • • This journey does not establish court-origin authenticity, legal truth, proposition support, admission, or standing.

This page is a presentation-only projection of retained artifacts and pinned source bindings. It performs no provider call, capture, Check, forum write, admission, support decision, or authority movement while rendering.