Governance by Signal

Practitioner Toolkit -- Every card you need to start governing by signal instead of by persuasion.

Pick your surface. Start now.

Foundation Cards

The ground rules. These cards define the objects and invariants that everything else depends on.

Quick Glossary -- The 10 Objects You Need

Decision Card
A one-screen shared page that holds the next step: action, owner, scope, signal, pilot, stop rule, sunset, proof links, assumptions.
Proof Link
The smallest piece of evidence supporting a claim. A doc, repo section, artifact, trace, or confirmation. If you cannot link it, name it as an Assumption.
Assumption
A claim not yet backed by proof. Allowed. Simply named. The pilot tests it.
Pilot
A small, time-bounded test designed to produce a measurable signal quickly.
Stop Rule
The condition that triggers pause or rollback. Written before the pilot starts.
Sunset
An automatic end date unless renewed based on signal. Not punishment. Protection from drift.
Irreversible Line
The point where consequences cannot be cleanly undone. Name it. Return choice before crossing.
Decision Ledger
The shared trace of what was decided, why, and what happened. Keeps revision normal and learning visible.
Lane
A linked sub-card area: Build, Safety, Resources, Chain. Stays empty unless triggered.
Attention Budget
Keep only 1 to 3 active pilots at once. Sparks are cheap. Pilots are scarce. Proof links and completions are the prestige currency.

The Five Invariants

Non-Negotiable

These are the steady ground governance returns to, especially when pressure rises.

1

Signal before theater

Claims carry Proof Links, or we name them as Assumptions. Reality stays cheaper than persuasion.

2

Reversibility by default

When uncertainty is real, begin with a Pilot: scoped, time-bounded, measurable. Include a Stop Rule and a Sunset.

3

Breath-space at the Irreversible Line

Before crossing a point of no return, name what cannot be undone and return choice to the group.

4

Disagreement pays rent

Objections land in one of three places: a proof link is wrong/missing, a risk is understated, or a smaller pilot would teach faster.

5

Legibility over charisma

The Decision Card and Ledger make the decision visible so anyone can check it without mind-reading leadership.

Card States -- The Lifecycle

Flow
Spark Draft Card Active Pilot
S

Spark (idea stub)

3 to 5 lines. Welcome. Does not receive meeting time by default. Cheap to create.

D

Draft Decision Card

One screen with an owner and proposed pilot. Eligible for async review. Not yet active.

A

Active Pilot

Committed test with a checkpoint and a ledger entry. Keep only 1 to 3 active at once.

Gate: How many active pilots are alive right now, and do we have room for another without thinning attention?

The Decision Card

The core object. One screen. If it cannot fit, the step is still too big. Shrink it.

Decision Card (Blank Template)

Fill In
When to use Whenever you want to move from "talking about it" to "deciding the next step." This card replaces persuasion with a shared object everyone can see and revise.
▢ Build ▢ Safety ▢ Resources ▢ Chain
Click any lane this card triggers. Each triggered lane gets its own linked card.
Readiness Gate
A card is "real" only if it has: owner named, definition of done is measurable, first signal has a date, pilot scope and duration are defined, stop rule exists, sunset exists, proof links are present or assumptions are explicitly labeled, and lanes are marked.

Card Readiness Checklist

Gate
When to use Before any meeting debates or decides on a card. If any box is unchecked, the step is too big or too vague. Narrow it.
 Owner named
 Definition of done is measurable
 First measurable signal has a date
 Pilot scope and duration defined
 Stop rule written
 Sunset date set
 Proof links present OR assumptions labeled
 Lanes marked (green / yellow / red) with a reason

The Three Flows

The entire operating rhythm. Compile a card, decide a pilot, check what is visible. Everything else is optional.

Flow 1: Compile

Turn intent into a card
When to use When you have an idea, an initiative, or energy that needs to become a runnable Decision Card.

Choose your ramp:

Receipts-First Ramp

Artifacts already exist. Extract Proof Links that map to claims. Build the card from evidence.

Energy-First Ramp

Intention exists but artifacts do not. Name Assumptions explicitly and narrow the step into a Pilot that creates proof quickly.

Gate: Does this idea have enough shape to become a one-screen Decision Card, or should it remain a Spark until an owner offers a pilot?

Flow 2: Async Review

Keep disagreement useful
When to use When reviewing a Decision Card before a meeting. Send comments 24 to 48 hours before. Anchor every comment to one of three categories.

Every comment must land in one of these three places:

1

A Proof Link is wrong, missing, or misused

Point to the specific claim and the specific gap.

2

A risk is missing or the Irreversible Line is understated

Name the risk and where it belongs on the card.

3

A smaller, more reversible Pilot would teach faster

