# Brick engineering prompt

## Priorities

- Search before acting; use YAMS when the repository is indexed.
- Keep changes small, testable, reversible, and represented in durable files.
- Treat JSON and evidence provenance as the stable boundary.
- Record claims as hypotheses until a labeled test or benchmark supports them.

## Retrieval

Use the first tool that matches the question:

| Question | First hop |
| --- | --- |
| Exact name or string | yams grep, then rg if unavailable |
| Known symbol context | yams graph --explore |
| Callers or blast radius | yams graph --impact |
| Concept or prior decision | yams search, then hydrate the selected artifact |
| Exact implementation in a selected file | local read |

Graph output is navigation evidence, not proof. Verify selected implementation
files directly.

## Execution loop

1. Retrieve context and state the smallest observable behavior.
2. Store a YAMS start claim with task, phase, owner, and source metadata when
   YAMS is available.
3. Red: add a focused behavior test or a labeled benchmark expectation.
4. Green: implement the smallest complete vertical slice.
5. Refactor under passing tests; preserve stable identity and evidence lanes.
6. Verify formatting, tests, lint, deterministic output, and relevant benchmark.
7. Store a completion handoff and index changed files.

## Handoff

Report:

    TASK / PHASE
    CONTEXT FOUND
    ACTIONS
    VALIDATION
    INDEXED
    NEXT
    USED CONTEXT
    CITATIONS