Skip to content
DarkPrint
Phase

Testing

testing

Runs the checks and produces the evidence.

Where it sits

one of 5 · closed set
The lifecycle
  1. planning
  2. implementation
  3. testing
  4. debugging
  5. deployment

Read left to right as the arc of a piece of work. The order is the lifecycle, not a ranking. The arrows show the sequence a blueprint tends to run in, not one it must follow.

The five are the one dimension a local namespace cannot extend. A node type or a risk marker can be coined by anybody. A sixth phase would be a different definition of what a dark factory is. There is no abstract root above them either. A root would make the set look open.

A card may name one of them, several, or none. The five describe the blueprint, not every node inside it. An intake or a retrieval step may declare no phase at all. A node that both builds and repairs may declare two. Neither counts as an incomplete card.

Which phases a blueprint has nodes in is its phase coverage. Phase coverage is shown as a description of scope, for example: this blueprint covers planning, implementation and testing. It is not shown as boxes ticked out of five. A blueprint that stops before deployment has decided where it stops.

Who uses it

19 cards · 16 blueprints