# Conventions

## Intent

Capture conventions that agents should follow when working in this repo.

## Context

This repo values small, verifiable changes and file-based progress that
survives context resets.

## Constraints

- Keep notes brief and actionable.
- Do not store secrets or customer data.
- Prefer explicit configuration and clear error handling.

## Approach

- Read `ACTIVE/PLAN.md` and `ACTIVE/TASKS.md` before starting multi-step work.
- Update `ACTIVE/PROGRESS.md` after meaningful progress.
- Mark tasks done only when acceptance checks pass.
- Promote architectural decisions to ADRs in `DECISIONS/`.
- Run all relevant checks before marking any task complete:
  - `deno task test` — core test suite
  - `deno task bench` — benchmarks (if configured)
  - `deno lint` — lint compliance
  - `deno doc --lint mod.ts` — validate JSDoc on public exports (per-module)

## Edge cases

If work spans multiple iterations, capture risks in `ACTIVE/RISKS.md` to avoid
context loss.