ARCH: заложить контракт MCP semantic discovery
This commit is contained in:
+23
@@ -659,6 +659,29 @@ Contract-layer result:
|
||||
|
||||
This closes the misleading `capability_contract_missing` / `transition_contract_not_resolved` debug gap for the core phase18 path without changing the user-facing answer semantics.
|
||||
|
||||
## Progress Update - 2026-04-20 MCP Discovery Contract Seed
|
||||
|
||||
The first implementation slice of Big Block 5 added a non-runtime-disruptive contract owner for guarded MCP semantic discovery:
|
||||
|
||||
- `assistantMcpDiscoveryPolicy.ts`
|
||||
- `assistantMcpDiscoveryPolicy.test.ts`
|
||||
|
||||
This seed does not yet route live user traffic into discovery.
|
||||
|
||||
It establishes the safety contract that future runtime wiring must obey:
|
||||
|
||||
- Qwen3 may propose business-level MCP exploration primitives;
|
||||
- unregistered primitives are rejected by runtime policy;
|
||||
- raw model claims are never answer-authoritative;
|
||||
- every discovery answer must pass an evidence gate;
|
||||
- evidence must separate confirmed facts, inferred facts, and unknown facts;
|
||||
- probe execution cannot bypass the runtime-approved primitive plan.
|
||||
|
||||
Validation:
|
||||
|
||||
- `npm test -- assistantMcpDiscoveryPolicy.test.ts` passed 6/6;
|
||||
- `npm run build` passed.
|
||||
|
||||
## Execution Rule
|
||||
|
||||
Do not implement this plan as:
|
||||
|
||||
Reference in New Issue
Block a user