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

Document Release 1 adapter compatibility

Browse source
This commit is contained in:
Andraxion 2026-07-25 19:21:23 -04:00
parent 696b62f9f8
commit 4a8980110d
4 changed files with 38 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/CONTRACT.md
View file

@ -1,4 +1,4 @@
# DocForge 1.1 development contract
# DocForge post-1.0 development contract
## Authority boundary
@ -19,7 +19,7 @@ commit when Git is available; it cannot change repository state.
- Result envelope: `schemas/result.schema.json`, version 1.
- Changeset schema: `schemas/changeset.schema.json`, version 1.
- Index schema: version 1, disposable and reproducible.
- Core, CLI, and MCP server: version 1.1.0.dev0 on `Dev-Rewrite`.
- Core, CLI, and MCP server: version 1.1.0.dev0.
- Incremental extraction cache: version 1, disposable and reproducible.
Schema files describe the generic interchange contract. Runtime validation remains responsible for
@ -214,6 +214,11 @@ Cached and refreshed facts are always assembled into a complete projection and p
validation before publication. The full projection loader remains the fallback and equivalence
oracle.
The Release 1 `AdapterLoader` contract remains valid. A loader that supplies only
`load_projection()` stays on the complete-projection path. Incremental capability detection is
additive and cannot make the new methods mandatory for an existing adapter. An incremental loader
must also implement `load_projection()` so a clean rebuild and equivalence check remain possible.
Logic projections are not primary graph nodes. They remain source-scoped, function-owned,
independently cached control-flow data so ordinary search, Nodes, Flow, and Web do not become
statement graphs.