corp-v1-3darch/corp-v1-3darch-documentation
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: publish legacy feature catalogue
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-03 08:14:14 +00:00
parent 94ffd5d4cf
commit 3a2e19fc52
139 changed files with 8681 additions and 203 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scope/overview.md
+4 -3
View File
@@ -8,13 +8,14 @@ import ScopeIssueMatrix from '@site/src/components/ScopeIssueMatrix';
# Find governed product scope
The matrix is the complete operational index for the current governed catalogue. It includes all ten approved Epics; no Ideas, Questions, Features, or Tasks have been defined yet.
The matrix is the complete operational index for the current governed catalogue. It includes all ten Epics and their 32 required child Features. No Ideas, Questions, or implementation Tasks have been defined yet.
<ScopeIssueMatrix />
## How to read the baseline
- `IN_BACKLOG` records the accepted catalogue boundary, not implementation readiness or delivery progress.
- `EXACT` means the initial state is directly supported by the human decision evidence linked in each row.
- `EXACT` marks each Feature's directly evidenced `IN_BACKLOG` registration; `DERIVED` marks each Epic's roll-up from its required Features.
- **Approved for documentation** records acceptance of the catalogue entry; it is separate from delivery status and does not grant solution or implementation approval.
- **Not approved for Solution** means Architecture must not begin Feature solution work from this catalogue alone.
- Empty child and dependency sets are explicit current facts; they are not inferred completeness claims.
- Empty Task and release-evidence sets are explicit current facts; they are not inferred completeness claims.