End-to-end Governance Trace
One governed object's lifecycle, in one view — explicit standing, no inferred authority.
This page follows a single record — The New York Times v. OpenAI: litigation-intersection record (NYT-OPENAI-LITIGATION-0001) — through capture, retained-source availability, an authored proposal, the custody-ACK position, and current standing. It is read-only: it performs no admission, creates no custody record, and mints no authority.
The distinctions are the point. A retained capture can exist without this trace proving that a particular authoring run consumed it. The proposal input remains visibly proposed, while current Counterpedia standing is read separately from the admission store and its explicit governance decision. The transport custody ACK remains ABSENT rather than being inferred.
Capture
Three governed captures exist upstream, each bound to exact historical bytes by sha256 and a CaptureReceipt.
- Identifier of the governed capture event recorded upstream.
- Digest of the exact historical captured bytes.
- Digest of the upstream CaptureReceipt in thelaplage/counterpedia-acquisition, merge f00e8e856f447854b7b4459043c3b8c554787f0a.
- Identifier of the governed capture event recorded upstream.
- Digest of the exact historical captured bytes.
- Digest of the upstream CaptureReceipt in thelaplage/counterpedia-acquisition, merge af4f4304b5589474ff9359845bf97eab4eb39355.
- Identifier of the governed capture event recorded upstream.
- Digest of the exact historical captured bytes.
- Digest of the upstream CaptureReceipt in thelaplage/counterpedia-acquisition, merge f9aa8469360710b944fcf3b2fe53692a276e491e.
read fromlib/garpedia/nytOpenAiKnownSources.ts
Retained source
Each source's governed identity and exact capture digest converge on one canonical index entry — a governed_capture entry, or, where a same-capture_hash identity collision exists, its crosswalk-bound cp:source (which carries the folded src_* identity as an alias). This establishes retained-capture availability, not causal use by the authoring proposal.
- The source identity with a governed retained capture available.
- Existing source resolver result on the governed source identity and capture digest together; a folded capture resolves both keys to its crosswalk-bound cp:source (public_current), an unfolded one to its governed_capture entry.
- The retained source identity resolves on the same digest recorded by capture.
- The source identity with a governed retained capture available.
- Existing source resolver result on the governed source identity and capture digest together; a folded capture resolves both keys to its crosswalk-bound cp:source (public_current), an unfolded one to its governed_capture entry.
- The retained source identity resolves on the same digest recorded by capture.
- The source identity with a governed retained capture available.
- Existing source resolver result on the governed source identity and capture digest together; a folded capture resolves both keys to its crosswalk-bound cp:source (public_current), an unfolded one to its governed_capture entry.
- The retained source identity resolves on the same digest recorded by capture.
- This projection does not read an authoring execution/package artifact carrying the capture_ref consumed by the proposal. It therefore does not claim that this proposal consumed these retained bytes or that no refetch occurred during its authoring run.
read frompublic/counterpedia/source-resolution-index.json · lib/garpedia/sourceResolution.ts
Authoring proposal
The authored input remains a bounded v0.2 PROPOSAL with lifecycle_state "proposed" and zero ClaimSupportEdges. Proposal lifecycle is distinct from the record's separately governed current standing.
- The immutable proposal input stays proposed even when a separate governance decision has been applied to create current admitted standing.
- Canonical digest of the exact proposed record bytes.
- Zero claim bindings; co-presence confers no epistemic support.
read fromlib/counterpedia/contentV02AdmissionCatalog.ts
Transport custody ACK
No OT-04 transport custody acknowledgment has been produced into this Counterpedia record. Exact-artifact custody is therefore NOT CLAIMED here.
ABSENT is distinct from FAILED, NOT_EVALUATED, and REFUSED. No custody ACK is synthesized from the capture digest.
- A custody ACK would bind a named receiver to exact received bytes; it would not prove truth, conformance, authorization, or admission.
read from(none — no custody-ACK record exists in Counterpedia)
Drill down: what a custody ACK is, and what it would have proved →
Current standing
Current standing is read from the real admitted-content store and reader. The existing governance decision is applied there; this trace only observes that state and moves no authority.
- Current institutional standing and reader outcome, derived rather than hard-coded.
- contentV02Store current status for this page_id.
- Resolved through the same v0.2 entry-slug registry and reader used by the public route.
- An already-issued decision is deterministically revalidated/applied by the admission store. This projection originates no decision.
read fromlib/counterpedia/contentV02Admission.ts · lib/counterpedia/contentV02EntrySlug.ts · lib/counterpedia/readerV02Selection.ts · lib/counterpedia/contentV02AdmissionCatalog.ts
What this trace does not claim
- This page composes records that already exist; it creates no admission, custody record, identity, or authority.
- Captured bytes are historical and digest-bound; retained-capture availability does not by itself prove authoring consumed those bytes.
- The authored proposal remains proposed; current admitted standing is a separate state derived from the admission store and its explicit governance decision.
- Custody means a receiver holds exact bytes — not truth, conformance, authorization, or admission — and no custody ACK exists for this specimen.
- ABSENT is not FAILED, not NOT_EVALUATED, and not REFUSED.
- AUTHORITY_MOVEMENT is 0 in this correction: the trace reads already-governed standing and originates nothing.