MidPacific Soviet of Words and Letters Instructional Technologies / FM-MM-01
Field Administration / FM-MM-01 / Master Manuscript v1.0

The Manual Manual
How to Make and Execute a Plan

Norman Rule / One-Page Planning Method / GodSet Operator Routing

A practical workbook for turning one bounded outcome into a plan you can begin, witness, close, and run again.

Open Archive PDF Write It / Run It / Close It
84-page A5 workbook Worksheets and reusable plan template Secure checkout

First issued: 15 August 2018
License: CC BY-NC-SA 4.0   /   Edition: Master Manuscript v1.0
View the MPSoL archive record

A one-page method for work that must actually move
Start Here — What This Book Does

Make the work small enough to start.
Exact enough to finish.

The Manual Manual is for the moment when intention is present but execution is not. It replaces the swollen project plan with one bounded page: a result, the place where the work happens, a short sequence of visible actions, proof that the result occurred, and a closing act.

It is deliberately usable under load. You do not have to become organized first. You name what can be finished—or advanced to a stated gate—today, then leave a record your future self or another operator can follow.

Promise / △

Name One Result

Write a singular, observable outcome sized to finish today or reach a named gate. Begin with a verb and bind it to a real destination.

Container / ▢

Give Work a Place

Name the document, room, thread, call, folder, or app where each action occurs and where its evidence will remain.

Steps / ━

Use Visible Actions

Write three to seven actions that another person could perform without interpretation. Each step must change the state of something real.

Witness + Close / ❍ O

Prove It and End It

Define the signal, receipt, file, or state change that counts as done. Close by sending, filing, publishing, notifying, or recording.

One page.
No hidden work.

The plan page holds only what execution requires. Technical, legal, safety, contractual, and professional requirements still govern; the page names those sources and the authority required to proceed.

01 / Establish

Promise + Authority

What result is authorized now?

Name the controlling source, constraints, approval or stop authority, and the observable result this page will deliver.

Scope
One bounded outcome
Size
Today or named gate
Rule
No absent prerequisite
02 / Move

Containers + Steps

Where does action happen?

Open the actual tools and containers, then write three to seven verb-first actions with explicit owners, receivers, and timing.

Actions
Observable
Handoffs
Receipt required
Timing
Exact windows
03 / Complete

Checks + Close

What proves the result?

Attach located evidence, define the failure branch and reentry appointment, perform the closing act, and mark the Log Gate.

Proof
Third-party verifiable
Failure
Clean exit
Record
Who / when / where
Four-Part Field Course

Grammar first.
Coordination next. Proof after.

Twenty chapters move from the smallest unit of a plan to repeatable team programs. Each chapter ends in a worksheet, case box, or Log Gate so the method is practiced rather than admired.

I

Plan Grammar

What a plan is, the Promise Sentence, containers, executable steps, witnesses, closure, and the complete one-page plan.

II

Movement + Coordination

Roles, handoffs, receipt markers, deadlines, receive windows, failure branches, versioning, reentry, approvals, and protected focus.

III

Proof + Stewardship

Proof loops, ten-run Log Gates, useful metrics, program indexes, team governance, distribution, and maintenance.

IV

Reference

A complete F1–F12 glyph legend and a blank plan-page template ready to copy, print, write on, and run.

“By the end of the first page, you will have a stated result, an executable next action, and a record.”
— Norman Rule, The Manual Manual
When Plans Meet Reality

The method includes the stall.

Handoffs That Close

Every transfer names an owner, receiver, channel, object, receipt signal, window, and backup. No receipt means no completed handoff.

Time With Teeth

Replace ASAP and EOD with deadlines, short receive windows, duration blocks, and threshold gates tied to observable signals.

Clean Failure Branches

When work cannot proceed, tag and shelf it, record the blocker, schedule the next review, and reopen it through a versioned next move.

Load-Aware Return

Use the Hold & Pour procedure when emotional load interferes: record privately, choose the smallest safe return, and resume without pretending the load is absent.

Field Edition

Write in it.
Run the page.

The paperback is built as an active object: compact teaching sequences, fill-in exercises, case boxes, ten-run Log Gates, a glyph reference, and a reusable plan-page template.

Archive Edition

Read the Complete Manual

$0

The full 84-page workbook with a SCAD-selected further-reading appendix and direct links into the MPSoL archive.

Open the Free PDF
A5 / 148 × 210 mm84 pagesPerfect boundBy Norman RuleCC BY-NC-SA 4.0SKU FM-MM-01

Twelve operators.
Use only the one the page needs.

The Manual Manual turns the GodSet glyphs into working routes: initiate and deliver, establish the field, reduce scope, reset, synthesize, clear approvals, align time, shelf, hand off, hold load, reenter, and protect focus.

F1–F4 / Start + Reset

Send / Establish / Reduce / Air Out

Open the correct conditions, ship a bounded result, cut scope without breaking the promise, or reset an inactive page.

F5–F8 / Shape + Govern

Synthesize / Approve / Time / Shelf

Make a third form from two inputs, document authority, bind work to exact windows, or leave a clean record when blocked.

F9–F12 / Coordinate + Return

Link / Hold / Wake / Guard

Create explicit handoffs, contain emotional load, reopen archived work with a next move, and protect a focus period.