v0.5 → v0.6 Migration¶

v0.6 changed two sets of names that v0.5 readers may have cited: the four strategic positions and the Section 02 stewardship areas. This page is the single source of truth for both. The strategic-position crosswalk and its reasoning come first; the Section 02 conditions crosswalk is at the end.

The crosswalk¶

Why the names changed¶

The v0.5 names (Visionaries, Leaders, Niche Players, Challengers) were identical to Gartner's Magic Quadrant labels. That collision carried two costs: it implied an analyst-firm ranking the framework never intended, and the credibility of those labels was falling as the analyst model itself came under pressure. SF² needed names in its own register.

The v0.6 names come from how software actually gets built. They map the readiness axis to a production-method spectrum: how repeatable the work is.

Reading the axes¶

The vertical axis (Operational Readiness) is the lean transformation. Moving up means the work becomes more repeatable. The progression Craft to Mass to Lean traces repeatability rising, which is the core SF² thesis. The horizontal axis (Operational Complexity) is scale.

• Craft (Simple + Low): non-repeatable hand-work, a snowflake per build.
• Studio (Simple + High): repeatable work at small scale.
• Mass (Complex + Low): big-batch, siloed, low-flow work at large scale.
• Lean (Complex + High): the goal, repeatability sustained at scale.

Two terms that mislead if read casually¶

1. Mass is lean's antonym, not Ford's 1913 assembly line. In SF² terms, Mass means big-batch, siloed, low-flow work that has not yet earned repeatability. It is not the historical mass-production repeatability triumph. The repeatability win in this framework is Lean. A reader fluent in manufacturing history should not invert the readiness axis on the strength of the word alone.
2. Craft names a method, not a price tag. Craft means non-repeatable hand-work, not quality, premium positioning, or boutique branding. A Craft organization can do excellent security work; it just does it by hand each time.

Names that were considered and dropped¶

• Artisanal carried premium and boutique baggage that flattered the wrong cell. The underlying logic (non-repeatable hand-work) was kept as Craft.
• Lego is a registered trademark, a legal disqualifier on a CC-licensed framework.
• Omakase describes high-skill bespoke work, which is low repeatability, so it pointed at the wrong cell.
• Foundry and Refinery collided with existing products (Cloud Foundry, Palantir Foundry) and blurred into each other.

Citing the old names¶

If you are referencing material that used the v0.5 names, the table above is the mapping. The framework's substance (the two axes, the four positions, the movement paths) did not change. Only the labels did.

Section 02: stewardship areas became security conditions¶

In v0.5, Section 02 was titled Universal Risk Stewardship Responsibilities: five areas you steward. v0.6 reframes them as conditions you cultivate, splits the old Supply Chain area along the embedded/delegated line, and recasts Continuous Learning as the cross-cutting Adaptive Capacity condition.

The URL path stays 02-stewardship/ for stability, so existing links keep working. The one file that moved is continuous-learning.md, now adaptive-capacity.md.

The deeper change is register, not labels. v0.5 framed these as responsibilities you own and steward, scored on a maturity chart. v0.6 frames them as living conditions with no passing grade, cultivated and assessed rather than owned and managed. The Universal Security Conditions overview explains why that distinction carries weight.