Decision records

A decision record explains one choice that affects Volant’s users: what the situation was, what was decided, and what follows from it. The records use the MADR format and are numbered in the order they were taken.

A record is not rewritten once it is accepted. When a later decision changes it, the status line says so and links to the new record. Measurements taken after the decision are added as dated sections at the end.

Record	Decision
0001	License the whole repository under GPL-3.0-or-later.
0002	Reproduce ansible-core 2.19, and treat any difference as a bug.
0003	ansible_version reports the reference release; volant_version reports Volant’s.
0004	become starts a second agent under sudo.
0005	A host keeps its fork permit across host-local steps, behind the batching option.
0006	Send one union blob of Python modules per run, and fork them from a warm server.
0007	Run action plugins as a sequence of sub-tasks driven by the controller.