## Goals

- G-1: A connected repository goes from a new issue to an announced release with no human step but the maintainer's decisions
  measure: issue_to_release_p90 < 2d
- G-2: Agents' work holds a quality bar the maintainer can trust without reading every diff
  measure: change_failure_rate <= 5%
- G-3: The person who asked for a change hears where it is available at each stage and can confirm it works
- G-4: The maintainer sees in one place what waits on them, across all their repositories
- G-5: Agents keep to the written direction: work outside the goals is postponed or declined with its reason
- G-6: Agents pursue a goal: they propose the work that reaches it, and the maintainer approves it
- G-7: The loop knows whether each goal is met, from a measure, and proposes changing the direction when it is

## Non-goals

- N-1: Executing a rollout: staged rollout, traffic shifting, and deploys to customers belong to the platform; shipmill decides and verifies (D-31)
- N-2: A server or state of its own: the forge holds the state, in issues, labels, pull requests, tags, and deployments
- N-3: Making the maintainer's decisions: accepting an opportunity, approving a spec, or changing this direction
- N-4: The software lifecycle outside the delivery loop for now: strategy, discovery, operations and SLOs, support, deprecation
- N-5: A coding agent or model of its own: shipmill directs an existing agent

## Quality bar

- Q-1: Fail fast: a malformed config or an unexpected state stops with exit 2 and a message naming the fix, never a guess
- Q-2: Every write an agent makes is attributed to the App, never to a person (D-14)
- Q-3: A release ships only code whose CI passed on the exact release commit, and a breaking change reaches a stable release only after the maintainer's decision
- Q-4: Every acceptance criterion of a spec has a test that names it
- Q-5: A change honours the settled rules in `docs/decisions.md`, or records a superseding entry the maintainer approved
- Q-6: The release side works without the agents
