Establish Milestone 0 compatibility and quality gates
This commit is contained in:
parent
15a913003c
commit
8ebb78a71d
15 changed files with 1114 additions and 27 deletions
|
|
@ -189,10 +189,13 @@ extraction. Under this binding:
|
|||
|
||||
- `docforge_get_logic` returns `adapter_policy_forbids_logic`;
|
||||
- a nonempty Logic projection is rejected before index publication;
|
||||
- a pre-existing index containing Logic is rejected before any read or live-viewer snapshot;
|
||||
- hash-bound canonical application refresh uses the same policy-bound index;
|
||||
- `adapter_ast_upgrade` and `function_logic_extraction` appear as excluded operations; and
|
||||
- changing the policy requires changing the process configuration and starting a new MCP process.
|
||||
|
||||
The policy governs the DocForge binding and conforming MCP clients. DocForge still exposes no
|
||||
filesystem sandbox and cannot prevent an unrelated process with direct repository write access
|
||||
from editing adapter files. Repository permissions and project instructions remain responsible for
|
||||
that broader boundary.
|
||||
The policy governs the DocForge binding and conforming MCP clients. DocForge can enforce published
|
||||
and indexed Logic, but it does not inspect arbitrary adapter source to prove which parser
|
||||
implementation the adapter uses. DocForge still exposes no filesystem sandbox and cannot prevent
|
||||
an unrelated process with direct repository write access from editing adapter files. Repository
|
||||
permissions and project instructions remain responsible for that broader boundary.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue