AGENTS.md git:20261024.ed1e2c9A

Immutable. This exact content never changes and is served at /api/v1/blob/ef510760c3017e7d.

# AGENTS.md

Agent-facing configuration for this repo.

## Agent skills

### Issue tracker

Issues live in GitHub Issues (`MrBinnacle/skill-harness`), operated via the `gh` CLI. See `docs/agents/issue-tracker.md`.

### Triage labels

The five canonical triage roles plus a disposition axis, each label string equal to its name. See `docs/agents/triage-labels.md`.

### Domain docs

Single-context: `GLOSSARY.md` + `docs/adr/` at the repo root, maintained by `/domain-modeling`. See `docs/agents/domain.md`.

`GLOSSARY.md` is the vocabulary of record: use its terms in prose and identifiers, respect its Avoid-notes, and when code and glossary disagree, the code is the primary source — fix the glossary, then decide whether the code's term deserves a rename of its own.

## Interface and experience

Remove redundant UI copy. Use clear hierarchy, intuitive controls, and contextual cues to make interfaces self-explanatory. If users need extra text, redesign the interaction.

Optimize UX, DX, and AX as one system. Maximize usability, clarity, and reliability without compromising security, accessibility, or existing functionality.

## Prose voice — literal-humanist register

Instance of the **Register** row of the taste doctrine, class 2 (public prose in `skill-harness`). It lives in `TASTE.md` in the owner's private research repository. The test is stated there once; this section is its application to this repository.

Default register for every substantive prose artifact in this repo: README, docs, ADRs,
issues, pull requests, release notes, review comments, commit bodies, diagnostics. It does
not restyle source code.

For substantive prose:

1. State what happened — dates, amounts, versions, quoted terms.
2. Name the mechanism — translate each label into the action it performs.
3. State the consequence and its allocation — who gained, who paid.
4. State the finding. Never leave the operative conclusion for the reader to infer.
5. Attach uncertainty only to the proposition that is actually uncertain.
6. End with the next action, test, or decision.

Syntax: short sentences, concrete nouns, direct verbs, active voice, one step per
sentence. Never: euphemism after the underlying action is known; "perhaps",
"possibly", or "arguably" as cushioning for a supported claim; "readers may
conclude"; sarcasm or victory laps; passive voice that hides the responsible
component; abstractions that erase the person affected.