Synced from
references/inspiration-frameworks.mdinscript-poolskill on 2026-05-18. Edit upstream in the skill; this file is overwritten on next sync.
Inspiration Frameworks — Append-only Canon
Rolled-up patterns observed across analyzed inspiration videos. Mode C draft-script consults this as advisory;
_canon/value-frame/consumes it as architectural distillate.
How this file grows
- Mode E (
modes/extract-inspiration-framework.md) appends one entry per source after analyzingcontent-pool/inspiration/<slug>/ - Each entry: 5-7 lines max — this is the rolled-up canon view, not the per-source full extraction (that lives in
content-pool/inspiration/<slug>/framework-extraction.md) - Sorted by analysis-date DESC (newest first)
- Append-only — past entries are NOT rewritten when patterns repeat. Pattern repetition is the signal that distillation into
_canon/value-frame/architectural-rules.mdis warranted.
Entry shape
## <slug> — <one-line title> (<analysis-date>)
- **Source:** [`content-pool/inspiration/<slug>/`](../../../../content-pool/inspiration/<slug>/) · @<creator-handle>
- **Daniel-read:** "<2-3 line annotation verbatim from metadata.daniel_annotation>"
- **Hook archetype:** <Tier-1/2/3 from shortform-virality.md>
- **Retention shape:** <one-line summary of the 0-3s/12-18s/30-60s windows>
- **Value-density:** <1-5> / Payoff: <one-line on what makes viewer NOT swipe at second-hook gate>
- **Two-beat / contrarian-reframe:** <yes/no per axis + 1 example>
- **Architectural extract:** <1-2 lines on what distillates to Value-Frame canon>When to distill into _canon/value-frame/architectural-rules.md
After ≥3 entries, Mode E Step 7 prompts Daniel to distill. Patterns that appear in ≥2 entries are candidate canonical rules. Daniel approves/edits before write to _canon/value-frame/architectural-rules.md.
Entries
inline-15ffb1bb — Four hours ago Elon Musk · Terrafab + AWS pattern-match (2026-05-07)
- Source:
content-pool/inspiration/inline-15ffb1bb/· inline-paste (no URL/file) - Daniel-read: “Performt weil specific-number lede ($20B) + contrarian twist (80% to space) + pattern-match to AWS/Bezos historical analog. Insider-positioning (‘3 years ahead’) ist clean. ABER: comment-bait CTA close — das ist anti-pattern (AP-01), NICHT kopieren.”
- Hook archetype: Tier-1 Pattern D (Specific-Number) + Pattern B (Contrarian)
- Retention shape: 0-3s timestamp+$ anchor / 12-18s “200B chips + now here’s where it gets crazy” double-hook / 30-50s AWS analog / 60s+ insider-position + CTA-bait (anti-pattern)
- Value-density: 4/5 / Payoff: specific-scale + meta-promise double-mechanic at second-hook gate
- Two-beat / contrarian-reframe: YES / YES (explicit)
- Architectural extract: R-02 Specific-Number Lede + Contrarian Pivot; R-03 Pattern-Match Historical Analog; R-04 Insider-Positioning Reward; AP-01 Comment-Bait CTA close (forbidden)
inline-76b9ce24 — Massive shit about to happen · silo-effect / pin-device prediction (2026-05-07)
- Source:
content-pool/inspiration/inline-76b9ce24/· inline-paste (no URL/file) - Daniel-read: “Mischung aus Kontext-News und eigener Meinung. Architektur-These zur Zukunft der personalisierten AI über consolidation-layer. Performt weil concrete prediction (pin-device, OpenAI/hark/anthropic) + stakes-claim (killing software companies) + observational-witness close ohne CTA-bait. Future-of-tech / interoperability-thema dichtest abgebildet.”
- Hook archetype: Tier-1 Pattern A (Vulnerability) + Pattern E (Future-Prediction)
- Retention shape: 0-3s stakes-claim + filmed-on-record-anchor / 12-18s “the gap is very big. Here’s why” promise-payoff / 23-60s experiential-silo-naming (phone/computer/family) / 60-90s pin-device prediction with OpenAI/hark/anthropic candidates / 90-130s stakes-amplification + observational-witness close
- Value-density: 4/5 / Payoff: shared experiential silo-naming creates instant resonance pre-prediction
- Two-beat / contrarian-reframe: YES (~4 instances) / YES (implicit — silo-thesis vs mainstream AI-talk)
- Architectural extract: R-01 Vulnerability + Stakes-Claim Lead; R-05 Observational-Witness Close (no CTA-bait); experiential-silo-naming as viewer-problem framing pattern