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

10
ACTIVE_SLICE.md
View file

@ -1,11 +1,17 @@
# Active slice
All planned DocForge gates, DFG-0 through DFG-9, are complete. No implementation gate is active.
```text
Slice: DFG-9 controlled application decision
Slice: DFG-9 controlled application decision (complete)
Goal: Decide from DFG-7 and DFG-8 evidence whether a developer-only canonical changeset application command is justified.
In scope: Review read-only and proposal workflow evidence; define the exact human authorization boundary; evaluate repeated integration work; require clean base hashes and repeat validation; and either specify one narrow application command or record manual integration as permanent policy.
Out of scope: OpenClaw canonical application; automatic commit, push, deployment, or publication; arbitrary commands; accounts; HTTP transport; a web UI; and implementation before the evidence review supports it.
Done when: The project records either a proven narrow developer-only application contract or a reasoned decision to keep proposals manually integrated.
Owners: DocForge owns proposal evidence and generic safety constraints. Each project owns canonical source semantics and integration policy. A developer retains authorization, review, build, Git, and publication ownership.
Proof: DFG-8 bound OpenClaw to content-only updates for existing AssetForge chapters. A real changeset validated, diffed, previewed, and was manually integrated through the Worldforge builder. Create, move, delete, metadata, relationship, root-manifest, and cross-family changes were denied. Conflict, stale-source, raw-HTML escaping, canonical preservation, and post-integration base-conflict proofs passed.
Decision: Manual canonical integration is the permanent DocForge 0.x policy. No application command was added.
Proof: DFG-8 required one reviewed content replacement after DocForge had already validated, diffed, and previewed the proposal. It completed without failure or material repeated work. An application command would add canonical writers, authorization, rollback, and project-format ownership without measured need. Existing protocol and proposal tests prove that MCP and proposal workflows cannot alter canonical sources.
```
**Next gate:** None planned. Monitor real adoption. Reopening canonical application requires a new
approved gate and measured evidence under `docs/APPLICATION_DECISION.md`.