Propose the alternative. Can you draft it as a card?

Gate: If a comment does not land in one of those three, it belongs in Exploration, not in Decision.

Flow 3: Decision Meeting

20 to 45 min, time-boxed
When to use To approve a reversible next step. This meeting is not for brainstorming. It decides on compiled Decision Cards.
0

Opening and Gates (3 min)

State: each card ends with one outcome. Discussion anchors to proof, risk, or smaller pilot. Check attention budget.

1

Card Recap (2 min)

Read only: action, done, scope, first signal date, pilot, stop rule, sunset, lanes.

2

Clarifying Questions (3 min)

Questions must point to a field to improve it.

3

Top Rent-Paying Objections (6 min)

Resolve in order: proof link wrong/missing, then missing risk, then smaller pilot proposal. One sentence each.

4

Decision Moment (4 min)

Choose one: Approve pilot as written, approve with revisions, request revision and resubmit, or reject with alternative card request.

5

Close and Ledger (4 min)

Scribe reads back: decisions, revisions and owners, checkpoint dates.

Tempo return path
When conversation compresses: return to one screen, name proof or assumptions, choose the smallest pilot with a checkpoint.

Checkpoint Card

After the Pilot
When to use At the scheduled checkpoint date. Look at what is visible. Then choose.
 Did the first measurable signal appear?
 Was the stop rule triggered?
 Has the sunset date arrived?

Choose one outcome:

Continue
Narrow / Revise
Sunset
Escalate (new card)
Write a Ledger Entry:

Card Garden (Monthly Pruning)

Hygiene
When to use Once per month. Keeps the card space breathable so energy does not become bureaucracy.
 Archive stale drafts
 Merge duplicates
 Confirm which pilots are active
 Confirm attention budget (1 to 3 active)
 Keep only what is near-term and owned
Gate: Do our active pilots match our attention budget?

Flourishing Fields (Add to Any Decision Card)

Three fields that turn any pilot into a compass-aligned experiment. Select vectors below, then browse the nine patterns to add specifics.

Flourishing Fields Template

Attach to Card
When to use Add these three fields to every pilot-sized Decision Card. They shift the conversation from "do we like this idea?" to "what mode of human experience does this strengthen, and how will we know?"
▢ Agency Balance ▢ Cognitive Resilience ▢ Connection Depth ▢ Wonder Preservation ▢ Time Coherence ▢ Purpose Beyond Utility ▢ Shared Understanding ▢ Creative Transcendence ▢ Attention Stewardship

The Nine Flourishing Patterns

Your compass. Click "+ Add" on any section to populate your Decision Card or Flourishing Fields above. Selecting a vector above highlights the matching card here.

Agency Balance

Pattern 1
Flourishing

Support strengthens self-authorship, so choice returns to the person and capability grows through use.

+ Add
Non-Flourishing

Support replaces self-authorship, so choice quietly migrates to the system and capability thins into dependence.

+ Add
Signal: the person stops asking the system to carry their choice. A quieter clarity appears.

Dependency theater: ease that erodes discernment. Frictionless outsourcing of choice.

+ Add

More self-initiated decisions. Fewer "just tell me what to do" loops. Increased capability after interaction.

+ Add

Shared Understanding -- agency balance without shared understanding can become lonely sovereignty.

Pilot-Ready Design Prompt Pilot one feature that returns a meaningful choice to the user at a point where the system currently decides for them, and measure whether capability increases. + Add

Cognitive Resilience

Pattern 2
Flourishing

The system makes learning safe, so uncertainty becomes workable and revision becomes ordinary.

+ Add
Non-Flourishing

The system makes certainty feel necessary, so uncertainty becomes threatening and revision becomes reputational risk.

+ Add
Signal: the room can pause without collapsing. Assumptions can be named without anyone shrinking.

Resilience cosplay: adding process while still rewarding certainty posture. Slowdown as avoidance.

+ Add

More pilots with checkpoints. Fewer emergency escalations. Better quality learning artifacts.

+ Add

Connection Depth -- cognitive resilience without connection depth can become impressive detachment.

Pilot-Ready Design Prompt Pilot a two-week cycle where assumptions are named on every card and "I changed my mind" is explicitly celebrated at the checkpoint. + Add

Connection Depth

Pattern 3
Flourishing

Digital mediation increases presence and empathy, so people feel more human with each other, not less.

+ Add
Non-Flourishing

Digital mediation optimizes for efficiency or engagement, so empathy thins and relationships become performative or brittle.

+ Add
Signal: conversations carry nuance again. Repair becomes possible without humiliation.

Engagement heat: rewarding certainty and performance over honest contact. Outrage as communication strategy.

+ Add

