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

13
README.md
View file

@ -10,11 +10,11 @@ isolated previews through the explicit render boundary.
## Current gate
DFG-1 through DFG-6 are complete. Awesome Ski Game proves that the generic core can index, retrieve,
compile context, accept isolated proposals, and render previews for unrelated project families. Two
simultaneous MCP server processes remain project-bound and cannot cross-read or mix derived state.
DFG-7 is the active gate: adopt DocForge for read-only Worldforge retrieval while retaining the
existing builder and rollback path. Canonical application remains external and closed to MCP.
DFG-1 through DFG-7 are complete. Worldforge now uses two explicit read-only sessions for its main
documentation and AssetForge documentation. Real-task retrieval, bounded context, cross-session
isolation, stale-state rejection, and rollback to the existing manual index are measured. DFG-8 is
the active gate: allow AssetForge-only proposals through a separate reviewed changeset workflow.
Canonical application remains external and closed to MCP.
## Development
@ -44,4 +44,5 @@ Project adapters implement `AdapterLoader` and return one ordered, immutable `Ad
`AdapterProject` validates the projection and exposes it through the same disposable index used by
generic projects. Project-specific context, query ordering, and render-model policy remain in the
adapter. Shadow adapters are local integration tools; the normal MCP server does not discover or
execute them.
execute them. An explicit integration may bind a validated adapter project to DocForge's read-only
MCP surface without enabling proposal tools.