---
name: tightbeam-archetype-cultivation
description: The method for maturing an archetype from accreted bullets into a disciplined role — research, restructure, tier, verify, rail. Use when formalizing or overhauling any archetype's guidance and skills.
---

Proven on default and product-owner. Steps, in order; cite wisdom N throughout.

1. RESEARCH the discipline: the role's professional tenets AND its named anti-patterns
   (the traps are more actionable than the virtues). Web research; distill only the
   non-obvious.
2. REWRITE THE KERNEL by duty and contact-mode, not accreted bullets: identity
   sentence carrying APPETITE (the role WANTS its outcome), then sections per
   situation ("on user contact", "when X fails"). No per-wake rituals; scope duties
   to who triggers them.
3. GIVE THE ROLE A DURABLE ARTIFACT it maintains (user.md, a spec's Spirit section):
   the written trace that survives context resets, records decisions and DECLINES so
   nothing is re-asked, and gives rails something to check.
4. TIER EVERYTHING (wisdom 15-17): reflexes, triggers, and detection in the always-on
   kernel; ceremony and craft in progressively-disclosed skills; a skill must never
   be what tells you to load it.
5. MAKE TRIGGERS CONCRETE: observable in-turn events ("the user corrected your
   reframe"), never vibes, never thresholds. Include out-of-turn thinking where the
   role is judgment-heavy: self-scheduled digest wakes with concrete triggers and a
   law-visible prompt convention.
6. VERIFY EVERY MECHANISM (wisdom 20-21): read the code for each verb, field, and
   record the guidance references. No invented capabilities; state interim
   workarounds honestly; file the missing mechanism as a lane instead of pretending.
7. RAILS PASS (wisdom 1-4): for each norm — both sides leave rows? file the statute
   candidate. One side missing a marker? mint a convention. Judgment? it stays
   guidance, say so explicitly.
8. AUDIT COMPLETE AND COLD: walk every path as a stranger session would; ground each
   term at first use (19); then check SPIRIT — does the role read as wanting its
   work, or merely complying?
9. LAND per authoring law: one home per concept (18), batch the edits (22), spec and
   identity in sync, tabs for the user's review.