Signed-in RUNSITE bench
Sign in to open the RUNSITE workspace where prep, runboard continuity, and prep-library launch stay in Chummer.
Open detailsPrep
RUNSITE
RUNSITE keeps prep packs readable in public, and each runsite keeps its own scene style for quick orientation with optional 3D tours.
Site cards
Threat clocks
Scene styles
Signed-in prep bench
Limits
Files, with the limits clearly stated.
Spatial-prep guide only. This page does not promise tactical overlays, live map control, or full VTT integration.
Connected page
RUNSITE prep
Public runsite packs are inspectable without an account, but prep and runboard continuity stay in signed-in workspace and run pages.
Public runsite pack
2 inspectable runsite pack(s) are already readable without opening the signed-in prep path.
Open detailsPrep details
Inspect the workspace, run, and prep-library pages before treating RUNSITE like a static map gallery.
Open detailsRoute overlays, host clips, and tours may assist orientation, but Chummer owns prep status, runboard status, and workspace continuity.
Files
Open the files when you need detail.
Each card opens to the readable notes.
Redmond dockyard pack
Runsite packet with entry vectors, heat clocks, and exit status kept in one next step.
Style: Research Lab
Entry vectors
Threat clocks
Exit status
Everett switchyard pack
Spatial-prep packet for switchyard pressure with player-safe path separation.
Style: Office Building
Site card
Pressure path
Player-safe split
Ready status; Core Engine still needs caution
Next 12 Biggest Wins remains the active wave; journey status is ready; overall progress is 100% in 'Public-fit polish'; the longest pole remains Core Engine; support closure is clear Install-path parity still needs review because local release details are stale.
As of 2026-07-03
Next question: What is the smallest cross-repo slice that makes the campaign OS indispensable and turns trust, adoption, and publication depth into a real launch advantage?
100% · Public-fit polish
43 measured snapshot(s)
0 waiting closure / 0 pending human response
Recommended now
No published build is on the page yet.
Who can get it now
No release download is published yet.
Release status
Passed · Current preview files remain downloadable for status testing, but release support is needs review until stale details and Hosted Build privacy, retention, recovery, and erasure decisions are refreshed Treat the current release as limited because final release details are still blocked by live public web recrawl stale, rule source minimum coverage stale, and ruleset readiness stale Treat the current release as limited because the local release status package is stale.
Launch readiness
Hold parity claims on public routes, support surfaces, and publication lanes because the local release status package is stale.
Service status
Pilot defaults are — Canary green on all active lanes; next review due 2026-07-26. Next decision: Hold the broader rollout until public route coverage exists.
Closure health
0 waiting closure / 0 pending human response. 0 open support packets across 0 reported cases.
Adoption health
Current release status is posted. 5 tested paths and 10 checked pages are on record. 43 weekly snapshots are on record for the current public release picture.
Progress trend
Flat trend 0% from 2026-06-19 to 2026-07-03. Trend window: 2026-06-01 100% → 2026-06-02 100% → 2026-06-04 100% → 2026-06-12 100% → 2026-06-17 100% → 2026-06-18 100% → 2026-06-19 100% → 2026-07-03 100%. Trend sparkline: ▁▁▁▁▁▁▁▁
Journey pulse
Ready · Journey status is steady on current published details. · 0 blocked / 0 warning
Current caution
Current focus: Core Engine. 43 weekly snapshots are on record. What is the smallest cross-repo slice that makes the campaign OS indispensable and turns trust, adoption, and publication depth into a real launch advantage? No red blockers are open and published flagship readiness status is green.