hearting-codex

Use when the user asks to analyze existing code, a paper, or a document and no usable persistent analysis exists, or to refresh stale analysis; default initial analysis to persistent output. Not for conversational, read-only, or no-file analysis; orientation, context recovery, status, experiments, external research, source changes, or completed-work audits.

Use when durable cross-project user preferences must be inferred from coding, writing, or analysis evidence and stored as a profile. Not for one-project context recovery, casual preference acknowledgment, or ordinary task execution.

Use when an agent or operator needs to browse or query an existing Cairn artifact projection without changing artifacts or runtime state. Not for primary task routing, ingest, mutation, activation, deactivation, apply, migration, namespace switching, or flat-browse fallback ownership.

Use when completed work or artifacts need a read-oriented inspection for drift, inconsistency, omissions, or unsupported claims. Not for implementing fixes, producing the primary artifact, or replacing execution-stage verification.

Use when an approved cheatsheet or patching guide must be applied to the real source artifact and the applied result verified. Not for drafting or refining the cheatsheet, or for unrelated source implementation.

Use when source code must be implemented, debugged, refactored, or code-audited through a plan, execution, test, and report loop. Not for requirements-only changes, new empirical experiments, or document-only editing.

Use when a visual product surface needs references, design tokens, components or mockups, review, and development handoff. Not for implementing an already-approved design in code or for document prose work.

Use when a new document has an independent audience and document goal. Not for experiment reports (lab), existing-document edits, or code.

Use when experiments need setup, evaluation/analysis, failure reproduction, or result reporting, including fixed results without new measurements. Not for reusable evaluation code, independent documents, or fixed-data document layout/caption edits.

Use when documents need factual, structural, stylistic, or review-driven correction; preserve history. Not for new documents, empirical work, or evaluation/result reporting (lab).

Use when a task needs a durable survey of new academic, technology, or market evidence before downstream specification or production. Not for repository-only project analysis, a simple factual lookup, or work already grounded by sufficient current evidence.

Use when preparing deployment/release or a delivery archive (package mode). Not for code, new inference/evaluation, report rewriting, or unauthorized deployment; package mode does not run the deployment/review loop.

Use when product requirements, architecture, evaluation policy, or another blueprint must be created or materially updated before implementation. Not for implementing an already-approved specification or for editing unrelated documents.

Use only when autopilot-code dispatches the implementation stage for an approved plan. Not for top-level user requests or primary capability routing.

Use only when autopilot-code dispatches the planning and plan-check stage. Not for top-level user requests or primary capability routing.

Use only when autopilot-code dispatches plan revision after user notes, plan-check feedback, or verification failure. Not for top-level user requests or primary capability routing.

Use only when autopilot-code dispatches the final code-cycle reporting stage. Not for top-level user requests or primary capability routing.

Use only when autopilot-code dispatches implementation verification and evidence recording. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches component, mockup, or preview construction. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches the development-handoff packaging stage. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches design environment and state initialization. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches visual-reference collection and brief creation. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches design quality, token-contract, and breakage review. Not for top-level user requests or primary capability routing.

Use only when autopilot-design dispatches design-token definition or revision. Not for top-level user requests or primary capability routing.

Use only when autopilot-draft or autopilot-refine dispatches an internal strategy or draft refinement stage. Not for top-level user requests or primary capability routing.

Use only when autopilot-draft dispatches document strategy and evidence-plan creation. Not for top-level user requests or primary capability routing.

Use when the acting agent needs to store, retrieve, resolve, hand off, or promote a scoped working-memory item in support of current work. Not for primary task routing, broad artifact triage, or replacing the capability that owns the current work.