Book Isle procedure reading: check stopping conditions, exceptions and unfinished states

When instructions say repeat the previous step, readers need a stopping rule and an exception route. Preserve a short procedure in Book Isle and manually identify input, branches, stopping and output. The example classifies invented cards, not real devices. It checks textual completeness rather than repeating numerical algorithm tracing, and assumes no workflow execution or completion judgement by the app.

Fix a short procedure and task scope

Choose an authorised completed instruction with a clear start and record book, edition, chapter, step number, purpose and adjacent limits. Distinguish procedure, case narrative and suggestion rather than making all mandatory. Begin with three to five steps, excluding a whole policy chapter or hazardous operations. Record inputs and expected outputs, marking absent ones unspecified. Separate paraphrase from excerpts without adding a stopping rule merely to make a neat chart; those gaps are precisely what the audit examines.

Write condition and destination for each branch

Record if, unless, otherwise and until with action and destination, not verbs alone. In an invented three-card procedure, numbered cards go to classified, unnumbered ones to review, then the next card is taken; finish only after checking all. A and C are numbered, B unnumbered, producing two classified and one review item. These are original values, not source data. If an instruction says inspect exceptions but gives no onward route, mark the branch incomplete instead of assuming skip or retry.

Distinguish finish, skip and manual review

Finish reaches the task’s stated stopping rule; skip leaves an action undone; manual review leaves further work. Preserve the source’s meanings rather than calling all completed. B going to review is not successful classification, but may allow the batch inspection to finish if the task is inspect all rather than resolve all. Separate item and batch states. If the source requires resolving every review item first, do not import this example’s stopping rule; verify its own definition.

Check progress and exits in loops

For return or retry loops, identify what changes each iteration and what exits it. The card example must advance to a new object rather than stay at B while claiming traversal. Record absent retry limits or exception exits as unspecified rather than inventing three attempts. Stopping your reading is a pause with a reason, not satisfaction of the procedure’s termination condition. Check the description on paper or in personal notes without repeated real-system operations to prove termination.

Test the text with ordinary and exceptional cases

Walk A, B and C through input, condition, action, next step and final state, retaining three cards total. In a second invented case change only B to numbered; unchanged rules produce three classified and zero review. Both are consistency tests, not the author’s observed results. If overlapping conditions send a card two places, inspect priority or permission for multiple membership rather than choosing the first branch automatically. Preserve missing information instead of forcing totals to hide ambiguous rules.

Leave and return to recheck source conditions

Keep supported references or external locators for procedure, exception explanation and output definition, with step numbers and distinctive phrases. Leave the Book Isle reader and return to check negation, only, until and otherwise sentence by sentence. Reopen copies/exports to inspect branch indentation, numbering and unspecified labels; plain prose works without a special form. Recheck step numbers and stopping rules after edition changes rather than transferring by title alone. Preserve source and additions separately for later corrections.

Do not treat unknown input as a false condition

If B’s number is obscured, it is no longer the original definitely unnumbered case. Mark number unknown and inspect rules for rechecking, holding or stopping instead of forcing the no-number branch to finish the table. Preserve absent handling as a source gap, not your chosen repair. The original two-classified/one-review result applies to known attributes and does not establish the obscured case’s result. Distinguish unobserved from absent so input quality is not mistaken for faulty branching. Further verification is a next action, not an automatically supplied attribute.

Finish the stopping/unfinished boundary record

Finish with branch destinations, stopping rule, unresolved items and whether you merely paused. Review status depends on definitions, repeated loops may never advance, and a missing retry limit cannot receive a familiar invented value without changing the procedure. Retain one source question. Scope the result to textual completeness, not actual execution or safety review; a clear card does not mean the app ran or accepted the process.

Related guides and sources

Book Isle algorithm appendices: hand-trace each state with three invented inputs; Book Isle definition reading: necessary conditions, sufficient conditions and counterexamples.

Checked on November 6, 2026: Apple public version information lists Book Isle 1.1.4, requiring iOS / iPadOS 15.6 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.