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

16
docs/INCREMENTAL_INDEXING.md
View file

@ -1,9 +1,23 @@
# Incremental Adapter Indexing
DocForge Release 1 adapters return one complete immutable projection. That contract remains
supported. The `Dev-Rewrite` compiler adds an opt-in source-scoped contract that avoids reparsing
supported. The incremental compiler adds an opt-in source-scoped contract that avoids reparsing
unchanged files while preserving the same validated, atomically published graph.
## Release 1 compatibility
The incremental interface is additive:
- An existing adapter implementing only `load_projection()` continues to work unchanged.
- Existing generic projects, descriptors, canonical sources, changesets, and indexes require no
migration.
- Only adapters implementing both `load_manifest()` and `extract_source()` use the incremental
path.
- Incremental adapters must still implement `load_projection()` for clean rebuilds and equivalence
testing.
- Existing adapters receive identical correctness behavior but no incremental speedup until they
opt in.
## Safety model
Incremental indexing is an extraction optimization. It does not weaken publication: