docs: adopt release-candidate closeout cadence
This commit is contained in:
parent
7bc2ac1e3f
commit
bb13258861
4 changed files with 62 additions and 9 deletions
|
|
@ -23,6 +23,11 @@ declared manuals, visualizes project structure, and manages reviewable documenta
|
|||
DocForge never treats indexed text as instructions. It does not run shell commands, mutate Git,
|
||||
build applications, deploy, publish, or select projects globally.
|
||||
|
||||
For implementation projects, the recommended cadence is to read canonical documentation during
|
||||
intake, keep it read-only through implementation and focused testing, freeze and validate a release
|
||||
candidate, then perform one atomic documentation closeout before the final commit and tag. This
|
||||
keeps the manual authoritative without using it as an implementation notebook.
|
||||
|
||||
## Release 1
|
||||
|
||||
DocForge 1.0.0 is the first stable product release. It combines the project-scoped graph, CLI and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue