__TITLE__
__LEDE__
At a glance
Open questions & decisions needed
Nothing here is signed off until these are answered. Every open item is listed in the Open questions view and traced back to its source document.
Functionality coverage — no silent loss
Every legacy capability is either built and tested, still outstanding, or explicitly deferred with a recorded justification. Nothing is dropped by accident. See the Functionality coverage view for the full breakdown.
Deliberately not built (deferred)
Capabilities consciously deferred, each recorded in the descope register with a rationale so none can be lost by accident.
How to read this pack
Documents are labelled by how they were produced:
- Machine-extracted generated directly from the source code and regenerable — this is what the code actually does.
- Derived analysis synthesised from the code and stakeholder material — good, but interpretive.
- Provisional depends on an open question or a source that could not be read.
This pack is fully self-contained: it opens in any browser with no internet and no server, and it is the only file you need to send to a reviewer.
Open questions
Every unresolved decision, ambiguity or gap in the pack, with the document it came from. Answering these is what turns this pack into a reliable baseline.
| ID | Decision or confirmation needed | Assumption / context | ⚠ | Source |
|---|
No open questions were found in the pack.
Functionality coverage
The evidence that no functionality is lost. Every feature, user story and acceptance criterion is tracked to a status; anything not built is either outstanding or explicitly deferred.
Features
| Feature | Title | Priority | Stories | Criteria | Status |
|---|
Deferred functionality (descope register)
| Requirement ID(s) | Feature / Story | Rationale | Owner |
|---|
Feature index
The buildable features, in dependency order. Each carries its own user stories, acceptance criteria and test mappings.