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

feat: add adapter read-only MCP boundary

Browse source
This commit is contained in:
Andraxion 2026-07-22 05:59:20 -04:00
parent 1943c36ef3
commit f1e31487c0
17 changed files with 209 additions and 45 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-7 Worldforge read-only adoption
Goal: Use DocForge for routine Worldforge retrieval while the established builder and integration workflow remain authoritative.
In scope: A Worldforge project descriptor, separate Worldforge and AssetForge read-only sessions, real-task retrieval comparisons, context size and lookup measurements, omission and stale-state checks, and a documented rollback path.
Out of scope: AssetForge proposal adoption; canonical changeset application; replacing the Worldforge builder; deployment changes; arbitrary commands; Git mutation through MCP; accounts; HTTP transport; and a web UI.
Done when: Multiple real Worldforge tasks use project-bound DocForge retrieval without authority errors, phase drift, cross-family leakage, worse context quality, or loss of the current local-command rollback path.
Owners: Worldforge canonical sources and builders retain facts and output ownership. DocForge owns bounded read-only retrieval. Worldforge-specific profile and ordering policy remains in the Worldforge adapter.
Proof: DFG-6 loaded Awesome Ski Game through the generic path with five nodes, six edges, five unrelated families, and no project-specific core vocabulary. Indexing, search, filters, traversal, bounded context, isolated proposals, validation, and preview passed. Two simultaneous real MCP server processes remained bound to separate projects and could not cross-read nodes or mix indexes, changesets, previews, or output paths.
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.
```