delegatelisted

Delegation only pays off if each ticket can be executed correctly by a fresh session that has never seen this conversation and has no access to the reasoning that produced the plan. Model capability and session separation are different: a Junior-safe ticket may run on the same, a lighter, or a stronger model, while Senior-required work must run in the user-selected senior-capability mode. ## Context Contract **Required:** an approved implementation plan from `charter` — Step 0 stops without one · the resolved architecture file, to check Absolute Invariants and security/compliance boundaries when classifying each item's tier. **Conditional:** the existing delegation queue, when it already has unstarted or in-progress tickets — read before appending, never silently overwritten. **Excluded by default:** anything outside the approved plan's scope — this skill splits an already-approved plan, it does not re-plan. **Outputs:** the written queue (three tier-grouped lists, full ticket specs for all three, and a unified Execution Sequence showing every ticket's dependencies across tiers), one ready-to-paste handoff block per Junior-safe ticket in dependency order, and a plain checklist per Owner-required item — never a session handoff, since no AI session executes those. **Write authority:** the tier-resolved `delegation-queue.md` only — append tickets with stable, never-reused numbers; never touch the code the tickets describe. Fresh-session isolation covers conversation conte