ADR — Pack lifecycle: batch (produce+close) vs downstream layers (apply+skills)
Context
The pack-creation-guide initially listed Application (per-project, via GENESIS Phase 8) and Layer-3 production skills as linear phases after extraction. During visual-identity planning this was challenged: are Apply/Skills really sequential batch steps?
Decision
A knowledge pack's lifecycle splits into two distinct parts:
Pack-batch (linear, produces + closes the knowledge asset): thesis+slug → curation → acquire → extract → hub → closure. The pack closes here as a knowledge asset.
Downstream layers (separate, on-demand, NOT batch phases): per-project Application (GENESIS Phase 8 gate) + Layer-3 production skills. They consume the pack's EUs independently, on their own timelines.
Rationale
design-functionalism is closed (452 EUs), yet its Phrasis application (Phase 8) is still pending — application is independent of closure. Closure = the knowledge asset is complete (hub built); it is not gated on consumption. Application tasks live in project-space, not pack-space. Treating Apply/Skills as batch phases conflated production with consumption.
Consequences
Pack closes after hub + closure-events + cross-pack-hub-update + walking-podcast — without waiting on applications.
Application (per-project) + Layer-3 skills are ongoing downstream work, triggered on demand (e.g. `/runa-logo-forge` for visual-identity).
pack-creation-guide phases renumbered: batch P0-P5 (closure), downstream = unnumbered separate section.
Evidence
Applied to visual-identity 2026-05-25 (closed P0-P5 as knowledge asset; `/runa-logo-forge` Layer-3 + per-project application = downstream, separate). Mirrored in community-engagement plan.