WORK-495
ID:WORK-495Status:draft

Add spec implemented/shipped and ADR rejected statuses

Close the "is it built / is it available?" gap on specs, and give ADRs an honest "considered and declined" state. Rides on the consolidated vocabulary from WORK-492.

Priority:highComplexity:moderateMilestone:v0.28.0Source:SPEC-049

Criteria completion

Criteria completion: 0 of 7 (0%) checked; tracking started on Jul 9, no incremental history yet0%25%50%75%100%Jul 9Jul 11

Tracking started Jul 9 — check back for trends.

Branches 2
History 2
  1. 283ce5a
    Created (draft)by bjornolofandersson
  2. 9a519fd
    Content editedby Claude
    plan: add v0.28.0 plan-model-hardening milestone and work breakdown

Acceptance Criteria

  • spec rune accepts implemented and shipped status values (schema, enums.ts, MCP)
  • spec rune accepts an optional released-in attribute (semver format, e.g. v0.11.4)
  • decision rune accepts a rejected status value (in addition to proposed | accepted | superseded | deprecated)
  • config.ts status sentimentMaps render implemented / shipped (positive) and rejected (negative/muted) appropriately; render-pipeline orderings place them correctly
  • plan validate errors on a status="shipped" spec that lacks released-in
  • implemented / shipped are registered in TERMINAL_STATUSES.spec and ACHIEVING_STATUSES.spec; rejected is terminal for decision
  • Tests cover schema acceptance, the shipped-without-released-in error, and badge sentiment

Dependencies

  • WORK-492 — adds values to the consolidated enums.ts shape

References

  • SPEC-049 — spec (New spec statuses, New ADR status)