Chummer
Open ChummerRequest early access

Program telemetry

Current customer state lives on Current release.

This page is the weighted program report for people who want the deeper delivery read, not the main customer-facing status surface.

Open current release
Chummer6

Progress report for a product becoming a build machine.

The project is moving from canon and architecture into a more coherent public product: clearer entry surfaces, hardened rules, stronger shared UI, and a more credible path toward release.

See the program pulseRead the timelineHow the ETA works
Overall progress 100% Weighted milestone completion across the 5 public product parts.
Current phase Public-fit polish The architecture is real; the focus is on making it boring, fast, and public-ready.
Next checkpoint The fastest-moving areas are the ones closest to milestone closure.
Longest pole Core Engine Hosted account, registry, and media surfaces still carry the deepest remaining completion wave.
Public route truth

Every public route card carries an explicit proof state.

Support, feedback, and governance are separate lanes. Package/install claims stay tied to current release, journey, and rollback evidence instead of collapsing into one generic trust message.

/downloads

Downloads and install truth

Implemented
supportable_install

Package compatibility, install, update, rollback, and revoke claims are published from the current release shelf instead of helper folklore.

2 compatible installer tuple(s) are published. Rollout state is promoted_preview, support posture is preview_supported, and rollback stays watch.
Compatibility: 2/2 installer tuplesRollback: watchRevoke: not_revoked
  • Release channel: published
  • Release proof: passed
  • Install journey: blocked
  • Fix availability: Only send fixed notices after the affected install can receive the published channel artifact now on the shelf.
/home/work

Desktop workbench

Implemented
desktop_flagship

The public route only claims the flagship workbench when executable proof and veteran-familiar desktop signals agree.

Desktop executable exit gate is not fully proven.
  • Flagship readiness: warning
  • Desktop executable gate: fail
  • Workbench route proof: present
/account/access

Account, restore, and device continuity

Implemented
restore_and_portability

Account value is framed as claim, restore, second-device continuation, and support continuity, not as a browser ritual.

A person can install the flagship client, claim it, restore the right workspace, and continue safely on a known install.
  • Journey state: blocked
  • Account route proof: present
  • Journey recommendation: Resolve the blocking artifact or posture gap before widening promotion or trust claims.
/account/support

Support and recovery

Public stable
support

Support is a closure lane tied to install and release receipts. It is not the same thing as votes, proposals, or roadmap wishes.

0 open packet(s); 0 waiting on release truth.
  • Support packets artifact: present
  • Open packets: 0
  • Waiting on release truth: 0
/feedback

Feedback and discovery

Public stable
feedback

Feedback is an advisory intake lane. It informs governed discovery work, but it never masquerades as support closure or shipped rollout authority.

Public or design-impact feedback is routed through the Karma Forge discovery loop shape: ProductLift/FacePop signal, Deftform pre-screen, Icanpreneur interview, MetaSurvey validation, Teable/NextStep review, Product Governor decision, and ProductLift/Emailit/Signitic closeout.
  • Workflow ready: yes
  • Discovery system ready: yes
  • Candidate count: 0
/roadmap

Governance and rollout posture

Preview bounded
governance

Governance cards describe launch, canary, rollback, and claim-safety posture. They do not imply immediate rollout just because a proposal exists.

Resolve the blocking golden-journey gaps before widening publish claims.
  • Completion audit: fail
  • Launch expand: blocked
  • Freeze launch: active
  • Canary: accumulating
  • Rollback: watch
  • Journey summary: blocked
Public view

Where the program stands right now.

These are the product parts a normal reader can understand without caring how the repos are split. Each line shows weighted progress, recent momentum, and a near-term ETA based on the current milestone map and the recent delivery pace.

Core Rules Engine

Deterministic mechanics, reducer truth, and compatibility-safe runtime hardening.

Stale momentum
ETA
100% weighted milestone progress

Workbench & Shared UI

Character building, inspectors, dense data UX, and the reusable Chummer design system.

Stale momentum
ETA
100% weighted milestone progress

Live Play

Player and GM shell, local-first sync, browser session transport, and offline-resume play surfaces.

Stale momentum
ETA
100% weighted milestone progress

Community Cloud & Publishing

Accounts, groups, sponsorship, public entry, publishing, registry, and media execution services.

Stale momentum
ETA
100% weighted milestone progress

