The Manual Manual
(or, How to Make & Execute a Plan)
Master Manuscript — v1.0 • August 15, 2025
Compiled with GodSet glyphs (F1–F12). Licensed CC-BY-NC-SA.
Colophon & Notice of Use
License: Creative Commons BY-NC-SA 4.0. You may share and adapt with attribution, for non‑commercial use, under the same license.
Design: one-page plan pages with glyph footers, Log Gates, and field-ready worksheets.
Symbols: △ (Promise), ▢ (Container), ━ (Step), ❍ (Witness), O (Close), F1–F12 (GodSet operators).
Credits: Compiler (Norman). Clerk (Archive). Thanks to the committee and field testers.
Foreword — On Pages That Carry You
I wrote this because I have watched good people stall on the first page. Not for lack of will—just too much weight in the hands. A plan should set something down so you can move. That is what this book does. It gives you one page that carries you.
We keep it small on purpose. One promise (△), one container you can actually hold (▢), a short line to cross (━), a witness that does not argue (❍), and a closure that feels like a door you can close (O). You’ll see small glyphs in the margins. They’re not mystical; they’re handrails for attention. The GodSet gives us a simple grammar for moving work through a day.
Some names you’ll meet: F1 – Send It when it’s time to ship; F2 – Make It Ours to claim the desk and begin; F3 – Drop It to cut what doesn’t belong right now. When you stall—and we all stall—F4 – Air It Out is in the footer of every page: notice, exhale, remember the promise, align, re-box, seal. If the work needs to sleep, we’ll F8 – Tag & Shelf without shame. When it’s time to return, F11 – Wake the File and step back in. If the heart is full, F10 – Hold & Pour gives you a cup to set it down so your hands are free again.
This book is gentle, but it does not blur. Each page asks for actions that move bodies, checks that can be witnessed, and one small record. We use a Log Gate—ten little boxes at the bottom—to run the same page enough times for the click to happen. Most good things arrive just after the count. When they do, we mark O+ and keep going.
You will also see us care about time (F7) and people (F9). Trains and bridges. We say exactly who owns a step and who receives it. Plans that float between names do not sail; they drift. We don’t drift here.
If you’re coming to this at two in the morning, eyes hot and hands shaking a little, you’re in the right place. We will not ask you to become a different person first. We will ask you to write one sentence that promises something you can finish today; to name the few tools you will actually touch; to choose three verbs that can be done with what you have; to decide what “done” looks like; and to mark one small box when you try.
Please don’t measure yourself against someone else’s calendar. The page you fill is yours; our symbols are only there to keep the path visible when it gets dark. If fear arrives, it can sit in the cup while you work. If the page will not move, we reset, or we shelf it with love, and we return when the light changes.
By the end of the first page, something will work again. That is the only standard we keep.
— Norman Rule, C/07
for those who are carrying more than they can hold, and still choosing
to move.
How to Read This Book
This manual is a field tool. Each section is a two‑page spread: a short teaching + a worksheet or case box. Fill the page; do not add theory.
Symbols (quick key)
△ Promise • ▢ Container • ━ Steps • ❍ Witness • O Close • F1–F12 operators.
Page Flow
Top to bottom: Promise → Containers → Steps → Checks → Roles/Handoffs → Schedule → Failure Branch → Reentry → Close → Log Gate → F4 footer.
How to Use
Pick one page. Read the left column. Fill the worksheet. Run the steps. Mark the Log Gate. If stalled, use the F4 footer and either shrink (F3) or shelf (F8) with an F11 reentry.
The Manual Manual — Section 1 (v1.1)
What a Plan Is (and Isn’t)
Promise (△): By the end of this section you will be able to tell a working plan page from an idea, and you will write a one-line promise that a tired future‑you can complete today.
1. Definition — A Plan Page
A plan page is a one‑page contract with yourself or your team that moves a specific outcome from potential to closure. It fits on a single sheet. It contains: a Promise (△), a Container you will actually use (▢), 3–7 Steps written as verbs that move bodies (━), one or more Checks you can witness (❍), and a Close you can perform in the real world (O). Nothing else is required.
2. What It Is Not
Not a brainstorm. (Unscoped ideas live elsewhere.)
Not a wish. (If the outcome cannot be witnessed, it’s not on this page.)
Not a backlog item. (Backlogs collect possibilities; this page creates action.)
Not an essay. (Explanations go to the archive. Here we move.)
3. Bodies, Verbs, Containers
Bodies: Plans move people, not thoughts. If no one can perform the step with their hands, the step is wrong.
Verbs: Start each step with an action verb a stranger could enact without interpretation. Avoid “review,” “align,” or “consider” unless followed by a visible act (send, file, publish).
Containers: Work needs a place to happen. Name the room, doc, call, or app (▢) where the step will occur. If the container is missing, that is your first step.
4. Outcome Over Effort
Effort is noble; outcomes are observable. Prefer outcomes you can point at: a message sent, a file published, a package posted, a meeting confirmed. Write checks (❍) that a third party could verify without your explanation. Effort counts only if it leaves a trace in the container you named.
5. The Two‑Minute Sanity Check (❍)
Read your Promise out loud. Can you complete it today with what you have? If not, cut scope (F3 ▽).
Point at the Container. Is it open and real? If not, create it now or change the plan (F2).
Count the Steps. 3–7? Each begins with a verb? If not, rewrite.
Name the witness. How will you know this closed? If you can’t say, add a check (❍).
Name the Close. What happens in the world when this page is done (O)?
6. Failure Modes & Routing
Scope creep → Route to F3 – Drop It (△ → ▢ → ▽).
Stall or overwhelm → Run the footer reset F4 – Air It Out (❍ → ▽ → △ → /|\ → ▢ → O).
Dependency blocks → Move the blocked item to a new page; shelf this one with F8 – Tag & Shelf (▢̷ → ⎔) and schedule F11 – Wake the File (꩜).
Vague verbs → Replace with a visible action (send, upload, publish, call, print, file).
Case Box A — Three Tiny Plan Pages (2–3 steps each)
A1) “Send the beta email to three nodes and log the URLs (O).”
Open the draft in the Product Updates doc (▢).
Send to 3 recipients (F1 ▢▢▢) and paste the sent links into the log (O).
Block 15 minutes to receive (F7 ∴).
A2) “Publish three journal SKUs and complete one live checkout (O).”
Create 3 products with titles, prices, SKU codes in CMS (▢).
Switch Stripe to live; run one checkout successfully (❍).
Post the live URLs to the team thread (F9).
A3) “Confirm Tuesday’s vendor call and file the agenda link (O).”
Send confirmation with agenda link (F1).
File the link in ‘Vendor/Calls/2025-08’ doc (▢).
Add calendar invite; check it appears on both calendars (❍).
Worksheet — Draft Your Promise (△)
Write one sentence in this shape (finish‑today sized):
“{Verb} {Object} to {Recipient/Container} and {Close}.”
Your draft:
________________________________________________________
________________________________________________________
________________________________________________________
Container you will use (▢): _________________________________________
One witness (❍): ____________________________________________________
Close action (O): ____________________________________________________
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run a plan page.)
The Manual Manual — Section 2 (v1.0)
The Promise Sentence (△)
Promise (△): By the end of this section you will write a finish‑today promise that binds scope, actor, container, and close. It will pass the Five‑Check test and anchor your plan page.
1. What the Promise Is
The Promise Sentence is the smallest unit of a working plan. It binds intent to an observable close. It belongs at the very top of the page, alone, so that a tired future‑you can find the rail and move.
2. The Five‑Check Test (❍)
Observable — someone else could witness it without your explanation.
Singular — one outcome only; bundles become steps or new pages.
Finish‑today sized — no bigger than the hands you have right now.
Containered — it names the real place where it will land (▢).
Verbed — begins with a visible action verb (send, file, publish, print, call, buy, post).
3. Shapes That Work (fill‑in patterns)
Choose one and write it straight. Keep adjectives out unless they narrow scope.
“{Verb} {Object} to {Recipient/Container} and {Close}.”
“By {Time}, {Verb} {Object} in {Container}, then {Close}.”
“Decide {X}, record it in {Container}, and {Close}.”
“Confirm {Event} with {Person} via {Channel} and {Close}.”
4. Anti‑Patterns → Repairs
Vague verbs (“review”, “align”) → add a visible act: “review → edit → send” or replace with “publish/file/send”.
Multiple outcomes (“write + design + ship”) → pick one; move the rest to steps or a new page (F3 ▽).
Hidden dependency (“send deck” but no deck exists) → first make container real; or split into two pages.
Unbounded size (“draft chapter”) → shrink to a hand‑sized slice: “draft lead paragraph + 5 bullets and file in doc (▢)”.
No witness (“make progress”) → add a check: “progress note filed in log (❍)”.
5. Shrinking With F3 — Drop It (△ → ▢ → ▽)
When in doubt, reduce until the finish‑today condition is true. You can always wake the file later (F11 ꩜).
6. Special Promise Types
Decision promises — “Decide vendor A/B and record choice + one reason in ‘Procurement Log’ (▢), then notify (O).”
Waiting promises — “Open receive window 15 minutes at 3:00 (F7 ∴), log any replies (❍), then close (O).”
Load‑aware promises — If emotion is high, append a cup: “Name the fear in one line in the journal (F10), then send.”
7. Field Exercise — Draft 3, Choose 1 (△)
Write three promises below using the shapes from §3. Run each through the Five‑Check test, circle the strongest, and copy it to the top of your plan page.
1) _________________________________________________________________
2) _________________________________________________________________
3) _________________________________________________________________
Five‑Check pass? ☐ Observable ☐ Singular ☐ Finish‑today ☐ Containered ☐ Verbed
8. Minimal Deliverables (O)
One chosen Promise Sentence that passes all five checks.
A short “Not‑Now” list for items cut via F3 (▽).
The name of the container where the outcome will land (▢).
Case Box B — Promises That Hold Under Pressure
B1) Product: “Publish v0.2 release notes to /Product/Updates (▢) and post link in #announcements (O).”
B2) Vendor: “Confirm Tuesday 10:00 with Acme, attach agenda, and file invite URL in ‘Vendor/Calls’ (▢), then mark calendar (O).”
B3) Personal admin: “Pay invoice #447 via portal (▢) and save receipt PDF to /Finance/2025 (O).”
B4) Creative: “Draft 1 lead paragraph + 5 bullets for Section 3 in ‘Manual Manual’ doc (▢) and push change‑note to log (O).”
B5) Load‑aware: “Write the one‑line fear in the journal (F10 ❍→▢→⬒→▽), then send the partner email (O).”
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you write and run a Promise.)
The Manual Manual — Section 3 (v1.0)
Containers & Fields (▢)
Promise (△): By the end of this section you will name the real place your outcome will land, make it present, permissioned, and searchable, and bind your page to it.
1. What a Container Is (▢)
A container is the place where the outcome lands and lives. It can be a doc, a thread, a folder, a calendar entry, a physical bin, or a room. If the container is not real, the plan will slide off the page. Making the container real is often Step 1.
2. Field vs. Container
Field = the surrounding space that supports the work (room, time block, attention bubble).
Container = the specific object that holds the outcome (doc, task, thread, folder).
Use F2 – Make It Ours to claim the field. Use ▢ to name the container. Use O to close in it.
3. Quality Criteria (the five checks)
Present — it exists now (created, opened, or cleared).
Addressed — it has a concrete path/URL/location you can point at.
Permissioned — the right people can read/write without friction.
Indexed — it can be found later (searchable name + tags if available).
Bounded — it has a clear purpose so it doesn’t become a junk drawer.
4. Minimal Naming Standard
Use a short pattern that makes search and sorting obvious. Examples:
“2025-08-15 — Journal Pilot — Release Notes” (doc)
“Vendor/Calls/2025-08/Acme-Agenda” (folder path)
“MM: Section 3 Draft v1.0 — Containers & Fields” (doc)
“Finance/2025/Invoices/0447-Receipt.pdf” (file)
5. Common Containers (with cues)
Document (▢): working text, decisions, and links → pairs well with F11 ꩜ (reentry).
Thread/Channel (▢): announcements and bridges → pairs with F9 (link two).
Task/Ticket (▢): state changes and checklists → pairs with F6 (approvals).
Calendar Entry (▢): time-bound promises → pairs with F7 ∴ (thresholds).
Physical Folder/Box (▢): artifacts and mailers → pairs with F1 (ship).
Room/Table (▢): session space → initialize with F2 (claim the space).
6. Five-Minute Container Setup (F2 → ▢ → O)
Name it using the standard, create/open it now (Present + Addressed).
Add one line at the top: Promise (△) + Owner + Date (Bounded).
Set permissions for the receivers (Permissioned; run a ‘can you see it?’ ping).
Drop one anchor artifact: link, file, or outline (Indexed).
Paste its path/URL back onto your plan page and into the log (O).
7. Anti-Patterns → Repairs
DMs as container → move to a named thread/channel; link it on the page.
Screenshots as record → store the source file; screenshot becomes illustration only.
Multiple duplicate docs → pick the earliest canonical; archive the rest via F8 (▢̷ → ⎔).
Private ownership → assign a second editor; post the path in a shared index.
No index → create a parent index doc/folder and list your containers there (F11).
8. Field Exercise — Make It Real (F2)
For your current plan page, choose the correct container type and complete the five checks. Fill the boxes, then copy the path/URL to the top of your page.
Container name: ____________________________________________
Path/URL/location: _________________________________________
Who can read/write: ________________________________________
Index/parent folder: _______________________________________
Purpose sentence: __________________________________________
Case Box C — Containerization in Three Contexts
C1) Product Release
Create doc “2025-08-15 — v0.2 Release Notes” in /Product/Updates (▢).
At top: △ “Publish v0.2 notes” + Owner + Date.
Grant view to #announcements group; paste link to plan page (O).
C2) Vendor Onboarding
Create folder “Vendor/Acme/2025-08-Call-Setup” with subdoc ‘Agenda’.
Invite vendor email to Agenda doc; test view (❍).
File signed NDA PDF into folder; link back to tracker (O).
C3) Creative Drafting
Create doc “MM — Section 4 Draft — Steps That Move Bodies”.
At top: △ “Draft lead + 5 bullets” and a tiny index of sections.
Add change-note area; log O when saved and linked to master index.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you make a container real and bind a page to it.)
The Manual Manual — Section 4 (v1.0)
Steps That Move Bodies (━)
Promise (△): By the end of this section you will write 3–7 steps that a stranger could enact without interpretation, each ending in a visible state change in a real container (▢).
1. What a Step Is (and the Grammar)
A step is a single physical act that causes a visible change in the world. Grammar:
Verb + Object + Container/Recipient + Limit/Quality + (Check/Record).
Example: “Upload (verb) v0.2 PDF (object) to /Product/Updates (▢) and paste the link in #announcements (check/record).”
Example: “Call (verb) Acme (recipient) for 5 minutes (limit) and confirm Tuesday 10:00; file invite URL in Vendor/Calls (▢).”
2. The Rule of 3–7 (why it matters)
Fewer than 3: the page probably hides work—expand or make containers real (F2).
More than 7: the verbs are too small—group or move to a new page (F3 ▽).
3. The Atomicity Test (❍)
Can a single person do it in one sitting without switching roles?
Does it end with a state change you can point at (sent, posted, saved, filed, scheduled)?
If it stalls for >10 minutes → branch: F8 (tag & shelf) or create a new page.
4. Timebox vs. Completion
Use timeboxes for exploration or receiving; prefer completion verbs for delivery.
Timebox: “Read vendor contract for 15 minutes; list 3 issues in ‘Legal Notes’ (▢).”
Completion: “Send revised contract to vendor and file PDF copy in /Legal/2025 (▢).”
5. Handoff Steps (F9 — Link Two)
Name the receiver by role or group (“post in #announcements”, “email Norman”).
Add the receipt marker (reply, ✅ reaction, calendar accept).
Close with a record: paste link/path in the log (O).
6. Verb Bank (visible, body-moving)
send, publish, post, upload, file, print, stamp, mail, pack, deliver, call, book, confirm, schedule, record, paste, attach, label, rename, move-to, archive, tag, link, scan, export
7. Anti-Verbs (fix with a visible act)
review → edit → send
align → decide → record
consider → list options → pick → file
note → write 3 bullets in ‘Log’ (▢)
8. Sequencing with Glyphs (margin cues)
Initialize field (F2) → write steps (━) → place checks (❍) → seal (O).
If approvals exist, place F6 (⬒) before the ship step.
If timing matters, mark the receive window with F7 (∴).
9. Field Exercise — Write Your 3–7 Steps (━)
Write steps using the grammar. End each with a state change in a container.
1) _________________________________________________________________
2) _________________________________________________________________
3) _________________________________________________________________
4) _________________________________________________________________
5) _________________________________________________________________
6) _________________________________________________________________
7) _________________________________________________________________
Quick self-check: ☐ Atomic ☐ Visible close ☐ Right container ☐ Receiver named (if handoff) ☐ 3–7 total
Case Box D — Rewriting Weak Steps
Original (weak): “Review release notes.” → Strong: “Edit v0.2 notes in ‘Product/Updates’ (▢), then publish to /Product/Updates and post link in #announcements (O).”
Original (weak): “Align with vendor.” → Strong: “Email Acme with Tuesday 10:00 proposal; when they accept, paste invite URL into ‘Vendor/Calls/2025-08’ (▢).”
Original (weak): “Make progress on section.” → Strong: “Draft 1 lead paragraph + 5 bullets in ‘MM/Section 5 Draft’ (▢) and push change-note to log (O).”
Original (weak): “Handle invoices.” → Strong: “Pay invoice #447 via portal (▢) and save receipt PDF to /Finance/2025; paste path in finance log (O).”
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run a 3–7 step page.)
The Manual Manual — Section 5 (v1.0)
Witness & Closure (❍ → O)
Promise (△): By the end of this section you will write checks that anyone can verify without your explanation and define a closure that leaves a trace in a real container (▢).
1. What Counts as a Witness (❍)
Observable — a third party can point to it without your help.
Located — it lives in a named container (▢) with a path/URL.
Time-stamped — it carries when; ideally who and where as well.
Minimal — the lightest evidence that proves the change happened.
2. Witness Types (with examples)
Binary state: “File exists at /Product/Updates/v0.2 (▢).”
Receipt: “Email sent; ‘Delivered’ shows in outbox thread (▢).”
Third‑party signal: “✅ reaction in #announcements within 15 min (F7).”
Artifact placed: “PDF stored at /Finance/2025/0447-Receipt.pdf (▢).”
Calendar accept: “Invite shows ‘Accepted’ for Acme (F9 link two).”
Approval mark: “Ticket #321 moved to ‘Approved’ (F6 ⬒).”
3. Writing Checks That Hold
Shape: “Check: {signal} in {container/path}.” Keep feelings out; put location in.
Good: “Check: link to v0.2 appears in /Product/Updates and loads under 2s (❍).”
Weak → repair: “Reviewed” → “Edited doc and posted change-note at top (▢).”
Weak → repair: “Looks fine” → “QA checklist completed; all boxes ticked in ‘QA-Run’ sheet (▢).”
4. Closure (O) — What Happens in the World
Ship: publish/post/send/submit.
Seal: file, archive, tag & shelf (F8), move to done column.
Bridge: notify receiver and log the link (F9).
Receipt: paste path/URL in the change log (꩜ if reopening later).
5. O vs. O+ (the click)
O = closure as promised. O+ = closure plus threshold crossed (insight, adoption, or repeatability). Mark O+ only when it clicks; don’t chase it.
6. Breadcrumb Minimum (record box)
Who closed (initials), when (time/date), where (container path).
One line: “NR — 2025‑08‑15 14:10 — posted release link to #announcements; path: /Product/Updates.”
7. Anti‑Patterns → Repairs
“Done” with no evidence → add one link, one file, or one receipt.
Local‑only proofs (desktop files) → move to shared ▢ and paste path.
Ephemeral chat message → copy link into index doc (▢) for retrieval.
“Will follow up” → create a new plan page; don’t leave futures on closure.
8. Definition of Done — Mini Template
Fill these lines; paste into the top of your page and your container (▢).
DoD: {One sentence outcome}.
Check (❍): {Signal} at {Path/URL}.
Close (O): {Action} and {Record line}.
9. Field Exercise — Write 3 Checks & 1 Close
For your current plan page, write three checks and one closure. Keep them minimal and located.
Check 1: __________________________________________________________
Check 2: __________________________________________________________
Check 3: __________________________________________________________
Close (O): ____________________________________________________________
Record line: __________________________________________________________
Case Box E — Tighten the Finish
E1) Product Release
Check: “v0.2 notes live at /Product/Updates and link loads <2s (❍).”
Close: “Post link in #announcements; paste URL into Change Log (O).”
E2) Vendor Call
Check: “Calendar shows ‘Accepted’ for Acme; invite URL filed in Vendor/Calls (▢).”
Close: “Send ‘confirmed’ email; paste thread link into tracker (O).”
E3) Finance
Check: “Portal shows ‘Payment received’; receipt saved as /Finance/2025/0447-Receipt.pdf (▢).”
Close: “Tag invoice #447 as ‘Paid’ in ledger; note txn ID (O).”
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run witness + closure.)
The Manual Manual — Section 6 (v1.0)
The One-Page Plan — Anatomy & Use
Promise (△): By the end of this section you will assemble a complete one-page plan—blank and filled—using the standard anatomy, with the F4 reset in the footer and a Log Gate at the bottom.
1. The Standard Anatomy (top → bottom)
Header: Title + Promise (△) — one line only.
Tools & Containers (▢) — what you will actually touch.
Steps (━) — 3–7 verbs that move bodies; each ends in a state change.
Checks (❍) — the witness signals that prove closure.
Roles & Handoffs (F9) — who owns steps; who receives outputs.
Schedule / Thresholds (F7 ∴) — deadlines, receive windows, gates.
Failure Branch (F8) — how to exit cleanly if stalled; next appointment.
Reentry Tag (F11 ꩜) — when/why this reopens; “next poke.”
Close (O) — the real-world act that seals the page.
Log Gate — ten tiny boxes; fill one each run.
Footer — Emergency Reset (F4) mini-ritual.
2. Order of Operations (how to fill it)
F2 — Claim the field: sit, breathe, open the right container (▢).
Write the Promise (△): finish-today sized, observable, verbed, containered.
List Tools/Containers you will use; create any missing ones now.
Draft 3–7 Steps (━); end with a visible state change in a real ▢.
Attach Checks (❍) where needed; keep them minimal and located.
Name Roles & Handoffs (F9): owner, receiver, receipt marker.
Set Schedule/Thresholds (F7): deadlines or short receive windows.
Define the Failure Branch (F8): tag & shelf rule; next appointment.
Add Reentry (F11 ꩜): when you’ll wake the file and why.
Write the Close (O): what happens in the world immediately on completion.
Draw the Log Gate: □ □ □ □ □ □ □ □ □ □
3. Margin Glyphs (light-touch cues)
Place △ beside the Promise; ▢ beside each container name.
Mark approvals with ⬒ (F6) before the ship step.
Mark timing with ∴ (F7) beside any receive window.
Use ❍ bullets to denote checks; end page with O.
If you shelve, mark ▢̷ and ⎔ in the branch; add ꩜ on reentry.
4. Print Hygiene (pre-flight)
Title and Promise present at top; footer F4 present at bottom.
3–7 steps total; no vague verbs as final words.
At least one check (❍) and one close (O).
Every handoff names a receiver and a receipt marker (F9).
Log Gate drawn; date at top-right if you want a stackable pile.
5. Worksheet — Build Yours Now
Fill each line; write small and literal. Then copy into your plan page template.
Title: _______________________________________________________________
Promise (△): _________________________________________________________
Tools & Containers (▢): ______________________________________________
Steps (3–7): _________________________________________________________
Checks (❍): __________________________________________________________
Roles & Handoffs (F9): _______________________________________________
Schedule / Thresholds (F7 ∴): ________________________________________
Failure Branch (F8): _________________________________________________
Reentry Tag (F11 ꩜): _________________________________________________
Close (O): ____________________________________________________________
6. Mini Template (copy-paste)
Title — {Short name}
Promise (△): {One line outcome}
Tools & Containers (▢): {Docs/threads/rooms/apps}
Steps (━): 1) {verb…} 2) {verb…} 3) {verb…} 4) {verb…} 5) {verb…}
Checks (❍): {Signal(s) at path(s)}
Roles & Handoffs (F9): {Owner → Receiver + receipt marker}
Schedule / Thresholds (F7 ∴): {Deadline/receive window}
Failure Branch (F8): {Tag & shelf rule + next appointment}
Reentry (F11 ꩜): {When/why wake file}
Close (O): {Publish/post/file/notify + record line}
Log Gate: □ □ □ □ □ □ □ □ □ □
Case Box F — Annotated One-Page Plan (Journal Pilot in 72h)
Title: Journal Pilot v0.1 — 3 SKUs
Promise (△): Launch a 3-item journal pilot page live with checkout in 72 hours.
Tools & Containers (▢): CMS product module; Stripe; /Product/Journal-Pilot doc; #announcements thread.
Steps (━):
Create 3 products with titles/prices/SKUs; attach mockup (▢).
Configure shipping (flat domestic); test one checkout (❍).
Draft 3 blurbs (≤40 words) and paste into product pages.
F6: Run approval checklist; fix red flags; switch Stripe to live (⬒).
Publish products; copy live URLs; verify mobile view (O).
Post announcement link in #announcements; block 15 minutes to receive (F7 ∴).
Checks (❍): Test order succeeds; pages load <2s; prices correct.
Roles & Handoffs (F9): You → Dev (template wire) → Marketer (blurbs) → You (publish). Receipt = ✅ in #announcements.
Schedule / Thresholds (F7 ∴): T-0 now; T-24 assets ready; T-48 staging; T-72 live.
Failure Branch (F8): If payment fails after 2 attempts: tag ‘PAYMENT-BLOCK’; shelf; schedule F11 for tomorrow 10:00.
Reentry (F11 ꩜): Day-7 review: add one photo variant; consider bundle pricing.
Close (O): Log ‘Pilot live’; paste URLs into Change Log; notify the three nodes.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run a complete page.)
The Manual Manual — Section 7 (v1.0)
Roles & Handoffs (F9 — Link Two)
Promise (△): By the end of this section you will assign single ownership to each step, name explicit receivers, and define receipt markers so handoffs are visible and closed in real containers (▢).
1. What a Handoff Is (F9)
A handoff links two people (or groups) across a container. It names who sends, who receives, where it lands, and how receipt is proven. No receipt, no handoff.
2. Ownership Rules (one owner per step)
Each step has exactly one owner (person or role).
Receivers are named by role, group, or person (no “someone”).
Ownership changes only on handoff; that change is recorded (❍).
3. Handoff Grammar
Shape: “{Owner} → {Receiver} via {Channel/Container ▢} with {Object}; Receipt: {Signal}; When: {Time/Window}.”
Example: “You → #announcements via Slack (▢) with ‘v0.2 link’; Receipt: ✅ within 15 min; When: by 16:00 (F7 ∴).”
Example: “You → Vendor via email (▢) with agenda; Receipt: calendar ‘Accepted’; When: today 10:00–11:00.”
4. Receipt Markers (❍) — choose one
Reply message (“ACK”, “Received”).
Reaction (✅) in the target thread within a window (F7 ∴).
State change (“Approved/Done” column; ticket moved).
Artifact appears (file posted at path; commit ID in PR).
Calendar accept (meeting shows ‘Accepted’).
5. SLA Windows (F7 ∴) & Escalation
Immediate (≤15 min), Same-day, Specific time block (e.g., 10:00–11:00).
If no receipt by window end: ping once; then escalate to named backup.
Escalation path is printed on the page; use roles, not only names.
6. Handoff Checklist
Owner named? Receiver named?
Channel & Container named (▢)?
Object named (file, link, decision, agenda)?
Receipt marker defined (❍)?
Window set (F7 ∴) and backup named?
Record line written (who/when/where)?
7. Anti-Patterns → Repairs
“Someone please review” → “Dev Lead reviews; Receipt: ✅ in #dev by 15:00; backup: QA.”
DM approvals → Move to ticket/thread; mark state change in system (F6 ⬒).
Two owners on one step → pick one owner; the other becomes receiver or backup.
Unsearchable proofs → place evidence in a shared ▢ and paste the path.
Handoffs with feelings instead of signals → replace with a receipt marker.
8. Micro-Templates (copy & adapt)
Email:
Subject: {Outcome} — {Date}
Body: Sent to: {Receiver}. Container: {Path/URL ▢}. Receipt requested:
{Signal} by {Time/Window}.
Slack/Thread:
{@Receiver} {Outcome}. Container: {Path/URL ▢}. Please {Signal} by {Time/Window}. Backup: {Role}.
Calendar Invite Footer:
Receipt = ‘Accepted’. Agenda path: {▢}. If not accepted by {Time}, escalation to {Role}.
9. Field Exercise — Bind Your Handoffs (F9)
Write handoffs for your current plan’s steps using the grammar. Keep them short and provable.
1) Owner → Receiver via {Channel/▢} with {Object}; Receipt: {Signal}; When: {Window}
2) Owner → Receiver via {Channel/▢} with {Object}; Receipt: {Signal}; When: {Window}
3) Owner → Receiver via {Channel/▢} with {Object}; Receipt: {Signal}; When: {Window}
4) Owner → Receiver via {Channel/▢} with {Object}; Receipt: {Signal}; When: {Window}
Record line: __________________________________________________________
Case Box G — Four Handoffs in the Wild
G1) Product → Announce
You → #announcements via Slack (▢) with ‘v0.2 link’; Receipt: ✅ within 15 min; When: by 16:00; Backup: Ops.
Record: “NR — 16:05 — ✅ seen by Ops; link pasted in Change Log (▢).”
G2) Vendor → Call Setup
You → Vendor via email (▢) with agenda link; Receipt: calendar ‘Accepted’; When: today 10:00–11:00; Backup: Coordinator.
Record: “10:12 ‘Accepted’ shown; invite URL filed in Vendor/Calls (▢).”
G3) Dev → PR Review
You → Dev Lead via GitHub (▢) with PR #221; Receipt: state ‘Approved’; When: by 14:00; Backup: QA Lead.
Record: “13:40 Approved; merged; release tag posted in /Product/Updates (▢).”
G4) Fulfillment → Shipment
You → Warehouse via ticket (▢) with pick-pack list; Receipt: tracking # in ticket; When: EOD; Backup: Shift Lead.
Record: “UPS 1Z… posted; customer notified; PDF label filed in /Shipping (▢).”
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you define and run a handoff.)
The Manual Manual — Section 8 (v1.0)
Time & Thresholds (F7 ∴)
Promise (△): By the end of this section you will place clear time gates and receive windows on your page, remove vague timing language, and bind each window to a containered signal so progress is visible and schedulable.
1. What F7 Is
F7 marks the train times—the moments a thing may depart or arrive. It creates short, named windows where something can happen and be witnessed. We use it to make time observable and fair.
2. Four Timing Units (use the right one)
Deadline — a latest acceptable moment (e.g., 16:00). Closes with O.
Window — a short period held open to receive something (e.g., 15:00–15:15). Closes with ❍ if signal appears, or with F9 ping + escalation if not.
Duration block — a fixed block reserved to do work (e.g., 30 minutes). Ends with a state change in ▢.
Threshold gate — a Go/No-Go decision point that determines the next branch.
3. The Trains Table (name your departures)
List the few trains that matter for this page. Write absolute times, not vibes.
T-0 (start): ________________ | Action: __________________________
T-1 (receive window): ________ | Signal (❍): _____________________
T-2 (deadline): ______________ | Close (O): _______________________
Backup train (if missed): _____ | Escalation: ______________________
4. Receive Windows (how to run them)
Open the window on the calendar; title includes ‘Window ∴’.
State what you are waiting for and where it will land (▢).
Keep windows short (5–30 minutes). Close them on time.
If signal arrives → mark ❍ and proceed. If not → F9 ping once, then escalate per page.
After closing, write a one-line record in the container (who/when/where).
5. Timeboxing vs. Delivery
Use timeboxes for exploration/receiving; don’t confuse them with delivery.
Every timebox ends with a concrete state change in ▢ (notes filed, options listed, next page spun up).
Delivery steps end with O: publish/post/send/submit.
6. Naming Standard (calendar & titles)
“MM — {Outcome} — Window ∴ {Start–End}”
“MM — {Outcome} — Deadline {Time}”
“MM — {Outcome} — Work Block {Length}”
Always include the container path/URL in the calendar description.
7. Threshold Gates (Go/No-Go)
A threshold gate decides the branch. You must name the criterion, the check, and the branch that follows.
Gate: “If two approvals (F6 ⬒) present in Ticket #321 by 14:00 → Ship; else → Shelf via F8 and book F11 tomorrow 10:00.”
Gate: “If test order succeeds (❍) by 16:30 → Announce; else → Fix + re-test; new window 17:00–17:15.”
8. Anti-Patterns → Repairs
“ASAP/EOD” → replace with an exact time + timezone (e.g., 16:00 PT).
Open-ended waiting → create a receive window and close it on time.
Stacked meetings with no state change → convert one into a work block with an outcome.
Hiding time in DMs → place window on calendar; paste container path.
“Ping until they answer” → define one ping, then a named escalation path.
9. Field Exercise — Put F7 on Your Current Page
Fill and copy to your plan page and calendar.
Outcome: ___________________________________________________________
Work block: ________________ | State change in ▢: _________________
Receive window (∴): ________ | Expected signal (❍): ______________
Deadline: __________________ | Close (O): _________________________
Escalation (if no signal): ________________________________________
Case Box H — Three F7 Scenarios
H1) Announcement Receive
Window: 15:00–15:15 ∴ in calendar; waiting for ✅ in #announcements (▢).
At 15:15, if no ✅ → ping owner once; if still no signal by 15:20 → escalate to Ops.
Record: “15:16 ✅ seen; link pasted into Change Log (▢).”
H2) Vendor Confirmation
Deadline: 10:30 for ‘Accepted’.
If not accepted by 10:30 → resend invite with ‘Reply YES’; window 10:30–10:40 ∴; if still no, escalate to Coordinator; shelf page (F8) with F11 for 14:00 tomorrow.
H3) Shipping Cutoff
Work block: 09:00–09:30 to pick-pack (state change: label PDF in /Shipping ▢).
Deadline: 10:00 carrier pickup; Close (O): tracking # posted in ticket.
Gate: If label not printed by 09:45 → swap to courier; notify customer.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run a window or gate.)
The Manual Manual — Section 9 (v1.0)
Failure Branches (F8 — Tag & Shelf)
Promise (△): By the end of this section you will define clean exit criteria, choose a tag, capture a shelf record, and schedule a reentry so stalled pages stop bleeding time and attention.
1. What a Failure Branch Is
A failure branch is not a punishment. It is an intentional exit that protects the work and your attention when the page cannot proceed. You name why, where it sleeps, and when you will wake it.
2. The F8 Sequence (glyph)
▢(△) → —— → ┃ → ▢ → ▢̷ → ⎔ (◯)
▢(△): Acknowledge the current container and promise.
——: Stop the current motion (put the pen down).
┃: Draw the vertical line — boundary crossed; page leaves main flow.
▢: Create/choose shelf container (folder/index row).
▢̷: Tag the form as suspended with a clear label (e.g., PAYMENT-BLOCK).
⎔ (◯): Archive placement; record the link and next appointment (F11).
3. Tripwires (when to branch)
Time: 10-minute stall or missed receive window (F7 ∴).
Attempts: two consecutive failures on the same step.
Dependency: external approval or asset missing (F6/unknown).
Authority: you lack permission/access and cannot obtain it now.
Quality: the minimum bar fails twice; risk of rework grows.
Health/Safety: emotional or physical overload — route via F10 first, then decide.
4. Tags (name the pause)
Use short, searchable tags. Examples:
PAYMENT-BLOCK, APPROVAL-WAIT, DEP-EXT, ASSET-MISSING, CLARITY-MISSING, ACCESS-DENIED, TIME-GATE, SCOPE-TOO-LARGE
5. Shelf Record (the minimum)
Write one line in the shelf index (▢):
“{Tag} — {Why in 8–12 words} — Owner: {Role/Name} — Next: {F11 time/date} — Path: {URL/Folder}.”
Example: “APPROVAL-WAIT — ticket #321 needs legal ⬒ — Owner: PM — Next: 2025-08-16 10:00 — Path: /Product/Releases/v0.2.”
6. Reentry (F11 ꩜) — the appointment
Put the appointment on the calendar with a verb (“Wake v0.2 file”).
Define the reentry outcome (decide/ship/abandon).
Attach the shelf container path/URL in the calendar description.
At reentry, run F4 (mini reset) before proceeding.
7. Repairs While Shelved (optional)
Narrow scope (F3 ▽) to a finish-today slice.
Substitute a different receiver or channel (F9).
Decouple blocked step into a new page; let this one close.
Ask for the missing thing once, clearly; then stop pinging.
Create a threshold gate (F7) for the next attempt.
8. Anti-Patterns → Repairs
Lingering pages with no status → Tag & Shelf now; write the shelf record.
Silent abandonment → F8 with a closing note; then archive.
Vague tags (“stuck”) → choose a concrete tag; name the why in 12 words.
Rework loop → introduce a gate: “If fail again, retire page; new page for fix.”
Private shelves → move shelf record to a shared index (▢) and link it.
9. Field Exercise — Design Your Failure Branch
Fill the blanks; copy to your plan page and shelf index (▢).
Tripwire(s): _________________________________________________________
Tag: _________________________ Shelf Container (▢): ________________
Shelf Record (one line): ____________________________________________
Reentry Appointment (F11): __________________________________________
Escalation (if still blocked at F11): _______________________________
Case Box I — Three Clean Exits
I1) Payment Gateway Fails Twice
Tripwire: two failed live charges.
Tag: PAYMENT-BLOCK; Shelf: /Commerce/Payment-Issues (▢).
Record: “PAYMENT-BLOCK — live charge failing; Stripe status unclear — Owner: Ops — Next: 2025-08-16 10:00.”
Reentry (F11): decide fallback (manual invoice) or retry after status page clears.
I2) Legal Approval Missing
Tripwire: no ⬒ by 14:00 (F7).
Tag: APPROVAL-WAIT; Shelf: ticket #321 ‘Blocked’ column (▢).
Record: “APPROVAL-WAIT — legal review pending — Owner: PM — Next: 2025-08-16 09:30 — Path: /Product/Release-321.”
Reentry: if ⬒ present → ship; else → escalate to Counsel per page.
I3) Vendor Unresponsive
Tripwire: window 10:00–10:15 ∴ passes; no “Accepted”.
Tag: DEP-EXT; Shelf: ‘Vendor/Calls/2025-08’ tracker (▢).
Record: “DEP-EXT — no accept from Acme — Owner: Coordinator — Next: 2025-08-15 15:00 — Path: /Vendor/Calls.”
Reentry: send alternate time; if no response by next gate → retire page.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you branch cleanly with F8.)
The Manual Manual — Section 10 (v1.0)
Reentry & Versions (F11 ꩜)
Promise (△): By the end of this section you will wake a sleeping page cleanly, write a change-note, choose the right path (reopen, retire, or fork), and set the next appointment so the work moves again.
1. What F11 Is
F11 is the moment we return to a page on purpose. We don’t relive; we reenter. We accept what the last attempt taught us, update the record, and either continue, retire, or fork.
2. The F11 Sequence (glyph)
꩜ → △ → ▢ → ━ → ❍ → O
꩜: Wake — acknowledge the shelf index or archive note.
△: Restate the current promise in one line (shrink if needed).
▢: Open the container; make sure it’s present and permissioned.
━: Write the next 3–7 steps (atomic, body-moving).
❍: Place one witness signal.
O: Name how closure will happen in the world.
3. When to Wake
Appointment arrives (from F8 shelf record).
Trigger event (approval lands, asset arrives, gate passes).
Threshold reached (Log Gate completes; insight suggests a new attempt).
4. Reentry Ritual (60–180 seconds)
Run F4 mini reset: ❍ notice → ▽ exhale → △ intent → /|\ align → ▢ re-box → O seal.
Read the last change-note and shelf tag; say out loud what changed.
Shrink the promise (F3 ▽) until finish-today is true.
Name the first step you will do now; if none exists, retire the page.
5. Change-Notes (the minimum record)
One line per wake. Shape:
“{Date/Time} — {Reason for wake} → {Change or decision} — {Next step/appointment} — {Initials}.”
Examples:
“2025-08-16 10:05 — Legal ⬒ arrived → publish v0.2 notes — announce at 11:00 — NR.”
“2025-08-16 14:40 — asset missing persists → retire page — spin new page ‘Photoshoot’ — F11 tomorrow 10:00 — NR.”
6. Versions (naming & numbers)
Use simple doc semver: v0.x during drafting; v1.0 on first public release; bump minor (v1.1) for edits that don’t change promise; major (v2.0) for new promise.
Title pattern: “{Project} — {Artifact} — v{X.Y} — {Date}”.
Keep a Change Log at the top with newest-first entries.
If you fork, link parent ↔︎ child in the first line of each doc.
7. Fork or New Page? (decision)
Fork = same promise, different approach (two solutions in parallel).
New page = different promise or container. The old page should close or retire.
If both remain open, define explicit handoffs and gates to prevent drift.
8. Retirement (good endings)
Retire when the promise is no longer needed or has been replaced.
Write a brief burial note in the index (▢): why, where the successor lives, and any learnings.
Archive to ⎔; mark with ꩜ in the parent index so reentry can find lineage.
9. Anti-Patterns → Repairs
Zombie pages (no appointment) → add F11 with a concrete time or retire now.
Wakes with no change-note → write one line before doing anything.
Silent forks → print parent/child links in both docs and the index.
Major edits under v1.0 → bump version and restate promise.
Private reentry → move the change-note into the shared container (▢).
10. Field Exercise — Wake One Page Now (F11)
Pick a shelved page and complete this sequence. Copy into the container and your index (▢).
Shelf tag & path: ____________________________________________________
Reason for wake: _____________________________________________________
Restated promise (△): ________________________________________________
First step (━): ______________________________________________________
Witness (❍): _________________________________________________________
Close (O): ____________________________________________________________
Change-note (one line): ______________________________________________
Next appointment (F7 time): _________________________________________
Case Box J — Three Reentries, Three Outcomes
J1) Approval Arrived → Reopen & Ship
Wake: ꩜ from ticket #321 (⬒ present).
Restate: “Publish v0.2 notes to /Product/Updates and announce (O).”
Next: post link in #announcements; window ∴ 11:00–11:15 for ✅.
Change-note: “10:05 legal ⬒ → ship; announce 11:00 — NR.”
J2) Asset Still Missing → Retire & Spin New Page
Wake: ꩜ — asset not delivered again.
Decision: retire current page; create new page ‘Photoshoot’ with its own promise.
Record: burial note in index; link to new page.
Change-note: “14:40 asset missing persists → retired; new page Photoshoot — F11 tomorrow 10:00 — NR.”
J3) Scope Was Wrong → Fork & Compare
Wake: ꩜ — repeated stalls on monolith step.
Decision: fork into ‘Two-Phase Release’ (draft + announce later).
Define gates: If draft published by 16:00, schedule announce tomorrow; else shelve fork.
Change-note: “15:10 forked to Two-Phase; gate 16:00 — NR.”
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you wake a page and move it.)
The Manual Manual — Section 11 (v1.0)
Initiate & Ship (F2 / F1)
Promise (△): By the end of this section you will deliberately open a field (F2), make one working container real (▢), and ship a small outcome to three nodes (F1) with a visible receipt and a short receive window.
1. Two Keys: F2 then F1
F2 — Make It Ours: claim the space, open the right container, name the purpose. It removes friction from the first step.
F1 — Send It: deliver a small, finished outcome to real receivers with a receipt and a short window (∴).
2. F2 — Make It Ours (field ritual, 60–120 sec)
Sit, breathe once. Say the Promise out loud (△).
Open/create the container (▢); title it with date + short name.
Clear the desk/app; close unrelated tabs; place only what belongs.
Permission check: can the receivers read what they must? Fix now.
Anchor line at top of ▢: Promise + Owner + Date.
3. F1 — Send It (the micro-ship)
Draft the outcome at hand-size (blurb, link, file, invite).
Address three receivers/nodes (3 different paths is ideal).
Ship via the chosen channel(s).
Open a 5–15 minute receive window (F7 ∴).
Record one line in ▢ with link(s) and time (❍ → O).
4. Why Three Nodes? (cascade)
Redundancy: one misses, one skims, one lands.
Diversity: team, stakeholder, and archive all see it.
Momentum: creates replies that pull the next step forward.
5. Handoff Hygiene (F9)
Name each receiver and channel (▢ link).
Define the receipt marker (✅, reply, state change).
If no receipt by window end, ping once, then escalate (named backup).
6. Anti-Patterns → Repairs
Endless prework before starting → run F2 now; write the anchor line.
Shipping without a path → paste link/path in the container and log.
One-node sends → add two more nodes (archive + team).
Huge first ship → shrink to a hand-sized outcome (F3 ▽).
7. Field Exercise — F2 → F1 Now
Run this sequence for your current page and paste it into ▢.
Container path/URL (▢): ______________________________________________
Anchor line at top (Promise + Owner + Date): _________________________
Outcome to ship (hand-sized): _______________________________________
Three nodes (name + channel): _______________________________________
Receive window (∴): _________________________________________________
Receipt marker (❍): _________________________________________________
Record line (who/when/where): _______________________________________
Case Box K — Four Tiny Ships
K1) Release Note Seed
F2: Create “2025-08-15 — v0.2 Notes” in /Product/Updates (▢).
F1: Post first 3 bullets to #announcements, email PM, paste link in Change Log.
Window: 15:00–15:15 ∴; Receipt: ✅ in #announcements or PM reply.
K2) Vendor Confirm
F2: Create ‘Vendor/Calls/2025-08/Acme-Agenda’ doc (▢); add invite URL.
F1: Send agenda link to Acme; Window: 10:00–10:15 ∴; Receipt: ‘Accepted’.
Record: invite URL filed in tracker; time stamped.
K3) Support Ticket Bump
F2: Open ticket; add Promise + Owner + Date at top.
F1: Post summary to #support, link ticket to #product, email customer.
Window: 20 minutes; Receipt: status changes to ‘Assigned’.
K4) Personal Admin
F2: Open /Finance/2025 folder; create ‘Receipts-Aug’ doc (▢).
F1: Upload latest receipt; email yourself the path; paste into doc.
Window: 5 minutes; Receipt: link opens from phone.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you F2 then F1.)
The Manual Manual — Section 12 (v1.0)
Shape & Reduce (F3 / F5 — Drop It, Make a Third)
Promise (△): By the end of this section you will cut your plan to finish‑today size (F3 ▽) and synthesize two inputs into a single, stronger artifact (F5) that you can ship or decide on now.
1. Why Shrink (F3 ▽)
Friction hides in size. Reduction exposes the first true step.
Small surfaces ship; large surfaces stall.
You can always wake the rest with F11 ꩜ later.
2. The F3 Sequence (glyph)
△ → ▢ → ▽
△ — restate the promise in 12 words.
▢ — confirm the container you will actually use.
▽ — drop non‑essentials into a Not‑Now list (kept in ▢).
3. Scope Ladder (pick the lowest rung that still delivers)
Rung A — “one sentence + link”.
Rung B — “lead paragraph + 5 bullets”.
Rung C — “single screen / single page”.
Rung D — “1 receiver / 1 approval”.
Rung E — “pilot version (3 nodes)”.
4. What to Drop (fast rules)
Anything that requires a new team or tool today.
Anything you cannot witness today (❍).
Decorations and non‑critical options.
Decisions that can be made after first ship.
5. F5 — Make a Third (synthesis)
When two inputs collide, we don’t average them—we create a third thing that’s truer than either alone.
Glyph sketch: △ → ☒ → ☒ → ⋱ → ◯
Name Input A and Input B (where they live ▢).
Extract constraints and promises from each.
Draft the Third: a single artifact that satisfies the shared promise.
Close it somewhere real (O) and link both parents.
6. Synthesis Grammar (copy & adapt)
“Combine {A} and {B} into {Third} stored at {▢}; decision/witness: {❍}.”
“Resolve conflict between {A} and {B} by choosing {Rule}; record in {▢}; notify {Receiver} (F9).”
“From {A findings} × {B constraints}, produce {one‑page} in {▢}; ship by {time} (F7).”
7. Checks & Closes for F3/F5
Check (❍): Not‑Now list saved at top of the container (▢).
Check (❍): Third artifact exists at path; parents linked.
Close (O): post the Third to receivers; paste link in change log.
8. Anti‑Patterns → Repairs
Scope yo‑yo (“small → big → small”) → pick a rung and lock it until ship.
Compromise mush → write a crisp Third; don’t blend tones or goals.
Private Not‑Now lists → put them in the shared ▢ with date and owner.
Synthesis with no receiver → add F9 handoff and receipt marker.
9. Field Exercise — Reduce, Then Make a Third
Current page: shrink once with F3, then create one Third with F5. Fill and paste into ▢.
Restated promise (12 words): _______________________________________
Container path (▢): _________________________________________________
Not‑Now items (▽): _________________________________________________
Inputs (A, B): ______________________________________________________
Third artifact: _____________________________________________________
Receiver + receipt (F9/❍): _________________________________________
Close (O): __________________________________________________________
Case Box L — Three Reductions, Three Thirds
L1) Website Hero Copy
Input A: emotive draft; Input B: product constraints doc (▢).
Third: 1‑sentence hero + 5 bullets; path: /Site/Hero v0.3 (▢).
Close: post link to #announcements; window ∴ 15:00–15:15; receipt ✅.
L2) Vendor Selection
Input A: price sheet; Input B: support SLA notes (▢).
Third: one‑page decision note with A/B ruled by ‘lowest TTR’; link parents.
Close: email decision to stakeholders; ticket state → Approved (F6 ⬒).
L3) Bug Triage
Input A: crash logs; Input B: three user calls (▢).
Third: repro steps + minimal fix spec; path: /Product/Bugs/221 (▢).
Close: assign ticket; post PR link when merged; receipt = state change.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you reduce and synthesize.)
The Manual Manual — Section 13 (v1.0)
Protect & Glide (F6 / F12 — Clerical Luck, Quiet Guard)
Promise (△): By the end of this section you will set a clean approval lane (F6 ⬒) with visible receipts and build a protected focus bubble (F12) so your plan moves through without friction or interruption.
1. What F6 Is — Clerical Luck (⬒)
F6 makes passage smooth. It is the quiet work that prevents stalls: approvals in the open, paths that resolve, names that match, versions that are obvious. The ship still sails under F1; F6 clears the channel.
Approvals are explicit and visible (no private DMs).
Receipts are state changes in a real system (ticket → Approved, doc → Signed).
Artifacts carry names, versions, and paths that match the promise.
2. The F6 Sequence (glyph)
△ → ▢ → ⬒ → ∴ → ❍ → O
△ — restate the outcome to approve (one line).
▢ — open the container; place the artifact there (single source).
⬒ — name approver(s) and their lane(s); write how they will signal.
∴ — set a short approval window (receive time).
❍ — define the witness signal (state change, ✅, signature).
O — on approval, ship or log as specified by the page.
3. Lanes & Roles (keep it simple)
Owner — edits the artifact and drives the page.
Reviewer — suggests changes; no stop power.
Approver — grants the go; one or two keys maximum.
Escalation — named backup if approval window passes.
4. Approval Grammar (copy & adapt)
“Request: {Outcome}. Path: {▢}. Approver(s): {Names/Roles}. Window: {Start–End ∴}. Receipt: {Signal/State}. Backup: {Role}. Version: {vX.Y}.”
Example: “Request: v0.2 release notes. Path: /Product/Updates/v0_2 (▢). Approver: PM. Window: 15:00–15:15 ∴. Receipt: Ticket #321 → Approved. Backup: Ops. Version: v0.2.”
5. F12 — Quiet Guard (focus bubble)
F12 protects the presence needed to finish. It is a boundary you can feel: fewer inputs, one container, one promise, one time block.
Glyph: △ → ⬒ → ▢ → ❍ → O
Set a 25–50 minute block; title it “Quiet Guard — {Outcome}”.
Hard boundary: DND on; notifications off; door sign if in-room.
Single surface: one document/window; everything else parked.
Parking lot: create a small list at top for intruding thoughts; do not branch during the block.
Close with a visible change in ▢ (save, post, commit, send).
6. Glide Checklist (preflight)
Names match across doc, ticket, and calendar.
Version appears in title and change log (top of doc).
Links resolve; attachments open; file types are right.
Accessibility: alt text on images; readable contrast if shipping public.
Approval window placed on calendar; receivers named; backup present.
7. Anti-Patterns → Repairs
Approvals in DMs → move to a shared ▢ with a state change.
Endless reviewers → lock lanes: one reviewer, one approver (two-key max).
Stealth edits after approval → bump version; log change-note; re-approve if scope changed.
Fake deep work (many tabs) → Quiet Guard: one surface, one promise.
“Tapping to check” during block → parking lot the thought; resume after O.
8. Field Exercise — Build Your Shield & Bubble
Fill these; copy to your page and calendar.
Artifact path (▢): _________________________________________________
Approver(s) + receipt (⬒/❍): _______________________________________
Approval window (∴): _______________________________________________
Backup (role): _____________________________________________________
Quiet Guard block (length/time): ___________________________________
What closes at O: _________________________________________________
Case Box M — Glide Paths in Practice
M1) Marketing Email — One-Key Approval
Path: /Marketing/Emails/Launch-v0_2 (▢).
Approver: Marketing Lead; Window: 14:00–14:15 ∴; Receipt: MailerLite ‘Approved’.
Quiet Guard: 30 min to finalize copy; O: schedule send + paste link in log.
M2) Legal Notice — Two Keys
Path: /Legal/Notices/Terms-Aug (▢).
Approvers: Counsel + PM; Window: 10:00–10:20 ∴; Receipt: Ticket → Approved with both checks.
Quiet Guard: 45 min to integrate edits; O: post PDF + notify #announcements.
M3) Design Asset — Focus & Hand-off
Path: /Design/Hero-v0_3 (▢).
Quiet Guard: 50 min Figma work; O: export PNG + upload; F9 handoff to WebDev; Receipt: ✅ in #web within 15 min.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you run F6 or F12.)
The Manual Manual — Section 14 (v1.0)
Align to Time — Deep F7 (Cadence, Critical Path, Buffers)
Promise (△): By the end of this section you will set a working cadence, map a critical path for your page sequence, and place buffers and windows so the plan moves on time without drama.
1. Time Surfaces (four lenses)
Clock — exact moments (16:00 PT).
Calendar — blocks, windows, and deadlines (∴ / O).
Rhythm — repeating beats (daily/weekly/monthly).
Season — arcs and constraints (launch week, holidays, quarters).
2. F7 Design Elements
Anchors — fixed points (kickoff, release, review).
Windows (∴) — short, named receive periods that open/close on time.
Deadlines — latest acceptable moments (ship or branch).
Gates — go/no‑go decisions that select the next branch.
3. Cadence Ladder (pick your beats)
Daily: two hand-sized outcomes max + one Quiet Guard block (F12).
Weekly: one review (F4 mini reset + F11 reentry) and one announce (F1).
Fortnight/Sprint: one theme; retire stale pages (F8) on day 10.
Monthly: harvest & change-log; publish one public artifact (O).
Quarterly: choose three rails; everything else becomes Not‑Now (▽).
4. Critical Path (lite) — find the chain that sets the date
We don’t need a Gantt to see the hinge. Do this in a doc (▢).
List the steps/pages that must happen in order (owner + duration).
Mark dependencies (A → B).
Sum durations across the longest dependent chain = your critical path.
Everything else is slack; run it in parallel or drop it (▽).
5. Buffers (three kinds)
Focus buffer — a Quiet Guard block before any hinge step (F12).
Receive buffer — add 5–15 minutes after windows for late signals (∴).
Ship buffer — a small cushion before public deadlines to avoid night work.
6. Time Math (safe & simple)
Earliest Start/Finish: ES = max(all predecessors’ EF). EF = ES + duration.
Slack = Latest Start − Earliest Start. Zero‑slack tasks live on the path.
Two‑train rule: never double‑book the same owner on parallel zero‑slack steps.
7. Timezones & Handoffs (follow the sun)
Always write absolute times with zone (e.g., 16:00 PT / 23:00 UTC).
Schedule overlap windows (≥30–60 min) for F9 handoffs; define the receipt.
If no overlap exists, use paired windows: sender closes at T; receiver opens at T+Δ.
8. Capacity Plan (don’t overload the day)
Max two significant outcomes per person per day.
10‑step week rule: team commits to 10 clear steps; extras become Not‑Now (▽).
Hold 20% uncommitted time for resets, issues, and reentry (F4/F11).
9. Anti‑Patterns → Repairs
“ASAP/EOD” → replace with precise times + windows.
No buffers on hinge steps → add F12 before, receive buffer after.
Everything sequential → split independents; run in parallel.
Hidden timezone pain → print zones in titles; use overlap windows.
Owner overload → reassign or move to Not‑Now; protect the path.
10. Worksheet — Build Your Time Frame (copy to ▢ + calendar)
Fill this for your current plan sequence.
Anchors: _____________________________________________________________
Critical chain (A → B → C): _________________________________________
Owner per chain step: ________________________________________________
Durations (each): ____________________________________________________
Windows (∴) + receipts (❍): _________________________________________
Buffers (focus/receive/ship): _______________________________________
Public deadline (O): _________________________________________________
Slack items (parallel or drop): ______________________________________
Case Box N — Three Alignments
N1) Launch Week — Path to Wednesday 16:00 PT
Anchor: Release at Wed 16:00 PT; announce at 16:15 (O).
Chain: QA → Legal ⬒ → Publish → Announce.
Windows: QA 13:00–13:30 ∴ (checklist in ▢); Legal 14:00–14:15 ∴ (ticket → Approved).
Buffers: 30‑min Quiet Guard before publish; 15‑min receive buffer after announce.
Gate: If Legal not ⬒ by 14:15 → slip release to Thu 10:00; notify now (F9).
N2) Vendor Integration — US ↔︎ EU
Overlap: 08:00–09:00 PT (17:00–18:00 CET) daily ∴ for handoffs.
Chain: API key → sandbox test → config merge → live test → invoice.
Receipts: PR merged; test order succeeds; invoice paid (▢/❍).
Buffers: 24‑hour ship buffer before go‑live to avoid late‑night support.
N3) Content Campaign — Monthly Cadence
Anchors: Editorial freeze E‑3 (Mon), publish E (Thu) 10:00 PT.
Windows: Design review Tue 13:00–13:15 ∴; Legal ⬒ Tue 14:00–14:15 ∴.
Gate: If asset not in by Mon 16:00 → swap to backup post; record in change log.
Harvest: end‑month change‑log + public PDF (O).
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you align a sequence with F7.)
The Manual Manual — Section 15 (v1.0)
Hold, Pour, Return (F10 / F11 — Emotional Load & Reentry)
Promise (△): By the end of this section you will contain emotional load without derailing the plan, using F10 to hold and pour in a safe container (▢), then F11 to reenter with a finish-today step.
1. What F10 Is (gentle and practical)
F10 is a hand-sized ritual for when the work is heavy. We give the feeling a place to sit so hands can move again. Not therapy, not avoidance—a containerized pause that preserves the plan’s momentum.
2. The F10 Sequence (glyph)
❍ → ▢ → ⬒ → ▽ → O
❍ — Notice: name the feeling as a weather report (“fear”, “shame”, “grief”, “anger”, “fog”).
▢ — Cup: open the container that will hold it (journal line, ‘Load’ doc, index card).
⬒ — Shield: set a 2-minute boundary (timer), privacy, and a rule: “this does not leave the cup.”
▽ — Pour: write one line (≤ 12 words) in plain language; no analysis. Optionally add one reason.
O — Close: mark a check in the margin, then return to the plan (F11 if needed).
3. Cup Types (choose one you can reach)
Journal line (paper) — fastest; tear-off or keep bound.
Private ‘Load’ doc in /Personal or project index (▢).
3×5 card — write and box; file or shred after logging.
Voice memo (≤ 30 sec) — title with date + tag; paste path in ▢.
4. When to Use F10 (tripwires)
Hands shake, breath shallow, scrolling impulse, or tight jaw.
Ruminating the same sentence more than twice.
Avoiding the next visible verb.
Conflict energy: urge to DM or post a vent.
After loss, bad news, or high-stakes ship.
5. One-Line Fear (how to write it)
Write like weather: “Fear: they will say no.”
Keep it under 12 words; no metaphors; no character judgments.
Optional: add one cause line (“Because …”). Stop there.
Finish with a physical cue: one slow breath; shoulders drop.
6. Guardrails & Hygiene
Time-box: 2 minutes; use a timer.
Privacy: the cup is not for the timeline; do not paste in public threads.
Containment: no decisions inside the cup; decisions live on the plan page.
Record minimum: date/time + 3-word tag (“fear/ship/cost”) in ▢.
7. Pairing F10 with the Plan (F7, F6, F11)
After O, open a 5–10 minute receive window (∴) to sense if you can continue.
If the feeling points to a real risk, create one check or gate (❍/F7).
If it requires approval or safety, route via F6 ⬒ (e.g., ask for a second set of eyes).
If you cannot continue now, branch with F8 and schedule F11 for the next appointment.
8. Anti-Patterns → Repairs
Doomscrolling disguised as research → set a 10-minute window; produce one artifact or stop.
Venting in public channels → pour in private cup; craft a handoff if action needed (F9).
Repeat pours with no reentry → schedule F11; restate promise small; move one step.
Therapy-by-colleague → keep the cup personal; ask for a boundary if needed.
9. Field Exercise — Cup & Return
Run F10 once now; then set a tiny F11 reentry. Copy to ▢.
Cup chosen (▢): ______________________________________________________
One-line feeling (≤12 words): ________________________________________
Optional cause (≤12 words): __________________________________________
Boundary (minutes, privacy rule): ____________________________________
Reentry (F11) time: _________________________________________________
First step on reentry (━): ___________________________________________
Record line (who/when/where): _______________________________________
Case Box O — Four Loads, Four Returns
O1) Shipping Anxiety
F10: “Fear: the email will annoy them.”
Cup: journal line; 2 min; private.
F11: shrink promise to “send to 1 node”; O: paste link in log; Window: 5 min; Receipt: ✅.
O2) Conflict Heat
F10: “Anger: they ignored the spec.”
Cup: ‘Load’ doc; write one cause line; stop.
F11: pick one action: file the mismatch in ticket; request review window ∴.
Guardrail: no DMs until record exists in ▢.
O3) Grief / Bad News
F10: “Grief: can’t focus today.”
Cup: voice memo (30 sec); title with date; path in ▢.
Decision: branch page with F8; wake tomorrow 10:00 (F11); first step = smallest possible (open doc, write one sentence).
O4) Creative Block
F10: “Fear: it won’t be good.”
Cup: 3×5 card; shred after O.
Reentry: Quiet Guard 25 min; step = write lead + 5 bullets; close by pasting into doc (▢).
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you hold, pour, and return.)
The Manual Manual — Section 16 (v1.0)
Proof Loops & Log Gates
Promise (△): By the end of this section you will design a repeatable proof loop, set a 10-run Log Gate, and measure O vs. O+ so practice turns into a working habit.
1. What a Proof Loop Is
A proof loop is a short, repeatable run of your plan page to cross a threshold. Ten passes is the default. The click—the felt ease—is O+; closure as promised is O.
2. The Log Gate (design)
Ten tiny boxes (▢▢▢▢▢▢▢▢▢▢) at the bottom of the page.
Fill one box per completed run (O). After the tenth, run once more; mark O+ only if the click happens.
Place date/time initials above the strip if needed; keep ink light.
3. Loop Anatomy (per run)
F2: claim field; open container (▢).
Run 3–7 steps (━); close with O.
Mark one box; write one record line (who/when/where).
If it stalls → F8 shelf + F11 appointment; do not force the run.
4. Measures That Matter
Time-to-first-O (minutes).
Error rate (% of runs that needed repair).
Handoff clarity (receipts present?).
Ease score (1–5, optional note).
5. Loop Sizes (pick one)
Tiny: 5-run gate (skill warm-up).
Standard: 10-run gate (new practice).
Long: 20-run gate (team habit).
6. Anti-Patterns → Repairs
Skipping the strip → redraw the gate; log from the next run—no guilt.
Changing rules mid-loop → finish the current ten; rewrite on a new page.
Counting attempts as runs → only O counts; retries are part of a run.
7. Worksheet — Build Your Loop
Practice/Page: ______________________________________________
Gate size (5/10/20): _________ Start date: _________________
Measure(s): __________________________________________________
O+ criterion (one line): ____________________________________
Case Box P — Three Loops
P1) Daily Email Bridge
Run: send one bridge note; paste link in log (O).
Gate: 10 runs; O+ when replies become predictable.
P2) Support Triage
Run: process 5 tickets to ‘Assigned’ with receipts.
Gate: 10 runs; O+ when average time < 12 min.
P3) Writing Warm-up
Run: lead + 5 bullets filed to draft (▢).
Gate: 10 runs; O+ when drafts start under 5 minutes.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one per completed run.)
The Manual Manual — Section 17 (v1.0)
Metrics That Matter (Small, True, and Visible)
Promise (△): By the end of this section you will choose three small, observable metrics per page and one weekly roll-up so the plan stays honest without drowning in dashboards.
1. Three-Number Rule (per page)
T1: Time-to-first-result (minutes to O).
T2: Errors or repairs (count per run).
T3: Handoff clarity (receipts present: yes/no).
2. Weekly Roll-up (team view)
Throughput: pages that shipped (count of O).
WIP: pages in progress (count).
Blocked: pages shelved via F8 (count + tags).
3. Where Metrics Live (▢)
Top of the container: a tiny table (date, O, errors, receipt).
Change Log: newest-first, keep entries short.
Index page: one-line per page, link to container.
4. Safe Formulas (no drama)
Avg T1 = Σ minutes to O / runs.
Error % = repairs / runs.
Receipt % = handoffs with signals / handoffs total.
5. Anti-Patterns → Repairs
Vanity metrics → delete anything not tied to O, ❍, or F7.
Lag-only metrics → add one leading indicator (window met?).
Private spreadsheets → move to shared ▢; paste link on page.
6. Worksheet — Your Three
T1: ________________ T2: ________________ T3: ________________
Weekly roll-up note (1 line): ______________________________________
Case Box Q — Metric Sets
Q1) Release Page
T1: minutes to publish; T2: approval retries; T3: ✅ in #announcements.
Q2) Vendor Onboarding
T1: days to first meeting; T2: missing docs; T3: calendar ‘Accepted’.
Q3) Support Workflow
T1: minutes to first reply; T2: reopen count; T3: ticket state receipts.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one per week you track cleanly.)
The Manual Manual — Section 18 (v1.0)
From Page to Program (Ladders & Rails)
Promise (△): By the end of this section you will sequence pages into ladders and rails, run a weekly review, and keep a clean index so individual plan pages become a reliable program.
1. Ladders vs. Rails
Ladder: a stack of pages that build depth (learners, features).
Rail: a recurring path that carries operations (support, releases).
2. The Index (one page to find them all)
Title: “Program Index — {Project}”.
Sections: Ladders, Rails, Archive (꩜/⎔ links).
One line per page: Promise, Owner, Path (▢), Status (Open/O/⎔).
3. Weekly Review (F4 + F11)
Run F4 mini reset; review each Open page; shelf or shrink.
Wake exactly three pages (F11) for the next week; retire others.
Publish a one-paragraph weekly note with three ships (F1).
4. Program Risks & Gates
Gate: ‘If more than 7 Open pages → force-shelf to ≤7’.
Gate: ‘If no ship this week → Quiet Guard block + one tiny F1 by Friday’.
Gate: ‘If path owner overloaded → reassign or Not-Now (▽)’.
5. Anti-Patterns → Repairs
Roadmap with no pages → convert to pages now; index them.
Program drift → add F7 anchors and windows; print them.
Backlog hoarding → Not-Now list lives in ▢; reviewed monthly.
6. Worksheet — Build Your Index
Program name: ______________________________________________
Ladders (pages): ____________________________________________
Rails (pages): ______________________________________________
Three wakes for next week (F11): ____________________________
Case Box R — Program Patterns
R1) Product Program
Ladder: Research → Spec → Draft → QA → Publish.
Rail: Release weekly; Index: /Product/Index (▢).
R2) Partnership Program
Ladder: Intro → Pilot → Review → Expansion.
Rail: Monthly check-ins; Index: /Partners/Index (▢).
R3) Content Program
Ladder: Idea → Draft → Design → Review → Publish.
Rail: Thursday publish; Index: /Content/Index (▢).
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each week your program ships.)
The Manual Manual — Section 19 (v1.0)
Team Usage & Governance (Draft → Field Test → Release)
Promise (△): By the end of this section you will operate a simple governance loop so pages improve in the field, changes are logged, and the library stays trustworthy.
1. Roles
Owner — writes and runs the page.
Clerk — maintains change logs and index links (▢).
Librarian — reviews for clarity; archives (⎔) retired versions.
Chair — calls decisions; resolves stalemates; approves major changes.
2. Lifecycle
Draft → 20-minute field test → Revise → Release → Archive.
Release note: one paragraph; path; version; date.
Archive note: why retired; successor page link (꩜/⎔).
3. Change Control
Minor (vX.Y): wording fixes; no promise change; Clerk logs.
Major (vY.0): promise or structure change; Chair approval.
Emergency change: F4 fix; log within 24 hours.
4. Reviews
Clarity review: verbs, checks, containers, roles present.
Safety review: data/privacy; approvals visible (F6).
Usability review: run in 20 minutes; note friction points.
5. License & Credits
Default: CC-BY-NC-SA printed in colophon.
Credit contributors in change log; keep names near their lines.
6. Anti-Patterns → Repairs
Shadow pages → fold in or retire; update index.
No change notes → add them at top; newest-first.
Shelf with no F11 → assign a wake time or retire now.
7. Worksheet — Your Governance Loop
Who is Owner/Clerk/Librarian/Chair? ________________________
Release cadence: __________________________________________
Where do change logs live (▢ path)? ________________________
Case Box S — Library in Motion
S1) Fast Fix
Field test shows confusion; Owner edits verbs; Clerk bumps v0.4; Librarian notes change.
S2) Major Rewrite
Promise changed; Chair approves v1.0; release note posted; old page archived (⎔).
S3) Retirement
Page obsolete; archive note with successor; index links updated.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time governance runs cleanly.)
The Manual Manual — Section 20 (v1.0)
Distribution & Maintenance (Print, QR, Archive)
Promise (△): By the end of this section you will prepare printable sets with QR links to living copies, publish a public PDF, and keep a clean archive so the manual stays useful.
1. Print Set (field kit)
Paper: 24–28 lb for durability; grayscale ok; margin room for notes.
Bundle: Plan Page template + Glyph Legend + top 20 pages.
Footer: F4 on every page; Log Gate present.
2. QR to Living Copy
Each printed page carries a QR to its ▢ container.
QR caption includes version and date.
If page bumps major version, QR resolves to new canonical; old PDF remains in ⎔.
3. Channels
Team: #announcements with change notes and links.
External: public PDF + checksum; lightweight landing page.
Index: one master doc with all paths (▢).
4. Maintenance Cadence
Weekly: ship list (O); retire stale pages (F8).
Monthly: harvest learnings; bump versions; update the public PDF.
Quarterly: deprecate low-use pages; celebrate the top three ships.
5. Cost & Supply
Estimate: pages × copies × print cost; keep a petty cash line.
Stock: keep 10 spare kits in a labeled box; restock monthly.
6. Anti-Patterns → Repairs
Dead QR links → point to canonical index, not file versions.
One-off PDFs → publish a stable set; archive superseded copies.
Unlabeled stacks → print cover sheets with date and contents.
7. Worksheet — Your Distribution Plan
Audience(s): _______________________________________________
Kit contents: ______________________________________________
QR target (▢ path): ________________________________________
Public PDF location: _______________________________________
Archive path (⎔): __________________________________________
Case Box T — Two Launches
T1) Internal Rollout
Print 50 kits; QR to team index; announce in #announcements; window ∴ 15 min for ✅; track receipts.
T2) Public Drop
Post public PDF; checksum in release note; archive v1.0; set F11 for v1.1 review next month.
Log Gate: □ □ □ □ □ □ □ □ □ □ (Fill one each time you ship or update the set.)
Appendix A — Glyph Legend
Exhibit B — Glyph Legend & F4 Footer Plate
Core GodSet (doctrinal):
F1 – Send It: △ → ▢ → ━ → ▢▢▢ → O — Initiate & deliver; three nodes of return.
F2 – Make It Ours: △ → /|\ → ▢ → ❍ → O — Claim the room/desk; bless the container.
F3 – Drop It: △ → ▢ → ▽ — Simple dissolution; scope cuts.
F4 – Air It Out: ❍ → ▽ → △ → /|\ → ▢ → O — Reset a stale page; reopen cleanly.
F5 – Make a Third: △ → ☒ → ☒ → ⋱ → ◯ — Synthesis out of two inputs.
F6 – Clerical Luck: △ → ▢ → ⬒ → ∴ → O — Shielded passage / approvals.
F7 – Catch the Train: △ → ▢ → ━ → ∴ → O — Time alignment; thresholds.
F8 – Tag & Shelf: ▢(△) → —— → ┃ → ▢ → ▢̷ → ⎔(◯) — Failed form archive; no shame.
F9 – Link Two: △ → ▢ → ▢ → ━ → O — Social bridge; clear handoff.
F10 – Hold & Pour: ❍ → ▢ → ⬒ → ▽ → O — Grief drain; continue work.
F11 – Wake the File: ꩜ → △ → ▢ → ━ → O — Archive reentry; versioning.
F12 – Quiet Guard: △ → ⬒ → ▢ → ❍ → O — Protected presence; focus bubble.
Footer Plate (copy-paste to any sheet):
Emergency Reset (F4): ❍ Notice → ▽ Exhale → △ Remember intent → /|\ Align → ▢ Re-box → O Seal
Appendix B — Plan Page Template (Blank)
Exhibit A — Plan Page v0.1 (GodSet Integrated)
Use this one-page sheet to make and execute a plan. Fill it top-to-bottom; do not add theory. Emergency reset (F4) is in the footer.
Promise (intent): △ One line outcome for this page.
Scope / Constraints: F3 △ → ▢ → ▽ Name what you will NOT do; cut gently.
Tools / Containers: ▢ Docs, rooms, threads, apps to use.
Roles & Handoffs: F9 △ → ▢ → ▢ → ━ → O Owner of each step; who receives the output.
Schedule / Thresholds: F7 △ → ▢ → ━ → ∴ → O Deadlines, gates, and receive windows.
Steps (verbs that move bodies) ━
1. ___________________________________________
2. ___________________________________________
3. ___________________________________________
4. ___________________________________________
5. ___________________________________________
6. ___________________________________________
7. ___________________________________________
Checks (witness before closing): ❍ What must be true/visible to close?
Failure Branch (clean exit): F8 ▢(△) → —— → ┃ → ▢ → ▢̷ → ⎔(◯) If stalled, tag & shelf. Note why. Schedule F11.
Emotional Load (optional): F10 ❍ → ▢ → ⬒ → ▽ → O Name it; put it in the cup; let it drain.
Reentry Tag: F11 ꩜ → △ → ▢ → ━ → O When/why this reopens; next poke.
Close: O Immediate action when done.
Log Gate (fill one each run): ▢ ▢ ▢ ▢ ▢ ▢ ▢ ▢ ▢ ▢
Change Log (Master v1.0)
2025-08-15 — v1.0 — First master assembly. Sections 1–20 included; front matter + appendices A–B. — Clerk