feat(agent): make ingestion preparation reproducible
This commit is contained in:
1 parent
3b1b40f8b3
commit
65bc8a9422
9 files changed
+185
-40
No files matched your search
@@ -23,7 +23,9 @@ Choose a focused skill; load only its applicable protocol and pipeline files:
|
||||
|
||||
## Availability and reporting
|
||||
|
||||
Check the installed manifest and confirm required MCP tool names against `contracts/service-v1.json`; use the schema advertised for each discovered tool and inspect only a relevant pinned entry when necessary. Do not read every record schema during routine work. Use the host's native file listing and viewing tools for workspace inventory and pack instructions; do not invoke shell commands just to list files. This pack is bound to the local GEWU v1 contract, but native host workflows are NOT RUN. Do not invent commands or assume another host's custom tools exist. If required tools are unavailable or differ from the pinned contract, stop before mutation and identify the blocked stage; prepare local drafts only when requested and label them unaccepted.
|
||||
For a connected workflow, use MCP discovery and `diagnostics` to confirm the available tools, their advertised input schemas, role, capabilities and scope. Those discovered schemas are authoritative for this session. Routine ingestion does not require reading `manifest.json`, `service-v1.json`, record schemas, README sections or helper-script source to rediscover tools. If a required tool is absent or an advertised schema produces a concrete mismatch, stop before mutation; inspect only the relevant pinned contract entry to diagnose that mismatch, then report it if unresolved. Use the host's native file listing and viewing tools for workspace inventory and pack instructions; do not invoke shell commands just to list files. This pack is bound to the local GEWU v1 contract, but native host workflows are NOT RUN. Do not invent commands or assume another host's custom tools exist. If required tools are unavailable, identify the blocked stage; prepare local drafts only when requested and label them unaccepted.
|
||||
|
||||
For Antigravity, call MCP tools using the schemas attached to discovered tools. Do not read generated per-tool JSON files from the CLI's local MCP cache; they duplicate those schemas. Open one only after a concrete argument validation error. Do not inspect installer state or helper-script implementation during routine ingestion.
|
||||
|
||||
Knowledge changes go through typed MCP proposals. Local artifacts under `Drafts/` and `Runs/` support work but are not accepted knowledge. Only a service acceptance receipt establishes acceptance. Keep credentials and source bodies out of status summaries; do not claim a cloud-backed host keeps all content local.
|
||||
|
||||
|
||||
Reference in new issue
Block a user