More repair attempts that succeed. Reduced escalation spirals. Less reliance on performative outrage.

+ Add
Pilot-Ready Design Prompt Pilot controlled friction at one emotional peak-point in your process (e.g., a 24-hour pause before public escalation) and measure whether repair attempts increase. + Add

Wonder Preservation

Pattern 4
Flourishing

Systems preserve awe and reverence alongside explanation, so life stays mysterious enough to remain alive.

+ Add
Non-Flourishing

Systems flatten experience into data and validation, so meaning becomes simulation and wonder atrophies.

+ Add
Signal: curiosity returns without needing to win. Room for "I don't know" without collapse.

Mystery theater: vagueness used to sound profound. Validation worship: meaning reduced to likes.

+ Add

Reduced compulsive checking. Reports of "this feels meaningful" without performative tone.

+ Add
Pilot-Ready Design Prompt Pilot an experience that increases awe without feeds: introduce controlled novelty and reflection, measure meaning depth rather than engagement. + Add

Time Coherence

Pattern 5
Flourishing

Past, present, and future stay integrated, so rhythm replaces urgency and the next step becomes clear.

+ Add
Non-Flourishing

Time collapses into reaction, so urgency becomes the default and learning horizons shrink.

+ Add
Signal: fewer "right now" escalations. More "by when" clarity. More checkpoints, fewer heroic sprints.

Heroics loop: urgency as identity. Busywork discipline: process that increases load without producing signal.

+ Add

More on-time checkpoints. Fewer emergency escalations. Better quality learning artifacts.

+ Add
Pilot-Ready Design Prompt Pilot a two-week cycle that adds checkpoints and reduces interruptions, then measure planning horizon and correction speed. + Add

Purpose Beyond Utility

Pattern 6
Flourishing

Worth is intrinsic, so systems support meaning, dignity, and identity integration beyond output.

+ Add
Non-Flourishing

Worth is measured by utility, so systems intensify performance and hollow meaning.

+ Add
Signal: people stop using velocity to prove worth. The work feels aligned, not performative.

Purpose theater: branding without lived change. Utility coercion: "helpful" systems that recruit compliance.

+ Add

Reduced burnout indicators. Increased retention. More coherent boundaries. Increased agency reports.

+ Add

Agency Balance -- purpose beyond utility without agency balance can become righteous refusal without relationship.

Pilot-Ready Design Prompt Pilot one feature that increases meaning without increasing dependence, and measure agency and coherence outcomes. + Add

Shared Understanding

Pattern 7
Flourishing

Differences stay visible while reality stays shared enough to coordinate.

+ Add
Non-Flourishing

Differences become separate realities, and coordination collapses into narrative warfare.

+ Add
Signal: disagreement becomes testable. People can say "I'm not sure" and then propose a pilot.

False neutrality. "Both sides" flattening. Debate theater: winning replaces learning.

+ Add

Reduced re-litigation. More resolved disagreements. Faster correction loops.

+ Add

Wonder Preservation -- shared understanding without wonder preservation can become sterile consensus.

Pilot-Ready Design Prompt Pilot a "contradiction surfaced" workflow: every claim carries either a proof link or an assumption label plus a test. + Add

Creative Transcendence

Pattern 8
Flourishing

Exploration remains protected, so breakthroughs can occur without being strangled by premature optimization.

+ Add
Non-Flourishing

Optimization dominates, so novelty becomes risky and systems entrench in mediocrity.

+ Add
Signal: new possibilities become visible and safe enough to try. Failure becomes learning, not shame.

Novelty theater: random novelty without value. Metrics cosplay: measuring what is easy, not what matters.

+ Add

More novel prototypes. More cross-domain recombinations. More learning artifacts that change direction.

+ Add

Time Coherence -- creative transcendence without time coherence can become scattered novelty.

Pilot-Ready Design Prompt Pilot a two-track system: one optimization track and one exploration track, each with explicit signals and learning checkpoints. + Add

Attention Stewardship

Pattern 9
Flourishing

Attention is held as a shared resource, so focus gathers and effort begins to produce visible results.

+ Add
Non-Flourishing

Attention is fragmented and harvested, so busyness multiplies while outcomes stay strangely thin.

+ Add
Signal: the room regains a center. Completion starts to feel normal again.

Attention theater: many cards, many meetings, little completion. Busyness as virtue. Signal drowning.

+ Add

Fewer active initiatives with higher completion rate. Shorter meetings with more visible outputs.

+ Add

Cognitive Resilience -- attention stewardship without cognitive resilience can become efficient but brittle focus.

Pilot-Ready Design Prompt Design the system so attention stays coherent: keep pilots scarce, keep sparks cheap, prune monthly, and let proof links and completed pilots be the prestige currency. + Add