Search and discovery surfaces
222 entries are published into the archive index across 12 shelves, with Atlas, briefing, feed, OpenSearch, and diagnostics routes wired.
Release Matrix
Operational proof for the archive, not just pretty shelves.
This surface tracks the launch-grade health of Steins;Gate Sanctum: content contracts, runtime surfaces, evidence coverage, and whether the generated archive still behaves like a reliable system.
Archive entries 222
Observer-safe now 166
Source domains 18
Sources per entry 1.3
Service worker sanctum-v15
Source pack generated 2026-03-23
Release gates pass 8
Release gates warn 0
Gate Checks
Download the matrix Launch-grade gates the repo has to keep passing.
Query-surface depth
3 campaign lanes, 9 work pivots, 63 media lanes, 16 source tiers, 12 year anchors, 4 freshness bands, 3 live-window states, and 4 evidence bands are exposed for archive filtering.
Evidence coverage
222/222 entries carry linked sources, averaging 1.3 source links per entry.
Timeline readiness
93/93 expected dated entries normalize to machine-readable dates.
Snapshot contracts
148/148 snapshot-first collections expose parsed fact blocks for structured detail rails.
Continuity labeling
123/123 collections that require explicit continuity labels provide them, and 222/222 entries still resolve to a cluster.
Offline and runtime surfaces
Service worker sanctum-v15 precaches 29 core paths and watches 14 runtime JSON surfaces.
Live branch intelligence
6 current signals, 6 access checks, and 6 active or upcoming windows are published via /signals, /research, and their JSON surfaces.
Coverage Totals
Open the archive console Expected metadata contracts across the entire archive.
Evidence Sources: 222/222
284 linked sources across the archive.
Timeline Dates: 93/93
Only collections that promise timeline data are counted here.
Structure Snapshots: 148/148
Snapshot-first collections keep their structured fact rails alive here.
Continuity Explicit labels: 123/123
All entries still resolve to a cluster, even when the label is collection-derived.
Query Depth 3 campaigns / 9 works / 63 media lanes
16 source tiers and 12 tracked years are exposed as direct archive pivots.
Graph Layer Signal network online
The archive now ships a relationship graph at /archive-network.json plus a browsable network view at /network.
Shelf Contracts
Open the atlas What each directory promises to ship.
Works 17 entries
Works
Core works should carry explicit continuity, a dated release anchor, and a structured snapshot block.
Sources: 17/17 Dates: 16/16 Snapshots: 17/17 Continuity: 17/17
Characters 17 entries
Character Dossiers
Character dossiers rely on continuity labels and snapshot facts, but most do not need a primary timeline date.
Sources: 17/17 Dates: 0/0 tracked Snapshots: 17/17 Continuity: 17/17
Glossary 20 entries
Glossary
Glossary entries are term-focused references, so they are tracked without dates, snapshot blocks, or explicit continuity tags.
Sources: 20/20 Dates: 0/0 tracked Snapshots: 0/20 tracked Continuity: 0/20 tracked
2011 Anime 26 entries
Steins;Gate 2011
Episode guides should stay timeline-ready, while continuity is derived from the shelf itself.
Sources: 26/26 Dates: 26/26 Snapshots: 0/26 tracked Continuity: 0/26 tracked
SG0 Anime 24 entries
Steins;Gate 0
SG0 episodes should stay timeline-ready, while continuity is derived from the shelf itself.
Sources: 24/24 Dates: 24/24 Snapshots: 0/24 tracked Continuity: 0/24 tracked
IBM Shorts 4 entries
IBM Cognitive Computing
IBM shorts should stay timeline-ready, while continuity is derived from the shelf itself.
Sources: 4/4 Dates: 4/4 Snapshots: 0/4 tracked Continuity: 0/4 tracked
Music 65 entries
Music Vault
Music entries lean on continuity labels and structured snapshot facts more than dated release anchors.
Sources: 65/65 Dates: 0/0 tracked Snapshots: 65/65 Continuity: 65/65
Print 24 entries
Print Archive
Print entries prioritize continuity labels and snapshot blocks; many do not yet normalize a machine date.
Sources: 24/24 Dates: 0/0 tracked Snapshots: 24/24 Continuity: 24/24
Places 2 entries
Places
Place dossiers are setting-first references, so timeline dates stay optional while snapshot facts and location context remain required.
Sources: 2/2 Dates: 0/0 tracked Snapshots: 2/2 Continuity: 0/2 tracked
Events 8 entries
Events
Event entries should remain dated and snapshot-first, while continuity is derived from the collection.
Sources: 8/8 Dates: 8/8 Snapshots: 8/8 Continuity: 0/8 tracked
Access 6 entries
Where To Watch / Play
Access checks should stay dated and snapshot-first, while continuity is derived from the collection.
Sources: 6/6 Dates: 6/6 Snapshots: 6/6 Continuity: 0/6 tracked
Current 9 entries
Observation Log
Current-log entries should stay dated and snapshot-first, while continuity is derived from the collection.
Sources: 9/9 Dates: 9/9 Snapshots: 9/9 Continuity: 0/9 tracked
Runtime Surfaces
Open the feed Operational routes and source-tier mix.
Published surfaces
Source-tier mix
Official 106 entries
Secondary 56 entries
Retail index 21 entries
Community 20 entries
JustWatch 3 entries
Secondary + Official 3 entries
Official retail event 2 entries
Official tourism 2 entries
Archive pivots
Campaigns 3
Works 9
Media lanes 63
Source tiers 16
Tracked years 12
Gap Queues
Inspect raw diagnostics Anything still missing from required contracts rises here first.
Timeline-first collections should stay machine-date ready.
No gaps detected in this required contract.
Snapshot-first collections should keep their structured fact rails intact.
No gaps detected in this required contract.
Continuity-explicit collections should keep direct cluster labels in frontmatter.
No gaps detected in this required contract.