Elpis AGENTS.md

Elpis Agent Map

Start

• Read docs/GUIDE.md; it is the product, architecture, and requirements source of truth.
• Read TASKS.md; work only on its Current Action unless Masih changes priority.
• Read docs/context.md and docs/sessions.md before touching context, session, or pruning behavior.
• Read docs/SHIPPING_RULES.md before a release or any change that reads the filesystem, environment, or network.
• Read docs/LOCAL_BUILD_RULES.md before running cargo on Masih's workstation.
• Verify repository state before editing and preserve unrelated user changes.
• Challenge unclear or solution-first requirements with $challenge-requirements before planning implementation.

Context Discipline

• Load only the guide sections and source files needed for the current task.
• Keep the active goal, changed files, verification, blocker, and next action visible.
• Summarize terminal output; do not carry raw logs once their result is known.
• After edits, retain the diff and verification result; reread file bodies on demand.
• Do not add slash commands unless Masih explicitly selects them.
• Worker agents must not edit GUIDE.md or TASKS.md; the coordinator owns those files.
• Do not delegate to Jules. The coordinator selects and manages workers and worktrees.

Definition of Done

• Masih is the sole arbiter of truth. CI, compilation, tests, and agent claims are evidence, not functional acceptance.
• Before important or difficult implementation work, turn the request into an explicit acceptance harness and confirm it with Masih.
• Implement, run the required automated checks, build/install when applicable, and hand Masih a plain user test checklist.
• A task becomes verified only after Masih accepts the user-visible behavior and the evidence is recorded in TASKS.md.
• Behavior must be implemented, not merely documented.
• Rust changes pass the applicable Rust checks. This repository contains no Python.
• Known gaps and skipped checks are stated plainly.