- system-overview-design.md: repaired with P0/P1/P2 gaps resolved, all 24 frozen baselines listed, error taxonomy, global ~/.air, IPC, TaskSpec/WorkerResult, PromptLayer, PermissionEngine, RuntimeEvent, state machines, capability trust, artifact naming, operations - Four cross-verification audit reports (GPT-5, MIMO 2.5, Opus 4.7, DeepSeek V4 Pro) - Three regression reviews (R1: initial repair closure, R2: second pass with PromptLayer L9 wording found, R3: full PromptLayer alignment verified) - AGENTS.md, plan.md, todo.md synchronized Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
4.1 KiB
Executable File
4.1 KiB
Executable File
AGENTS.md
Workflow Root
- This project uses
AirPlan/as the workflow root. - Keep planning, execution state, ADR, C4, validation, debug, and plugin runtime data under
AirPlan/. - The repo-root
AGENTS.mdonly bootstraps into this file.
AirArc Workflow
- Use
AirPlan/AGENTS.mdas the canonical project context entry point. - Load and maintain:
AirPlan/docs/analysis/requirements.mdAirPlan/docs/architecture/solution-architecture.mdAirPlan/docs/architecture/system-overview-design.mdAirPlan/docs/architecture/gpt5概要设计审查.mdAirPlan/docs/architecture/mimo2.5概要设计审查.mdAirPlan/docs/architecture/Opus4.7概要设计审查.mdAirPlan/docs/architecture/DeepSeek概要设计审查.mdAirPlan/docs/architecture/概要设计修复回归审查.mdAirPlan/docs/architecture/概要设计修复回归审查-R2.mdAirPlan/docs/architecture/概要设计修复回归审查-R3.mdAirPlan/docs/architecture/baselineV1.mdAirPlan/docs/architecture/db-schema-v1.mdAirPlan/docs/architecture/event-registry-v1.mdAirPlan/docs/architecture/tool-registry-v1.mdAirPlan/docs/architecture/scheduler-state-machine-v1.mdAirPlan/docs/architecture/prompt-layering-v1.mdAirPlan/docs/architecture/provider-capability-matrix-v1.mdAirPlan/docs/architecture/error-taxonomy-v1.mdAirPlan/docs/architecture/artifact-naming-v1.mdAirPlan/docs/architecture/scope-escalation-v1.mdAirPlan/docs/architecture/security-model-v1.mdAirPlan/docs/architecture/capability-trust-v1.mdAirPlan/docs/architecture/cross-platform-matrix-v1.mdAirPlan/docs/architecture/branch-deepcode-cli/AirPlan/docs/architecture/c4/module.mdAirPlan/docs/architecture/c4/code-view.mdAirPlan/docs/architecture/interface-contracts-v1.mdAirPlan/docs/architecture/runtime-semantics-v1.mdAirPlan/docs/architecture/多模型三视角审查联合评估.mdAirPlan/docs/architecture/adr/AirPlan/docs/architecture/decisions-round-1.mdAirPlan/docs/architecture/decisions-round-2.mdAirPlan/docs/architecture/decisions-round-3.mdAirPlan/docs/architecture/main-agent-state-machine.md
- Produce or refine
AirPlan/plan.mdandAirPlan/todo.md. - Keep plans optimized for lower-cost follow-up sessions, including scope, validation, file targets, and parallelization boundaries.
- AirArc is architecture-only: it may plan tasks and edit planning or architecture documents, but it must not write code or implement tasks directly.
AirEng Workflow
- Use
/airengas the sole scheduler for confirmed execution. - Prefer
AirPlan/state/airarc/reviews/execution-plan.json, thenAirPlan/state/airarc/reviews/parallel-review.json, before falling back to localAirPlan/todo.md. - Dispatch isolated
/airdosubagents with bounded concurrency instead of defaulting to parent-thread coding. - Monitor active workers on a 5-minute cadence, merge ready results, and continue later waves automatically when work remains.
- Keep
AirPlan/todo.md,AirPlan/plan.md,AirPlan/AGENTS.md, ADR, and C4 docs synchronized during dispatch, monitoring, repair, and merge. - AirEng owns global debug, XDB, repair, intervention, and document convergence, but it should only intervene directly for hard blockers and must return to scheduler mode immediately afterward.
AirDo Workflow
- Use
/airdofor one narrow task slice fromAirPlan/todo.md. - Before editing, load:
AirPlan/AGENTS.mdAirPlan/docs/architecture/adr/AirPlan/docs/architecture/c4/module.mdAirPlan/plan.mdAirPlan/todo.md
- Keep task-local progress resumable in
AirPlan/state/airdo/. - When AirEng owns orchestration, return shared document changes through
documentUpdates. - Route GUI work through AirXDB, debugging through AirDbg, network evidence through AirNDB, and static analysis through AirSDB when needed.