Tickets

We use GitHub Issues for work that changes code. This doc explains how to write issues that agents can implement reliably.

Issue template (suggested)

Goal

One paragraph: what user-visible behavior changes.

Scope

• In:
• Out:

Specs

Link to relevant docs, especially:

• event-contracts.md
• data-model.md
• specific module specs

Acceptance checklist

Observable behaviors. Avoid vague language.

Example:

• [ ] Clicking a node commits navigation and updates URL.
• [ ] Hovering a node previews navigation without URL change.
• [ ] Bio updates within 150ms on selection change.
• [ ] Smoke tour steps 1–6 pass.

Labels (suggested)

• slice (vertical slice)
• bug
• spec
• ui
• data
• performance