---
schema_version: 1
id: RAC-KV5113Q1YCVK
type: roadmap
---
# RAC v0.19.0 — Roadmap "Achieved" Lifecycle Status

## Status

Planned

## Outcomes

Roadmap status reads truthfully across the whole knowledge lifecycle. A
delivered roadmap can be marked as realized rather than being stranded at
`Planned`, so a reader can tell current intent from delivered intent from
retired intent at a glance — without consulting Git or release notes to
discover that a "Planned" item actually shipped long ago.

The change stays inside RAC's remit (ADR-017): status remains a knowledge
lifecycle, not a work tracker. The new terminal state records that an intent
was realized; it does not introduce progress, assignment, or scheduling, and it
is authored by a human at release rather than driven by a merge.

## Initiatives

- **Add an `Achieved` terminal status to the roadmap `ArtifactSpec`** as a live
  (non-retired) state, so links to a delivered roadmap remain valid. The
  validation message and `rac schema roadmap` pick it up automatically.
- **Record the boundary as a decision** (ADR-061) that refines ADR-017: a
  terminal "realized" knowledge-lifecycle marker is in scope; work-progress
  tracking remains out.
- **Cover the behavior**: `Achieved` validates, and a live artifact referencing
  an achieved roadmap is not flagged as pointing at a retired target.

## Success Measures

- `rac schema roadmap` lists `Achieved` among the allowed status values.
- A roadmap with `## Status: Achieved` validates cleanly, and references to it
  pass `rac relationships --validate` with no retired-target finding.
- Existing `Planned` items are unaffected; the corpus gates stay green.

## Assumptions

- Marking an item `Achieved` is a manual editorial step at release time;
  RAC does not flip it automatically (ADR-017).
- The existing lifecycle/retired-status mechanism (ADR-051) is the right seam:
  `Achieved` is simply a permitted status that is absent from `retired_status`.

## Risks

- Treating `Achieved` as retired would silently break inbound links to
  delivered roadmaps; mitigated by keeping it out of `retired_status` and
  testing the reference path explicitly.
- Scope creep toward work tracking; mitigated by ADR-061's explicit boundary
  and by adding exactly one terminal knowledge state, nothing more.

## Related Decisions

- ADR-061
- ADR-017
- ADR-051
