library-compoundlisted

# Library Compound ## Purpose Extract patterns from successful and failed outputs across the channel + program + audience and compound them into three concrete targets: `reference/swipe-file/` (anonymized specimens, framework-tagged, filed by asset type), `reference/frameworks/` annotations (creator-specific calibrations appended to the framework files), and `workspace/published/` records (the per-video performance log, including postmortems). Plus hook-bank tier-up, retention-curve signature updates, and KPI band recalibrations. This skill makes the OS smarter every cycle. ## Decision Logic The compound library is the long-term moat, and it accumulates into named paths — every cycle, the same three destinations: - Outputs that performed in top-decile become `reference/swipe-file/` entries (anonymized, framework-tagged, filed under `hooks/` `intros/` `scripts/` `titles/` `thumbnails/` etc.) for cycle-N+1 reference - Outputs that performed in bottom-decile become postmortem entries (anonymized) in `workspace/published/` — patterns to avoid - Frameworks calibrated against actual channel performance get annotations appended in `reference/frameworks/` ("for this creator, this framework runs at X parameter") - Hook bank tiers based on real hook performance - Retention curve signatures update from real per-video curves - KPI bands recalibrate from real channel data `reference/swipe-file/` + the framework annotations + the `workspace/published/` record are the channel's compound