three altitudes — three processes

Vinaya's life cycle

Plan·Execute·Archive

Milestone

A milestones life cycle.

Created once by the architect. After that its status is read off its tranches — planned, active, complete — and never written by hand.

always

The goal

Plain prose. What you're trying to get done, written for people.

if you want it

A release

The version it aims at. One named field — never guessed out of a title. Completing the milestone doesn't cut the release — that's still a hand act today.

if you want it

A list of tranches

One line per batch of work. Written before any of them exists.

the whole thing · 10 seconds

One milestone, start to finish.

Every tranche under one goal, played once at speed. Only what a milestone can see.

one milestone · N tranches · time runs left to right0.0s / 10.0s
goal
milestone opensmilestone complete
tranche 1
planexecutearchive
tranche 2
planexecutearchive
tranche N
planblocked by tranche 1executearchive
the architect opens the milestone

first

Plan

Someone decides what this is for, and which batches get it there. The one real judgement call here.

who does itThe Architect
what ends itThe goal written, the tranches named
starts withYour idea
ends withA milestone

then

Tranches run

Each tranche runs its own loop. The milestone doesn't drive them — it waits.

who does itThe tranches, on their own
what ends itEach tranche finishing its own loop
starts withA named tranche
ends withThat tranche, filed

and that's it

Close

Not started, in flight, finished — all read off the tranches. No field to forget.

who does itNo one — it just reads true
what ends itThe last tranche archiving
starts withEvery tranche done
ends withA complete milestone

one level in

Each of those tranches does the same three things.

where this is going

Same stages. Nobody driving.

Today a person or a small script decides when each stage starts. Next, the engine does. Only who says go changes.