binbin

One time axis; each bar is a system, a job or a programme. Where they overlap is where they were running together — the part a list cannot show and this cannot hide. Drag to pan, scroll to zoom; wherever the pointer sits, the readout says how many were running that day.

Every bar's dates are quoted from the case study it links to — sources are recorded in content/periods.ts, each naming the sentence it was read from, and a project with no stated dates gets no bar. A bar is the build, not the relationship: one still maintained afterwards carries a hairline to today, and one whose end is not recorded fades out and is left out of the running-at-once count, because counting it would be a guess wearing a number. Most of these systems are still in production with nobody touching them, which is not the same as being maintained. Bars known only to the year or month fade at both ends. The four figures below are computed from the same spans, not typed.

Each row carries its own slice of the axis above it. The short red line under a name is the time that system took.

Not principles read somewhere. Each came from one specific thing, caught in acceptance or in the week before launch. They are written as rules rather than as virtues, because a virtue is not evidence of anything.