superstack-executelisted

# superstack-execute <!-- Absorbed from godmode's execute skill (godmode @ adacebb) through the evidence door (DECISIONS.md D-3), adapted to superstack's state layer: the plan file is the sole authority (no STATE.md), receipts feed the claims-log, camp rides superstack-continuity, one-way doors ride the outward gate. Deliberately deferred pieces are listed in D-3, not silently dropped. --> **First act on every load: emit the load receipt** — append one line (`skill-load execute <date> <session-id>`) to `.superstack/receipts/loads.log`. Mechanical proof the loop was loaded; a session that skipped it is countable. ## Opening a plan (once per campaign) One ACTIVE plan per project. Write `.superstack/plans/<slug>.md`, first line `<!-- plan: <slug> status: ACTIVE -->`. Header: a `goal:` line — what this campaign is for, one clause, surfaced at every session start and moved only by the owner (superstack-scope's rule, same reason); the verify command and what green literally prints (or the overlay oracle row it uses); the frontier block (below); the 2–3 load-bearing rulings as pointers to statutes/anchors — never restated; this skill's name as the resume protocol. Body: milestones carrying **intent + done-when + true dependency edges** (an edge is real only when verified) — never implementation detail. Admit only the non-derivables: rulings, paid knowledge, done-definitions, true edges. Test for every line: *could a competent stranger with the spec and repo re-derive this?* Dele