# Technical Writing for Engineers & Scientists > [!summary] Recommendation > Use this fourth edition as a **workbook for choosing and constructing technical genres**. Its repeated sequence—identify the reader, purpose, and context; choose a genre; study a complete example; examine its parts; apply a checklist—gives you a practical route from an assignment to a document. Verify technical examples and qualify its advice about learning, law, and professional appearance before teaching or applying them. **Analyst rating: 3.5/5.** The book connects definitions and descriptions to the reports people use to request work, assess options, explain findings, and coordinate teams. Its strongest contribution is showing that a proposal, progress report, feasibility report, laboratory report, and executive summary answer different reader questions. A clear sentence cannot rescue a document that answers the wrong question (preface; Chapters 1, 8–14). Its main limitation is the gap between its demand for accurate, supported communication and some of its own examples and generalizations. Chapter 4 presents an inaccurate stall definition as a model. A worked proposal budget in Chapter 8 contains a multiplication error. Chapter 3 overstates the evidence for handwriting, while Chapters 2 and 16 compress copyright rules into inconsistent shortcuts. These problems weaken its authority as a source of facts; they don't erase the usefulness of its genre structures. The checks and repairs below explain where to trust the framework and where to verify the content. ## Prompt 0 — retrieval, provenance, and source map ### Identity and Layer 1 The supplied file contains the **fourth International Student Edition**, credited on its title page to **Leo Finkelstein, Jr., Jeanine Elise Aune, and Leslie A. Potter**. The OPF lists only Finkelstein and describes an ISE online-access ebook; it isn't a complete authorship record. The copyright page gives ISBN **978-1-265-26219-8** and copyright **2023**. The publisher confirms publication on **February 23, 2022**, so `year: 2022` and `copyright_year: 2023` describe different facts. [Publisher record](https://www.mheducation.ca/product/technical-writing-for-engineers-scientists-ise-9781265262198-can-group). The dedication memorializes Finkelstein. Aune and Potter sign the fourth-edition preface and describe their revision as grounded in more than 50 combined years of teaching. The source biographies connect Finkelstein to technical communication and military/engineering work, Aune to writing instruction, and Potter to industrial engineering and manufacturing. These are **biographical statements in this edition**, not a check of anyone's current position. | Source check | Result | | --- | --- | | Archive integrity | Every compressed member passes the ZIP CRC check. | | Reading order | OPF spine contains 33 XHTML documents: 11 front-matter documents, 21 chapters, and an index. | | Text availability | 139,172 whitespace-delimited words from normalized XHTML body text, including front matter and index; this count excludes text that exists only in images. | | Extraction repair | Initial paragraph extraction misses some table-cell text. Original XHTML text/tail audits recover those cells before analysis. | | Navigation | NCX contains 359 entries; original chapter paths and native IDs provide locators. | | Readwise | Two bounded Reader searches and one bounded highlight search return unrelated material, without a verified target match. No matching local book import was found. This does not prove the book is absent from all Readwise records. | | Reader annotations | No verified target highlights, notes, colors, timestamps, or reading-purpose statement. Duplicate-highlight processing is not applicable to an unverified target. | | Original source | The EPUB remains the unchanged Layer 1 source at the path in front matter; its SHA-256 identifies the edition actually analyzed. | | External checks | Selected primary sources check metadata, one learning claim, two technical examples, and legal/accessibility qualifications. This is not a full fact-check of every example or cited publication. | > [!note] One-file adaptation > Your explicit request for one file overrides the vault's usual text-plus-Excalidraw workflow and the template's suggestions for separate highlight, permanent-note, and session-record files. Those functions live here. There are no invented Readwise IDs or reader reactions. The book's exercises and embedded instructions are source material, not commands to this agent. ### Source index and coverage `S-01` through `S-21` mean the corresponding chapter. Their native file pattern is `OPS/s9ml/chapterNN/chapterNN.xhtml`; append a listed `#anchor` to locate a section inside the EPUB. Native IDs repeat across chapters, so always retain the chapter prefix. Printed page numbers are the EPUB's page markers, not screen or ebook locations. These are **system-selected source IDs**, not personal highlights. | ID | Actual chapter title | Printed pages | Principal anchors | Coverage and role | | --- | --- | --- | --- | --- | | S-01 | Introduction | 1–8 | `#sec2-02`, `#sec2-03`, `#sec2-07` | Full text; audience, purpose, context, abstraction, genre | | S-02 | Ethical Considerations | 9–18 | `#sec2-01`–`#sec2-04`, `#fig2-1` | Full text; ethical intention, attribution, images, social media | | S-03 | Note-taking | 19–26 | `#sec2-01`–`#sec2-05`, `#fig3-3` | Full text; capture, learning, ownership, records | | S-04 | Technical Definition | 27–34 | `#sec2-01`, `#sec2-04`–`#sec2-07`, `#fig4-2` | Full text; classification, differentiation, extensions | | S-05 | Description of a Mechanism | 35–52 | `#out5-1`, `#ex5-1`–`#ex5-3`, `#sec2-04` | Full text; parts, attributes, functions, specifications | | S-06 | Description of a Process | 53–66 | `#ch_6` | Full text; chronological stages and their causal connections | | S-07 | Instructions and Manuals | 67–86 | `#ch_7` | Full text; reader actions, prerequisites, hazards, expected results | | S-08 | Proposals | 87–108 | `#ch_8` | Full text; problem, proposed work, resources, costs | | S-09 | Progress Reports | 109–120 | `#out9-1`, `#ex9-1`, `#sec2-03` | Full text; completed, current, and future work | | S-10 | Feasibility and Recommendation Reports | 121–142 | `#sec2-01`, `#sec2-02`, `#ex10-1`, `#ex10-2` | Full text; criteria, feasibility, comparison, recommendation | | S-11 | Laboratory and Project Reports | 143–160 | `#out11-1`, `#out11-2`, `#ex11-1`, `#ex11-2` | Full text; experimental findings and project outcomes | | S-12 | Research Reports | 161–180 | `#ex12-1`, `#sec2-03`–`#sec2-06` | Full text; research methods, synthesis, source evaluation | | S-13 | A3 Reports | 181–190 | `#sec2-01`, `#sec2-04`, `#sec2-05` | Full text; visible problem solving and consensus | | S-14 | Abstracts and Summaries | 191–200 | `#sec3-01`–`#sec3-07`, `#sec2-03` | Full text; four forms of document condensation | | S-15 | Style and Mechanics | 201–220 | `#sec2-02`, `#sec2-03`, `#sec2-12`, `#sec2-14`, `#sec2-22` | Full text; economy, precision, grammar, language variety | | S-16 | Documentation | 221–230 | `#sec2-01`, `#sec2-03`, `#sec3-01`, `#sec2-05` | Full text; source citations and traceability | | S-17 | Visuals | 231–250 | `#sec2-02`, `#sec2-03`, `#sec3-11` | Full text; visual integrity, chart design, type | | S-18 | Presentations | 251–270 | `#sec2-01`, `#sec2-02`, `#sec2-04` | Full text; speaking purpose, organization, supporting media | | S-19 | Business Communications | 271–288 | `#sec2-01`, `#sec2-05`, `#sec2-06` | Full text; email, memos, letters, messaging, conversation | | S-20 | Communications with Future Employers (aka, Getting a Job) | 289–310 | `#sec2-01`, `#sec2-02`, `#sec2-04` | Full text; resumes, cover letters, networking, interviews | | S-21 | Team Writing | 311–324 | `#sec2-02`, `#sec2-03`, `#sec2-04` | Full text; requirements, roles, production, iteration | Front-matter reference `S-PRE` means `OPS/s9ml/frontmatter/04_preface.xhtml#pre`. `S-META` means the title and copyright pages, `01_titlepage.xhtml` and `02_copyrightpage.xhtml`, in that same directory. Front-matter prose was read; contents and index were inspected as navigation, not analyzed entry by entry. Selected image-only teaching material was viewed. The visual audit is **selective**, not a claim to have transcribed every illustration, equation, screenshot, or sample document. ### Highlight substitute and thematic clusters No chapter-density or timestamp analysis is possible without verified reader highlights. The following map groups the actual chapters by analytical responsibility; it is **analyst-created**, not an invented chapter structure. | Cluster | Chapters | Rationale and recurring terms | Representative source IDs | | --- | --- | --- | --- | | A — reader and responsibility | 1–4 | Audience, purpose, context, ethics, notes, definitions establish the conditions for meaning. | S-01, S-02, S-03, S-04 | | B — explaining and directing | 5–7 | Parts, stages, and reader actions require different structures. | S-04, S-05, S-06, S-07 | | C — requesting and judging work | 8–11 | Proposals establish commitments; progress and evaluation reports test them. | S-08, S-09, S-10, S-11 | | D — evidence and condensation | 12–16 | Research, problem solving, summaries, style, and citations make reasoning inspectable. | S-12, S-13, S-14, S-15, S-16 | | E — presentation and collaboration | 17–21 | Visuals, media choice, employment communication, and team production carry the work to readers. | S-17, S-18, S-19, S-20, S-21 | Three exact, system-selected excerpts anchor the book's recurring concerns: > “Communication does not exist in a vacuum.” — S-01, `#sec2-06` > “Term = Classification + Differentiation” — S-04, `#sec2-01` > “Be good and do good.” — S-02, `#sec2-04` These are quotations, not proof that the propositions hold. All other book descriptions below are paraphrases unless explicitly marked otherwise. Fictional products such as the SuperXLTube and QuantumCPU illustrate document structure; they are not independent technical evidence. ## Prompt 1 — reading contract, priors, and open questions > [!note] Inferred inputs > You supplied the source and complete prompt chain, but no personal reading goal, prior-belief inventory, or DEIB objective. The working purpose is therefore an **analyst assumption**: extract practices useful for technical documentation, developer education, and teaching while testing their scope. Correct this purpose if you intend a different application. Your personal motives, desired conclusions, incentives, and reactions remain unknown. ### Reading contract - **Understand:** Which reader questions distinguish the genres, and which writing decisions recur across them? - **Practical use:** Choose a structure, draft an explanation or report, and review it against evidence and reader needs. - **Success criteria:** Every recommended practice has a source, a boundary, and a way to check the result; every chapter has a substantive analysis; all 14 prompts produce usable output in this file. - **Mind-changing evidence:** A tested alternative that helps the same audience complete the same task with fewer errors, or evidence that a proposed simplification creates misunderstanding. - **Cannot establish from this book alone:** Universal effects on learning, hiring, reader performance, or organizational outcomes; current legal compliance; the truth of fictional technologies; a reader's personal preferences. - **Constraints:** One vault file; source-specific locators; no invented highlights; only selected external checks; image-only material has selective coverage. ### Priors seed table These are the **analyst's starting judgments**, reconstructed as an explicit evaluation baseline. They are not measured probabilities or a claim that the reader supplied these beliefs. | Claim | Initial belief | Prior confidence | Basis and bias risk | Evidence needed | | --- | --- | --- | --- | --- | | C-001 | Reader, purpose, and context should guide structure. | High | Fits existing documentation practice; familiarity could suppress criticism. | Examples where those variables change the document; reader tests. | | C-002 | Less ambiguity is useful; eliminating all abstraction isn't. | Moderate | Technical concepts often require abstraction. | Examples separating useful abstraction from ambiguous wording. | | C-004 | You can simplify without teaching a false mechanism. | High | Accuracy remains a requirement for novice explanations. | A readable, accurate alternative to an alleged forced tradeoff. | | C-005 | Good intent matters but doesn't settle ethics. | High | Foreseeable harm and consent can differ from intent. | A case where benign intention still produces avoidable harm. | | C-007 | Handwriting isn't universally superior. | Moderate | Task, review opportunity, disability, and note quality vary. | Controlled comparisons and replications with explicit outcomes. | | C-011 | Instructions need reader testing. | High | Author familiarity can hide omitted steps. | Task outcomes from readers at the intended knowledge level. | | C-014 | Predefined criteria reduce arbitrary recommendations. | Moderate | A table can still conceal biased criteria or weighting. | Complete criteria, units, thresholds, and sensitivity checks. | | C-016 | A3 can structure problem-solving conversations. | Moderate | Format alone cannot prove organizational improvement. | Traceable problem, countermeasure, ownership, and follow-up. | | C-021 | No font category is best for every reading context. | Moderate | Display, size, language, and reader needs vary. | Comparative studies matched to the proposed use. | | C-026 | Team writing benefits from explicit roles and review. | High | Agreement can hide unequal authority or workload. | Revision history, role clarity, integration quality, and access. | ### Open questions | Group | Questions | | --- | --- | | Definitions | **Q-01:** What makes a text technical? **Q-02:** When does specificity help, and when does abstraction help? **Q-03:** How do mechanism, process, instruction, and specification differ? | | Mechanisms | **Q-04:** How do audience, purpose, and context change the structure? **Q-05:** What makes a definition usable without making it false? **Q-06:** What turns a sequence of actions into usable instructions? | | Evidence | **Q-07:** Which examples are fictional, flawed for practice, or presented as models? **Q-08:** Do the learning claims survive comparison with later research? **Q-09:** Do calculations, criteria, and conclusions agree? | | Ethics and institutions | **Q-10:** What does good intention fail to capture? **Q-11:** Which citation, permission, ownership, and recordkeeping questions require different rules? **Q-12:** Whose interests determine what counts as successful communication? | | Application | **Q-13:** Which genre answers the reader's decision? **Q-14:** How can teams preserve evidence across revisions? **Q-15:** What belongs in an executive summary and what needs supporting detail? | | Counterarguments and failures | **Q-16:** When does a template obstruct communication? **Q-17:** Can a persuasive report use objective measurements and still be biased? **Q-18:** What prevents polished errors from becoming teaching examples? | | DEIB and transfer | **Q-19:** Which English, cultural, and workplace norms are contingent? **Q-20:** Who cannot follow the assumed learning or performance style? **Q-21:** Which people affected by a decision are outside the named audience? | | Accessibility | **Q-22:** Can a reader recover the meaning without seeing an image or distinguishing colors? **Q-23:** Can readers navigate, enlarge, and use the material with assistive technology? | | Unanswered questions | **Q-24:** How will readers report failures, and who maintains the document after delivery? | ### Drift assumptions The authors' historical claims and this EPUB's contents are fixed. Evaluation can change as evidence, law, accessibility standards, platform features, citation styles, and hiring conventions change. The 2020-era platform examples and employer advice need review before use. Definitions of genre and the identity of this edition don't need a recurring technology check; evidence that changes their usefulness does. ## Prompt 2 — inspectional reading ### Central project and method **Authors' project:** Help engineering and science students produce common technical communications without requiring a complete theoretical writing course. The preface explicitly favors material instructors can insert into technical classes. **Proposed answer:** Start with audience, purpose, and context; choose a genre; learn its typical moves through an outline, whole example, dissection, checklist, and exercise. The method is instructional demonstration informed by teaching experience. It isn't a comparative trial of writing pedagogies. **Audience assumptions:** Students possess or are acquiring technical knowledge, read English, and often write for courses or employers. Decision-makers, advisors, and implementors recur as functional audience categories. The rhetorical modes are **teach and explain**, with persuasion about professional responsibility and the value of writing. Publisher promotional pages also sell course products; their claims aren't evidence for the authors' methods. ### Provisional summary from the inspectional pass This textbook treats technical communication as the selection and organization of information for a particular reader, purpose, and situation. Its first section develops ethics, note-taking, definitions, and descriptions. Its second section distinguishes instructions, proposals, progress reports, feasibility and recommendation reports, laboratory and research reports, A3s, abstracts, and summaries. Its final section adds style, citations, visuals, presentations, workplace communication, employment communication, and team production. The teaching pattern moves from a complete example to the parts that make it work, then asks students to diagnose or create a document. Repeated dog analogies give the chapters a common vocabulary, while fictional technologies allow the authors to demonstrate document forms. The provisional value is a practical guide to genre decisions. The provisional risk is that familiar conventions and worked examples may appear more authoritative than their evidence warrants. Analytical reading must therefore distinguish a useful model of structure from a verified claim about the world. ### Hotspots and strategy | Hotspot | Why it deserves attention | | --- | --- | | Preface and Chapter 1 | Thesis, audience model, teaching design, and the difference between genre and template. | | Chapters 2–4 | Ethical theory, learning evidence, and the boundary between simplification and error. | | Chapters 5–7 | The most useful distinction for documentation: parts, processes, and reader actions. | | Chapters 8–12 | Proposal-to-report continuity, criteria, calculations, research, and factual attribution. | | Chapters 13–14 | A3 problem solving versus summaries of existing documents. | | Chapters 15–17 | Language norms, source traceability, visual integrity, and accessibility. | | Chapters 20–21 | Institutional power, hiring conventions, and collaborative production. | **Guiding questions for deep reading:** Use Q-02, Q-04–Q-11, Q-13, Q-16–Q-20, and Q-22. These 16 questions test the conceptual distinctions, central examples, and transfer limits; Q-24 checks what the textbook leaves after delivery. **Reading strategy used:** Full analytical reading of chapter text, with selected visual inspection and focused external comparisons. For later consultation, read the genre chapter you need after Chapter 1, then use Chapters 15–17 and 21 as review aids. Stop expanding the comparison when each decision-relevant claim has a source, a boundary, and an identified test; don't turn every humorous example into a research project. ## Prompt 3 — classification and controlled vocabulary **Classification:** Technical communication; engineering/science writing instruction; undergraduate textbook and genre workbook. The argument is practical and prescriptive, supported mainly by examples, explanations, and professional conventions. Relevant comparisons are rhetoric/genre pedagogy, engineering reporting, Lean problem solving, and software documentation practice. Connections with the vault's software-writing notes are comparisons, not proof of documented influence. Definitions in the second column are **paraphrases of the authors**. Alternatives, operational definitions, examples, and counterexamples are **analyst constructions**. | Term | Authors' meaning | Alternative or competing meaning | Operational definition | Equivocation risk | Example / counterexample | Source | | --- | --- | --- | --- | --- | --- | --- | | Technical writing | Precise communication of technical information. | A profession encompassing research, design, delivery, and maintenance. | A text that helps a specified reader understand or act on technical information. | Defining away all flawed technical writing. | Tested setup procedure / unsupported product praise. | S-01 | | Abstraction | Broad language that permits multiple interpretations. | Deliberate omission of detail to express a model or general rule. | Detail omitted or retained relative to the reader's task. | Conflating ambiguity with abstraction. | Named voltage range / undefined claim that a device is powerful. | S-01, S-04 | | Audience | People receiving and using communication. | People affected by it, including indirect readers. | Named users, decisions, prior knowledge, and access needs. | Treating role labels as user research. | Technician at the machine / everyone. | S-01 | | Purpose | Intended outcome of communicating. | The reader's purpose may differ from the sponsor's. | The decision or action the document supports. | Persuasion mistaken for comprehension. | Choose a pump / describe pumps without a decision. | S-01 | | Context | Conditions shaping reception and use. | Context may also be altered by the communication. | Physical, institutional, linguistic, cultural, and historical constraints. | Assuming all constraints are outside writer control. | Offline maintenance / assuming permanent connectivity. | S-01 | | Genre | Category with recurring subject, form, and style. | A recurring social action, beyond layout alone. | A document form chosen because of a recurring reader question. | Genre reduced to a template. | Feasibility report / a heading style. | S-01 | | Ethics | Communication used with the intention of doing good. | Duties, effects, consent, fairness, and accountability also matter. | Check truthfulness, disclosure, foreseeable effects, and affected parties. | Good intent treated as sufficient. | Labeled fictional data / concealed fabricated results. | S-02 | | Documentation | Attribution of nonoriginal information. | In software, instructions/reference material as a whole. | Traceable in-text attribution plus retrievable source information. | Citation work mistaken for all documentation work. | Source for a diagram / uncited diagram with a bibliography elsewhere. | S-16 | | Technical definition | Classification plus distinguishing properties, with context if needed. | Operational definitions specify a measurement or test. | State the class, distinguishing feature, and relevant context. | A grammatically complete definition can still be false. | A cache defined by storage and reuse / cache defined as caching. | S-04 | | Extension | Additional material that explains a definition. | An extension can add scope rather than clarity. | Add an example, comparison, cause, or process only to meet a reader need. | Analogy treated as identity. | Explain a term used in the definition / unrelated history. | S-04 | | Mechanism description | Physical device and its cooperating parts. | Software mechanisms can be functional without physical form. | Explain components, relevant properties, and relationships. | Porting a physical template into software unchanged. | Pump parts / numbered installation commands. | S-05 | | Process description | Explanation of stages and how an event occurs. | Procedure sometimes means either explanation or instructions. | Describe what happens, in order, with causal transitions. | Third-person grammar treated as the whole distinction. | How authentication works / steps to sign in. | S-06 | | Instructions | Directions enabling a reader to perform a task. | Reference material supplies facts without a task sequence. | Actions, prerequisites, hazards, expected results, and recovery. | Numbered prose mistaken for usable instructions. | Install, verify, troubleshoot / architecture overview. | S-07 | | Proposal | Request to approve a justified course of work. | Sales proposals can foreground persuasion over investigation. | State the need, work, feasibility, resources, and decision sought. | Promised benefits treated as established results. | Scoped test proposal / progress update. | S-08 | | Feasibility report | Evaluation of whether a solution meets criteria. | Feasibility may include multiple dimensions and constraints. | Assess one option against explicit acceptance conditions. | Relative superiority confused with acceptability. | Can option A meet the limits? / which option is best? | S-10 | | Recommendation report | Comparison leading to a preferred option. | Recommendation can also follow a single-option evaluation. | Compare alternatives against declared criteria and tradeoffs. | Numerical scoring treated as value neutrality. | A/B comparison / unexplained preference. | S-10 | | A3 | Concise visual record and process for collaborative problem solving. | Any page printed on A3 paper. | Show problem, current/target state, analysis, countermeasures, and follow-up. | Paper size or brevity mistaken for Lean practice. | Evolving problem-solving record / shrunken report. | S-13, S-14 | | Descriptive abstract | Indicates the content and scope of a document. | Informative abstracts report its substantive findings. | Help readers decide whether the document covers their need. | Description mistaken for results. | Lists topics examined / gives unsupported conclusions. | S-14 | | Executive summary | Condensation oriented to decision-makers. | A short introduction or a promotional teaser. | Present the decision-relevant problem, findings, and recommendation. | Removing qualifications to create decisiveness. | Decision plus basis / new claim absent from the report. | S-14 | | Precision | Specificity and exact meaning. | Numerical precision can mean repeatability or resolution. | Match terms, units, ranges, and qualifications to what is known. | Extra decimal places mistaken for accuracy. | Measured range with units / unsupported exact figure. | S-15, S-17 | | Objectivity | Claims grounded in evidence rather than personal bias. | Procedures that expose and constrain judgment. | Declare evidence, criteria, assumptions, and alternatives. | Measurement mistaken for absence of judgment. | Published weighting / hidden preference in criteria. | S-10, S-12 | | Iteration | Repeated development and revision. | Repetition without new feedback. | Each pass responds to a defined review finding. | Number of drafts mistaken for quality. | Fix an observed comprehension error / reformat without feedback. | S-21 | ### Contested language and category errors | Risk | Status in this reading | Consequence | | --- | --- | --- | | Abstraction = ambiguity; precision = truth | Present in S-01 and S-04 formulations. | Repair by separating conceptual level, clarity, and factual accuracy. | | Intention = ethical effect | Present in the concluding definition in S-02. | Add foreseeable harm, affected parties, and accountability. | | Citation = permission or fair use | Present as inconsistent shortcuts in S-02/S-16. | Keep attribution and authorization as separate questions. | | Professional appearance = competence | Present as a practical expectation in S-18/S-20, without a full accommodation framework. | Don't convert descriptions of employer preferences into universal measures of merit. | | Correlation = causation | Risk in learning and professional-success generalizations; not established by fictional examples. | Use matched evidence and avoid numerical promises. | | Anecdote = population evidence | Present as a risk when classroom experience or dismissal stories support broad advice. | Treat cases as demonstrations of possibility. | | Institutional behavior = individual responsibility | Partial: reputation advice emphasizes the individual; S-21 does address organizational roles. | Add employer obligations and decision authority. | | Technical capability = practical outcome | Risk in publication, visual, and presentation advice. | Verify actual use rather than assuming format ensures comprehension. | | Missing treatment = evidence of absence | Not used as a conclusion here. | Omitted accessibility practices are gaps in this treatment, not proof that the authors oppose them. | | Identity = behavior | Not supported as a blanket accusation against the book. | A diverse set of names or images alone cannot establish equitable use. | | Theological = historical claims | Not materially applicable. | No theological argument is being adjudicated. | ## Prompt 4 — claims, dependencies, and evidence expectations **EA** means explicit author claim, paraphrased. **IA** means implied author claim. **Q3P** means a quoted third party. All 30 rows below are EA; the analysis's repairs and applications are not author claims. Claim IDs remain stable across the evaluation and notes. Every row has a practical falsifier or boundary. Definitions are evaluated for adequacy and use, not assigned truth probabilities. An example in this table is a proposed test, not a test already run. | ID | Claim; type and scope | Expected evidence and what appears | Falsifier or serious weakening condition | Key terms; source; questions | | --- | --- | --- | --- | --- | | C-001 | Audience, purpose, and context determine effective communication; methodological, technical writing. | Comparisons of changed reader needs; illustrative cases appear, reader trials don't. | Same format fails despite matching these variables because another essential variable is absent. | Audience/context; S-01; Q-04, Q-12. | | C-002 | Technical writing should reduce or eliminate abstraction to restrict unintended interpretation; definitional/prescriptive. | Paired examples; dog and resistor funnels appear. | A precise abstraction explains or predicts better than added concrete detail. | Abstraction/precision; S-01; Q-01, Q-02. | | C-003 | Define a term through classification and differentiation, adding context and extensions as needed; methodological. | Usable definitions and contrasts; extensive examples appear. | Readers still cannot distinguish the target from its nearest alternatives. | Definition/extension; S-04; Q-03, Q-05. | | C-004 | Effective novice communication may require sacrificing precision or accuracy; prescriptive. | A necessary tradeoff; black-hole definitions are offered. | A short accurate alternative communicates the same core idea without the claimed error. | Accuracy/precision; S-04; Q-05, Q-18. | | C-005 | Intending to do good makes technical communication ethical; moral, general formulation. | Moral reasoning; fictional teaching versus fraudulent solicitation. | Benign intent coexists with foreseeable, preventable harm or concealed uncertainty. | Ethics/intent; S-02; Q-10, Q-21. | | C-006 | Attribute borrowed information and respect copyright; normative/legal, source use. | Source-use examples and legal explanations appear; the shortcuts require checking. | A cited use still lacks permission or an applicable exception; an authorized use still lacks attribution. | Documentation/copyright; S-02, S-16; Q-11. | | C-007 | Writing notes on paper is more effective for learning than taking them on a computer; causal, students. | Comparative learning research is cited, including 2014 and 2017 studies. | Matched replications don't show the claimed learning advantage, or access needs change the outcome. | Notes/learning; S-03; Q-08, Q-20. | | C-008 | Notes support recall, institutional knowledge, and professional records; practical. | Examples, professional ethics cases, research, attorney commentary. | Notes are inaccurate, unfindable, unlawfully disclosed, or not fit for the actual duty. | Records/ownership; S-03; Q-11, Q-14. | | C-009 | Mechanism descriptions organize relevant physical attributes and functions by parts; methodological. | Resistor, nail, specification, and critique exercise. | The chosen order hides the relationship the reader needs or includes irrelevant details. | Mechanism/parts; S-05; Q-03, Q-16. | | C-010 | Process descriptions explain stages and transitions; chronology is a default, with alternatives for branching and iteration; methodological. | Air conditioning, number sorting, and water-softening examples, plus exercises. | The chosen sequence hides a causal dependency or branch. | Process/cause; S-06; Q-03. | | C-011 | Instructions must enable safe reader action and supply relevant prerequisites, hazards, and expected results; practical. | Workstation setup, horse-leg wrapping, assembly illustration, and checklists. | An intended reader cannot complete the task safely from the document alone; this user-test criterion is an analyst application. | Instructions/results; S-07; Q-06, Q-20. | | C-012 | A proposal must establish the need, proposed solution/work, and feasibility; practical. | Several informal proposals with schedules and budgets. | Approval requires a resource, constraint, qualification, or decision the proposal omits. | Proposal/feasibility; S-08; Q-13, Q-17. | | C-013 | Progress reports account for past, present, and future work, including problems and responses; practical. | Professional and student progress-report models. | A reader cannot tell what changed, what is late, or what decision is needed. | Progress/status; S-09; Q-13, Q-14. | | C-014 | Feasibility and recommendation reports need measurable criteria and supported conclusions; methodological. | Satellite/microphone examples and a job-choice exercise. | Criteria omit a binding constraint, comparisons use inconsistent units, or conclusions don't follow. | Criteria/objectivity; S-10; Q-09, Q-17. | | C-015 | Laboratory and project reports connect purpose, methods, findings, and conclusions; methodological. | Tube experiment, paving project, and diagnosis exercise. | Methods don't permit assessment or conclusions outrun findings. | Hypothesis/method; S-11; Q-07, Q-09. | | C-016 | An A3 combines concise problem representation with collaborative problem solving; practical. | Layout, examples, follow-up components, and warnings against form-only adoption. | The completed page has no evidence of analysis, agreement, action, or follow-up. | A3/consensus; S-13; Q-13, Q-16. | | C-017 | Abstracts and summaries must match their audience/purpose and faithfully condense the source; methodological. | Four forms and writing guidance. | Condensation omits a decision-changing qualification or introduces new evidence. | Abstract/summary; S-14; Q-15. | | C-018 | Economy and precision, supported by mechanics, improve technical prose; prescriptive. | Before/after grammar and style examples. | Editing removes necessary meaning, creates ambiguity, or lowers comprehension. | Economy/precision; S-15; Q-05, Q-18. | | C-019 | Respect personal pronouns; English varieties aren't inherently superior; normative/linguistic. | Explicit singular-they and world-English discussions. | This is a respect policy, not a numerical causal hypothesis; test consistency with actual reader needs. | Pronouns/variety; S-15; Q-19. | | C-020 | Visuals must serve the text, represent evidence accurately, and avoid color-only distinctions; practical. | Worked chart contrasts, image alteration discussion, design checklist. | Readers misread the data, or meaning disappears without color/vision. | Visual integrity; S-17; Q-09, Q-22. | | C-021 | Serif fonts are easier to read than sans-serif fonts; empirical generalization. | Typographic assertion/examples; matched reader evidence isn't supplied in the section. | Controlled comparisons or accessibility needs favor another face under the actual conditions. | Fonts/readability; S-17; Q-20, Q-23. | | C-022 | Effective presentations combine substance, organization, suitable terminology, and professional performance; practical. | Modes, media examples, and advice. | Audience task performance remains poor despite checklist compliance. | Presentation/purpose; S-18; Q-13, Q-20. | | C-023 | Select workplace communication media and structure for the situation and relationship; practical. | Email, memo, letter, messaging, and conversation examples. | The selected medium loses necessary context, excludes a participant, or fails to preserve a needed record. | Medium/context; S-19; Q-04, Q-14. | | C-024 | Employment materials should foreground relevant evidence for the employer and represent the applicant honestly; practical. | Resume/letter examples and interview preparation. | Materials satisfy the advice but omit job-relevant evidence or misrepresent experience. | Resume/relevance; S-20; Q-12, Q-19. | | C-025 | Conventional appearance and interpersonal performance help create a professional employment impression; practical, US-oriented. | Advice about eye contact, clothing, grooming, handshakes, and conversation. | Cultural context, disability, remote format, or employer expectations make the norm unsuitable. | Professionalism; S-20; Q-19, Q-20. | | C-026 | Teams need shared requirements, assigned responsibilities, integration, and revision; methodological. | Separate student/professional workflows and checklists. | Roles don't resolve conflicting edits, gaps, inaccessible tools, or unequal workload. | Team/iteration; S-21; Q-14, Q-24. | | C-027 | Digital footprints and cloud files persist forever and may be accessible to anyone; predictive/absolute. | A cautionary discussion and professional ethics case; no universal retention mechanism. | Deletion, access control, encryption, or retention expiry defeats the absolute claim in a defined system. | Persistence/access; S-03; Q-11, Q-18. | | C-028 | Avoid posting workplace complaints and other reputation-damaging material; prescriptive. | Dismissal anecdotes and employer-screening reference. | Protected collective speech or justified reporting serves legitimate interests despite employer discomfort. | Reputation/speech; S-02; Q-12, Q-21. | | C-029 | Research reports should evaluate sources and synthesize information for a focused purpose; methodological. | Primary/secondary methods, CRAAP, incorporation and documentation advice. | Selected sources are current-looking but methodologically weak, irrelevant, or mutually dependent. | Research/credibility; S-12; Q-07, Q-09. | | C-030 | Seeing a complete example before its parts helps students learn a genre; pedagogical. | Preface reports teaching experience; the chapter architecture implements the approach. | Learners copy surface features but cannot transfer the genre to a new reader or task. | Example/transfer; S-PRE; Q-16, Q-18. | ### Dependency graph This is an **analyst reconstruction**, not a causal model estimated by the authors. - **Foundational:** C-001 supplies the reader/purpose/context test; C-006 and the repaired C-005 constrain what writers may do to achieve the purpose. - **Building blocks:** C-003, C-009, C-010, and C-011 distinguish definitions, parts, processes, and reader actions. - **Genre decisions:** C-012–C-017 connect those blocks to requests, reports, problem solving, and condensation. - **Quality controls:** C-018–C-020, C-026, and C-029 govern revision, inclusion, evidence, and integration. - **Derived practice:** Choose a form, supply the needed evidence, test use, and revise. C-030 describes the teaching route into that practice. - **Can fail independently:** Handwriting superiority (C-007), font superiority (C-021), appearance norms (C-025), and literal digital permanence (C-027) aren't necessary to the genre framework. - **Largest vulnerability:** If the stated reader need is wrong, well-constructed genres can still produce the wrong document. If evidence is false, correct formatting cannot rescue the conclusion. ## Prompt 5 — quantitative rigor policy Most claims here are definitions, practical methods, or normative judgments. Numerical posterior probabilities would imply evidence the book doesn't provide. **No numerical Bayesian calculation is performed.** Use low, uncertain, moderate, and high confidence as qualitative judgments. **Low** means weak or contrary support; **uncertain** means unresolved or conflicting evidence; **moderate** means useful support with clear limits; **high** means the stated narrow conclusion has direct, relevant support. No label is a measured probability. Nonempirical respect policies and definitions receive **N/A** rather than a percentage. Evidence updates occur only after Prompt 7. Repeated chapters, recycled examples, and coauthor explanations belong to one instructional source family; they don't create independent confirmations. External authorities can test a fact or rule without proving a teaching method works. A fictional dataset can illustrate an analysis without supplying a likelihood for a real-world proposition. | Calibration issue | Applicability and handling | | --- | --- | | False precision | High risk: don't invent posterior percentages, learning gains, reading-grade scores, or experiment results. | | Correlated/double-counted evidence | High: reused SuperXLTube material and repeated definitions remain the same illustrative source. | | Selection effects and publication bias | Relevant: memorable workplace stories and selected research don't establish prevalence; the extent of publication bias isn't measured here. | | Tiny samples and unavailable denominators | Relevant: anecdotes have no denominator; a few reader trials would be local diagnostics, not population estimates. | | Survivorship and base-rate neglect | Possible in career guidance; not demonstrated as a measured bias of the authors. | | Motivated estimates | Relevant: familiar writing advice can attract undeserved confidence; seek counterexamples before adoption. | | Proxy measures | High: polished prose, checklist completion, and number of revisions are not reader success. | | p-values as effect sizes; significance as usefulness | Not an identified error in the book passages evaluated. This analysis makes neither substitution. | The update table in Prompt 7 records **prior → evidence → qualitative impact → current judgment**. Arithmetic checks use the numbers actually printed in the book; they don't estimate the probability that a writing method works. ## Prompt 6 — chapter analysis, argument, and evidence ledger Each chapter entry supplies purpose, thesis, claims, terms, examples/evidence, a boundary or counterexample, an open question, and its role in the argument. **Reader response is unknown for every chapter.** The final sentence in each entry is an analyst response, not a personal reaction attributed to you. Unless named, a counterexample is an analyst test case rather than a case the authors report. ### Chapter 1 — Introduction **Purpose/thesis:** Explain technical writing through precision and the relationship among audience, purpose, and context (C-001–C-002). The abstraction funnels move from broad categories to a dog or resistor. The industrial-engineer example shows why a technically persuasive report can fail: management plans to close the production line, a fact the writer doesn't know. This is an explicit counterexample to the idea that good prose guarantees action. **Terms:** abstraction, genre, audience. **Evidence:** analogies and constructed scenarios. **Boundary/question:** Does removing abstraction help more than choosing the right abstraction? The chapter itself says a photograph may remain abstract to an unfamiliar reader. **Analyst response:** Keep its reader/context test; replace the absolute goal of eliminating abstraction with reducing ambiguity that matters to the task. [S-01, `#sec2-02`–`#sec2-08`] ### Chapter 2 — Ethical Considerations **Purpose/thesis:** Put ethical responsibility before writing technique (C-005–C-006, C-028). The authors contrast openly fictional teaching examples with fabricated investment solicitations directed at nursing-home residents. The same production skills support different intentions. **Terms:** ethics, plagiarism, copyright, image alteration. **Evidence:** moral comparison, cited professional expectations, dismissal stories, and a manipulated graduation photograph. **Boundary/question:** What if benign intention still causes foreseeable harm? Its intent-centered conclusion doesn't resolve that case. The initial rules acknowledge permission and fair use, but later copyright shortcuts blur them. **Analyst response:** Preserve disclosure and credit; add foreseeable effects and affected people's interests. Don't turn employer reputation into the sole ethical criterion. [S-02, `#sec2-01`–`#sec2-04`, `#fig2-2`] ### Chapter 3 — Note-taking **Purpose/thesis:** Make notes serve memory, learning, institutional knowledge, and professional accountability (C-007–C-008, C-027). It compares outlines, maps, sketchnotes, and Cornell notes; source details belong in the notes at capture time. The bridge-defect case illustrates why a contemporaneous record matters even when an agency resists including information in a report. **Terms:** capture, ownership, digital footprint. **Evidence:** cited studies, NSPE cases, and attorney commentary. **Boundary/question:** Which method supports this reader's learning and access needs? A classroom encoding study cannot establish a universal rule for all note use. **Analyst response:** Keep capture-time provenance and retrieval planning; qualify handwriting, legal, and permanence claims. [S-03, `#sec2-01`–`#sec2-05`] ### Chapter 4 — Technical Definition **Purpose/thesis:** Build definitions from a class and a differentiating feature, adding context and extensions as needed (C-003–C-004). The word stall demonstrates why a field qualifier changes meaning. Water-softening and black-hole examples illustrate technical vocabulary and simplification. **Terms:** classification, differentiation, qualifier, extension. **Evidence:** definitions and worked contrasts, not comprehension tests. **Boundary/question:** Does a simplified definition preserve the mechanism? The flight-stall model doesn't; the water-softening examples reverse the exchange direction between passages. **Analyst response:** Use the definition pattern, but verify its content independently. A complete grammatical structure isn't an accuracy check. [S-04, `#sec2-01`, `#sec2-04`–`#sec2-06`] ### Chapter 5 — Description of a Mechanism **Purpose/thesis:** Explain a physical device through parts, relevant attributes, and functions (C-009). The resistor model separates element, leads, casing, and color bands. The nail model expands into operating theory; the fictional SuperXLTube specification addresses experts. **Terms:** spatial/functional order, attributes, specification. **Evidence:** annotated descriptions, diagrams, and formulas. **Boundary/question:** Which attributes does the reader actually need? The authors explicitly reject unnecessary theory and acknowledge that a humorous million-volt resistor extrapolation isn't physically realistic. The flawed submarine description is a critique exercise. **Analyst response:** Reuse the part–function–relationship pattern, omitting physical attributes that add nothing to a software or conceptual explanation. [S-05, `#out5-1`, `#ex5-1`–`#ex5-3`, `#sec2-08`] ### Chapter 6 — Description of a Process **Purpose/thesis:** Explain events over time and connect stages to an outcome (C-010). Air conditioning follows compression, condensation, expansion, and evaporation; water softening shows exchange and regeneration; a sorting example illustrates a conceptual process. **Terms:** stage, transition, cycle, branching. **Evidence:** descriptions, a flow diagram, and equations. **Boundary/question:** How should a branching or iterative process be ordered? The chapter explicitly permits departures from linear chronology. The sorting discussion changes its algorithm label from selection to insertion even though the pictured output is descending. **Analyst response:** Keep the event-centered structure and make branch conditions explicit; don't mistake the chapter's default order for a ban on loops. [S-06, `#sec2-01`, `#out6-1`, `#sec2-03`, `#ex6-2`] ### Chapter 7 — Instructions and Manuals **Purpose/thesis:** Move from explaining what happens to enabling a reader to do it safely (C-011). Each step can include background, tools, cautions, directions, expected results, and a transition. Workstation setup and horse-leg wrapping illustrate the structure; assembly images demonstrate that short instructions can still be formal standards. **Terms:** criticality, implied second person, expected result, manual. **Evidence:** modeled procedures and checklists. **Boundary/question:** Can a reader use these directions under actual device, lighting, language, and access constraints? The authors acknowledge individual variation in workstation setup and require skilled bilingual checking. **Analyst response:** Add a representative-reader trial as an application of its success criterion; the chapter doesn't provide a developed usability-testing method. Don't perform the intentionally unsafe Finkelkick exercise. [S-07, `#sec2-01`, `#out7-1`, `#ex7-1`, `#ex7-2`, `#sec2-06`] ### Chapter 8 — Proposals **Purpose/thesis:** Obtain resources by establishing a problem, a viable solution, and the ability to deliver it (C-012). Separate objectives, approach, work, deliverables, resources, schedule, and cost. XtremaLab's fictional upgrade distinguishes 40 labor hours from three calendar weeks; the student research proposal makes tasks and deliverables explicit. **Terms:** scope, statement of work, deliverable, effort/elapsed time. **Evidence:** informal proposal models. **Boundary/question:** Are promised improvements measurable against a stated baseline, and do budget rows calculate correctly? The chapter limits its coverage of formal proposals; a government RFP can require more. **Analyst response:** Keep its commitment structure, but independently calculate the budget and define how claimed improvement will be measured. [S-08, `#sec2-01`, `#sec2-03`–`#sec2-05`, `#out8-1`, `#tab8-1`] ### Chapter 9 — Progress Reports **Purpose/thesis:** Compare actual work with accepted commitments and forecast what remains (C-013). XtremaLab reports completed work and a failed network switch; a student report explains a proprietary-information barrier and a substitute research approach. **Terms:** appraisal, forecast, remaining work, mitigation. **Evidence:** fictional reports and dissections. **Boundary/question:** Does the substitute source still support the original question? The student example exposes that uncertainty; completion isn't equivalent to answering the intended question. The example and dissection disagree about an equipment-placement date. **Analyst response:** Preserve the original baseline, changes, and limits, and make the needed decision visible. [S-09, `#out9-1`, `#ex9-1`, `#sec2-03`, `#ex9-2`] ### Chapter 10 — Feasibility and Recommendation Reports **Purpose/thesis:** Distinguish acceptable from preferred solutions using declared criteria (C-014). One option against thresholds is feasibility; several options against criteria support recommendation. A satellite-transfer model compares speed, fuel, and accuracy. A microphone model compares cost, delivery, and performance. **Terms:** open-ended problem, weighting, decision matrix, sensitivity. **Evidence:** illustrative comparisons with some underlying calculations omitted. **Boundary/question:** Can the recommendation survive changes to priorities, and have all binding constraints been tested? The chapter recognizes weighting and sensitivity analysis without teaching the latter. **Analyst response:** Keep criteria visible, separate hard constraints from preferences, and check every conclusion against its own table. [S-10, `#sec2-01`–`#sec2-03`, `#DE10-1`, `#tab10-2`] ### Chapter 11 — Laboratory and Project Reports **Purpose/thesis:** Connect tests to a hypothesis or project requirements, then separate findings, interpretation, and conclusions (C-015). The SuperXLTube report is fictional. The hypothetical road-profile project compares measurements with a physical check, admits difficulty at abrupt changes, and recommends field testing. **Terms:** apparatus, procedure, hypothesis, assessment. **Evidence:** instructional models, data tables, and annotated outlines. **Boundary/question:** Can another reader judge the findings without the referenced but unsupplied appendices? The project example's limitations are a strength, but its performance isn't independently established. **Analyst response:** Keep claims within the stated test conditions and don't force a recommendation when the findings don't support one. [S-11, `#out11-1`, `#out11-2`, `#ex11-1`, `#ex11-2`] ### Chapter 12 — Research Reports **Purpose/thesis:** Select and synthesize research to answer a focused technical question (C-029). The QuantumCPU report and its documentation are explicitly fictional; the Ferranti Pegasus report is presented as historical research. Primary-method discussion includes interviews, surveys, experiments, measures, and human-research approval. **Terms:** primary/secondary research, synthesis, CRAAP. **Evidence:** report models, source-evaluation questions, and methodological examples. **Boundary/question:** Does an authoritative-looking source have appropriate methods and independent corroboration? CRAAP is a screening aid, not a substitute for examining evidence. **Analyst response:** Trace important claims through sources and record dependence; don't describe the chapter as lacking research-method discussion. [S-12, `#ex12-1`, `#ex12-2`, `#sec2-03`–`#sec2-06`, `#fig12-3`] ### Chapter 13 — A3 Reports **Purpose/thesis:** Use a concise visual record to develop and communicate collaborative problem solving (C-016). The mouse-loss example links current state, target, causes, options, assignments, and follow-up. Hospital and manufacturing examples show other layouts. **Terms:** Lean, consensus, root cause, countermeasure, PDCA. **Evidence:** examples and professional references; no controlled adoption study. **Boundary/question:** Is agreement real, and does someone own the follow-up? The authors explicitly criticize forced consensus, premature completion, and attention to page dimensions at the expense of analysis. **Analyst response:** Treat the A3 as evidence of a process only when the investigation, decisions, and follow-up are traceable; the authors explicitly say it doesn't make a company Lean. [S-13, `#sec2-01`–`#sec2-05`, `#fig13-2`–`#fig13-6`] ### Chapter 14 — Abstracts and Summaries **Purpose/thesis:** Condense information differently for selection, study, or decision (C-017). Descriptive abstracts identify coverage; informative abstracts convey substance; academic summaries preserve main ideas; executive summaries support a decision without reading the whole report. **Terms:** stand-alone summary, keywords, fidelity. **Evidence:** paired QuantumCPU abstracts, a summary of the chapter, and a hospital-maintenance executive summary. **Boundary/question:** Which qualification would change the reader's decision if removed? The authors prioritize actual submission requirements over defaults and distinguish A3s as summaries of a process rather than a text. **Analyst response:** Preserve decision-changing limits even when a one-page convention encourages compression. [S-14, `#sec3-01`–`#sec3-07`, `#sec2-03`] ### Chapter 15 — Style and Mechanics **Purpose/thesis:** Use economy, precision, and coherent mechanics to express technical meaning (C-018–C-019). Examples replace vague claims with quantities and show how modifiers, pronouns, punctuation, and parallelism affect interpretation. **Terms:** economy, antecedent, active/passive, agreement. **Evidence:** before/after examples and convention-based explanations. **Boundary/question:** Does a shorter sentence retain necessary conditions? The chapter permits passive voice when the actor is irrelevant, recognizes prestige-language prejudice, supports stated pronouns and singular they, and rejects ranking English varieties. **Analyst response:** Preserve these qualifications; don't adopt every grammatical shortcut as a complete language rule or treat a dialect difference as technical incompetence. [S-15, `#sec2-02`–`#sec2-05`, `#sec3-05`, `#sec2-14`, `#sec2-22`] ### Chapter 16 — Documentation **Purpose/thesis:** Make borrowed information attributable and recoverable (C-006). Here documentation means citations, not the entire software-help system. Examples cover print, websites, repositories, interviews, and other sources; version or commit information can identify a code source. **Terms:** common knowledge, reference, locator, consulted/cited. **Evidence:** citation examples and style guidance. **Boundary/question:** Can a reader locate the actual version and distinguish cited sources from material merely consulted? The chapter acknowledges missing metadata and warns against trusting automatic citations. **Analyst response:** Keep recoverability and attribution; replace its categorical fair-use formula with a current, jurisdiction-specific source. [S-16, `#sec2-01`–`#sec2-06`, `#sec3-01`, `#sec3-07`] ### Chapter 17 — Visuals **Purpose/thesis:** Select and label visuals so they communicate the intended evidence without distortion (C-020–C-021). A truncated-axis chart makes a $1,000 difference between $68,000 and $69,000 look larger; the repair adds a zero baseline, units, patterns, and context. **Terms:** reproducibility, chart, diagram, schematic, typography. **Evidence:** deliberate good/bad visual contrasts. **Boundary/question:** Can a reader recover the same meaning without color or visual perception? The chapter addresses color-vision access and rejects fabricated photographic diversity, but this EPUB leaves informative raster content without alt attributes. **Analyst response:** Keep its integrity checks, add semantic alternatives, and qualify its universal serif-font and large-type judgments. [S-17, `#sec3-01`, `#sec3-03`, `#fig17-2`, `#fig17-3`, `#sec3-11`] ### Chapter 18 — Presentations **Purpose/thesis:** Match spoken content, organization, terminology, and media to an audience and situation (C-022). Dog-treat manufacturing slides move from dense prose toward an assertion plus a visual. **Terms:** informative, demonstrative, persuasive, impromptu, extemporaneous, manuscript. **Evidence:** slide models, rules of thumb, and presentation advice; no measured attention study accompanies its universal claims. **Boundary/question:** Can the delivery mode meet language and disability needs? The book permits scripts for translation or legal precision and sitting in some settings. **Analyst response:** Retain rehearsal, equipment checks, and substantive summaries; add captions, accessible materials, and flexible participation instead of enforcing a single performance style. [S-18, `#sec2-01`–`#sec2-04`, `#sec3-07`, `#fig18-5`, `#fig18-6`] ### Chapter 19 — Business Communications **Purpose/thesis:** Choose a medium and structure that support action and the relationship (C-023). A poor enrollment email contrasts with a contextualized request. A course-agreement memo sets reciprocal responsibilities and includes accommodation provision. **Terms:** transmittal, memorandum, record, inquiry. **Evidence:** actual/fictitious messages and templates, not response-rate trials. **Boundary/question:** Does an informal conversation need a later written record? The chapter asks teams to agree on messaging rules and security approval and recognizes different comfort levels. **Analyst response:** Keep the clear request, timing, recipient check, and appropriate record; don't treat a phone call as guaranteed confidentiality. [S-19, `#ex19-1`–`#ex19-3`, `#sec2-05`, `#sec2-06`] ### Chapter 20 — Communications with Future Employers **Purpose/thesis:** Present job-relevant evidence through an application and conversation sequence (C-024–C-025). Sunny Misumoto's package demonstrates selective evidence, quantified work, a tailored letter, and follow-up. **Terms:** resume, CV, networking, screening, fit. **Evidence:** example documents, career advice, and personal stories. **Boundary/question:** Which apparent professionalism rules measure capability, and which measure conformity or access? The authors acknowledge field/region differences, nontechnical paid work, hardship, and the candidate's right to assess fit. They also use judgmental one-page rhetoric and prescribe eye contact, grooming, and handshakes. **Analyst response:** Retain truthful evidence and preparation; adapt format and interaction to current requirements and access needs without pressuring private hardship disclosure. [S-20, `#sec3-01`, `#sec3-05`, `#sec2-02`, `#sec3-12`, `#ex20-2`] ### Chapter 21 — Team Writing **Purpose/thesis:** Integrate expertise into one document through shared requirements, assigned work, coordination, and revision (C-026). Student snow-removal work and a government proposal illustrate different scales of collaboration. **Terms:** ground rules, theme, compliance matrix, lead writer, iteration. **Evidence:** process models, group-development references, and the coauthors' workflow. **Boundary/question:** Can everyone contribute, review, learn, and receive recognition? The chapter requires tool access for all, permits shared leadership, and says the lead writer mustn't become the only writer. **Analyst response:** Use its explicit responsibilities and whole-document review, then add a way to resolve disagreements and preserve ownership after delivery. [S-21, `#out21-1`, `#sec3-03`, `#sec3-04`, `#sec3-09`, `#sec3-10`] ### Argument sequence and weakest link 1. People need to understand, decide, or act on technical information. 2. Their knowledge, purpose, and setting determine the necessary information. 3. Definitions, descriptions, and instructions organize different kinds of meaning. 4. Genres arrange those elements around recurring reader needs. 5. Evidence, source attribution, clear language, visuals, and review support the genre's purpose. 6. Writers should choose and revise the document against that purpose. **Weakest link:** The book often moves from a plausible demonstration or familiar convention to a broad claim of effectiveness. Neither a polished example nor teaching experience establishes universal reader outcomes. The repair is to narrow the claim to its situation and add actual reader evidence; it doesn't require rejecting the genre framework. ### Evidence ledger | Evidence ID | Claims | Type and source | Independence and quality | Limits | | --- | --- | --- | --- | --- | | E-01 | C-001–C-003, C-009–C-018, C-023–C-026, C-030 | Authored examples, dissections, checklists; S-PRE, S-01–S-21. | One coauthored instructional source family; direct evidence of the method taught. | Fiction and repetition aren't independent tests of effectiveness. | | E-02 | C-005, C-006, C-008 | Professional ethics cases and legal sources cited in S-02/S-03/S-16. | External sources are named, but most underlying cases weren't independently retrieved in this session. | Grade the book's account separately from the original case. | | E-03 | C-007 | Mueller/Oppenheimer 2014 and Carter et al. 2017 cited by S-03. | Independent studies exist in the reference list. | Their full methods weren't reread here; citing them doesn't establish every learning context. | | E-04 | C-007 | Urry et al. 2021 direct replication; publisher abstract inspected. | Independent counterevidence for the narrow immediate-learning assertion; 74 laptop and 68 longhand participants. | Immediate quiz without study opportunity; not every learning outcome or access need. [Study](https://doi.org/10.1177/0956797620965541). | | E-05 | C-004 | FAA stall explanation and NASA's accessible black-hole explanation. | Independent technical authorities; directly relevant to definition accuracy and the alleged tradeoff. | They test examples, not the whole pedagogy. [FAA](https://www.faa.gov/sites/faa.gov/files/2022-01/Angle%20of%20Attack%20Awareness.pdf), [NASA](https://spaceplace.nasa.gov/black-holes/en/). | | E-06 | C-006, C-028 | Copyright Office fair-use framework and NLRB social-media guidance. | Independent primary legal guidance, read in this session. | US scope; not an individualized legal determination. [Copyright Office](https://www.copyright.gov/fair-use/), [NLRB](https://www.nlrb.gov/about-nlrb/rights-we-protect/the-law/employees/social-media). | | E-07 | C-012, C-014, C-020 | Original-image inspection and arithmetic/source-consistency checks. | Reproducible checks of the supplied artifact. | Establish local errors or design features, not how often the book errs. | | E-08 | C-020–C-022 | XHTML image inventory and selected raster inspection, compared with WCAG's non-text-content requirement. | Direct markup evidence plus an independent accessibility standard. | No complete conformance or screen-reader assessment. [WCAG 2.2](https://www.w3.org/TR/WCAG22/#non-text-content). | Four ledger rows contain independently retrieved external evidence (E-04, E-05, E-06, E-08). That is **not four independent demonstrations that the book's methods work**. E-04–E-06 qualify or oppose specific overstatements; E-08 exposes a delivery gap. E-02/E-03 remain partially verified bibliographic pointers. ### Reading and completion controls For future use, give high attention to the matching genre, its assumptions, and its evidence; medium attention to related style/visual chapters; skim repeated explanations only after you understand their role. Before teaching, externally check the factual examples and current rules you plan to use. Compare abstraction/ambiguity, documentation/citation, and A3/summary terminology before reusing those words. Prompt 7 begins only after every chapter has a source entry, all 30 claims have scopes and tests, fiction and exercise status are separated, and the counterevidence is recorded. Those conditions are met. No reader experiment or book exercise has been run as part of this reading session. ## Prompt 7 — evaluation and fair criticism ### Strongest reconstruction **Authors say:** Readers need accurate technical information shaped for their purpose and context. Genres reduce the writer's uncertainty by organizing recurring decisions and actions. Examples and checklists teach how to construct those genres. **Authors imply:** Writers who learn the recurring moves can transfer them to new technical tasks. The preface's teaching experience supports this as a practical expectation, not a quantified guarantee. **Evidence shows:** The book implements that sequence across 21 chapters and supplies contrasting models. It also contains local inaccuracies, inconsistent shortcuts, and untested generalizations. **We infer:** Its transferable value lies in asking why each document element is needed, then checking the resulting communication against a real task. **We conclude:** Adopt the genre distinctions and review questions. Repair overbroad claims, verify technical content, and supply accessible delivery. **Still uncertain:** Comparative learning gains, actual workplace adoption results, the best method for a particular reader, and the accuracy of examples not independently checked. ### Claim-by-claim evaluation Grades assess **support for the stated claim**, not whether the advice sounds familiar. A = direct, strong, independently supported; B = substantial but limited; C = suggestive/incomplete; D = weak or poorly matched to the generalization; F = unsupported or contradicted as stated; N/A = chiefly definitional or normative. A B for a method means the example explains it well, not that controlled outcome evidence exists. | Claim | Support and grade | Strongest objection / counterexample | Current conclusion and repair | | --- | --- | --- | --- | | C-001 | B — repeated situations show how purpose changes content. | Sponsor-defined audience can exclude affected people. | Keep; add indirect readers and affected stakeholders. | | C-002 | C — funnels show increasing specificity. | A precise model or API abstraction can clarify through omission. | Reduce harmful ambiguity; don't eliminate useful abstraction. | | C-003 | B — pattern and extensions are explained in detail. | A definition can fit the pattern and still misstate the mechanism. | Keep as a drafting pattern with content verification. | | C-004 | D — examples don't prove accuracy must be sacrificed. | FAA corrects the stall mechanism; NASA gives an accessible accurate core definition. | Reduce detail, preserve the causal core, label limits. | | C-005 | N/A — explicit moral reasoning. | A sincere writer can negligently cause foreseeable harm. | Intent matters but isn't sufficient; add effects and accountability. | | C-006 | B — citation practice has extensive direct support; legal shortcuts are weaker. | Attribution doesn't by itself authorize reproduction or settle fair use. | Retain source credit; separate the legal inquiry. | | C-007 | D — cited studies don't establish the universal claim. | A direct replication doesn't support the proposed immediate-learning advantage. | Choose and test an accessible method for the task; no universal paper rule. | | C-008 | B — source capture and professional records have coherent examples. | More notes can also preserve errors or expose confidential information. | Keep with accuracy, access, ownership, and retention rules. | | C-009 | B — part/function examples make the method usable. | A physical-attribute inventory can obscure a software relationship. | Use the structure only where parts and attributes answer the reader's question. | | C-010 | B — stages and transitions are demonstrated; branching exceptions are explicit. | A linear sequence cannot represent all concurrent paths. | Keep the author's own contextual exception. | | C-011 | B — instructions identify action and expected results. | Clear-looking directions can omit tacit steps. | Keep; add representative-reader testing as analyst application. | | C-012 | B — proposal components and effort/schedule distinction are clear. | A credible format can contain unmeasurable promises and incorrect costs. | Require baselines, verified arithmetic, and explicit exclusions. | | C-013 | B — baseline/status/forecast structure is direct. | Date inconsistency and unsupported optimism can mislead management. | Reconcile source records and state what remains uncertain. | | C-014 | B — criteria and comparison are well explained. | Hidden weights or a failed threshold can invalidate a recommendation. | Separate hard constraints, preferences, and evidence; test sensitivity. | | C-015 | B — models distinguish method, findings, interpretation, and limits. | Missing appendices prevent complete reproducibility. | Keep; supply enough method and evidence for the claimed result. | | C-016 | B — process and artifact are distinguished; misuse is explicitly discussed. | A polished page can conceal coercion or no follow-through. | Keep the anti-coercion and follow-up conditions. | | C-017 | B — four purposes and source fidelity are explained. | A one-page constraint can remove a decision-changing qualification. | Let the real decision and submission requirements control length. | | C-018 | B — edits demonstrate clarity mechanisms. | Deleting a necessary qualifier changes the technical claim. | Edit for exact meaning before shortness or house style. | | C-019 | N/A — respect and language-variety principles. | Institutional conventions can still penalize difference. | Retain respect; distinguish accommodation from enforced conformity. | | C-020 | B — chart contrasts expose specific distortions. | An accurate picture still excludes readers without a usable equivalent. | Preserve data integrity and provide semantic alternatives. | | C-021 | D — a universal font claim lacks matched evidence here. | Reader, script, size, medium, and individual access needs vary. | Treat font choice as a context-dependent design decision. | | C-022 | C — models explain presentation choices, not guaranteed attention. | Compliant slides can still fail comprehension; one performance style excludes some presenters. | Keep preparation; assess understanding and support alternate delivery. | | C-023 | B — messages demonstrate purpose, context, and action. | A medium preference can conflict with accessibility or recordkeeping. | Match the medium to the participants and required record. | | C-024 | C — examples show tailoring; no causal hiring comparison. | Relevant candidates can lack networks or face biased screening. | Use truthful evidence without promising an interview or job. | | C-025 | D — conventions and opinions don't establish capability. | Eye-contact/handshake rules don't fit every disability, culture, or format. | Treat contingent expectations as information, not a measure of worth. | | C-026 | B — roles, integration, and whole-document review are explicit. | A designated leader doesn't automatically distribute workload fairly. | Keep shared access/review; record authority and conflict handling. | | C-027 | F — literal forever/everyone claims lack a universal technical basis. | Persistence and access depend on copies, permissions, retention, and deletion mechanisms. | Warn that copies may persist or spread; don't promise universal retention or access. | | C-028 | D — dismissal stories support possibility, not a blanket speech rule. | Some group discussion of working conditions is legally protected. | Distinguish harmful disclosure, discriminatory conduct, and protected reporting/activity. | | C-029 | B — methods, source scrutiny, and synthesis are explicit. | A checklist can't establish research validity or independence. | Examine methods and trace sources beyond appearance and authority. | | C-030 | C — teaching experience plus enacted examples. | Students can imitate layout without understanding the genre. | Assess transfer to a new audience and purpose, not template completion. | **Grade distribution:** 18 B, 4 C, 5 D, 1 F, and 2 N/A; no A grades. The pattern favors the book's explained procedures over its broad empirical generalizations. The moral/language principles receive N/A rather than invented measurements, and none of the instructional methods earns a claim of independently established universal effectiveness. ### Reproduced checks and substantive repairs **1. A clear definition can teach the wrong mechanism.** Chapter 4 defines an aircraft stall through lift falling below weight and describes it as insufficient speed. Figure 4.2 repeats the lift/weight formulation. The FAA identifies exceeding the critical angle of attack as the cause and explains that a wing can stall at any airspeed. This is a content error in a teaching model, not an intentional critique exercise. Repair the definition around the aerodynamic condition, then explain the term at the audience's level. [S-04, `#sec2-01`, `#fig4-2`; FAA, E-05](https://www.faa.gov/sites/faa.gov/files/2022-01/Angle%20of%20Attack%20Awareness.pdf). **2. Simplification doesn't require the stated false choice.** Chapter 4 contrasts an expert black-hole definition with a supposedly accessible version that calls a black hole a collapsed neutron star and adds claims about fusion inside it. NASA's explanation for children states the essential gravity/escape property without those assertions. That provides a counterexample to the forced choice between intelligibility and accuracy; it doesn't establish that every technical detail belongs in a novice definition. [S-04, `#sec2-06`; NASA, E-05](https://spaceplace.nasa.gov/black-holes/en/). **3. The proposal budget has a verifiable arithmetic error.** Table 8.1 prints travel as **60 miles at $0.35 per mile**, with a cost of **$48**. The product is **$21**. Holding the table's other rows fixed, its **$3,248** total becomes **$3,221**. The error is **$27**. Both the original image and the calculation were checked. This is a worked model, separate from the later intentionally deficient wastewater exercise. [S-08, `#tab8-1`] **4. A conclusion must resolve its table's mismatch.** The microphone model lists required sensitivity of **12.5 mV/Pa** and actual sensitivity of **10.2 mV/Pa**, yet says all requirements are met or exceeded. The report supplies no acceptance rule explaining that difference. Its categorical conclusion therefore doesn't follow from the displayed requirements. This is an internal-document finding, not a test of a real microphone. [S-10, `#tab10-2`, `#ex10-2`] **5. The paper-versus-computer claim is too broad.** The inspected abstract of Urry et al.'s direct replication reports 142 participants and doesn't support the claim that longhand improves immediate learning through better encoding. The study's immediate quiz without review doesn't decide long-term learning, every course, or disability access. The warranted update is to reject the textbook's universal formulation, not to declare typing universally better. [S-03, `#sec2-02`; E-04](https://doi.org/10.1177/0956797620965541). **6. Attribution and lawful use are different checks.** Chapter 16 says fair use requires full documentation and that lacking it makes the use a copyright violation. The Copyright Office instead describes a case-specific, four-factor inquiry; educational purpose alone doesn't settle it. Chapter 2's early rules already distinguish permission/fair use from citation more carefully. Repair the later shortcut by preserving that distinction. [S-02, `#sec2-01`; S-16, `#sec3-01`; E-06](https://www.copyright.gov/fair-use/). **7. Employer discomfort isn't the only relevant boundary.** Chapter 2 advises avoiding complaints about work or supervisors. NLRB guidance says some social-media discussions of pay, benefits, and working conditions can be protected concerted activity; individual griping isn't automatically protected. This qualifies a blanket avoidance rule without excusing threats, discriminatory conduct, or confidential disclosure. [S-02, `#sec2-04`; E-06](https://www.nlrb.gov/about-nlrb/rights-we-protect/the-law/employees/social-media). **8. A historical date also needs precision.** Chapter 3's attorney commentary calls the America Invents Act a 2012 law. USPTO records enactment on **September 16, 2011**, with first-inventor-to-file provisions effective **March 16, 2013**. This corrects the historical shorthand; no patent advice is inferred. [S-03, `#sec2-04`; USPTO enactment](https://www.uspto.gov/patents/laws/america-invents-act-aia/global-impacts-aia), [effective date](https://www.uspto.gov/patents/first-inventor-file-fitf-resources). The book also contains **deliberately deficient exercises**: the submarine, skating jump, unsafe kick, wastewater reports, and job-choice exercise ask readers to identify problems. Their defects aren't counted as the authors endorsing the defective reasoning. Fictional data are judged for instructional consistency, not mistaken for fabricated empirical research. ### Priors and posteriors, without false precision | Claim | Prior | Evidence evaluated | Qualitative update | Current confidence and reason | | --- | --- | --- | --- | --- | | C-001 | High | Reader-specific examples and contextual failure case. | No meaningful update. | High in the narrow design principle; outcomes still need testing. | | C-002 | Moderate | Funnel examples plus the chapter's own familiarity caveat. | Moderately decreases confidence in the absolute form. | Low in eliminating abstraction; moderate in reducing harmful ambiguity. | | C-004 | High confidence in accurate simplification | FAA correction and NASA's accessible explanation. | Moderately increases confidence in the prior. | High that the textbook hasn't established a necessary accuracy tradeoff. | | C-005 | High that intent isn't sufficient | Fiction-versus-fraud comparison doesn't address negligent harm. | No meaningful update. | High in the boundary; moral conclusion, not a posterior probability. | | C-007 | Moderate skepticism of universal paper superiority | Independent replication abstract against the narrow encoding account. | Moderately decreases confidence in the book's generalization. | Low in universality; uncertain across all learning contexts. | | C-011 | High in reader testing as an application | Detailed step structure but no developed test method. | No meaningful update. | High as a proposed verification practice; not falsely attributed to the chapter. | | C-014 | Moderate | Explicit criteria method and contradictory model result. | No meaningful update on the method. | Moderate; examples illustrate why independent checking remains necessary. | | C-016 | Moderate | Explicit process/format distinction and anti-coercion caveat. | Moderately increases confidence in conceptual fit. | Moderate; no causal adoption study. | | C-021 | Moderate skepticism of a universal font ranking | Uncited generalization; no matched comparative study inspected. | No meaningful update. | Low support for universality; actual font choice remains contextual. | | C-026 | High | Tool access, shared work, whole-document review, and workflow. | No meaningful update. | High in explicit coordination; local workload fairness remains untested. | ### Biases, fallacies, and counter-observations - **False dilemma:** C-004 makes accuracy and intelligibility appear mutually exclusive. The NASA comparison repairs this by retaining the core property while omitting specialist detail. This materially changes the teaching rule. - **Insufficient generalization:** C-007 and C-021 move beyond the scope of their presented evidence. Narrow them to a task, population, outcome, and medium before use. - **Intention/effect conflation:** C-005 treats benign intent as sufficient. The repair costs the original definition its simplicity but preserves its opposition to deception. - **Descriptive/normative slippage:** C-025 and C-028 risk turning employer preferences or sanctions into a standard of ethical or professional merit. Keep the practical context while allowing rights, access, and cultural variation. - **False precision risk:** A weighted matrix or numerical promise can look objective while hiding a baseline, hard constraint, or value choice (C-012/C-014). This is a risk demonstrated by document structure, not an accusation that all weighting is fallacious. - **Counter-observations:** The authors allow passive voice, acknowledge language change, recognize non-US English, admit limitations in the road project, oppose forced A3 consensus, permit shared leadership, and repeatedly prioritize actual audience requirements. These concessions argue against portraying the book as uniformly rigid. No claim of deliberate deception, author motive, systematic discriminatory intent, or measured prevalence follows from this analysis. The literal permanence claim cannot be repaired while retaining its absolute wording; it can be replaced with a narrower caution about persistence and dissemination. ## Prompt 8 — systems and intellectual context ### Context available to the revising authors The fourth edition combines Finkelstein's engineering-communication text with Aune and Potter's teaching experience at Iowa State. The preface describes a curriculum problem: engineering classes already carry substantial technical content, so instructors need writing instruction they can incorporate into those classes. That explains the modular chapters, repeated definitions, whole examples, dissections, and checklists. Repetition is a stated design choice, not evidence that the authors accidentally forgot earlier material. [S-PRE] The examples reflect engineering education, manufacturing, laboratories, military systems, workplace reporting, and US collegiate hiring. The book also includes family, equestrian, music, and dog analogies. These broaden the range of examples while assuming familiarity with some cultural references. The preface acknowledges that readers may dislike dogs, have allergies, or avoid them for religious reasons; it nevertheless assumes general familiarity with dogs and breeds. [S-PRE; S-01–S-21] References and situations often come from 2020–2021: remote teaching, pandemic precautions, online job searches, digital collaboration, and social-media consequences. Publisher pages promote Connect, remote proctoring, learning tools, and grading efficiency. Those promotions have different incentives and attribution from the authors' instructional argument. The source's claim that proctoring reports avoid personal bias is a **publisher claim without a fairness evaluation supplied here**; it isn't adopted as a finding. [Front matter, `09_acknowledgments.xhtml`, `10_connect.xhtml`] ### Intellectual-lineage map | Tradition or predecessor | Relationship supported by this source | What mustn't be inferred | | --- | --- | --- | | Audience/purpose/context and genre instruction | Explicit organizing framework in the preface and Chapter 1. | No claim that the authors originated those concepts. | | Engineering descriptions and formal reports | Core teaching forms, illustrated throughout Chapters 4–12. | No single format governs all disciplines or organizations. | | Cornell notes and visual note methods | Named alternatives in Chapter 3. | Their inclusion doesn't establish one universally best method. | | Toyota/Lean problem solving | Chapter 13 names A3, consensus building, direct observation, and PDCA. | A3 adoption isn't equivalent to adopting a Lean culture. | | Visual evidence traditions | Chapter 17 cites Tufte and Huff and demonstrates misleading encodings. | Those citations don't independently validate every typography claim. | | Group development | Chapter 21 names Tuckman's stages and later team literature. | The chapter doesn't establish that all teams move through an identical sequence. | | Software documentation practice | Existing vault notes provide a useful comparison for user research, versioning, and maintenance. | This is convergence/application, not documented causal influence on this book. | ### Context added by this analysis The 2021 replication of the handwriting study predates the publisher's 2022 release but follows many of the book's 2020 access dates. The available evidence doesn't show whether the revising authors saw it; don't assume deliberate exclusion. The current legal and accessibility sources are **external evaluation**, not text retroactively attributed to the book. For software documentation, this book contributes genre selection and evidence organization. The existing vault notes on [[4. Archives/Book reviews/Docs for Developers]], [[4. Archives/Book reviews/Docs Like Code]], [[4. Archives/Book reviews/The Product is Docs]], and [[4. Archives/Book reviews/Modern Technical Writing]] address adjacent concerns such as user research, review, publishing, and maintenance. Only their overview sections were consulted for this comparison; their books weren't reread as part of this session. **System inference:** Document success depends on more than the writer's skill. Sponsor priorities determine what gets funded, institutions define accepted formats, teams control review and publication, and readers bear the cost of omissions. The book recognizes many of these relationships, but its strongest practical procedures concentrate on producing the document. Maintenance after delivery and accessible publication need fuller treatment for ongoing software documentation. ## Prompt 9 — DEIB, multicultural, accessibility, and reading demands ### Inclusion strengths with textual support - **Language and identity:** Chapter 15 supports using stated pronouns and singular they, rejects ranking English varieties, and recommends feedback from the intended audience's country. These are explicit positions, not inferred from diverse example names. [S-15, `#sec2-14`, `#sec2-22`] - **Participation:** Chapter 21 requires access to collaboration tools for every member, permits shared leadership, and separates lead writing from doing everyone else's work. Chapter 13 rejects forced consensus. These are procedural protections, although their effectiveness isn't measured. [S-21, `#sec3-03`, `#sec3-09`; S-13, `#sec2-05`] - **Audience differences:** Chapter 7 discusses translation, reading literacy, device/environment variation, and individual differences in workstation setup. Chapter 19's course-agreement example includes accommodations. [S-07, `#sec2-01`, `#ex7-1`; S-19, `#ex19-3`] - **Visual integrity:** Chapter 17 addresses color-vision differences and criticizes altering photographs to fabricate demographic diversity. It asks writers to support the actual information rather than manufacture an appearance of inclusion. [S-17, `#sec3-01`, `#sec3-10`] - **Career context:** Chapter 20 recognizes paid nontechnical work, family hardship, field differences, and the applicant's own assessment of organizational fit. [S-20, `#sec3-05`, `#sec3-06`, `#sec3-12`] ### Exclusion and omission risks | Dimension | Textual observation | Analyst assessment and adaptation | | --- | --- | --- | | Agency and power | Decision-makers, advisors, and implementors dominate audience categories; fraud victims and affected residents appear in ethical examples. | Add people affected by the decision even when they neither approve nor implement it. | | Class and institutional access | Examples assume some access to equipment, instructors, libraries, professional clothing, and networks. | Provide low-cost practice materials and assess relevant evidence rather than access to status signals. | | Gender | Stated pronouns receive support; some business-letter defaults remain gendered. | Use the recipient's stated name, title, and pronouns; don't infer identity from appearance or a name. | | Race and ethnicity | Names and examples vary; fabricated photo diversity is rejected. | Representation alone doesn't establish equitable hiring, participation, or outcomes. No demographic outcome data are supplied. | | Religion and culture | The preface acknowledges reasons some readers avoid dogs. | Offer a non-animal analogy; the breed taxonomy isn't necessary to learn genre distinctions. | | Geography | Engineering and hiring examples often assume US institutions despite the ISE label. | Verify local legal, academic, employment, and language requirements before transfer. | | Disability | Guide-dog imagery and accommodations appear; some advice equates easier reading with more pictures. | Pictures don't replace text for every reader. Provide alternatives and test with the intended access methods. | | Neurodiversity | Organization and repeated scaffolds can aid predictability; performance rules emphasize eye contact, stillness, and fluent delivery. | Those rules can burden some learners and presenters. Judge meaning and task performance; offer scripts and alternative participation. | | Digital/financial access | The book promotes digital learning products and assumes access to tools; Chapter 21 explicitly checks team access. | Offline access, assistive support, and a no-purchase route need explicit planning. | | Universal claims from narrow evidence | Learning, fonts, and hiring advice generalize beyond the supplied support. | State the population, task, and outcome before adopting a rule. | These are observations about the text and risks of application. The source doesn't supply the demographic data needed to measure differential outcomes or infer the authors' private attitudes. ### Multicultural transferability | Practice | Transfer assessment | Required adaptation | | --- | --- | --- | | Reader/purpose/context inquiry | Strong conceptual transfer. | Ask local users; don't import the audience profile. | | Definition by class and difference | Useful starting form. | Check local terminology, translation, and alternative conceptual categories. | | Proposal/report structure | Useful when it matches the receiving institution. | Follow actual submission requirements and explain unfamiliar genre names. | | English style conventions | Conditional. | Select the intended English variety; explain rather than stigmatize differences. | | Ethics, citation, copyright | Attribution principle transfers; specific rules vary. | Separate ethical credit from jurisdiction, license, contract, and discipline rules. | | Resumes, titles, interviews | Strongly context-dependent. | Confirm field/country norms, access needs, and employer instructions. | | A3 and team process | Conditional on participation and authority. | Preserve dissent, accessible records, ownership, and follow-up. | ### Artifact accessibility audit The XHTML inventory finds **489 image occurrences** across the 33 spine documents: **485 omit `alt` and 4 have empty `alt`**. Counts include repeated checkboxes, logos, and decorative images; they aren't counts of unique substantive figures. Selected source images confirm that budgets, comparison data, A3 examples, grammar corrections, and slides can contain meaningful text that isn't fully repeated in surrounding prose. | Check | Observed result | Practical implication | | --- | --- | --- | | Extractable text and structure | Chapters contain text, headings, native IDs, and page markers. | The book isn't wholly image-based; useful navigation and search are possible. | | Informative image alternatives | No nonempty `alt` values in the inventoried image tags. | Important raster content needs equivalent text or another accessible representation. Captions recover only part of some examples. | | Color | Chapter 17 teaches non-color distinctions and includes patterned chart repairs. | This is a content strength; it doesn't establish every figure's contrast or nonvisual equivalence. | | Dense pages | A3 examples and some tables/slides compress multiple relationships. | Supply linear explanations and readable data; don't make one-page appearance the only accepted form. | | Typography | Font/point-size advice prioritizes conventional appearance. | Actual legibility and user enlargement requirements take precedence. | | Audio and speech | Presentation advice lacks a developed captions/transcripts workflow. | Add captions, transcripts, accessible handouts, and alternate participation for teaching. | | Assistive technology and reflow | No full screen-reader, keyboard, contrast, or ebook-reader reflow test performed. | No conformance claim or blanket statement about every reader's behavior. | WCAG 2.2's non-text-content criterion supplies a relevant benchmark for text alternatives; a complete EPUB accessibility determination requires more than this markup inventory. [WCAG 2.2, SC 1.1.1](https://www.w3.org/TR/WCAG22/#non-text-content). **Reading level estimate:** Upper-secondary to undergraduate syntax, with higher reference demands in electronics, physics, chemistry, research, and hiring examples. This is an analyst estimate, not a measured grade level. The repeated outlines and plain explanations lower some syntactic burden; unfamiliar breeds, acronyms, jokes, equations, and raster text add separate burdens. A reader can understand each sentence and still lack the technical background to judge its example. **Supplementary perspectives:** Include intended users with disabilities, multilingual readers, people outside US collegiate hiring, and affected non-decision-makers in review. For instructional design, pair this book's genre models with the user-research and maintenance perspectives in the linked documentation notes. These additions are recommendations, not claims that those perspectives were consulted during this session. ## Prompt 10 — notes pipeline All note candidates remain embedded. Suggested filenames are names for possible future extraction, not newly created files or unresolved links. ### Fleeting notes - Does a document fail because its sentences are unclear, or because its genre answers the wrong reader question? Compare C-001 with C-012–C-017. - Which of your technical explanations needs an accurate simpler definition? Use C-003/C-004, without assuming you prefer more or less detail. - Which uncertainty disappears when a report becomes a one-page summary? Check C-017 before treating brevity as success. - Who inherits maintenance after the team delivers? Q-24 remains open; Chapter 21 supplies production coordination more fully than ongoing ownership. - Personal surprise, disagreement, and reading motivation remain unrecorded because you haven't supplied them. ### Literature notes **LN-01 — A document's structure follows its reader's decision.** The preface and Chapter 1 connect audience, purpose, and context to genre selection. The same subject can require a description, proposal, feasibility report, or instructions. This is the authors' organizing principle, supported by examples rather than comparative reader studies. C-001; S-PRE; S-01. ^ln01 **LN-02 — Definitions need both a useful form and correct content.** Chapter 4 offers classification plus differentiation and several extensions. Its stall and simplification examples show why the formal pattern needs a separate accuracy check. The first sentence is the authors' method; the second is this analysis's source-checked criticism. C-003–C-004; S-04; E-05. ^ln02 **LN-03 — Requests and reports preserve a chain of commitments.** Chapters 8–11 distinguish proposed work, actual progress, option evaluation, and tested findings. Their recurring examples show how later documents depend on earlier scope and criteria. Dates, costs, and conclusions still require checking across versions. C-012–C-015; S-08–S-11. ^ln03 **LN-04 — A3s summarize problem solving, not another document.** Chapter 13 treats an A3 as both a process and its concise record. Chapter 14 explicitly distinguishes it from summaries of texts. The authors warn against forced agreement and missing follow-up. C-016–C-017; S-13 `#sec2-05`; S-14 `#sec2-03`. ^ln04 **LN-05 — Visual integrity and accessible delivery are separate checks.** Chapter 17 demonstrates misleading axes and supports color-independent distinctions. The EPUB's raster tables and absent image alternatives create a separate delivery problem. The first observation comes from the book; the second comes from this session's artifact audit. C-020; S-17; E-08. ^ln05 **LN-06 — Team authorship requires shared review and access.** Chapter 21 assigns coordination to a lead writer without making that person do everyone's work. It requires tool access and review of the complete document. This supports explicit collaboration practices without proving a universal team structure. C-026; S-21. ^ln06 ### Permanent-note candidates **PN-01 — Choose a document form from the decision it supports.** Before drafting, name the reader, the decision or action, and the conditions of use. Choose a genre because its information order supports that purpose. A correct template can still produce the wrong document if the initial purpose is wrong. **Confidence:** high as a design heuristic. **Scope and conditions:** technical communication with an identifiable use; negotiate conflicting audiences rather than assuming one universal reader. **Support:** [[#^ln01]], C-001. **Suggested filename:** `Choose document form from the reader decision.md`. **Attribution:** analyst synthesis. ^pn01 **PN-02 — Simplify detail without changing the causal explanation.** Remove specialist detail when it isn't needed for understanding or action, but preserve the relationships that make the explanation true. An accessible definition should remain compatible with a fuller account. Verify examples separately from their grammar. **Confidence:** high for this boundary; the best wording requires reader feedback. **Scope and conditions:** explanatory simplification, not a demand to include every exception in every sentence. **Support:** [[#^ln02]], C-003/C-004, E-05. **Suggested filename:** `Simplification must preserve the causal explanation.md`. **Attribution:** analyst repair, not an author quotation. ^pn02 **PN-03 — A recommendation needs traceable criteria, not just a score.** Record hard constraints, preferences, units, evidence, and weighting before treating a comparison as grounds for a decision. Check that every conclusion follows from the displayed values. Numerical appearance doesn't make a judgment neutral. **Confidence:** high for consistency checking; moderate for any particular weighting method. **Scope and conditions:** decisions involving alternatives and criteria; values and uncertainty remain explicit. **Support:** [[#^ln03]], C-014, E-07. **Suggested filename:** `Recommendations need traceable criteria.md`. **Attribution:** analyst synthesis. ^pn03 **PN-04 — A concise problem-solving record needs an accountable process.** A short page becomes useful when it records investigation, options, ownership, and follow-up. Brevity or visual polish alone doesn't establish agreement or improvement. Preserve unresolved questions and dissent. **Confidence:** moderate; evidence here is instructional and experiential. **Scope and conditions:** collaborative problem solving; accessible linear detail may accompany the visual. **Support:** [[#^ln04]], C-016. **Suggested filename:** `Concise problem records need accountable follow-up.md`. **Attribution:** analyst synthesis extending the authors' cautions. ^pn04 **PN-05 — Verify meaning in both the evidence and its delivery.** A correct chart can remain unusable if readers can't perceive its labels or access its data. Check the underlying numbers and their visual encoding, then provide a usable equivalent for nonvisual access. **Confidence:** high in the distinction. **Scope and conditions:** informative visuals; decorative images need different treatment, and automated markup checks don't replace user testing. **Support:** [[#^ln05]], C-020, E-08. **Suggested filename:** `Evidence integrity and accessible delivery need separate checks.md`. **Attribution:** analyst synthesis. ^pn05 ### Structure note and Idea Compass | Navigation | Connection | | --- | --- | | Parents | Reader-centered technical communication, evidence evaluation, professional responsibility: C-001, C-005, C-006. | | Children | Definitions, instructions, report criteria, summaries, team-review practices: [[#^pn01]]–[[#^pn05]]. | | Friends | [[4. Archives/Book reviews/Docs for Developers]] for reader research; [[4. Archives/Book reviews/Docs Like Code]] for review/publishing; [[4. Archives/Book reviews/The Product is Docs]] for organizational work. | | Competitors | Useful abstraction versus eliminating abstraction; accessible accurate simplification versus sacrificing accuracy; reader outcomes versus conventional professional appearance. These are competing propositions, not labels attached to people. | The internal map is **reader decision → definition/description/instruction → appropriate genre → evidence/review → delivery and follow-up**. Q-05 connects precision to learning; Q-09 connects reports to evidence; Q-20/Q-22 connect design to access; Q-24 connects production to maintenance. No project or MOC was edited and no reciprocal links were added elsewhere. ### Attribution audit Do **not** attribute to the authors: the five permanent notes as written; the numerical budget repair; the FAA/NASA correction; the current legal qualifications; the proposed reader tests; a claim that the authors endorse the book's deliberately bad exercises; a claim that they oppose singular they or all non-US English; the software-documentation analogies; or this analyst rating. No personal belief, emotion, reader highlight, or completed experiment has been invented. The local EPUB supplies author wording; source IDs identify paraphrases; external sources supply the stated checks; the analyst owns the repairs and applications. ## Prompt 11 — teaching pack **Audience:** Technical writers, engineering students, developer educators, or contributors who need to explain a system or justify a decision. **Prerequisites:** Familiarity with one low-risk technical task; no prior knowledge of Lean, electrical engineering, or the book's animal analogies is required. **Learning objectives:** Learners can (1) distinguish a mechanism description, process explanation, and instructions; (2) select a report genre from a reader's question; (3) preserve accuracy while simplifying; (4) reconcile a conclusion with criteria and data; and (5) identify a delivery barrier in a visual. **Key vocabulary:** Audience, purpose, context, genre, classification, differentiation, criterion, hard constraint, finding, interpretation, summary, A3, text alternative. ### Proposed 60-minute lesson | Time | Activity | Evidence of learning | | --- | --- | --- | | 0–10 min | Present one hypothetical file-export feature to a user, administrator, and budget owner. Learners state each person's question. | A reader/purpose/context statement for each. | | 10–20 min | Compare a parts description, process explanation, and action sequence for that feature. | Learners explain why the forms differ rather than identify headings alone. | | 20–30 min | Write a two-sentence definition for a novice; a partner marks any missing or false relationship. | Simplification retains the causal core and defines unfamiliar terms. | | 30–40 min | Inspect the Chapter 8 travel row and recalculate it; compare the Chapter 10 requirement with its conclusion. | Learners distinguish arithmetic errors from unsupported inference. | | 40–50 min | Convert a miniature report into either an executive summary or an A3 outline, explaining the choice. | Source fidelity for a summary; problem/process/owner/follow-up for an A3. | | 50–60 min | Review one chart and its text equivalent; revise the draft using observed feedback. | The numerical message is recoverable without color or seeing the chart. | The file-export scenario is **analyst-created**. No product behavior or command is presented as real. The table checks use source numbers already verified in Prompt 7. This is a lesson plan, not a session that has been taught. ### Discussion and misconception checks - **“All abstraction is bad.”** Ask learners to identify one precise generalization that helps more than a list of concrete cases. - **“A citation makes reuse legal.”** Separate attribution from permission, license, and applicable exceptions; use the legal-source qualification rather than adjudicating a participant's case. - **“Fewer words mean better communication.”** Ask what decision-changing condition disappeared in the edit. - **“The highest weighted score is feasible.”** Screen hard constraints before ranking preferences. - **“An A3 is a report shrunk to one page.”** Ask where the investigation, agreement, owner, and follow-up appear. - **“An accessible document just needs more pictures.”** Ask how the same meaning reaches a reader who can't see them. **Case studies:** The fictional proposal budget demonstrates arithmetic review; the stall definition demonstrates form versus factual correctness; the A3 versus executive-summary comparison demonstrates different purposes. Don't ask learners to perform hazardous, medical, financial, or physical procedures from the book. **Assessment options:** A short document with a stated audience/purpose/context; an annotated genre comparison; a peer explanation of a chosen criterion; or an oral/textual critique of a chart. Assess correct distinctions, source fidelity, logical support, and access. Don't grade eye contact, handwriting, accent, or conformity to one delivery style as subject mastery. **Reflection prompts:** Which assumption about the reader changed your draft? Which omitted detail would change the action? What evidence supports the conclusion? Which participant or affected group didn't appear in the original audience description? **Facilitator cautions:** Fictional technologies are not scientific evidence. The handwriting and font generalizations remain disputed or insufficiently supported. Do not attribute this analysis's repairs to the authors. Hiring examples can involve sensitive experiences; use fictional cases and don't require disclosure of grades, disability, finances, or family hardship. Disclose that image inspection was selective and that current external checks cover only named claims. **Accessibility and multicultural adaptations:** Supply accessible text before the session; use structured headings and editable tables; caption speech; allow typed, spoken, or asynchronous responses; support enlargement; explain idioms; provide a non-dog analogy; invite preferred names/pronouns and relevant local conventions without requiring personal disclosure. **Further reading:** Use the existing [[4. Archives/Book reviews/Docs for Developers]] note for reader research and [[4. Archives/Book reviews/Docs Like Code]] for review practices. Use the [Urry et al. study abstract](https://doi.org/10.1177/0956797620965541) to discuss evidence scope and [WCAG's non-text-content criterion](https://www.w3.org/TR/WCAG22/#non-text-content) for accessible equivalents. These sources answer specific gaps; they aren't interchangeable confirmations of the textbook. ## Prompt 12 — actions, PARA, experiments, and drift ### Action inventory | Category | Proposed action and reason | | --- | --- | | Take when drafting | State the reader, purpose, context, and chosen genre before outlining; it makes wrong-document errors visible. | | Take when reviewing | Recalculate displayed totals and compare conclusions with criteria; the source checks show that polished examples can fail both. | | Take when teaching | Label fiction, deliberate error exercises, and factual models; learners need to know which kind of evidence they're handling. | | Consider | Trial a short instruction or summary with intended readers, using the experiments below. | | Avoid | Turning an analyst synthesis into an author quotation or a personal conviction. | | Avoid | Enforcing handwriting, font, eye-contact, handshake, or one-page conventions as universal measures of competence. | | More evidence needed | Local reader comprehension, assistive-technology behavior, current institution-specific requirements, and ongoing ownership. | | Context-specific | Formal proposals, scientific reports, A3s, and employment materials need their actual receiving organization's requirements. | **Most likely misuse:** Copying a convincing model or checklist and treating completion as evidence of accuracy, usefulness, or accessibility. The budget, definition, and raster-table findings make that failure concrete. ### PARA routing | Bucket | Route | Why | | --- | --- | --- | | Projects | No project created. A future documentation task may use one embedded candidate. | No active deliverable or project owner was supplied. | | Areas | Technical writing and teaching practice, conceptually. | These are ongoing responsibilities, not completed one-off projects. No area note changed. | | Resources | Vocabulary, literature notes, source checks, and teaching pack remain embedded. | They are reusable reference material within the requested single file. | | Archives | This complete reading record resides in `4. Archives/Book reviews/`. | This is the requested canonical destination. | ### Two proposed reversible experiments Neither experiment has been run, scheduled, or entered in the vault's experiment ledger. Dates are proposed review points, not reminders or commitments. | Experiment | Claim and hypothesis | Action | Measure | Duration | Stop condition | Proposed review | | --- | --- | --- | --- | --- | --- | --- | | X-01 — genre and reader task | C-001/C-011; [[#^pn01]]. A purpose-specific instruction with expected results may reduce uncertainty. | On a sandbox or fictional task, ask 3–5 consenting intended readers to use a draft. Record questions and missed steps; revise and try another comparable task. Let readers use their preferred access tools. | Completion without author rescue, incorrect actions, missing prerequisites, and reader explanations of the result. Record counts and observations, not population percentages. | Two sessions within 14 days. | Stop if the task touches live/private data, causes distress, or cannot be completed with the chosen access method; fix before continuing. | 2026-10-04 | | X-02 — summary preserves the decision | C-014/C-017; [[#^pn03]]. A criteria-based summary may preserve the decision and its qualifications. | Give 3–5 consenting peers a short fictional options report and its proposed summary. Ask what they would choose, why, and what could change the choice. | Whether they identify the same hard constraints, tradeoffs, evidence limits, and unresolved questions. Log omissions individually. | Two drafts within 21 days. | Stop if summarization changes the evidence or hides a binding constraint; repair before asking for another judgment. | 2026-10-11 | **Decision rules:** Adopt the revised practice locally if readers complete the intended task and recover the necessary qualifications. Adapt if failures cluster around language, format, or access. Test further if results conflict or the sample omits a relevant audience. Reject the current draft if it creates a new factual or task error; revise PN-01 or PN-03 accordingly. Defer broader adoption when suitable readers or an appropriate low-risk task aren't available. These small tests diagnose local problems; they don't establish a universal causal effect. ### Drift register | Material | What could change | Source and cadence | Reassessment / early trigger | | --- | --- | --- | --- | | Copyright and workplace-speech application | Rules, decisions, jurisdiction, contracts, employer context. | Current primary legal guidance and qualified local interpretation before consequential use. | Recheck on each use; no evergreen compliance conclusion. | | Learning and typography claims | Research synthesis or better-matched population/task evidence. | Original studies and reviews when adopting a teaching policy; semiannual check only if used. | 2027-03-20, or a new replication/review. | | Accessibility practice | Standards, publishing formats, assistive behavior. | W3C/EPUB accessibility guidance and actual reader testing before publication. | Format/platform changes or an access failure. | | Citation, tools, social media, hiring formats | Submission rules, software, employer instructions, regional norms. | The receiving organization and current official documentation at use time. | Changed requirements or a rejected/unusable submission. | | Source identity and historical wording | The supplied artifact doesn't change; another edition may differ. | Compare ISBN, title page, copyright, and hash when replacing the source. | New edition or different EPUB. | The genre distinctions, this file's source quotations, and its reproduced arithmetic don't require scheduled drift monitoring. Revisit them if a different edition or contrary evidence changes the relevant claim. ## Prompt 13 — visual thinking pack All visuals remain inside this note. Green indicates thesis, blue concepts, orange proposed actions, and purple connections. Labels and shapes carry meaning independently of color. Dashed arrows represent analyst inference or an unverified outcome. The tables and prose supply text equivalents. ### Visual specifications | Visual | Purpose, nodes, and connections | Grouping/layout and uncertainty | Sources | | --- | --- | --- | --- | | V-01 — book and argument map | Reader/purpose/context connects to building blocks, genres, quality controls, and delivery. | Left-to-right; three book sections grouped; a dashed link marks reader success as requiring verification. | C-001, C-003, C-009–C-020, C-026; S-01, S-04–S-21. | | V-02 — genre decision tree | Reader asks about meaning, parts, events, actions, resources, progress, options, findings, or condensation. | Top-to-bottom decision branches; mixed needs can require linked documents. | C-003, C-009–C-017; S-04–S-14. | | V-03 — evidence map | Instructional examples, external checks, observed source defects, repaired claims, and local testing. | Separate what the book shows from what the analyst verifies; no arrow equates fiction with empirical proof. | E-01, E-04–E-08; S-03, S-04, S-08, S-10, S-17. | | V-04 — A3 layout | Problem/current state/target/causes/options on the left; chosen action/owner/date/measures/follow-up on the right. | Two columns plus a full-width uncertainty/access strip; use links to detail, not illegible compression. | C-016; S-13, S-14; analyst accessibility additions. | | V-05 — concept comparison | Mechanism, process, instructions, executive summary, and A3 compare by input, reader question, and output. | Plain table immediately below; distinction is functional, not just grammatical or visual. | C-009–C-011, C-016–C-017; S-05–S-07, S-13–S-14. | ### V-01 — book and argument map ```mermaid flowchart LR APC["Audience, purpose, context"] subgraph I["I: Fundamentals, chapters 1-6"] ETH["Ethics and source records"] DEF["Definitions"] DESC["Parts and processes"] end subgraph II["II: Technical documents, chapters 7-14"] ACT["Instructions"] REP["Proposals and reports"] SUM["A3s, abstracts, summaries"] end subgraph III["III: Other useful material, chapters 15-21"] QC["Style, citations, visuals"] SHARE["Presentations, messages, team writing"] end USE["Reader understands, decides, or acts"] APC --> ETH APC --> DEF --> DESC DESC --> ACT DESC --> REP --> SUM ETH --> QC ACT --> QC SUM --> QC --> SHARE SHARE -. "verify in use" .-> USE classDef thesis fill:#dcfce7,stroke:#166534,color:#111827; classDef concept fill:#dbeafe,stroke:#1e40af,color:#111827; classDef action fill:#ffedd5,stroke:#9a3412,color:#111827; class APC thesis; class ETH,DEF,DESC,ACT,REP,SUM,QC,SHARE concept; class USE action; ``` **Text equivalent:** The book moves from foundational decisions and building blocks to document genres, then expression and collaboration. That instructional sequence supports a reader outcome only when actual use verifies it. The grouping follows the preface; the arrows reconstruct relationships rather than establish causal effects. ### V-02 — genre decision tree ```mermaid flowchart TD Q{"What does the reader need?"} Q -->|"Meaning of a term"| D["Definition"] Q -->|"Parts and relationships"| M["Mechanism description"] Q -->|"What happens"| P["Process description"] Q -->|"What to do"| I["Instructions"] Q -->|"Approve resources"| PR["Proposal"] Q -->|"Know project status"| PG["Progress report"] Q -->|"Judge an option"| F["Feasibility report"] Q -->|"Compare alternatives"| R["Recommendation report"] Q -->|"Assess tests or inquiry"| L["Lab, project, or research report"] Q -->|"Condensed source document"| S["Abstract or summary"] Q -->|"Follow problem solving"| A["A3 process record"] ``` **Text equivalent:** Select by function. If the reader needs both a decision and an implementation procedure, link the appropriate documents. The tree doesn't imply that one document can never combine functions. ### V-03 — evidence and repair map ```mermaid flowchart LR EX["Book examples and checklists"] --> FORM["How a genre is constructed"] FACT["Primary external sources"] --> CHECK["Check selected factual claims"] ART["Original tables and XHTML"] --> REPRO["Reproduce arithmetic and markup findings"] FORM --> REPAIR["Keep method; repair scope or content"] CHECK --> REPAIR REPRO --> REPAIR REPAIR -. "proposed, not run" .-> TEST["Reader task and access tests"] TEST -. "local evidence only" .-> ADOPT["Adopt, adapt, or reject"] classDef concept fill:#dbeafe,stroke:#1e40af,color:#111827; classDef action fill:#ffedd5,stroke:#9a3412,color:#111827; classDef connection fill:#f3e8ff,stroke:#6b21a8,color:#111827; class EX,FORM concept; class FACT,CHECK,ART,REPRO connection; class REPAIR,TEST,ADOPT action; ``` **Text equivalent:** Examples demonstrate construction. Primary sources and source-artifact checks test selected claims. Analyst repairs still need local reader evidence before becoming a practice rule. None of the proposed test arrows represents a completed experiment. ### V-04 — implementation-ready A3 / Excalidraw layout Use a **1600 × 1000** canvas with a 60-pixel margin and 40-pixel gutter. Place the title and problem owner at y=40; a green thesis/target box spans x=60–1540, y=100–200. The blue left column, x=60–750, contains current state, evidence, causes, and alternatives in four stacked boxes. The orange right column, x=790–1540, contains selected countermeasure, owner/date, measures, and follow-up. A purple bottom strip, y=820–950, contains links to source evidence, unresolved questions, dissent, and the Idea Compass. Use visible words as well as colors. Connect the cause box to alternatives, alternatives to selected action, and measures back to the target. Dashed connectors mark assumptions and unresolved causal links. Link each box to a relevant heading or block in this note; don't copy dense source images into the canvas. Provide the same information as ordered text beneath the drawing. This is an implementation specification only; no Excalidraw file was created. ### V-05 — concept comparison | Form | Input | Reader question | Output | | --- | --- | --- | --- | | Mechanism description | A device and its parts. | What is it made of, and how do its parts relate? | Organized attributes/functions. | | Process description | Events and relationships. | What happens, and in what order or branches? | Explanation of the process. | | Instructions | A task and execution conditions. | What do I do, and how do I recognize the result? | Actionable directions. | | Executive summary | An existing report. | What should I know or decide without reading it all? | Faithful decision-relevant condensation. | | A3 | An evolving problem-solving process. | What is the problem, why, what will change, and who follows up? | Concise evidence-and-action record. | **Omitted visuals:** A formal causal-loop diagram would imply causal dynamics not established by this book. A full historical timeline, a separate stakeholder network, and additional terminology diagrams would repeat the context, DEIB, and vocabulary tables without adding a necessary distinction. V-01 covers book/concept/system/dependency relationships; V-03 covers evidence and action. The Idea Compass in Prompt 10 supplies navigation. ## Session completion check ### Work completed and adaptations | Prompt | Usable output | Adaptation or limitation | | --- | --- | --- | | 0 | Source identity, integrity, chapter map, source IDs, selected excerpts, provenance. | Local EPUB substitutes for an unverified Readwise target; no separate highlights file. | | 1 | Contract, ten priors, 24 questions, drift assumptions. | Personal purpose and responses remain unknown; application lens is labeled inferred. | | 2 | Book map, central project, provisional summary, hotspots, 16 guiding questions, strategy. | Actual chapters replace inferred clusters; visual coverage is selective. | | 3 | Classification, 22 terms, contested-language and category-error analysis. | Operational definitions and counterexamples are analyst-created. | | 4 | Thirty claims with types, scope, evidence expectations, tests, questions, dependencies. | No numerical efficacy claims extracted from fictional examples. | | 5 | Qualitative confidence policy and calibration controls. | Numerical Bayesian updates intentionally not used because the evidence doesn't support them. | | 6 | Analysis of all 21 chapters, argument sequence, eight-row evidence ledger. | Not every underlying cited study or image was independently examined. | | 7 | Evaluation of all 30 claims, repairs, counter-observations, source checks, updates. | External verification is selected and explicitly bounded. | | 8 | Context and intellectual-lineage map. | Adjacent vault-note comparisons aren't full syntopical rereadings. | | 9 | Inclusion, transfer, accessibility, and reading-demand audit. | No measured grade score, full conformance audit, or assistive-technology user test. | | 10 | Fleeting notes, six literature notes, five permanent-note candidates, structure map. | Embedded blocks preserve the requested one-file boundary; no MOC or reciprocal-link edits. | | 11 | Teaching plan, objectives, activities, assessment, cautions, adaptations. | Designed, not taught. | | 12 | Action inventory, PARA decisions, two experiments, decision rules, drift register. | Proposed, not run or scheduled; no project, task, or experiment-ledger mutation. | | 13 | Five visual specifications, including three Mermaid diagrams and one canvas layout. | No separate visual file; omitted visual forms explained. | **Prompts not run:** None. **Next prompt:** None; the chain is complete. Work remains only if you choose to supply reader emphasis, inspect every remaining image, run the proposed experiments, or apply the teaching pack. ### Ranked source and verification limits 1. **Reader emphasis is unavailable.** No verified target highlights or personal reading contract were retrieved; the selections aren't evidence of your beliefs or priorities. 2. **Visual coverage is selective.** All chapter body text and recovered table-cell text were read. Chapters 6–10 received inspection of all substantive figures/tables; other groups received central-image inspection. Uninspected material includes some mechanism diagrams/photos, later chart and slide details, MRI and historical-computer photos, and decorative material. No claim here depends on their unseen labels. 3. **External verification is bounded.** Most references were read as the book's citations, not independently retrieved. The inspected learning study is its publisher abstract, not a new analysis of its dataset. No source supports a claimed population-level gain from the proposed methods. 4. **Source artifact isn't the full course package.** Referenced model appendices and instructor/Connect materials aren't supplied. Publisher marketing and accessibility claims don't establish this EPUB's behavior. 5. **Bibliographic link limitation:** The publisher verifies this edition and ISBN. The ISBN-derived Amazon link could not be retrieved, so its ASIN/listing match remains unverified. ### Corrections and assumptions retained - The filename's single-author label was expanded to the title page's three authors. - The date ambiguity was resolved using the publisher: publication in 2022; copyright 2023. The OPF modification timestamp is not the publication date. - The initial text extractor omitted some table cells; original-XHTML audits recovered them before the coverage claim. - During synthesis, generic examples and a testing-method attribution in the preliminary claims draft were replaced with Chapter 6's actual air-conditioning/sorting/water-softening examples and Chapter 7's actual workstation/horse-wrap examples. Reader testing is explicitly an analyst application. - The analytical purpose is inferred; no personal motives, feelings, incentives, or reader rating were invented. - Source-internal fiction, deliberately bad exercises, author claims, publisher claims, external evidence, and analyst recommendations remain separate. ### Validation record Checks run against this installed vault file: - YAML parses; all 14 prompt sections and all 21 chapter analyses are present. - All 30 claim IDs have matching evaluations. Their source IDs resolve to the chapter map. - All 178 explicit chapter/anchor references resolve in the original XHTML, covering 117 distinct targets. All three short quotations match the original text after whitespace normalization. - Wiki-links and internal block references resolve; Markdown fences close; no unresolved template variables remain. The archive contains all 14 canonical prompts with shared inputs resolved. - Pandoc parses the note and generates HTML, retaining the three Mermaid blocks and collapsible prompt archive. This checks document structure, not diagram rendering. - **Live preview limitation:** Obsidian displays the saved note in its quick-switcher list, but navigation actions do not open it during the check. The three Mermaid diagrams have not received a live render check in Obsidian; their syntax and textual equivalents remain available in this file. - The canonical destination is `/Users/courtneyrobertson/Documents/2nd Brain/4. Archives/Book reviews/Technical Writing for Engineers & Scientists.md`. No separate review, visual, permanent-note, or prompt-record deliverable is created. ## Work the Book — prompts used this session This section preserves the execution record inside the same note. The **canonical v2 specification** supplies the complete lists that were abbreviated in the pasted request. The user's explicit single-file instruction controls the output boundary. Exact canonical prompt text with resolved shared inputs is preserved in the collapsible record below so it can be reviewed or rerun. The adaptations are: local EPUB as Layer 1 when no target Readwise record is verified; system-selected source IDs instead of invented highlights; labeled inferred reader inputs; qualitative evidence updates; embedded notes and visuals; no external publishing, Reader mutation, scheduling, or adjacent vault edits. These adaptations control any conflicting multi-file defaults in the archived prompt text. ### Shared inputs and source snapshots | Input | Value | | --- | --- | | TITLE | Technical Writing for Engineers & Scientists | | AUTHOR | Leo Finkelstein, Jr.; Jeanine Elise Aune; Leslie A. Potter | | YEAR | 2022 (copyright 2023) | | EDITION | 4th, International Student Edition | | BOOK_ID | ISBN 9781265262198; no verified Readwise target ID | | BOOK_TYPE | technical | | MY_PURPOSE | Analyst-inferred: extract and evaluate practices for technical documentation, developer education, and teaching | | DEPTH | analytical | | CONSTRAINTS | One canonical vault file; local EPUB as Layer 1; distinguish source claims from analysis; full chapter text, selective image inspection; no adjacent changes or external mutations | | PARA_BUCKET | Archives | | VAULT_PATH_PREF | /Users/courtneyrobertson/Documents/2nd Brain/4. Archives/Book reviews | | EXISTING_KNOWLEDGE | Not supplied; do not attribute a baseline or personal beliefs to the reader | | DEIB_INTENT | Not supplied; analyst examines accessibility, language, cultural transfer, and affected stakeholders | | READWISE_TAGS | No target record verified; no tag filter applied | | READWISE_DATE_RANGE | No date filter applied | | SESSION_DATE | 2026-09-20 | | WORK_THE_BOOK_SPEC_PATH | /Users/courtneyrobertson/Documents/2nd Brain/6. Templates/Books/Work the Book.md | | WORKING_NOTE_PATH | /Users/courtneyrobertson/Documents/2nd Brain/4. Archives/Book reviews/Technical Writing for Engineers & Scientists.md | Canonical specification SHA-256: `d24a2add9dbb47a48603a382b0bc15520d77adf1e80e72262302da9021df8d53`. Pasted request SHA-256: `37067bbe9c5d1e8ad9f4741eb1c36f55409c3bcb748f644ba5f92db9f81c5383`. Executed: **0–13**. Skipped: **none**. Remaining: **none**. The source archive below preserves the prompts, not a second set of outputs. <details> <summary>Exact canonical prompt text with resolved shared inputs</summary> ````text # PROMPT 0 — Retrieval and Vault Setup You have MCP access to Readwise and my local Obsidian vault. Your first task is ingestion. Retrieve the available book material, preserve source material as Layer 1, and create or update the working notes. ## Inputs * Title: Technical Writing for Engineers & Scientists * Author: Leo Finkelstein, Jr.; Jeanine Elise Aune; Leslie A. Potter * Year: 2022 (copyright 2023) * Edition: 4th, International Student Edition * ISBN or Readwise book ID: ISBN 9781265262198; no verified Readwise target ID * Vault path preference: /Users/courtneyrobertson/Documents/2nd Brain/4. Archives/Book reviews * PARA target: Archives * Readwise tags: No target record verified; no tag filter applied * Readwise date range: No date filter applied ## Tasks 1. Use Readwise MCP to locate the book using its title, author, edition, ISBN, or Readwise ID. 2. Retrieve all available: highlights · reader notes · document notes · chapter information · page or location data · highlight colors · timestamps · book metadata. 3. Confirm that the retrieved record matches the intended book. Check for: books with similar titles · multiple editions · abridged editions · revised editions · translated editions · duplicate Readwise records. 4. De-duplicate highlights. Identify: exact duplicates · near duplicates with the same text but different timestamps · overlapping excerpts · highlights imported from multiple editions. Preserve meaningful differences in notes, locations, or editions. 5. Create or append to `Leo Finkelstein, Jr.; Jeanine Elise Aune; Leslie A. Potter — Technical Writing for Engineers & Scientists — Readwise Highlights.md`, including: book metadata · edition information · source provenance · retrieval date · Readwise book ID · total highlight count · all highlights verbatim · a stable highlight ID such as `RW-0001` · chapter · page or location · reader note or comment · highlight color · timestamp · edition-specific information when present. 6. Create or append to `2026-09-20 Technical Writing for Engineers & Scientists — Reading Notes.md`, including: YAML front matter · a link to the highlights note · a `Readwise Ingestion Summary` section · a record of missing or uncertain metadata. 7. Build a `Highlight Index` containing: total count · highlights by chapter · by location range · by date where useful · density · repeated terms · repeated phrases · recurring people, organizations, events, theories, or concepts. 8. When chapter information is unavailable, infer a provisional structure. Cluster using: location ranges · timestamps · recurring topics · argument transitions · repeated terminology · narrative or chronological shifts. 9. Label inferred groups as Cluster A, Cluster B, Cluster C, and so on. 10. Explain the rationale for each inferred cluster. 11. Produce a `Cluster Map`: | Cluster | Location or time span | Main topics | Rationale | Representative highlights | | --- | --- | --- | --- | --- | 12. Use three to five representative highlight IDs for each cluster. > [!warning] Layer 1 substitution rule (added in v2) > If the book is **not in Readwise**, do not abort the chain. Substitute the available source — local PDF, EPUB, print copy — as Layer 1 and use a page- or location-anchored ID scheme such as `P-####` in place of `RW-####`. State the substitution explicitly in the Layer 1 file's front matter and in the Ingestion Summary. > > Record what the substitution costs. The most important loss is **reader emphasis**: with no highlights, nothing signals what the reader found important, so every emphasis in the analysis is the system's. Say so. > > Also state a **coverage note**: which chapters were read in full, which were sampled, and which were not read. Claims from unread sections are **absent, not evaluated** — never let a coverage gap read as a finding of absence. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. Preserve source text exactly when quoting. Clearly label every inferred structure or conclusion. --- # PROMPT 1 — Setup, Contract, Baselines, Biases, Priors Act as my structured book-analysis system. We are producing one Obsidian-ready Markdown note across multiple runs. Preserve earlier sections unless a correction is required. Write clear headings and concise sentences. Prefer active voice. Apply analytical frameworks without giving generic explanations of those frameworks. ## Inputs Title · Author · Year · Book type · Purpose · Depth · Constraints · PARA target · Existing knowledge · DEIB concerns or goals ## Tasks ### 1. YAML Front Matter Create or update dataview-friendly fields: ```yaml title: author: year: edition: book_type: reading_level: reading_depth: para_bucket: gtd_contexts: status: source_status: created: updated: review_dates: executed_prompts: next_prompt: ``` Do not overwrite valid existing values without noting the change. ### 2. Reading Contract * why I am reading this book * what I hope to understand * intended practical use * success criteria * what evidence would change my mind * what the book cannot establish from the available evidence * constraints affecting this analysis > [!warning] Inferred-input rule (added in v2) > If `Analyst-inferred: extract and evaluate practices for technical documentation, developer education, and teaching`, `Not supplied; do not attribute a baseline or personal beliefs to the reader`, `One canonical vault file; local EPUB as Layer 1; distinguish source claims from analysis; full chapter text, selective image inspection; no adjacent changes or external mutations`, or `Not supplied; analyst examines accessibility, language, cultural transfer, and affected stakeholders` were not supplied, **infer them from available evidence and label the whole section as inferred**, with a visible callout and a correction prompt. Do not present inferred reader motives as stated ones. ### 3. Prior Beliefs and Incentives Document: what I already believe · what I think I know · where my knowledge is weak · what I want to be true · what I may resist accepting · personal, professional, social, ideological, or financial incentives that could affect interpretation. Do not infer personal motives without evidence. Label uncertain interpretations. Flag any incentive that would bias the analysis *toward* the book's conclusions, and mark where in the chain that bias would surface. ### 4. Open Questions Inventory Create 15–35 questions grouped under: definitions and terminology · mechanisms and causes · evidence and credibility · historical or cultural context · application · counterarguments · failure modes · DEIB and multicultural applicability · accessibility · unanswered or avoided questions. Tailor the categories to the book. Do not force irrelevant categories. ### 5. Priors Seed Table Create 8–20 rows. | Claim ID or placeholder | Initial belief | Prior confidence | Reason for prior | Evidence needed | | --- | --- | ---: | --- | --- | Use provisional claim labels when the claims inventory does not yet exist. ### 6. Drift Assumptions Identify facts or conditions that could change within one year and materially affect the book's conclusions: laws · technology · research · political conditions · markets · organizations · terminology · social norms · statistics · product capabilities · institutional leadership. Mark `Not materially applicable` when the claims are not time-sensitive. For older books, distinguish **claim drift** (impossible — the claims are fixed) from **evaluative-context drift** (live — what we now know that bears on them). ## Output Requirements Return Obsidian-ready Markdown. Separate: author-provided information · reader-provided information · system inference · unresolved uncertainty. --- # PROMPT 2 — Inspectional Reading Apply inspectional reading to **Technical Writing for Engineers & Scientists**. Use the table of contents, introduction, preface, conclusion, index, highlights, metadata, and cluster map when available. When source material is missing, simulate only what is necessary and state each assumption. ## Tasks ### 1. Build or Confirm the Book Map Use actual chapter and part titles when available; otherwise the inferred cluster map. For each part, chapter, or cluster identify: apparent purpose · central topic · relationship to the overall argument · available evidence · confidence in the mapping. Mark coverage status per chapter (read · sampled · not read) so the map doubles as an honest coverage record. ### 2. Identify the Book's Central Project Determine: the main problem or question · the author's proposed answer · the author's method · the intended audience · likely reader assumptions · the rhetorical mode. Rhetorical modes: teach · explain · persuade · advocate · warn · sell · defend · reinterpret · document · narrate · synthesize. Select all that apply and support each selection. ### 3. Produce a Provisional Summary Approximately 150 words. State clearly that it is provisional. Do not present inferences as confirmed author claims. ### 4. Identify Reading Hotspots List chapters, sections, or clusters most likely to contain: the thesis · foundational definitions · major evidence · controversial claims · methodological explanations · practical recommendations · limitations · counterarguments · conclusions. Explain why each deserves attention. ### 5. Create Guiding Questions Produce 10–20 questions for deeper reading. Prioritize questions that could: validate the thesis · expose unsupported assumptions · clarify ambiguous terms · test causal claims · identify omitted evidence · reveal scope limitations · separate description from prescription. ### 6. Recommend a Reading Strategy Choose one: skim · selective deep read · full analytical read · syntopical comparison · stop reading. Explain using the reader's purpose, available evidence, and expected value. State the condition that would change the recommendation. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 3 — Classification and Terminology Engine Build a controlled vocabulary for **Technical Writing for Engineers & Scientists**. Use highlight evidence whenever possible. Mark definitions as provisional when the source does not define a term clearly. ## Tasks ### 1. Classify the Book Identify: domain · subdomain · genre · type of argument · primary method · intended use · likely comparison books or traditions. Do not treat publisher categories as definitive. ### 2. Build a Controlled Vocabulary 12–40 important terms. | Term | Author's definition | Competing definition | Operational definition | Equivocation risk | Example | Counterexample | Evidence | | --- | --- | --- | --- | --- | --- | --- | --- | For each term: quote or paraphrase the author's definition · identify competing definitions · create a usable operational definition · explain equivocation risk · give an example and a counterexample · cite source IDs. Distinguish quotations from paraphrases. ### 3. Identify Contested Language Flag terms that: change meaning across chapters · carry ideological assumptions · function as praise or condemnation · collapse multiple categories · rely on specialist definitions · differ across cultures or disciplines · appear measurable but remain vague. ### 4. Create a Category-Error Watchlist Identify where the argument may confuse: correlation and causation · individual and institutional behavior · description and prescription · identity and behavior · intention and effect · anecdote and population-level evidence · legal and moral claims · theological and historical claims · technical capability and practical outcome · **absence of evidence and evidence of absence**. Include only applicable risks, and mark each as present, absent, or not applicable rather than silently omitting it. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 4 — Claims Inventory, Dependency Graph, Evidence Expectations Use the available highlights, notes, book map, and cluster map to extract the major claims. Do not require complete chapter information. ## Tasks ### 1. Create a Claims Inventory Extract 15–60 major claims with stable IDs `C-001`, `C-002`, … | Claim ID | Claim | Claim type | Scope | Testability | Expected evidence | Falsifier | Key terms | Source evidence | Cluster or chapter | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | Claim types: definitional · descriptive · historical · causal · predictive · interpretive · evaluative · moral · theological · methodological · prescriptive · practical. ### 2. Distinguish Claim Sources Label each claim: explicit author claim (EA) · implied author claim (IA) · quoted third-party claim (Q3P) · reader inference (RI) · unresolved interpretation (UI). Do not attribute a claim to the author unless the evidence supports that attribution. **Any claim labeled RI must carry a visible warning that it is not the author's sentence** and must not be quoted as such downstream. ### 3. Set Evidence Expectations For each claim, identify what evidence should exist if the claim is sound: primary sources · experimental studies · observational research · statistical data · archival evidence · interviews · surveys · case studies · comparative analysis · textual analysis · expert consensus · reproducible demonstrations · logical argument. Then state whether that evidence **appears in the book**. Summarize the pattern. ### 4. Define Falsifiers State what evidence would seriously weaken or overturn each claim. Avoid unfalsifiable placeholders such as "more research is needed." A claim for which no falsifier can be stated should be marked **unfalsifiable as stated**, which caps its epistemic status regardless of how well argued it is. ### 5. Build a Claim Dependency Graph Identify: foundational claims · supporting claims · bridge claims · derived conclusions · practical recommendations · claims that can fail independently · claims whose failure would weaken the whole book. Represent as a Markdown outline or Mermaid diagram. Visually mark load-bearing claims and single points of failure. ### 6. Map Claims to Open Questions Link each major claim to one or more questions from the inventory. Add new questions where the claims work generates them. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 5 — Quantitative Rigor Setup Establish a quantitative reasoning policy. **Use quantitative methods only when they improve the analysis. Do not invent numerical precision.** ## Tasks ### 1. Create a Bayesian Update Policy Define how the system will use: priors · likelihood · posterior estimates · confidence ranges · evidence quality · **dependence between evidence sources**. > [!important] Dependence is usually the dominant constraint > Where a book's evidence is largely one author's testimony, multiple passages agreeing with each other are **not independent confirmation** — they are one witness repeating himself. This alone should cap most posteriors well below "very high," independent of how well any individual claim is argued. ### 2. Define Confidence Bands | Label | Range | | --- | ---: | | Very low | 0–20% | | Low | 21–40% | | Uncertain | 41–60% | | Moderate | 61–75% | | High | 76–90% | | Very high | 91–100% | Treat these as structured estimates, not measured probabilities, unless actual data supports them. ### 3. Create a Priors and Posteriors Table | Claim ID | Prior | Evidence | Likelihood impact | Posterior | Confidence range | Notes | | --- | ---: | --- | --- | ---: | --- | --- | Do not update claims before evaluating their evidence. Claims not primarily empirical should be marked **N/A — not empirically adjudicable** and excluded rather than given fake numbers. ### 4. Establish Calibration Warnings Flag: false precision · double-counted evidence · correlated sources · publication bias · survivorship bias · base-rate neglect · tiny samples · selection effects · motivated estimates · unavailable denominators · proxy measures · p-values treated as effect sizes · statistical significance treated as practical significance. Assess each as applicable or not, with severity. ### 5. Define a Non-Quantitative Fallback Where numbers would mislead: strongly decreases confidence · moderately decreases · no meaningful update · moderately increases · strongly increases. **Scope down honestly.** If the book contains almost no quantitative evidence, say so and run the qualitative fallback rather than building an apparatus the source cannot support. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 6 — Analytical Reading Scaffold Build the structure required for a full analytical reading. Use chapters when available; otherwise clusters. ## Tasks ### 1. Create Chapter or Cluster Analysis Slots For each: purpose · thesis · major claims · key terms · evidence · examples · counterexamples · assumptions · unanswered questions · relation to the argument spine · relevant source IDs · reader response. Note explicitly where a chapter offers **no counterexamples** — that is a structural finding, not an empty field. ### 2. Build the Argument Spine 1. starting assumptions 2. foundational definitions 3. major premises 4. intermediate conclusions 5. central conclusion 6. practical recommendations Mark gaps and uncertain transitions. **Name the weakest link explicitly** and say what would repair it. ### 3. Create an Evidence Ledger | Evidence ID | Claim IDs | Evidence type | Source | Independence | Quality | Limitations | Source IDs | | --- | --- | --- | --- | --- | --- | --- | --- | Summarize how many evidence items are **genuinely independent of the author**, and note whether any independent evidence tells *against* the author's conclusions. ### 4. Build a Reading Plan Recommend: reading order · chapters or clusters to prioritize · sections to skim · claims requiring external verification · terminology requiring comparison · stopping points for synthesis · estimated attention level, not completion time. ### 5. Create Completion Criteria Define what must be present before Prompt 7 begins. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 7 — X-Ray Analysis and Fair Criticism Conduct a claim-by-claim evaluation. Cite sources by ID. Separate what the author says from what the analysis concludes. **Apply the principle of fair criticism: first reconstruct the strongest reasonable version of the argument, then evaluate it.** ## Tasks ### 1. Reconstruct the Core Argument Present: the central question · the thesis · foundational premises · major supporting claims · argument sequence · final conclusions · practical implications. Mark uncertain reconstructions, and flag anywhere the reconstruction is more systematic than the author intended. ### 2. Evaluate Each Major Claim | Claim ID | Author's claim | Support summary | Evidence grade | Strongest objection | Counterexample | Current conclusion | | --- | --- | --- | --- | --- | --- | --- | ### 3. Grade the Evidence * **A:** Direct, strong, relevant, independently supported * **B:** Substantial but limited * **C:** Suggestive or incomplete * **D:** Weak, indirect, anecdotal, or poorly matched * **F:** Unsupported, contradicted, or materially misleading * **N/A:** Claim does not depend primarily on empirical evidence Explain each grade briefly. Then **report the distribution and read it** — the pattern of what grades well and what grades badly is usually more informative than any single grade. ### 4. Update Priors For claims in the Bayesian table, update: prior · evidence considered · dependence concerns · posterior · confidence range · reason. **Do not use mathematical language to disguise subjective judgment** — state plainly that these encode judgment, and name the single most important input to the update. ### 5. Scan for Biases and Fallacies Identify only when warranted by the text: confirmation bias · selection bias · survivorship bias · availability bias · authority bias · motivated reasoning · fundamental attribution error · false dilemma · straw person · equivocation · circular reasoning · hasty generalization · anecdotal fallacy · appeal to popularity · appeal to tradition · appeal to novelty · genetic fallacy · composition or division error · correlation-causation error · base-rate neglect · moving the goalposts · unfalsifiable framing. For each: cite the claim or source · explain the reasoning · state how strongly it affects the conclusion · **distinguish a genuine fallacy from a rhetorical weakness**. Also record **counter-observations in the author's favor** — places where the author allows a counter-argument to win, concedes a weakness, or reports evidence against their own position. These temper bias findings and are easy to miss. ### 6. Attempt Repairs Before rejecting a weak claim, attempt the strongest reasonable repair: narrowing scope · refining a definition · replacing a causal claim with a correlational one · adding a missing condition · separating descriptive and prescriptive claims · acknowledging exceptions · reducing certainty · specifying the relevant population or context. State whether the repaired claim remains faithful to the author's larger argument, and what the repair costs the author rhetorically. Mark claims that are **not repairable** and say why. ### 7. Separate Attribution from Analysis Use consistently: **Author says** · **Author implies** · **Evidence shows** · **We infer** · **We conclude** · **Still uncertain**. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 8 — Systems, Context, Historiography Place **Technical Writing for Engineers & Scientists** within its broader systems and intellectual context. ## Tasks Analyze: historical context · institutional context · political and economic incentives · technological context · cultural assumptions · disciplinary traditions · relevant schools of thought · major debates · predecessor arguments · competing interpretations · later developments that affect the book · whose perspectives shaped the record · whose perspectives are missing. Distinguish: context available to the author · context added after publication · current interpretation · speculative explanation. Create a historiography or intellectual-lineage map when applicable. **Label any anachronistic comparison as convergent rather than causal** unless influence is documented. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 9 — DEIB, Multicultural, Accessibility, Reading-Level Audit Audit for diversity, equity, inclusion, belonging, multicultural applicability, accessibility, and reading demands. **Do not assume that demographic representation alone establishes fairness or usefulness.** ## Tasks Evaluate: whose experiences appear · whose are absent · who receives agency · who becomes an object of analysis · universal claims based on narrow samples · cultural, class, gender, racial or ethnic, religious, and geographic assumptions · disability framing · neurodiversity framing · language accessibility · jargon burden · assumed education · digital or financial access · practical barriers to applying the advice. Create: an inclusion strengths section · an exclusion or omission risks section · a multicultural transferability table · an accessibility audit · a reading-level estimate · recommendations for supplementary perspectives. For the strengths section, look for structural rather than rhetorical inclusion — guaranteed representation, procedural protection for minorities, mechanisms that survive a change of leadership. These count for more than stated commitments. For the reading-level estimate, distinguish **syntactic difficulty** from **reference density**. A reader can follow every sentence and still miss the argument when it runs through unexplained precedents. Separate textual evidence from reader inference. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 10 — Notes Pipeline Convert the reading analysis into a structured notes system. ## Tasks ### 1. Fleeting Notes Capture unresolved reactions, questions, connections, and reminders. ### 2. Literature Notes Concise notes tied directly to claims · concepts · evidence · chapters · clusters · quotations. Each retains source attribution. ### 3. Permanent Notes Standalone, atomic notes that: express one idea · use original wording · remain useful outside the book · link to supporting literature notes · identify uncertainty · avoid overstating the evidence. Include a stated **confidence** and a **scope and conditions** block. A permanent note that does not say where it stops applying will be over-applied later. ### 4. Structure Notes Maps of content for: the book · major themes · related projects · related disciplines · claim clusters · unresolved questions. Check existing MOCs for adjacency before creating new ones, and add **reciprocal** links — a one-way link is half a connection. ### 5. Attribution Audit Confirm that every quotation, paraphrase, claim, and inference has the correct author or source. **Do not attribute the system's conclusions to the book's author.** Produce an explicit "do not attribute to the author" list covering: reader-inferred claims (RI) · anachronistic comparisons · cross-domain analogies · every permanent note. ## Output Requirements Return Obsidian-ready Markdown. Include suggested filenames and links. Do not create duplicate notes unnecessarily — but do split permanent notes into their own files, since atomic notes embedded in a working note cannot be linked to or resurfaced. --- # PROMPT 11 — Teaching Pack Turn the analysis into a teaching resource. ## Tasks Create: audience description · learning objectives · prerequisite knowledge · key vocabulary · lesson sequence · discussion questions · misconception checks · case studies · activities · reflection prompts · assessment options · facilitator cautions · accessibility adaptations · multicultural adaptations · further reading. Distinguish: what the book argues · what the evidence supports · what remains disputed · what learners should examine critically. **Do not teach disputed claims as settled facts** — including the analysis's own conclusions. Where an inferential question is genuinely live, teach it as live; those are usually the best teaching moments in the material. Facilitator cautions should name: where the analogies will run away with the room · what coverage limits to disclose · where the material may be personally sensitive to participants · and anything that must not be attributed to the author. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 12 — Action, PARA, Experiments, Drift Monitoring Convert useful conclusions into responsible actions. ## Tasks ### 1. Action Inventory Identify: actions to take · actions to consider · actions to avoid · questions requiring more evidence · ideas useful only in specific contexts. Under "avoid," name the **most likely misuse of this analysis** explicitly. ### 2. PARA Routing Assign material to Projects · Areas · Resources · Archives, with a brief rationale for each routing decision. It is a valid result for nothing to route to Projects. ### 3. Experiments Design small, reversible experiments. | Experiment | Related claim | Hypothesis | Action | Measure | Duration | Stop condition | Review date | | --- | --- | --- | --- | --- | --- | --- | --- | Avoid testing advice that creates unreasonable medical, legal, financial, interpersonal, or safety risks. Where an experiment involves other people, conduct it as ordinary conversation and disclose what you are doing — never as covert study. Where a book's claims are historical and not directly testable, test the **transferred** propositions from the permanent notes instead. ### 4. Decision Rules Define what outcomes would lead to: adoption · adaptation · further testing · rejection · deferral. Name which permanent note gets revised under a rejection outcome. ### 5. Drift Monitoring For each claim that may age quickly: what could change · sources to monitor · review frequency · expiration or reassessment date · conditions triggering early review. State separately which claims **will not drift**, so they are not re-reviewed pointlessly. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- # PROMPT 13 — Visual Thinking Pack Translate the analysis into visual structures suitable for Excalidraw, Mermaid, or another visual-notes tool. ## Tasks Create specifications for: book map · argument map · claim dependency graph · evidence map · terminology map · causal-loop diagram · timeline · stakeholder map · systems map · comparison matrix · decision tree · concept map · action map. **Include only visuals appropriate to the book, and say which you omitted and why.** For each visual provide: title · purpose · nodes · connections · grouping · labels · uncertainties · source claim IDs · source highlight IDs · recommended layout. Provide Mermaid syntax where Mermaid can represent the visual effectively. For Excalidraw-oriented visuals, provide an implementation-ready layout description. Encode coverage gaps and weak inferential steps **visually** — dashed borders, warning nodes — so the diagram cannot be read as more confident than the analysis. ## Output Requirements Return Obsidian-ready Markdown that can be appended to the working note. --- ```` </details>