Account JACKPOINT workspace
Sign in to open the JACKPOINT publication workspace where review, publication status, and campaign-return history stay on Chummer paths.
Open detailsBriefings
JACKPOINT
JACKPOINT keeps dossiers and mission briefs readable in public, while publication review and campaign return history stay on account pages.
Dossier cards
Mission briefs
Account publication workspace
Limits
Files, with the limits clearly stated.
Dossier and mission-brief output only. GM spoilers, draft publication notes, and private campaign return state stay signed in.
Connected page
JACKPOINT briefing
Public dossiers and briefings are readable without an account, but publication review and campaign-return history stay signed in.
Public briefing guide
2 briefing(s) are already readable without opening the signed-in publication path.
Open detailsBriefing details
Read the account and publication paths before treating JACKPOINT like a generic export page.
Open detailsNarration, export, or promotion helpers may assist packaging, but Chummer owns publication status, source, and spoiler boundaries.
Files
Open the files when you need detail.
Each card opens to the readable notes.
Emerald Sprawl briefing
Player-safe mission brief with objective status, pressure line, and source-safe dossier framing.
Style: Dossier
Objective pressure
Contact status
No GM-private spoilers
Dockyard contact dossier
Short dossier card for a contact path with limited trust notes and follow-up hooks.
Style: Dossier
Dossier card
Player-safe contact notes
Follow-up hook
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.