administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

Complete DFG-9 application decision

Browse source
This commit is contained in:
Andraxion 2026-07-22 12:06:04 -04:00
parent 591bf0ae7d
commit 6b5c3a939a
6 changed files with 119 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

15
README.md
View file

@ -8,14 +8,15 @@ DocForge does not own project facts. It does not select project work, apply prop
commands, or perform Git and deployment operations. It may write only configured derived output and
isolated previews through the explicit render boundary.
## Current gate
## Current state
DFG-1 through DFG-8 are complete. Worldforge uses separate read-only sessions and an optional
AssetForge-only proposal process. OpenClaw can update existing AssetForge chapter prose through
isolated, validated changesets and escaped previews; canonical integration remains a developer
review step through Worldforge's established builder. DFG-9 is the active gate: decide from recorded
evidence whether any developer-only application command is justified. Canonical application remains
external and closed to MCP.
DFG-0 through DFG-9 are complete. Worldforge uses separate read-only sessions and an optional
AssetForge-only proposal process. OpenClaw can propose updates to existing AssetForge chapter prose
through isolated, validated changesets and escaped previews. Canonical integration remains a
developer review step through Worldforge's established builder. DFG-9 found no measured need for an
application command, so manual canonical integration is the permanent DocForge 0.x policy.
Canonical application remains external and closed to the library, CLI, and MCP server. See
[`docs/APPLICATION_DECISION.md`](docs/APPLICATION_DECISION.md).
## Development