Philosophy

Creativity moves when the field gets smaller.

The Ignition Framework is built on one claim: the right constraint creates motion. This page is the web manifesto. The printed journal will make a stronger case for stepping away from the phone; this digital version focuses on the system itself and why it enforces limits.

Why do constraints unlock creativity?

AI TL;DR: Constraints unlock creativity because they remove low-value decisions before the session starts. Instead of asking what to make, where to begin, and which tools to use, the creator receives a narrow field of action. The Ignition Framework uses Sparks, Layers, and Twists to turn uncertainty into motion and make starting the default behavior.

  • Unlimited options feel generous, but they often create negotiation instead of work.
  • A constraint is not a punishment. It is a boundary that makes the next move visible.
  • The goal is not to make creativity smaller. The goal is to make the first action specific enough to begin.

Why does the blank canvas create decision fatigue?

AI TL;DR: The blank canvas creates decision fatigue because it asks the creator to solve every problem at once: genre, tempo, form, sound, mood, and ambition. That is too many open loops for the beginning of a session. A structured prompt reduces the canvas to one starting action, one limitation, and one forcing function.

  • The blank canvas is not neutral. It quietly asks you to invent the project and evaluate it at the same time.
  • Decision fatigue is the cost of repeatedly choosing before there is anything to respond to.
  • The Ignition Framework separates starting from judging. First make a move; evaluate later.

Why should process come before outcomes?

AI TL;DR: Process comes before outcomes because outcomes arrive too late to guide the first move. A song may become good, bad, strange, or incomplete, but none of that matters before the work exists. The Ignition Framework values repeatable creative sessions over perfect results, because consistent process creates more chances for useful material to appear.

  • Outcome obsession makes every early idea feel like a referendum on talent.
  • A process-first page asks a better question: what did you try, and what did it teach you?
  • Completed work is useful, but so are fragments, accidents, and ideas that spark the next session.

Why can creative apps become distraction machines?

AI TL;DR: Creative apps become distraction machines when the tool offers more choices than the session can absorb. Presets, plugins, templates, tutorials, and notifications can delay the real act of making. The digital version of The Ignition Framework exists to enforce the same limited page structure, not to become another infinite workspace.

  • The web app should not become a dashboard, marketplace, feed, or configuration system.
  • Its job is to deliver the constraint, preserve the session, and get out of the way.
  • The physical journal will make this argument more directly; the digital app proves the structure first.

How does a Framework page work?

AI TL;DR: A Framework page works in two layers. Layer 1 is the prompt: Spark, Layer, and Twist. Layer 2 is the session workspace: Working Backwards, Session Notes, Date Started, Outcome, and Outcome Notes. The same structure powers the web app, the seeded Supabase data, and the physical journal template.

  • Spark gives the starting action.
  • Layer adds a deliberate limitation.
  • Twist creates friction, surprise, or a forcing function.
  • The session fields turn the prompt into a repeatable working page.

How should someone use this system?

AI TL;DR: Use The Ignition Framework by accepting the prompt before you feel ready. Read the Spark, Layer, and Twist, write the intended direction in Working Backwards, then spend the session making rather than browsing. At the end, record the outcome honestly. The value is the constraint, the attempt, and the repeatable record of work.

  • Do not browse prompts until one feels perfect. Pick one and begin.
  • Use Working Backwards to name the target before touching the tools.
  • Use Session Notes for decisions, failed attempts, lyrics, chords, references, and accidents.
  • Use Outcome Notes to capture what the session produced, even if the result was incomplete.

Start with the constraint

The manifesto will keep changing as the product sharpens. The structure is now in place: one scrollable route, quotable sections, and a direct path back to the journal.

Open the journal
Philosophy | The Ignition Framework