CounterpediaExplore knowledge. Follow the sources.

/demos/network

Network

Projection-composition shellRead-only · authority movement 0

Eight scenes, frozen in docs/contracts/CP_NETWORK_CONTRACT0.md (CP-NETWORK-CONTRACT0) and mirrored as typed data in lib/counterpedia/networkSceneRegistry.ts (CP-NETWORK-SCENE-REGISTRY0), walk one human question end to end: capture, discovery, source routing, authoring, evidentiary standing, governed traversal, verification, and continued validity. Counterpedia is a reader here — it composes reads and invocations of other repos' own owned seams, never computes or fabricates a scene's answer on its own authority.

A scene with no wired or no landed binding renders its typed unavailable state, visibly — never a mock, never a silently-omitted section, and never fixture data standing in for a live read.

Scene 1 · NETWORK-S1-CAPTURECAPTURE_SEAM_NOT_WIRED

Where did this document actually come from, and what bytes were captured?

Owner: counterpedia-acquisition · Schema: acquisition.capture_receipt.v0

CAPTURE_SEAM_NOT_WIRED

No acquisition capture execution-port binding is configured for this deployment (COUNTERPEDIA_ACQUISITION_URL / COUNTERPEDIA_ACQUISITION_URL_CAPTURE_TOKEN unset). No capture is performed and no capture receipt is fabricated.

NO_COURTLISTENER_CAPTURE_RECEIPT_ARTIFACT_CONFIGURED

No acquisition.courtlistener_selected_capture.v0.1 receipt artifact is configured for this deployment (COUNTERPEDIA_NETWORK_COURTLISTENER_CAPTURE_RECEIPT_ARTIFACT_PATH unset). No fixture is substituted. The courtlistener-selected-capture projection adapter (lib/counterpedia/projectionClient/adapters/courtlistenerSelectedCaptureAdapter.ts) is landed; only a concrete receipt artifact is unconfigured here.

Authoritative action lives at: acquisition service's own capture-receipt view (owner repo)

Scene 2 · NETWORK-S2-DISCOVERYNO_RUN_ARTIFACT_CONFIGURED

What candidate sources exist for this subject, and who found them?

Owner: Source Intelligence (SI) · Schema: si.discovery_run_projection.v0.1

NO_RUN_ARTIFACT_CONFIGURED

The SI-READ-SEAM0 seam itself is landed (si.discovery_run_projection.v0.1) — no DiscoveryRunProjection RUN ARTIFACT is configured for this deployment (COUNTERPEDIA_NETWORK_SI_DISCOVERY_RUN_PROJECTION_ARTIFACT_PATH unset). No fixture is substituted.

Scene 3 · NETWORK-S3-SOURCE-ROUTINGNO_ROUTE_PLAN_ARTIFACT_CONFIGURED

How did the system decide which source(s) to route to, and in what order?

Owner: Source Intelligence (SI) · Schema: si.provider_route_plan.v0.1

NO_ROUTE_PLAN_ARTIFACT_CONFIGURED

CP-NETWORK-S3-ROUTE-PLAN-CONSUMER0: no si.provider_route_plan.v0.1 artifact is configured for this deployment (COUNTERPEDIA_NETWORK_SI_PROVIDER_ROUTE_PLAN_ARTIFACT_PATH unset). No fixture is substituted. The provider-route-plan projection adapter (lib/counterpedia/projectionClient/adapters/providerRoutePlanAdapter.ts) is landed; only a concrete route-plan artifact is unconfigured here.

Scene 4 · NETWORK-S4-AUTHORINGAUTHORING_SEAM_NOT_WIRED

What draft was produced from this source, and by which authoring path — fresh fetch or held capture reuse?

Owner: counterpedia-authoring · Schema: authoring.proposal.v0

LIVE_AUTHORING_ORCHESTRATION_NOT_WIRED

counterpedia-authoring's live draft-from-url / draft-from-source endpoints are landed at the owner repo, but this repo runs NO consumer-side HTTP orchestration against them — this scene never re-authors and never re-fetches a source URL. It projects only an already-produced, immutable authoring output artifact (below), when one is configured.

