Graduation / promotion

Description

Scaffolding → adult form. The structural pattern where a provisional, exploratory, or scaffolded artifact becomes the canonical adult version through promotion. The transition is qualitative, not just gradual: at some threshold, the scaffolding role ends and the adult role begins. Often the move that creates a uniformity dividend (the first instance was exploratory; the promoted version becomes the canonical shape).

Composition

= lifecycle + projection. The lifecycle is the progression through stages (scaffolding → mature); the projection is the carrying-forward of structure from earlier stage to later stage with selective transformation. Not all features of the scaffolding survive promotion; the projection step decides what carries.

When it applies / triggers on

User-initiated: User signals an artifact is at a transition point — either explicitly (“promote this to a doc”, “make X canonical”, “delete the GDoc, make repo canonical”) or implicitly (user shows enough investment that the previous artifact’s role is being outgrown). Trigger-verb signal is moderate: canonical appears in 1/22 (5%) of real-user-msg matches; promote / graduate appear in the regex but mostly in agent output rather than user prompts. Four recurring sub-shapes:

• Explicit promotion request — user says “make X canonical” or “pull this into the repo and delete the source” (example: “pull in that google doc to the repo, and make the repo version canonical… then you can delete the google drive version”).
• Cleanup-as-graduation reframe — user asks about cleanup; agent reframes as a promotion-pipeline question. (Example: “should we clean up memory?” → “memory-to-doc graduation is actually a healthy signal, not a cleanup problem… the memory was scaffolding; the doc is the adult form.“)
• Trigger-condition specification — defining the when of promotion (“raising capital, hiring, regulated data, formal LLC for scale” as explicit promotion triggers for the email-stack-to-Workspace transition). Generalizes from email-stack to any “stay-lightweight-until-trigger” architecture decision.
• Real-time meta-observation — agent observes a graduation happening in the current session (example: the three-value hierarchy going from nowhere → memory → committed doc, all in one session — the fastest graduation path possible).

Agent-initiated: Engine notices an artifact whose role-in-the-system is being outgrown (a memory that’s getting cited externally, a one-off pattern that has now occurred three times, a draft that’s accumulating commits). 8/30 of T2 top candidates are <task-notification> flavor — the elephant evaluates a goldfish’s output that crossed a graduation threshold (memory → doc, doc → committed-artifact).

Vocabulary cues: “graduate,” “graduates,” “graduation,” “promote,” “promotion,” “make X canonical,” “canonical,” “adult form,” “scaffolding,” “promotion trigger,” “memory to doc,” “raise to a doc,” “mature,” “dev → staging → prod.”

Situation-shape signals: Any artifact that has accumulated enough usage/citation/recurrence to be outgrowing its original container. Also: a “spring cleaning” framing of memory/scratch/notes is often a graduation-pipeline question in disguise; reframing it surfaces what the projection step preserves (e.g., behavioral guidance stays in memory; public argument goes to the doc).

Encounters

• “Memory was scaffolding; the doc is the adult form” — KCC documentation graduation: a memory-system note gets promoted to a committed doc when its scope and persistence justify it.
• Provisional decision → doctrine — KCC pattern: a one-off choice becomes a recurring pattern, then an explicit rule.
• Staging → production promotion — software deployment cycle: code matures through environments before becoming canonical.
• Piagetian developmental stages — child concepts mature through discrete stage transitions.
• Metamorphosis / adult form — biology: caterpillar → butterfly, tadpole → frog.

Composes with

• uniformity-dividend (creation relationship) — graduation is often the move that creates a uniformity dividend (promoting a one-off into the canonical pattern).
• route-as-context — promoting a one-off route pattern into a canonical convention is a specific instance.

When it doesn’t apply

• No clear stage transition — when an artifact gradually matures without a discrete promotion moment, the bundle’s specific work isn’t being done.
• Reversible scaffolding — when scaffolding is meant to be permanent and supportive (like furniture, not pupa), the bundle frame mis-describes the relationship.

Sources

• Software promotion lineage (dev → staging → prod).
• Piaget / developmental psychology.
• Metamorphic biology.
• Named as a bundle in the analogy-project brainstorm (2026-05-17, goldfish synthesis of saved insights).

Canonical exemplars from corpus (T2 2026-05-17)

• Memory-to-doc graduation as healthy signal (cwd: campconnect, session: idx=5): “Memory-to-doc graduation is actually a healthy signal, not a cleanup problem. The memory was scaffolding; the doc is the adult form. Your codebase already treats docs/parent-feedback.md this way — generalizing that shape would change memory-cleanup from ‘spring cleaning’ to ‘promotions process.‘”
• First real exercise of graduation pattern (cwd: campconnect, session: idx=6): “The graduation preserved what the memory uniquely contributes: session-local behavioral instructions. The doc owns the public argument. This clean split feels right; worth watching whether future graduations maintain it or drift.”
• Promotion triggers in Cloudflare-Workspace doc (cwd: campconnect, session: idx=4): “The GDoc treats the question as ‘free stack vs. eventually-graduate-to-Workspace,’ with explicit promotion triggers (raising capital, hiring, regulated data, formal LLC for scale).”
• Fastest graduation path possible (cwd: campconnect, session: idx=0, task-notification): “The three-value hierarchy went from nowhere → memory → committed doc — all in one session. Raw insight → structured memory → committed artifact, compressed because the thesis crystallized in a single conversation.”

Trigger pattern (T2): Graduation-promotion surfaces when an artifact is at a transition point — either explicitly (user proposes “promote this to a doc”, “make repo canonical”) or implicitly (user signals enough investment that the previous artifact’s role is being outgrown), with moderate trigger-verb signal on “canonical” and agent-side “graduate”/“promote.”