softcopy-feature-map
Purpose
Create feature candidates and preserve softcopy/feature_map.yaml as the human-approved formal boundary file.
Triggers
- Scan results exist
- Formal function mapping is needed
Non-triggers
- Facts intake
- Simple provisional application drafting without reviewed feature boundaries
Required outputs
softcopy/outputs/feature_map/feature_map.candidate.yamlsoftcopy/outputs/feature_map/feature_map_report.md
Hard rules
- Each feature must map to code, application claims, and manual sections
- Do not overwrite an existing approved
softcopy/feature_map.yaml - Unapproved feature maps cannot support formal readiness
Workflow summary
- Convert scan candidates into feature proposals.
- Add cross-links to code, manual, and application layers.
- Mark the feature map pending review until human approval.