Operating Manual

Use with Chapter 14. Connect existing records into a procedure for one recurring task. This template is a book-developed practice, not a new maturity model or a substitute for domain expertise.

Blank reusable template

Manual name and revision:

Task and useful result:

Person responsible for consequential judgment:

Existing project index and current-instruction route:

Charter and relevant permission boundary:

Supporting rationale, source, knowledge-map, and verdict locations:

Triggers and operations

Working packet: Task, applicable instruction, authorized input, required output, review criteria, relevant support, and known uncertainty.

What stays outside the packet:

What can be proposed by an assistant:

What requires my judgment:

Capacity rule when review cannot keep up:

Inspect one completed attempt

Literal input or stable source location:

Instruction actually supplied:

Actual output or saved location:

Review decision and precise reason:

What the decision does not approve:

Approved saved change, if any:

Reopened location and observed saved state:

Fresh use or regression check when appropriate:

Handoff

Completed:

Pending, with reason:

Records actually changed and checked:

Current instruction route:

Next authorized action and condition for proceeding:

Material not established by the evidence:

Manual fallback

How I perform the bounded task without AI:

Which unavailable capability would prevent completion:

What I should explain unaided:

Fictional worked sample: Audy and Himura Inc.

Manual: operating-manual-v1.

Task: Prepare and review a synthetic action-list example for the proposed thirty-minute workshop.

Authority: Audy reviews consequential meaning under the memory charter. The project index leads to the existing learning-loop-v1 selector, which selects instructions-v3. The knowledge map provides navigation. The worked rationale, distillation record, and verdict V13-01 explain and support behavior; they do not compete as selectors.

Scope: No customer communication, real commitments, learner-outcome claims, or instruction change is authorized merely by performing the draft.

Worked input and acceptable output

Synthetic input:

S14:1 The facilitator agreed to send the revised exercise notes on Thursday.

S14:2 The group agreed to ask the venue about access soon; no owner was assigned.

S14:3 A reminder on Friday was suggested, but no decision was made.

Review: An actual output may use different wording, but must preserve these distinctions. Assigning the venue inquiry to the facilitator or dating it Friday requires rewrite because the source supports neither. Erasing the explicit Thursday also fails.

Bounded acceptance: Accept this representation of the synthetic input after comparison. This does not validate the workshop or authorize any real action. No new general principle or instruction version is necessary merely because the existing rule worked.

Worked interruption

Synthetic input A:1: “The facilitator agreed to circulate the revised outline Monday.” B:1: “The facilitator agreed to circulate the revised outline Tuesday.” No order or supersession is established.

Acceptable interim output: shared action and owner retained; Monday (A:1) and Tuesday (B:1) shown as conflicting; applicable deadline unresolved; clarification required before one deadline can be presented as confirmed.

Handoff: “Shared action and owner extracted. Deadline remains Monday versus Tuesday. No superseding evidence supplied. Output is an unresolved account for review, not a confirmed schedule. Next action: obtain authorized clarification if proceeding beyond representation.” This specimen points to the interruption input and output; link your actual records when performing the exercise.

Resumption condition: New evidence is required to resolve the deadline. A new session alone does not satisfy that condition.

Manual fallback: Read source, fill the same table, compare each material field against its supporting phrase, and retain the same uncertainty. Human-produced work receives the same review.

Acceptance criteria

• One bounded task, responsible person, and current-instruction route are explicit.
• Triggers identify concrete operations and pending states.
• The working packet preserves source status and permission boundaries.
• At least one literal input and actual output can be compared.
• A verdict, completed rewrite, saved-state check, and later reuse are distinguishable.
• An interrupted task resumes with unresolved conditions intact.
• Retention follows the charter; routine success does not force a new durable rule.
• A manual fallback and unaided explanation expose what the operator understands.

Common failure and repair