openspec-change-visualizer

IN BUILD

"I want to build a lightweight structure or format that visualizes how any single change moved through openspec gates. so an openspec visualizer that looks at one change at a time. Mostly this is because I hear time and time again that despite all our tooling, most of us still ask the question 'what's going on?' 'what are we working on?' and thats surprisingly hard to answer still. I want to start with a change as the unit of currency." "apply is a long process, no matter what ai influencers say. You're unblocking, rethinking, hunting down api keys, etc."

STAGES

  1. proposal08-29 ↻ 08-29
  2. requirements08-29
  3. design08-29
  4. tasks08-29
  5. build—
  6. archived—

CAPABILITIES — 2 IN ONE CHANGE

  • change-claim-verification2 requirements
  • change-page5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1An active change openscode path
  • ✓1.2An archived change openscode path
  • ○1.3A barely-started change still openscode path
  • ✓1.4The current stage is markedcode path
  • ✓1.5A gate that was revisited is marked as revisitedcode path
  • ✓1.6A gate older than its rule is not counted against the changecode path
  • ✓1.7Each outcome carries its evidence kinddeferred
  • ✓1.8Outcomes that cannot be mapped say socode path
  • ✓1.9Each capability is listed with its requirementscode path
  • ✓1.10Every event names its stagecode path
  • ✓1.11A quiet stretch is shown with its lengthcode path
  • ✓1.12Two gates in one commit are named togethercode path
  • ○1.13A committed image is showncode path
  • ○1.14A recorded Figma frame is fetchedcode path
  • ○1.15No artifact means no empty framecode path
  • ✓1.16Work that shipped but is still uncheckedcode path
  • ✓1.17A task still waiting on a pull request that mergedcode path
  • ✓1.18Sources that agree produce nothingcode path
  • ✓1.19Both readings are statedcode path
  • ✓1.20Nothing is written backautomated test

WHAT HAPPENED

  1. ↺ BACK TO PROPOSAL

    proposal and specs and design and tasks landed

    2026-08-29 · 2 pull requests
    • #409docs(openspec-change-visualizer): define the experiment + discovery frames
    • #411feat(change-visualizer): index at /changes, and the hub shell

History read from a manifest built at 2026-09-30 (09e7bcc).

2 pull requests, found by commits touching the change folder