Overall Purpose

To discern whether a proposed feature deserves to be built—not by evaluating its surface appeal, but by listening to the deeper rhythm of the system it would enter. This protocol helps the founder shift from impulsive making to intentional unfolding.

Why this matters

Every build is a bet on the future. But some bets fracture the system, while others anchor it. Building too fast, too often, or too reactively can dilute the clarity of the product, exhaust the builder, and disrupt a rhythm the system was just starting to find. This protocol protects the coherence of what’s already working while making space for what’s truly ready to emerge.

Use this when…

• A new feature idea is pulling your attention
• You feel pressure to ship, grow, or catch up
• You’re unsure whether the time, effort, or energy are worth it
• You’ve said yes to too many things and want to make this one count
• You’re excited but want to check if it’s clean and clear underneath

Outcomes

Poor Outcome

The feature is built from urgency, mimicry, or unexamined pressure, entangling the product in complexity and fragmenting the direction of the build before a clear future can take shape.

Expected Outcome

A decision is made with some clarity and awareness of trade-offs, allowing the product to continue moving, though the long-term trajectory may carry subtle distortions or missed opportunities.

Excellent Outcome

The feature is built in alignment with timing, purpose, and system need, anchoring the next stage of the product in clarity that naturally invites stronger user flow and future evolution.

Transcendent Outcome

The feature is received not as a task, but as a moment of co-creation with the system itself, allowing the future to unfold with greater ease, trust, and coherence as the builder shifts from choosing what to build to listening for what wants to be built.

Themes