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

test: prove unrelated project isolation

Browse source
This commit is contained in:
Andraxion 2026-07-22 05:01:07 -04:00
parent 1c4aa79d1c
commit 1943c36ef3
12 changed files with 492 additions and 12 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-6 unrelated-project proof
Goal: Prove that DocForge's core works for a project with different families and no Worldforge phase assumptions.
In scope: An Awesome Ski Game fixture, generic loading and indexing, search, bounded context, changesets, preview rendering, two simultaneous project-bound servers, and cross-project isolation checks.
Out of scope: Worldforge read-only adoption; AssetForge proposal adoption; canonical changeset application; live workflow replacement; deployment; arbitrary commands; Git mutation; accounts; HTTP transport; and a web UI.
Done when: The second project works without the Worldforge adapter or vocabulary, all generic operations pass, and neither server can access the other project's sources, indexes, changesets, previews, or outputs.
Owners: DocForge core owns generic mechanics and isolation. Fixtures own their project-specific vocabularies. Worldforge-specific semantics remain in the Worldforge adapter.
Proof: DFG-5 mapped and validated all 532 Worldforge nodes and 830 edges, matched exact lookup, weighted search, filters, backlinks, dependencies, four deterministic bounded contexts, and all 32 generated outputs. The full AssetForge profile includes all ten nodes, reduced budgets record omissions, invalid budgets fail, and the proof writes no canonical or public files.
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.
```