AIWorkHub AGENTS.md

AIWorkHub MCP Agent Notes

This is the standalone canonical AIWorkHub repository.

Rules:

• Keep every repository's task and context source of truth in that repository's own .aiworkhub/ storage; never move task cards across repositories.
• Use the native AIWorkHub MCP surfaces rather than legacy AITools scripts or databases as model interfaces.
• Write operations must remain explicit and gated by AIWORKHUB_ALLOW_WRITES=1.
• Never run git add -A from this repository against the parent repository.

When printing worker auto-pickup or exact claim-start cards, use one self-contained fenced block per model. The instruction below must be the final non-empty line inside the same copyable block, never adjacent prose:

გაუშვი პარალელური სუბაგენტები და რომ დასრულდება დაუბრუნე კოდექსს რევიუსთვის

Target: AGENTS.md

AIWorkHub MCP tool-use policy

Order:

1. validate the injected AIWorkHub Task MCP receipt, identity and scope.
2. consume and acknowledge the injected project-context receipt.
3. manager uses aiworkhub_manager_source_graph_query; worker uses aiworkhub_worker_source_graph_query.
4. manager uses aiworkhub_manager_session_current_state; worker uses aiworkhub_worker_session_current_state.
5. manager uses aiworkhub_manager_ai_memory_search; worker uses aiworkhub_worker_ai_memory_search.
6. manager uses aiworkhub_manager_kb_search/get/related; worker uses aiworkhub_worker_kb_search/get/related.
7. manager uses aiworkhub_manager_context_graph_search, aiworkhub_manager_context_graph_range and aiworkhub_manager_context_graph_related when enabled; workers never access Context Graph.
8. execute exact card action and validation. Adaptive use:

• Role-specific AIWorkHub MCP tools are mandatory for managers and workers; legacy AITools scripts/databases are not model interfaces.
• Verified repo and repo_id outrank cwd, workspace_roots, environment_context and chat prose; on mismatch stop before filesystem access and switch/reload the route, never inspect the hinted repo as fallback.
• Task MCP receipt is always required; Source Graph is required for code tasks.
• Session Manager, AI Memory and KB run only when the card requests them or the task is non-trivial.
• Workers submit durable context changes only through the session/AI Memory/KB write-intent tools; a verified manager accepts or rejects each intent before canonical apply. Never write context databases directly.
• Do not make empty irrelevant calls to satisfy ceremony. Source Graph gate:
• When source_graph_required is true, stop if its bundle is unavailable, empty, stale or unacknowledged.
• Never use grep, rg, find, tree, broad cat/sed or recursive listing while Source Graph can index/process the target.
• A bounded exact-target fallback is allowed only after Source Graph reports that target unsupported or unindexed; record that reason.
• Re-query whenever the active symbol, dependency boundary, failure hypothesis, edit scope or validation target materially changes.
• Set workflow_stage on every Source Graph call: orientation, implementation, validation, review or rework; never relabel old calls after the fact.
• Start with focus/slice; escalate from returned evidence to context/calls/trace, impact, testmap/coverage and then a typed bundle only when needed.
• Use body for an exact symbol and bodygrep for indexed literal/body text; refresh once before any recorded bounded fallback.
• After Source Graph finds an exact target, prefer body/file preview; otherwise use a bounded read and never reread an unchanged range.
• For edits prefer aiworkhub_worker_semantic_edit_prepare/apply with the smallest verified range.
• Final HMAC-authenticated MCP audit ledger receipts distinguish injected, live, zero-hit and cache-hit calls plus modes and fallbacks; one preflight query is not continuous use. Exact-command exception:
• Exact validation/build/test commands named by the card are allowed.
• Exact known-path reads from the card or Source Graph are allowed; they are not broad discovery. Session Manager:
• Recover current state before non-trivial assumptions and preserve the returned session identity in the handoff.
• Never store secrets or fabricate session evidence. Manager Context Graph:
• Manager-only when enabled: search for non-trivial continuation, compaction/handoff recovery or prior-conversation facts; use range/related only from returned evidence.
• Workers never query or write Context Graph; durable context uses Session/AI Memory/KB write intents.
• Disabled or zero-hit is not failure; no empty ceremonial calls. AI Memory:
• After session recovery, issue one bounded task-specific query.
• Reuse returned durable decisions/lessons.
• Do not query legacy memory files directly. KB:
• Query authoritative project contracts/docs for unresolved factual context and preserve source identity.
• After a zero hit, do not repeat the query unless task scope changes. Stop at Codex review.