change-history-manifest

IN BUILD

"I want to build a lightweight structure or format that visualizes how any single change moved through openspec gates. … 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."

STAGES

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

CAPABILITY

  • change-history-source5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1Stage dates render without gitcode path
  • ✓1.2Pull requests render without gitcode path
  • ✓1.3Silences render without gitcode path
  • ✓1.4Findings render without gitcode path
  • ✓1.5A shallow clone refuses to generatecode path
  • ✓1.6Every change is coveredcode path
  • ✓1.7A newer local commit appearscode path
  • ✓1.8The manifest is used when git is absentcode path
  • ✓1.9The source is namedcode path
  • ✓1.10Genuinely empty is distinct from unavailablecode path
  • ✓1.11Regeneration is deterministiccode path
  • ✓1.12Generation writes nothing backcode path

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-08-29 · 1 pull request
    • #412docs(openspec): propose change-history-manifest

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

1 pull request, found by commits touching the change folder