Change tasks

A change task changes the product. One task gives one change that a person can check. When the work gives two changes, intake writes two tasks and sets depends_on.

Each task is one file in tasks/, and it stays there with its last status.

---
id: T-012
status: draft
milestone:
exploration:
repos: [acme]
depends_on: []
decisions: []
issue:
pull_requests: []
provider:
---

repos gives each repository that the task changes.
decisions gives the number of each decision that applies, not its text.
exploration gives the exploration that the task came from.
provider gives the agent of the build, when it is not the default of factory.json.

#The sections

Section	It holds
`## Goal`	What changes in the product, in plain words
`## Acceptance criteria`	One check on each line
`## Out of scope`	What this task does not do
`## Context changes`	What future tasks must know
`## Deployment requirements`	What you do to deploy this change: each environment variable, secret, migration, service and command
`## Questions`	Each open question, and its answer
`## Discovered work`	Other work that the build saw, and did not do
`## Evidence`	The proof of each criterion, and each decision about the code
`## Review`	The result of `accept`
`## Promoted`	What `accept` wrote to `context/`

triage adds ## Rework when the pull request needs a change. build does each item, replies on each comment, and removes the section.

#A criterion about how a page looks

A criterion about how a page looks points to the design. When it gives a size, a colour, a spacing or a position, probe changes it to point to the design. build proves it with a screenshot, not a test.