Canon & Public Guide

Product canon, horizons, participation workflow, public landing rules, and the public-facing guide bundle.

Stale momentum
ETA
100% weighted milestone progress
Timeline by product area

Major milestones, from what just landed to what comes next.

This is the public-facing version of the roadmap: one timeline per product part, focused on what changed, what is actively being closed, and what a complete checkpoint should look like.

Core Rules Engine

ETA
Landed

Hardening wave. Legacy purification, retention controls, observability slices, and stronger verifier guardrails moved forward.

Now

F1 closure. Finish observability, disaster recovery, and replay-safety proof.

Target

Auditable boring runtime. A boring, auditable core runtime with no hidden legacy cargo.

Workbench & Shared UI

ETA
Landed

Scope clarified. Remaining work was sliced into concrete queues for relationship graph, heat/favor, calendar, inspector, hub UX, portrait, and NPC persona.

Now

Workbench complete. Close workbench-complete and quality-hardening waves; centralize reusable UI primitives.

Target

Polished workbench. Complete desktop/browser workbench with accessibility, localization, and polished shared components.

Live Play

ETA
Landed

Play-shell hardening. Play-shell hardening and browser transport/offline resume work was republished as runnable backlog.

Now

E1 closure. Drive the final Play complete milestone across live-session depth and installable hardening.

Target

Reliable session shell. A reliable session shell that survives weak networks and resumes cleanly.

Community Cloud & Publishing

ETA
Landed

Public entry wave. Public landing shell, email auth delivery, sponsor tiers/account linking, and canon refreshes across registry/media moved forward.

Now

Completion wave. Finish adapter waves, hub-complete surfaces, docs/operator projection, assistant plane, and media-plane completion.

Target

Public participation stack. A cohesive hosted community and publication stack ready for real public participation.

Canon & Public Guide

ETA
Landed

Canon tightened. Public landing/auth/download canon, participation workflow, sponsorship backlog, and release-governance wave were tightened.

Now

Validator convergence. Finish release-completion proof and stronger validator-backed convergence across downstream consumers.

Target

One public story. One authoritative public story, compiled cleanly into every downstream surface.

Recent movement

What changed in the latest delivery burst.

Delivery reporting got clearer.

The public progress report, product-part grouping, and timeline view now read like one coherent status surface instead of scattered repo signals.

Public-facing product structure tightened.

Public milestones, guide surfaces, and landing routes now line up more cleanly around user-visible product areas instead of internal execution seams.

The public entry story became clearer.

Landing, auth, guide, and participation surfaces were tightened so the public front door stays closer to the actual product truth.

Workbench scope got easier to see.

The remaining desktop/browser UX work has been sliced into concrete milestone- and backlog-shaped queues instead of sitting as fuzzy later work.

Core is moving from split-state cleanup toward hardening.

The current core wave is no longer about who owns what; it is about observability, disaster recovery, replay safety, retention, and finishing the last legacy purification passes.

Cloud and publishing are now the clearest long pole.

The hosted stack is visibly moving, especially around public entry and email identity, but it still carries the largest remaining completion wave because registry depth, media execution, adapters, and broader hub product surfaces remain open.

Method

How the progress and ETA are calculated.

Progress is a weighted estimate built from the current milestone map, grouped into public-facing product parts instead of repo names. The ETA is a momentum-based planning band, not a promise: it uses remaining milestone weight, recent repo activity, and uncovered scope breadth as a public proxy until weekly historical snapshots are published. ETA is a momentum-based planning band, not a delivery promise. Weekly public progress history is now available; ETA uses recorded velocity where enough snapshots exist and falls back to the short-horizon momentum proxy elsewhere. Mapped public milestones are complete, but the full-product frontier remains open with 3 milestone(s). Full completion requires full frontier closure. The current supervisor ETA is tactical or otherwise not yet calendar-grade enough for a full-product parity forecast, so the public surface tracks the remaining frontier without publishing a parity date band.

Participation

How to participate

If you want to follow the rollout or join future contribution waves, the participation page explains the current public entry path. Open the participation page

What this means

The project no longer looks like a concept sketch.

The most interesting change is not a single feature. It is that architecture, execution, public entry, and product canon are starting to reinforce each other. That is the point where a serious internal system turns into something people can eventually use, trust, and follow.

Status snapshot: July 03, 2026.