NO_AUTHORING_HANDOFF_ARTIFACT_CONFIGURED

No authoring_admission_handoff.v0.1 artifact is configured for this deployment (COUNTERPEDIA_NETWORK_AUTHORING_HANDOFF_ARTIFACT_PATH unset). No fixture is substituted, and no draft/proposal is fabricated. The authoring handoff projection adapter (lib/counterpedia/projectionClient/adapters/authoringHandoffAdapter.ts) is landed; only a concrete handoff artifact is unconfigured here — see counterpedia-authoring's own output for a produced handoff.

NO_CAPTURE_PROVENANCE_ARTIFACT_CONFIGURED

No CaptureReceipt/provenance artifact is configured for this deployment (COUNTERPEDIA_NETWORK_ACQUISITION_CAPTURE_PROVENANCE_ARTIFACT_PATH unset). No fixture is substituted.

Authoritative action lives at: counterpedia-authoring's own draft/proposal view (port 8788)

Scene 5 · NETWORK-S5-EVIDENCE-STANDINGQUERY_SERVICE_UNREACHABLE

What did the Countergraph query-execution return for this object?

Owner: countergraph · Schema: countergraph.query-service-response/v0.1

QUERY_SERVICE_UNREACHABLE

No Countergraph query-execution artifact is configured for this deployment (COUNTERPEDIA_NETWORK_COUNTERGRAPH_EVIDENCE_STANDING_ARTIFACT_PATH unset). No fixture is substituted.

Scene 6 · NETWORK-S6-GOVERNED-TRAVERSALGOVERNED_AGENT_UNREACHABLE

Can I traverse this object's neighborhood and provenance under governance, and is there a receipt for that traversal?

Owner: countergraph-mcp + DAGR · Schema: dagr.srs.core.v5_1

GOVERNED_AGENT_UNREACHABLE

No governed-read GovernedReadResult artifact is configured for this deployment (COUNTERPEDIA_NETWORK_AGENT_GOVERNED_READ_ARTIFACT_PATH unset). No fixture is substituted. The 5 countergraph-mcp tools remain invocable only through the governed Agent/DAGR runtime boundary — see /agents.

Authoritative action lives at: /agents (open)

Scene 7 · NETWORK-S7-VERIFICATIONVERIFIER_UNREACHABLE

Can an independent verifier recompute the verdict on this receipt from bytes alone?

Owner: arcs-verify · Schema: arcs_verify.findings.v0

NO_VERIFICATION_REPORT_ARTIFACT_CONFIGURED

No verification-report artifact is configured for this deployment (COUNTERPEDIA_NETWORK_ARCS_VERIFY_REPORT_ARTIFACT_PATH unset). No fixture is substituted. The arcs-verify report projection adapter (lib/counterpedia/projectionClient/adapters/arcsVerifyReportAdapter.ts) is landed; only a concrete report artifact is unconfigured for this deployment — see arcs-verify's own CLI/output for the live read.

Authoritative action lives at: arcs-verify's own CLI/output (read-only)

Scene 8 · NETWORK-S8-CONTINUED-VALIDITYNO_CURRENTNESS_OBSERVATION_ARTIFACT_CONFIGURED

Is the displayed basis current relative to the reference record?

Owner: Counterpedia (`lib/counterpedia/currentness.ts`, `evaluateCounterpediaCurrentness`) · Schema: counterpedia.currentness/v0.1

NO_CURRENTNESS_OBSERVATION_ARTIFACT_CONFIGURED

No counterpedia.currentness/v0.1 observation artifact is configured for this deployment (COUNTERPEDIA_NETWORK_CURRENTNESS_OBSERVATION_ARTIFACT_PATH unset). No fixture is substituted and no observation is fabricated — this typed-unavailable read is distinct from an actual NOT_EVALUATED observation. The currentness compute (lib/counterpedia/currentness.ts) and this projection adapter are landed; only a concrete observation artifact is unconfigured here.

There is no aggregate verdict across these eight scenes and no field that combines them. Retrieval is not admission. Rendering is not verification. Deep-linking is not execution. A DAGR receipt is a governance artifact, not path evidence. NOT_EVALUATED is never rendered as PASS.