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

Complete DFG-8 adapter proposal support

Browse source
This commit is contained in:
Andraxion 2026-07-22 11:50:49 -04:00
parent f1e31487c0
commit 591bf0ae7d
14 changed files with 525 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

14
ACTIVE_SLICE.md
View file

@ -1,11 +1,11 @@
# Active slice
```text
Slice: DFG-8 AssetForge proposal adoption
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.
Slice: DFG-9 controlled application decision
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.
```