Agentic Process Engineering · v0.1.16

• Fit the four forms of initiative on one page: each row opens on who chooses the next step, and the four diagrams share one layout.
• Read Foundations, Examine and the conclusion more directly: remove repeated statements, keep each one where the reader needs it, and describe the conclusion's figure in one paragraph.
• Correct details of the Paper Trader, coaching and Savey cases against their sources, and cite Sky News for what DPD's chat could not do.
• Extend the glossary with the terms readers meet most often, including recipient, proposal, approval, admission verdict, envelope and synthesis, each defined in the book's own words.
• Use hand off for passing work to a recipient, in the prose and in the diagram labels, and redraw the diagrams of the customer chat chapter on the common figure grammar.
• Give every source note a short form with clickable labels, and keep glossary definitions and note calls with their text in the PDF.

Agentic Process Engineering · v0.1.15

• Revise the prose of Foundations, Examine and the conclusion to explain terms where they are needed and distinguish reported events from proposed designs.
• Clarify the relationship between SECI, organisational memory and shared guidance; explain how source marking passes from an operator’s practice to a process rule, and how a trace supports the case record.
• Keep current-order corrections separate from changes to stock prices, and distinguish a pending experience note from its still-absent outcome verdict. Give the constructed invoice flow a concrete output and acceptance check.
• Harmonise case, approval and synthesis terminology while preserving technical names and the scope of each operator’s authority.
• Shorten source notes with clickable reference labels, keep notes with their calls, and remove inherited spacing from closing questions.
• Correct the Follow caption, rename the worked customer-chat chapter with hand off, and replace its workshop cover with the customer-service design illustration.

Agentic Process Engineering · v0.1.14

• Open each Foundations chapter on one well-known case instead of a single fictional thread: the DPD customer chat in Frame, the one-dollar Tahoe in Delegate, the $31 dozen eggs in Follow, glue on pizza in Inform and Claudius the shopkeeper in Improve. Short contrasts complete each case, and every real case carries its source note.
• Carry these cases into Examine, whose last chapter now designs, step by step, a customer chat that can hand over; open the pattern system with the Replit code freeze.
• Draw the diagrams of Foundations and Examine with generic roles, so readers can reuse them; captions say who holds each role in the chapter’s case.
• Give the PDF and the HTML reader one typographic scale: body text, one-column width, headings, captions and notes keep the same form throughout the book.
• Replace the maintenance illustrations of Examine with two new ones.

Agentic Process Engineering · v0.1.13

• Review the whole book for consistency: one name for each thing, definitions at first use, and captions, figure descriptions, labels and table cells that say what the prose says, across Foundations, Examine, the patterns and the use cases.
• Tell the real cases more directly, keeping their facts and the distinctions each pattern relies on.
• Add two short fictional contrasts to Foundations: a support ticket that resembles an earlier one, and a refund that admission blocks while the operator’s authority still covers refunds.
• Align figures with the book’s visual grammar: proposals and mechanical checks are drawn neutral, and mandate frames appear where they state a scope.
• Compose the PDF with fewer blank areas and cleaner breaks: headings stay with their first paragraph, short paragraphs stay whole and code identifiers are no longer split. The HTML reader keeps its single column at every width.
• Use the current Casys mark throughout the book.

Agentic Process Engineering · v0.1.12

• Make pattern and use-case entries readable independently: remove redundant openings and reading-order cues while preserving local definitions, useful comparisons and evidence limits.
• Give Foundations and Examine more direct openings and substantive links between ideas, with shorter previews of the worked maintenance case.
• Add a brief fictional appointment example to distinguish the output produced from the outcome promised, and clarify which account the technician corrects before guidance review.
• Keep the Clark–Wilson source paragraph and its footnote clear of the two-column body after the shorter PAE opening, without reducing the text size.
• Restore two-column prose in the long Inform developments while keeping full-width figures, and reflow the Examine guide onto one page; preserve the single-column HTML reader.
• Align the Capture and review figure with the technician’s correction: name the conditions needed for comparison without asserting a difference from an earlier repair.
• Keep HTML prose within the reading column by neutralising print breaks and placing reference blocks above the text at every screen width.

Agentic Process Engineering · v0.1.11

• Use operator or the specific role throughout the book, reserve participants for research subjects, and remove the separate participant definition.
• Vary the examples before Foundations: introduce delegation through a fictional editorial task and reduce the author’s note’s reliance on the maintenance case.
• Introduce the maintenance roles before their diagram and replace the ambiguous “Retained” label with the maintenance lead’s approval action.
• Bring the maintenance opening onto one PDF page by placing the illustration beside the prose and keeping the diagram at its reading size; keep a Case Transfer reference beside the paragraph it introduces.
• Prefer case in narrative passages, explain process instance as its technical equivalent, and use review or reassessment where that occurrence has a more precise name. Preserve research terminology, technical pattern names and event identifiers.
• Align local accountability definitions with the book’s vocabulary, distinguish session renewal from operator replacement and effective access from authority, and clarify the object refused in the trading example.

Agentic Process Engineering · v0.1.10

• Align the six mechanism comparisons with the HTML prose column and stack their text in reading order.
• Center detailed diagrams at their intended reading width, keep the eight maintenance scenes compact, and scroll pattern maps together with their HTML labels on narrow screens.
• Apply manual HTML zoom to the entire book and retain the visible passage when changing zoom or returning to Fit. Keep the PDF composition unchanged.
• Reflow part and family dividers with readable prose and footers, keep narrow chapter titles on full lines, and follow the current reading location in the table of contents.
• Make HTML reading more compact with 16px prose, a 1.6 line height and smaller page margins, while preserving the text measure and detailed diagram widths. Keep the PDF composition unchanged.
• Preserve each table's descriptive accessible name on its keyboard-scrollable HTML region.

Agentic Process Engineering · v0.1.9

• Present the HTML reader as continuous, justified single-column prose with consistent type sizes, centered reading widths, adjacent footnotes and responsive spacing. Keep the PDF's page composition independent of the screen layout.
• Make detailed diagrams and tables readable on small screens with local horizontal scrolling, adapt illustrated openings, reference cards and question banners to the available width, and use the same contents and zoom controls in local and published previews.
• Separate three overlapping diagram labels in both HTML and PDF: the coaching accountability assignment, the permitted revision branch in Investigation, and the "Too broad" trial label in Practice Radar.

Agentic Process Engineering · v0.1.8

• Identify the eight maintenance coordination steps as 01.–08. and link each one from the table of contents and PDF outline.
• Introduce the subtitle “An Essay on Delegated Decision Authority” below the cover title and repeat both on a new interior title page. Place “With a Catalogue of Design Patterns” in italics on a light panel over the lower cover illustration.

Agentic Process Engineering · v0.1.7

• Shorten the cover definition by removing the repeated discipline name while retaining its meaning.
• Revise the closing service diagram: distinguish the person accountable for the process from the operator authorised to revise mandates, and let the local choice return directly to the process.
• Restore the mandate spaces, curved cooperation arrows and pale yellow backgrounds; show admission as a diamond, name the central Agentic operator, and end the cooperating route at a neutral white point. Align the caption and accessible descriptions with the figure.