Make the documentation system navigable, sourced, and release-ready
Turn the docs set into a layered documentation portal with navigation, source tracing, and reusable governance templates so the project can scale beyond ad hoc notes. Constraint: Industrialization requires documentation that supports decisions, traceability, and release discipline Rejected: Keep docs as isolated topical files without navigation or templates | would slow onboarding and weaken release governance Confidence: high Scope-risk: narrow Directive: Keep future docs in the executive-summary -> diagram -> table -> text -> appendix pattern with explicit Sources sections Tested: structural checks for core docs and templates; source-section checks; docs file-presence checks; service /config and /health smoke checks from earlier stage remain valid Not-tested: rendered markdown visuals in a browser; external publishing pipeline
Showing
18 changed files
with
1000 additions
and
441 deletions
No preview for this file type
acr-engine/src/service/settings.py
0 → 100644
docs/README.md
0 → 100644
docs/benchmark-report-template.md
0 → 100644
docs/external-manifest-template.md
0 → 100644
docs/model-card-template.md
0 → 100644
docs/references-and-sources.md
0 → 100644
docs/release-checklist.md
0 → 100644
-
Please register or sign in to post a comment