Goal: Let OpenClaw propose AssetForge documentation changes through an isolated, reviewable DocForge workflow.
In scope: AssetForge-family read, propose, validate, diff, and preview operations; a separate changeset area; explicit review; canonical Worldforge rebuild and verification; and conflict or workflow-failure evidence.
Out of scope: Non-AssetForge proposals; automatic canonical application; automatic commit, push, deployment, or publication; replacing the Worldforge builder; arbitrary commands; accounts; HTTP transport; and a web UI.
Done when: AssetForge updates complete through the proposal workflow without generated-file edits, lost concurrent work, cross-family mutation, or unauthorized publication.
Owners: AssetForge canonical sources remain owned by Worldforge and its established builder. DocForge owns isolated proposals and validation. Codex or a developer owns review and integration. OpenClaw receives only the declared AssetForge proposal boundary.
Proof: DFG-7 exposed exact read-only surfaces for separate Worldforge and AssetForge sessions. Eight real retrieval tasks retained all required results. Bounded context reported omissions, concurrent servers rejected cross-family reads, stale Worldforge state failed closed without affecting AssetForge, and the established manual index remained a complete rollback path.
