DECISIVE EDGE: Disciplined Sovereignty·Official site beadecisiveleader.com—the same catalog spine as Decisive Edge.How we handle tool dataPrivacy policy

Execution install · Life SOP

Decision sustainment framework: from EDGE Execute to a seven-day Life SOP

Most decisions die between alignment and Monday muscle memory. The Sustainment Engine converts your Execute line into micro-SOPs for seven days, simulates willpower draw-down against capacity inputs, mirrors the North Star gate for records, and exports a performance dashboard PDF—all locally in your browser.

Systems beat heroic intent

Discipline spikes are unreliable. Pre-decided morning launches, friction reducers, and binary evening audits offload choices so capacity signals stay honest.

How the simulation supports the argument

Watching strain climb as simulated willpower falls is a teaching aid: it explains why Life SOPs are not optional fluff for senior leaders—they protect cognition when calendars attack.

Open tool

The sections above are written for leaders and search engines reading ahead. When you are ready, jump into the live workspace—runs in your browser with the on-page privacy notices.

Open the Sustainment Engine

Sustainment Engine

Life SOP generator & command export

Module 1 turns your EDGE Execute field into a seven-day ramp of three micro-SOPs per day. Module 2 simulates willpower draw-down against your Capacity Matrix baseline. Module 3 compiles matrix, North Star gate, EDGE, and SOPs into a blueprint PDF with a commitment block.

Quick start: write Execute as if you were handing orders to your past self—verbs, objects, order of operations. If a day feels wordy, edit the text after export; the generator is a scaffold, not a personality test.

Pairs with Master Decision Dashboard and Capacity Matrix. Browser-only — nothing is stored server-side. Use Useful / Needs work at the bottom so we can tune copy and defaults.

Module 1 · SOP generator

Paste your Execute commitment (first physical sequence). Optional: sharpen friction copy with a one-line Decide anchor.

Tip: the evening line is always a single yes/no—no journaling homework. If you break protocol, answer “No,” note one sentence offline, and let the next morning launch pull you back.

Zero-Retention Policy:Your data is processed and purged. We don't train on your decisions.

DAY 01 · Install the anchor

7-day ramp
Morning launch (0–5 min)
Within 5 minutes of starting your day, perform the first physical move tied to: Name the first physical move for this decision (one sentence).
Friction reducer
Prep the environment tonight: surfaces, files, and gear for "Name the first physical move for this decision (one sentence)." are staged so the new path is one motion; add 20+ seconds of friction to the old default (logout, unplug, relocate).
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 02 · Repeat on low willpower

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
Time-box the old habit: allow it only after "Name the first physical move for this decision (one sentence)." is complete and logged (Day 2 — keep the sequence visible on one card).
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 03 · Tighten the environment

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
Physical barrier: remove the default cue from arm's reach; place a single token (card, object) where the new protocol starts — "Name the first physical move for this decision (one sentence).".
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 04 · Compress decision time

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
Default route costs more: if you catch yourself drifting to the old pattern, require a written one-line reason before you continue — anchor line: "Name the first physical move for this decision (one sentence).".
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 05 · Stress-test the default

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
Social friction: tell one accountability partner what "protocol followed" looks like today (Day 5); silence the easy bail-out channel until evening audit.
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 06 · Recover the drift window

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
Batch temptations: park distractions in a closed container/room until "Name the first physical move for this decision (one sentence)." is done — make recovery the high-friction path.
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

DAY 07 · Lock the operating rhythm

7-day ramp
Morning launch (0–5 min)
Morning launch (0–5 min): same physical class of action as Day 1 — Name the first physical move for this decision (one sentence). — shorten setup; no new decisions before the move.
Friction reducer
End-state lock: set tomorrow's environment before sleep — calendar block + object layout so "Name the first physical move for this decision (one sentence)." is the lowest-energy correct action.
Evening audit (binary)
Did I follow the protocol today? — record Yes / No only.

Module 2 · Willpower vs. system

Simulated waking day (0–16 h). Willpower depletes; decisions that lean on raw discipline push your effective strain into hotter zones. Life SOPs offload recurring choices so the Capacity Matrix signal stays closer to green.

This is a teaching visualization, not a biometric readout. Slide the hour forward after lunch meetings or late-night email sprints to see why pre-decided protocols matter—then mirror your real numbers from the full Capacity Matrix when you export the PDF.

Sliders: match today’s reality first—these values feed the simulation below and the Module 3 PDF export.

Willpower reserve

100%

Capacity matrix projection

Baseline effective strain (from sliders above): 48% · Optimal band

Willpower-only path48% · Optimal band
System + SOP path30% · Reserve

Green band in the product matrix maps to headroom + optimal band (effective strain under ~63%). SOPs cut how much depletion couples into strain so you stay inside operational margin longer.

Module 3 · Performance Dashboard export

North Star binary gate (same logic as the Master Decision Dashboard) and full EDGE fields are embedded in the tactical PDF.

North Star · binary filter

Financial integrity

Does this choice protect or improve financial truth?

Life direction

Does it move you toward the life you said matters?

Peace test

Will you still respect this decision at 2 a.m.?

Moral alignment

Does it honor every line you refuse to cross?

In the Master Decision Dashboard, a No under single-door mode can hard-stop the workflow; here answers are for your record—they print as-is on the Performance Dashboard PDF.

EDGE engine fields (for PDF)

Paste from your Master Decision workspace if you already drafted there—the Sustainment Engine keeps Execute in sync with the top-of-tool field when you leave Execute blank here.

Take it offline

PDF SITREP

One-click brief with Decisive Edge branding—drop into Slack, email, or your board pack. Generated locally in your browser; your notes never upload for this export.

Common questions

Short answers below match the structured data on this page—helpful for sharing the link with a colleague.

What does the Sustainment Engine do with my EDGE “Execute” field?
It turns your first physical commitment into a seven-day ramp: each day lists a short morning launch (under five minutes), one friction reducer so the new path is easier than the old default, and a single evening audit question you answer yes or no. That is the habit architecture side of execution—not motivation slogans, but repeatable moves.
Is anything I type saved on your servers?
No. The tool runs in your browser. PDFs are generated locally with jsPDF and download to your device. Optional analytics (tool opens and feedback) use coarse event names only—no transcript of your decision text is sent with those pings.
What is in the Performance Dashboard PDF?
A single blueprint-style report: your Capacity Matrix-style snapshot (the five sliders you set here), North Star binary lines, full EDGE fields you choose to include, the generated seven-day Life SOPs, and a digital signature block so you can name the commitment and file or print it.
How should I use this with the Master Decision Dashboard?
Draft the full EDGE chain there—including a concrete Execute line—then open the Sustainment Engine and paste Execute here (or copy from your notes). Run the Capacity Matrix first if you want realistic load numbers before you export the Performance Dashboard report.

Was this tool useful?