-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Cross Spec Consistency
-
None
-
Not Needed
Summary
Most specifications include a Status line in their header block, but its purpose and allowed values have never been formally defined. Current usage (per review discussion on PR #1992):
- Accepted: nearly all specs
- Draft: 1 spec (public suffix list)
- In Progress: 1 spec (odm-benchmarking)
- Obsolete: 1 spec (serverless testing)
We need to decide whether the Status line should be kept, redefined, or removed, and settle the related policy of which specs belong on master. CSOT, for example, is being removed per the CSOT decision doc while serverless-testing was just marked "Obsolete".
Current positions:
- Remove the status line entirely: if a spec is on master it is accepted by definition. This will require removal of non-accepted specs entirely or to alternative branches
- Keep a limited set of values: obsolete specs should be removed but there may be a use case for a single "In Progress" or "Draft" status for large specs that expand iteratively.
If we keep status line, it could be used as a meta tag to define a markdown file as a spec in DRIVERS-3692.
Motivation
Who is the affected end user?
Spec authors, reviewers, new engineers, external readers of the specifications repo, and LLM-based tooling that reads the repo (e.g. via AGENTS.md).
How does this affect the end user?
Readers can't tell what a Status value means or whether a non-Accepted spec should be implemented, and authors don't know which value to use or whether to include the line at all.
How likely is it that this problem or use case will occur?
Every new spec and every spec deprecation raises the question.
If the problem does occur, what are the consequences and how severe are they?
Inconsistent headers, possible confusion about whether obsolete or in-progress requirements should be implemented
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
No
Acceptance Criteria
A decision is recorded on whether specs keep a Status line, and if so, its allowed values and the meaning of each.
- is related to
-
DRIVERS-3692 Define how a document in the specifications repo is identified as a specification
-
- Backlog
-