/releases/widen0-structural-map
WIDEN0 → structural map
The public record of what was built behind the structural map: how the full 848,281-identifier target universe was acquired from Wikidata, released immutably, sampled, and rendered — with the exact figures and the boundaries of what the map does and does not mean.
Read the top for a 30-second explanation; the sections below preserve the exact technical record, including the deployment incident (labelled historical) and the final disposition.
In 30 seconds
What this is
We acquired the relationship graph for a full 848,281-identifier Wikidata universe from a dated 102.8 GB Wikimedia dump, built the released slice from the 35,994-row Wikipedia↔Wikidata join that was supplied to the graph build, and published a single immutable release. A refreshed 166,411-row join was produced afterwards and is recorded in the manifests; the graph, slice and release have not been rebuilt from it. A bounded, deterministic 2,689-node sample of that release is analysed for pure graph structure by Countergraph and rendered on the live map.
The map shows structure only — clusters, bridges, articulation points, islands. It is observed adjacency carried from a provider graph. It is not evidence, support, verification, admission, standing, importance, or ontology. A failed traversal is allowed; an invented one is not — and the acceptance audit recorded zero unresolved entry links, dead hrefs, hard defects, or invariant violations.
The chain
Acquisition → release → Countergraph → Counterpedia
- A dated Wikimedia dump is parsed deterministically into a Wikidata node/edge graph.
- That graph is published as one content-addressed immutable Counterpedia release.
- A bounded deterministic sample is materialised from the release as a structure-only carried graph.
- Countergraph computes graph-theoretic topology over that carried graph, preserving producer vocabulary.
- Counterpedia renders the exact returned topology artifact on /browse/map. No fixture fallback.
Acquisition & release
The immutable Wikidata graph release
- source dump
- 102.8 GB
- dated Wikimedia dump
- target identifiers
- 848,281
- found
- 848,210
- deterministic misses
- 71
- Lexeme IDs; disclosed, not silent
- parsed entities
- 121,453,279
- observed QID→QID rows
- 9,587,549
- join supplied to the graph build
- 35,994 rows
- sha256 b6ee74cd… — the released slice's actual recorded input
- refreshed join, not used by this release
- 166,411 rows
- sha256 3ae49c9b… — produced later; no rebuild performed
- graph-edge rows
- 1,566,412
- in the released graph
immutable release: sha256:5a62831ba7204a01ad18f95a42cb1f1df9e27401930ff91b232123cd782aac15
Market-scale acceptance
A 1,000-subject deterministic audit of the release
The same frozen 1,000-subject seed was run against the release. Coverage is measured honestly: a subject with no continuation is a real, allowed outcome; a link that resolves to nothing that exists is not.
- subjects resolved
- 1,000 / 1,000
- entry-link coverage
- 250 → 703
- of 1,000 (pre-WIDEN → WIDEN)
- entry links resolved
- 1,780 / 1,780
- 0 unresolved
- one-hop continuation
- 685 / 703
- 97.4% of edge-havers
- two-hop continuation
- 654 / 685
- 95.5%
- dead hrefs / hard defects
- 0 / 0
- 0 invariant violations
Disclosed producer gap: the Wikimedia source-affordance is 0 / 1,000 — the wikimedia branch carries no sections.sources today, so the desired source affordance was present for 0 / 1,000 audited subjects. That producer gap is disclosed rather than hidden or reclassified as an ingestion defect.
The public structural sample
What the live map is computed from
- nodes
- 2,689
- declared / structural edges
- 1,500 / 1,499
- components
- 1,190
- articulation nodes
- 129
- bridge edges
- 1,499
topology digest: sha256:a01487f30f05669ad138a73bbf0e1d2c4d25e2939d74ed1a02addfe7d4b83610
Boundaries
What the map does not mean
- structural edge ≠ support
- provider entity ≠ Counterpedia record
- same label / id text ≠ identity equivalence
- sampled topology ≠ full-corpus completeness
- cluster ≠ ontology
- bridge / articulation ≠ importance
- graph membership ≠ truth
- topology ≠ epistemic assessment, admission, standing, or verification
Deployment postmortem · historical
One production incident, recovered
This is a historical record of a resolved incident, kept for transparency. During go-live, a fresh Countergraph production build briefly failed to start because a stale carried-projection digest pin (unrelated to the structural work) no longer matched its fixture — the service correctly refused to start rather than serve mismatched bytes. Production was rolled back to the last-good deployment, the two digests were adjudicated (the payload had not changed; an upstream contract refresh had deliberately re-pinned the source commit), the pin was corrected, the structural bindings were added, the immutable deployment was verified directly, and only then promoted. Lesson recorded: persist and verify production environment before promoting a fresh build.
Disposition
Closed / green
WIDEN0 = CLOSED COUNTERGRAPH_PRODUCTION_STRUCTURAL = GREEN COUNTERPEDIA_PRODUCTION_STRUCTURAL_MAP = GREEN STRUCTURAL_MAP_PROD0 = CLOSED