THREE-GEN DESIGN PATTERN / SHAPE PROJECT

One object.
Three degrees of knowing.

Architecture establishes what can be guaranteed. A generic implementation makes it useful. Project authority decides what it means here.

THE RULE Specificity accumulates. Architecture does not.

RESPONSIBILITY PLACEMENT

Each generation is complete at its own level.

01
Define

What must every member of this family truthfully guarantee?

02
Realize

What is the useful generic form, independent of any one project?

03
Authorize

What does this generic thing become when the project finally gives it meaning?

Put a decision in the earliest generation that can honestly own it — and no earlier.

THE PAGE IS THE PROOF

Not diagram theater.

The explorer and the control inside it are real Web Component inheritance chains. Gen 3 does not repaint an unrelated widget; it inherits the actual behavior below it.

GEN 1ShapeElement
GEN 2ThreeGenExplorer
GEN 3ShapeThreeGenExplorer
GEN 1BaseInput
GEN 2TextBox
GEN 3ShapePromptBox