What the rider must keep doing

Shortening an instruction file is easy; proving it still behaves the same is the hard part. A golden task writes down the behaviour that must survive, so a later change can be checked against something rather than assumed.

Nothing here runs. A golden task records what a compiled rider must keep doing, so a later change can be checked against it. Running these against a model is a later phase — until then, no screen in this product is evidence that a compiled pack behaves like the one it replaced.

Your golden tasks (0)

None yet. Add a suggestion above, or start one below.