# Building Blocks: The Evolution of WordPress — Work the Book **System assessment:** Haden’s selected chapters document how WordPress tries to connect software freedom, easier publishing and wider participation. Named dissenters and unfinished inclusion work complicate the success story. The book supplies useful history and testimony; adoption figures, hopeful mechanisms and screenshots don’t establish universal inclusion, comparative security or current product behavior. For the conclusion, use Prompt 7. For source tracing, start with Prompt 0. Prompts 10–13 hold the proposed notes, teaching pack, private exercises and maps. This assessment covers the selected route, not all sixteen chapters. ## Prompt 0 — Retrieval and source setup ### Identity, preservation and coverage The queued “single page” suffix doesn’t describe this native container: it has 94 fixed-layout spine items. The titleleaf identifies Rebecca Haden, the two editors and executive editor named above; the cover identifies Milestones volume 2 and ©2023. Pages Publishing macOS is an export contributor, not a verified publisher. The cover prints `github.com/wordpress/book`; the titleleaf links the separate `WordPress/wp20-book` repository. No ISBN, reader rating or personal reading dates are inferred. The exact mounted path is missing. Authenticated Drive UI locates the exact filename; live metadata verifies its EPUB MIME, 18,917,413-byte size and canonical books parent. One streamed original transfer succeeds after the restricted transfer fails at DNS resolution. No inline fallback, original edit or library-wide download occurs. CRC, all 94 strict XML parses and raw/decoded NFC ZIP-name collision checks pass. These checks establish readable bytes, not historical accuracy or EPUBCheck certification. Selected pages contain 275 local `src`/`href` references; their file targets exist. External links are inspected as native apparatus, not silently counted as documents read. Profiles, government pages, news reports, underlying surveys and interviews remain NE unless E1/E2 below names an actual reading. No separate endnote section appears in the native contents. No sentence from an unread chapter enters the claims inventory. **Actual reading:** all text in chapters 4 (units 21–27), 6 (32–36), 8 (42–46), 9 (47–51), 16 (91–93), plus title/contents units 1–5. Selected body text totals 6,866 of 22,928 extracted whitespace words, or 29.9%; chapter bodies account for 6,423 words. Headings alone don’t establish reading of the other eleven chapters. Their claims are absent from this review, not evaluated. **Pixels viewed:** the native cover; eight meaningful title/chapter assets (anniversary glyph, four-phase roadmap, Gutenberg logo, Customizer menus, Simone release graphic, Obama Foundation, Trump-era White House and Biden-era White House screenshots); and 38 all-white layout images. The roadmap labels 2023 collaboration as a plan, not completed delivery. Political screenshots show historical interface content, not endorsement or verified policy effects. The menu screenshot supplies an affordance example, not a usability test. Image captions/context in the selected text are read; filename-style alternatives don’t supply meaningful accessible descriptions. ### Reader and lookup limits One bounded Reader title/author query (limit 3) returns unrelated articles, including AI Building Blocks for WordPress. No exact matching book, highlights or reader notes are verified. The original EPUB substitutes for Layer 1; this costs reader emphasis, timestamps, colors, tags and highlight locations. No matching Readwise-note link is invented. Exact title/author/source searches in both archive folders and the completion project find no prior review within that scope. Two actual Amazon searches yield no verified ASIN; null records uncertainty, not proof that no Amazon edition exists. All excerpts below are short native fragments, selected by the system. Locations count every element in original XHTML `body.iter()` from zero; whitespace normalization is the only comparison adjustment. Page N refers to `OPS/page-N.xhtml`, with printed footer usually N−1. Paragraphs wrap into separate XML lines, so fragments don’t join or repair them. | ID | Exact native fragment | Original location | Attribution | | --- | --- | --- | --- | | Q01 | “Automattic is not the equivalent of WordPress” | `OPS/page-21.xhtml#body-element-35` | Haden, institutional distinction | | Q02 | “everyone is welcome” | `OPS/page-24.xhtml#body-element-13` | Angela Jin, quoted welcome formula she finds insufficient | | Q03 | “diversity can have different meanings in different cultures” | `OPS/page-25.xhtml#body-element-7` | Jill Binder, reported by Haden | | Q04 | “themes were required to support the Customizer” | `OPS/page-32.xhtml#body-element-44` | Haden; requirement needs E1 scope | | Q05 | “has become even less standardized over” | `OPS/page-35.xhtml#body-element-55` | Haden, retrospective criticism | | Q06 | “full site editing with the block editor through the Customizer” | `OPS/page-35.xhtml#body-element-30` | Haden, interface ambiguity | | Q07 | “Gutenberg provided no clear benefits to compensate” | `OPS/page-44.xhtml#body-element-9` | Haden, writers’ reported experience | | Q08 | “not intended as the absolute truth” | `OPS/page-45.xhtml#body-element-38` | Tammie Lister, presentation warning | | Q09 | “especially for designers who are not developers” | `OPS/page-46.xhtml#body-element-33` | Haden, qualified capability claim | | Q10 | “The Washington Examiner reported” | `OPS/page-49.xhtml#body-element-9` | Haden, secondary cost attribution | | Q11 | “should put to rest the myth” | `OPS/page-51.xhtml#body-element-8` | Haden, adoption-to-security inference | | Q12 | “a political statement” | `OPS/page-51.xhtml#body-element-17` | Haden introducing a third-party interpretation | | Q13 | “developers are the only needed contributors” | `OPS/page-92.xhtml#body-element-45` | Haden, misconception she challenges | | Q14 | “The freedom to run the program, for any purpose.” | `OPS/page-93.xhtml#body-element-49` | Haden, license philosophy list | | Q15 | “The four freedoms” | `OPS/page-93.xhtml#body-element-46` | Haden, subsection heading | | Cluster | Full native span | Topics and rationale | Representative IDs | | --- | --- | --- | --- | | A — inclusion | 21–27 / chapter 4 | Contrast welcome, mechanisms and remaining power imbalance | Q01, Q02, Q03 | | B — Customizer | 32–36 / chapter 6 | Standardization meets incompatible user/developer expectations | Q04, Q05, Q06 | | C — Gutenberg | 42–46 / chapter 8 | Publishing aspiration meets transition costs and continuing dissent | Q07, Q08, Q09 | | D — politics | 47–51 / chapter 9 | Separate deployment, party affiliation, license values and security | Q10, Q11, Q12 | | E — future | 91–93 / chapter 16 | Prospective collaboration and nondeveloper roles meet software freedoms | Q13, Q14, Q15 | Density is three fragments per analytical cluster, not measured reader interest. Repeated concepts include freedom, change, users, participation and diversity. Named voices include Binder, Jin, Chomphosy, Mullenweg, Lister and Tadlock. The book quotes Courtney Robertson in unit 24 as a source-era contributor: that passage isn’t a new statement from the reader, proof of a current role or an independently verified 800-member/21-language count. ### Independent readings **E1:** [Justin Tadlock’s April 22, 2015 guideline announcement](https://make.wordpress.org/themes/2015/04/22/details-on-the-new-theme-settings-customizer-guideline/), full article body including Q&A, lines 82–150. Its rule concerns repository themes with custom settings: new submissions immediately, existing themes on their next update after October 21, without suspension. Motives include user consistency and review work; educational/extension limits remain. Comments/tutorials are unread; policy isn’t outcome evidence. **E2:** [WordPress Site Editor documentation](https://wordpress.org/documentation/article/site-editor/), selected definition and access paragraphs, lines 76–89; not the full article, screenshots, videos or linked documents. It identifies the block-theme Site Editor and its Appearance → Editor entry point. This clarifies terms but doesn’t prove an unspecified 2023 extension impossible. No WordPress runtime, security, accessibility or version-migration test runs. ## Prompt 1 — Contract, baselines, questions and priors > [!note] System-inferred contract > You haven’t supplied a reading purpose, beliefs, DEIB intent, rating or intended project. The proposed purpose is to understand how a software community connects inclusion and interface choices to publishing freedom. Success means separating dated events, attributed testimony, measurable outcomes and values. Correct this contract before treating its applications as your goals. The reader’s incentives are unknown. The system’s likely attraction to participation and usable software could favor Haden’s framing in Prompts 6–7. Counter it by retaining actual dissent and asking which users leave. Software versions, organizational roles, market share and maintenance status can drift; the printed 2023 claim itself can’t. | Question | Open question | | --- | --- | | O01 | What distinguishes the project, company and foundation? | | O02 | Which sessions and events enter the 19%/21% figures? | | O03 | How do applicants differ from selected speakers? | | O04 | Which procedures turn welcome into access? | | O05 | What counts as community health or growth? | | O06 | Who defines locally relevant diversity dimensions? | | O07 | Where does decision authority sit? | | O08 | What does one release squad establish about wider leadership? | | O09 | Which settings can a user preview? | | O10 | Which themes fall under the 2015 rule? | | O11 | What is the survey sample and nonresponse pattern? | | O12 | Is a CMS necessary for the specified editing task? | | O13 | Which interface does “through the Customizer” name? | | O14 | Who can’t complete a publishing task with the proposed tools? | | O15 | Which workflow losses deserve release-blocking weight? | | O16 | What do leavers report that continuing users don’t? | | O17 | How are website shares measured? | | O18 | Do the two budgets include the same services? | | O19 | What threat model could support security parity? | | O20 | How do political values differ from party affiliation? | | O21 | Which technical dependency links collaboration and multilingual work? | | O22 | How do nondeveloper contributors get authority and support? | | O23 | Can users complete a task with keyboard, assistive technology and translated instructions? | | O24 | Which missing records could change this selected-route assessment? | ### Retrospective priors These ten seeds reconstruct starting system judgments after reading; they aren’t preregistered beliefs or the reader’s beliefs. Confidence is qualitative, not a probability estimate. | Claim | Initial judgment | Prior confidence | Reason | Evidence needed | | --- | --- | --- | --- | --- | | C002 | Accept as reported; don’t treat as census | uncertain | No raw counts | Event list and session classifications | | C003 | Expect a local association | uncertain | Workshop mechanism plausible | Cohorts and selection rules | | C005 | Withhold the guarantee | low | Health undefined | Comparative defined outcomes | | C007 | Treat named testimony as a lead | uncertain | Leader samples unspecified | Role/geography comparison | | C009 | Expect a preview affordance | uncertain | Visible UI can separate preview/publish | Task demonstration | | C010 | Withhold all-theme scope | uncertain | Repository rules have eligibility | Dated primary policy | | C011 | Withhold percentages as compliance proof | low | Stock differs from obligations | Cutoff and options denominator | | C016 | Expect uneven transition outcomes | uncertain | Persistence selects users | Leaver and retainer evidence | | C018 | Withhold platform cost attribution | low | Cost categories unknown | Matched audited budgets | | C019 | Reject adoption as security evidence | high | Adoption measures deployment | Comparative security assessment | ## Prompt 2 — Inspectional reading The native contents define sixteen chapters; the five analytical clusters follow real chapter boundaries. This book narrates and documents a 2013–2023 software/community history and advocates wider contribution. The intended general contributor audience and the reconstructed project below are system inferences from its explanations, named interviews and closing invitation. | Chapter | Native title | Apparent purpose / connection | Coverage and map confidence | | --- | --- | --- | --- | | 1 | Catching up on 2013 | release/community baseline | Heading only; purpose inferred, body NE | | 2 | BuddyPress | social extensibility | Heading only; purpose inferred, body NE | | 3 | Plugging into Plugins | extension and maintenance | Heading only; purpose inferred, body NE | | 4 | Activating Diversity and Inclusion | participation versus power | Full selected chapter; text supports map | | 5 | WordCamp US Philadelphia | events and architecture | Heading only; purpose inferred, body NE | | 6 | The Customizer | preview and standards | Full selected chapter; text supports map | | 7 | WordCamp Jurisdictions | event boundaries | Heading only; purpose inferred, body NE | | 8 | A Modern Day Printing Press? | editor aspiration and disruption | Full selected chapter; text supports map | | 9 | Open Source: A Political Choice? | deployment and values | Full selected chapter; text supports map | | 10 | Wix and WordPress Go Head to Head | licensing and competition | Heading only; purpose inferred, body NE | | 11 | The WordPress Economy | funding and contribution | Heading only; purpose inferred, body NE | | 12 | WordPress Matures | maintenance responsibility | Heading only; purpose inferred, body NE | | 13 | The Pandemic | remote/event shifts | Heading only; purpose inferred, body NE | | 14 | “Parlez-vous WordPress s’il vous plaît?” | multilingual work | Heading only; purpose inferred, body NE | | 15 | Together Again | return and releases | Heading only; purpose inferred, body NE | | 16 | The Future of WordPress | prospective roles and freedoms | Full selected chapter; text supports map | ### Provisional selected-route summary Haden presents WordPress as a publishing project that changes through contributors, institutions and contested interfaces. Chapter 4 follows diversity efforts from speaker invitations and workshops to scholarships and a women-and-nonbinary release squad. It also reports U.S.-centered decisions and leadership that doesn’t reflect the community. Chapters 6 and 8 show why the Customizer and Gutenberg promise more control while disrupting developers, writers and existing workflows. Screenshots make interface changes visible; they don’t measure success. Chapter 9 uses government deployments and quoted costs to argue for WordPress’s legitimacy, then introduces software freedoms as political values. Deployment doesn’t settle security. Chapter 16 invites more kinds of contributors and connects future collaboration to multilingual work. This reconstruction treats participation, technical affordances and software freedoms as related goals with different evidence requirements. Named testimony supports particular experiences; broad population outcomes and universal assurances require records beyond the selected pages. Unread chapters may supply other evidence or counterarguments. **Reading strategy:** selective deep read, not whole-book evaluation. The hotspots are chapter 4’s participation denominators and actual concessions, chapter 6’s dated rule, chapter 8’s workflow disagreement, chapter 9’s security inference, and chapter 16’s prospective architecture. Prioritize the five full chapters in that order, then consult the omitted chapter matching any new historical question. Change to full analytical reading if you need an account of the entire decade instead of this inclusion/interface route. Stop for synthesis after each cluster; reference density is the attention cost, not a completion-time estimate. **Twelve guiding questions:** O01, O02, O03, O07, O10, O11, O13, O15, O16, O18, O19 and O21. Together they test institutions, denominators, rule scope, interface meaning, transition losses and causal bridges. ## Prompt 3 — Classification and terminology Domain: computing history; subdomains: open-source governance, contribution and publishing interfaces. Genre: illustrated institutional/community history using interviews and selected web records. Its argument mixes descriptive chronology with advocacy and forecasts. Software sociology, oral history and participatory design are comparison traditions, not independently read books in this run. Definitions below are paraphrases unless Q marks a quotation; operational definitions and countercases are system proposals. | Term | Author usage (paraphrase) | Competing meaning | System operational rule | Equivocation risk | Example | Countercase | Native evidence | | --- | --- | --- | --- | --- | --- | --- | --- | | WordPress | Publishing project/software | WordPress.com hosting service | Name project, software or service in each statement | Product/company conflation | Core contributor | Hosting subscription alone | 21:e35; Q01 | | Automattic | Related company | Entire WordPress community | Keep company employment separate from project roles | One employer for every volunteer | Company statement | Volunteer not employed there | 21:e14–36 | | Diversity | Multiple social differences | One demographic percentage | State local categories, population and authority | U.S. race taxonomy exported | Local language/status categories | Only speaker gender as whole inclusion | 25:e7–9; Q03 | | Inclusion | Welcome plus intentional spaces | Representation alone | Identify access procedure and who can use it | Invitation confused with completed participation | Travel scholarship | Welcome with unaffordable travel | 24:e13–24; Q02 | | Leadership | People making decisions | Any contributor | Specify decision role and selection process | Membership equated with authority | Release decision responsibility | Forum membership only | 24:e36–75 | | Customizer | Preview/settings interface | Any visual editor | Name theme/setting and preview/save route | Customizer equated with Site Editor | Menus screenshot | Block-theme Editor named a Customizer without proof | 32:e24–31; Q04–06 | | Standardization | Shared UI location | Identical theme capability | Compare location separately from controls offered | Common panel assumed common feature set | Menu placement | Unsupported theme option | 32:e41–51; 35:e55 | | CMS | Content management system | Only possible editing method | Specify who can edit what with which safeguards | Useful tool recast as necessity | Staff biography form | Simple controlled non-CMS edit, hypothetical | 35:e22–28 | | Block | Composable editing unit | Any content container | Identify editable unit and surrounding layout | Modularity mistaken for effortless work | Paragraph moved in editor | Custom integration needing code | 43:e48–51; 46:e33–36 | | Full site editing | Block-based site design | All website work without limits | Name interface, theme and task | No-code confused with no skill | Qualified designer use | Unknown extension treated as standard path | 35:e29–31; Q06; Q09 | | Breaking change | Workflow or page disruption | Only fatal software error | Record affected task and recovery burden | Different harms assumed identical cost | Writer flow disrupted | New control that preserves the task | 46:e14–19 | | Democratization | Wider publishing opportunity | Measured equal influence | Separate opportunity goal from access/outcome measure | Mission treated as achieved parity | Invitation across roles | Excluded contributor despite public software | 43:e34–51 | | Political | Values implicit in freedoms | Party affiliation | Label value argument versus deployment affiliation | Party-neutral mistaken for value-neutral | Tadlock license interpretation | Both parties using one platform | 51:e17–39; Q12 | | Security | Resistance to threats | Government adoption | Specify threat, configuration and comparison | Popularity substituted for test | Deployment recorded | Popularity with unknown vulnerabilities | 51:e7–8; Q11 | | Contribution | Developer and other project work | Code commits only | Name deliverable and decision/support channel | Role list assumed equal power | Translation/instructional design | Title without contribution task | 92:e34–49; Q13 | | Freedom | Four software freedoms | Guaranteed social equality/privacy | Keep license philosophy separate from user outcomes | Legal capability mistaken for institutional protection | Run program for any purpose | Open code without affordable access | 93:e46–61; Q14–15 | Contested words include “all,” “safe,” “beautiful,” “health,” “political,” “today” and “freedom.” Specify their scope before treating them as measurements. “Today” belongs to the source’s 2023 frame. **Category-error watch:** present — correlation/causation (C003 if exported), institutions/individuals (C007), intention/effect (C014), anecdote/population (C005), technical capability/outcome (C009), adoption/security (C019). Risk, not demonstrated error — identity/behavior (C008), license/moral outcome (C023). No selected-route theological/historical conflation is identified; theology isn’t a central claim domain here. Absence of underlying records means evidence unavailable in this route, not proof that no records exist. ## Prompt 4 — Claims, dependencies and evidence expectations EA means explicit author claim; Q3P means an attributed third-party claim; IA means implied author claim; RI means system inference, never the author’s sentence; UI means unresolved interpretation. No IA is required here. C013’s interface scope remains UI. C024 carries the RI warning in every reuse. A–E are the five source clusters; page:e references expand to the original path scheme in Prompt 0. | Claim | Attributed proposition | Type | Scope | Testability / expected evidence | Defeater or scope test | Key term | Source evidence | Cluster | Open question | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | C001 | EA: WordPress and Automattic are different institutions. | descriptive | project/company identity | identity records; native distinction appears | Identity evidence that the project and company are the same legal organization would defeat literal separation. | institutions | 21:e35–36; Q01 | A | O01 | | C002 | EA, reporting Mylo: Women present 19% of WordCamp sessions in 2012 and 21% in 2013. | historical quantitative | sessions in reported WordCamp counts | event dataset with session classification; aggregate report only | Original counts with a different session denominator or totals would weaken these percentages. | representation | 21:e72–78 | A | O02 | | C003 | EA, reporting Binder: Vancouver receives 7 women among 52 applications; after workshops the next year has 50% female speakers. | historical descriptive | different local cohorts and denominators | application/speaker records; anecdotal before/after account appears | Contrary local records would defeat numbers; matched untreated cohorts would test the separate causal hypothesis. | training | 22:e33–68 | A | O03 | | C004 | Q3P Jin: Welcoming language alone isn’t enough; intentional, consistent spaces and trust matter. | practical normative | event inclusion | coherent rule with barriers; participant account appears | Empirical falsifier N/A for the norm; compare whose participation the proposed procedure excludes. | belonging | 24:e13–24; Q02 | A | O04 | | C005 | Q3P Binder: A diverse community ensures long-term health and growth. | causal | community over an undefined long term | defined health measures and comparable communities; assertion appears | A diverse community declining under specified conditions defeats an unconditional guarantee, not the inclusion value. | health | 23:e21–24 | A | O05 | | C006 | Q3P Binder: Relevant diversity dimensions differ across cultures. | interpretive practical | local social categories | explicit contextual examples; race/language/status/religion discussion appears | N/A for a contextual interpretation; a local analysis can contest an omitted dimension without proving one universal taxonomy. | diversity | 25:e7–9; Q03 | A | O06 | | C007 | Q3P Sonneveld/Nimmons: Decision making remains U.S.-centered and leadership doesn’t reflect the global community. | descriptive comparative | source-era contributors and leaders | role/geography dataset and criteria; named testimony appears | A defined leadership/contributor comparison showing representative distributions would weaken the imbalance claim. | power | 24:e36–75 | A | O07 | | C008 | EA: WordPress 5.6 has a women-and-nonbinary release squad in 2020. | historical | one release squad | roster and release record; narrative plus promotional image appears | An authenticated roster contradicting the stated squad identity would weaken the description. | release | 27:e8–28; image16.jpeg | A | O08 | | C009 | EA: The Customizer previews appearance changes and reduces switching between admin and front end. | technical mechanism | supported appearance settings and themes | interface demonstration; description and screenshot appear | A supported setting requiring a separate unpreviewed view would bound the mechanism; error-reduction needs user data. | preview | 32:e24–31; image10.png | B | O09 | | C010 | EA: In 2015 all themes must support the Customizer. | historical rule | unqualified all themes, with directory context later | actual rule, eligible themes and effective dates; shorthand appears | A primary policy limiting eligible themes contradicts the unrestricted formulation. | standardization | 32:e41–58; Q04; E1 | B | O10 | | C011 | EA: Only 24% of directory themes support the Customizer in 2015; half of regular users never use it in a 2017 survey. | quantitative descriptive | source-era stock and survey | dates, eligibility, sample and questionnaire; percentages without methods appear | Eligible-theme audit or original survey returning different values defeats the specified statistic; stock percentage alone can’t test compliance. | adoption | 32:e52–65 | B | O11 | | C012 | EA: Without a CMS owners can’t safely update phone numbers or staff biographies without technical specialists. | causal necessity | all such owners/sites as phrased | defined safe task and comparison; explanatory assertion appears | A non-CMS workflow supporting those edits without a specialist defeats necessity; no such runtime trial occurs here. | CMS | 35:e22–28 | B | O12 | | C013 | EA; UI interface scope: Some themes offer block-based full site editing through the Customizer. | technical descriptive | unspecified themes and integration | named implementation and reproducible path; no named example appears | For any named theme, absence of the described integrated path would weaken that case; conventional Site Editor terminology doesn’t rule out every extension. | FSE | 35:e29–31; Q06; E2 | B | O13 | | C014 | Q3P Mullenweg/EA aspiration: Publishing tools should work for people across languages, abilities, and incomes. | normative goal | aspiration, not achieved universal access | explicit mission and inclusion criteria; analogy and aspiration appear | N/A for the goal; an exclusion is an implementation failure to investigate, not a disproof of the value. | democratization | 43:e34–51 | C | O14 | | C015 | Q3P Chomphosy: Breaking someone’s workflow counts as a problem alongside breaking a web page. | practical normative | definition of consequential disruption | workflow examples and coherent priority rule; direct statement appears | N/A for the priority rule; measuring each cost can contest equal resource allocation, which the rule doesn’t specify. | breaking change | 46:e14–19 | C | O15 | | C016 | EA: Users who persist find learning and compatibility concerns addressed. | descriptive outcome | continuing users, with broad concerns language | issue outcomes and leaver/retainer feedback; retrospective assurance appears | Unresolved concerns among defined continuing users would weaken coverage; leavers test exporting success to all users. | retention | 46:e5–13 | C | O16 | | C017 | EA: Website shares rise from 32.7% in 2018 to 35.4% in 2019. | historical quantitative | reported site-share metric | dated measurement source and denominator; figures appear | Original measurement under the same definition giving different percentages would weaken the comparison. | share | 46:e37–42 | C | O17 | | C018 | Q3P unnamed spokesperson via Examiner: The redesigned Trump-era White House website halves maintenance cost from $6m to $3m. | historical cost | claimed annual maintenance comparison | comparable budgets and scope; secondary quoted assertion appears | Audited matched cost categories showing no halving would defeat the amount; platform causation needs a separate design. | cost | 49:e9–18; Q10 | D | O18 | | C019 | EA: Government popularity settles the idea that WordPress is less secure than traditional websites. | inferential comparative | undefined platforms/threats | matched security assessment; deployment examples only appear | Higher adverse outcomes under a specified comparable threat model would defeat security parity; adoption already fails to supply that test. | security | 51:e7–8; Q11 | D | O19 | | C020 | Q3P Tadlock: The license’s freedoms make open-source use a political choice. | interpretive normative | political values, not party affiliation | textual interpretation of freedoms; attributed argument appears | N/A for value interpretation; disagreement about the meaning of political doesn’t disprove cross-party deployment. | politics | 51:e17–39; Q12 | D | O20 | | C021 | Q3P Mullenweg: Collaboration infrastructure in phase 3 helps multilingual phase 4. | predictive mechanism | 2022 prospective architecture | implemented dependencies and comparison; proposed mechanism appears | Multilingual support requiring none of the proposed shared infrastructure would weaken a necessity reading; a benefit reading needs measurable work saved. | roadmap | 92:e7–22 | E | O21 | | C022 | EA/Q3P Chomphosy: Contribution needs translators, instructional designers, legal and community work as well as developers. | practical normative | community roles named in the source | role descriptions and task coverage; explicit list appears | N/A for participation rule; a given task may need only developers, which doesn’t defeat the project-wide role inventory. | contribution | 92:e34–49; Q13 | E | O22 | | C023 | EA: The four freedoms express WordPress’s software philosophy. | definitional normative | run, study/change, redistribute, distribute changes | stated philosophy; explicit four-item list appears | N/A for philosophical description; actual license compliance across products remains a separate untested question. | freedom | 93:e46–61; Q14–15 | E | O20 | | C024 | RI — NOT the author’s sentence: A visible accessibility feature doesn’t establish whole-site accessibility conformance. | methodological rule | review interpretation of Biden-era screenshot | task-specific access evaluation; screenshots show only controls | Empirical falsifier N/A for the evidence rule; a complete audit supplies the omitted evidence instead of defeating the rule. | accessibility | 50:e9–17; image26.png | D | O23 | ### Dependency outline **Load-bearing reconstructed foundation:** institutional identity C001 and the value goals C004/C014/C023. C002/C003/C007/C008 describe particular inclusion efforts and deficits; they don’t depend on C005’s guarantee. C009 supports a preview mechanism; it doesn’t entail C016’s universal transition success. C010/C013 need correct rule/interface scope before transfer. C017 is separate from a causal Gutenberg growth claim, which this review doesn’t attribute. C018 and C019 fail independently: cost testimony and security inference aren’t one evidential bridge. C021 is a proposed dependency, not a shipped result. C022 widens possible contribution roles. **Weakest bridge:** C019 moves from named government adoption to comparative security without a threat model or assessment. Repair requires a relevant assessment or withdrawing that inference. Failure of C019 doesn’t erase the deployment examples or the book’s invitation to participate. Maps in Prompt 13 encode these boundaries. ## Prompt 5 — Quantitative rigor The book offers counts and percentages but no selected-route sampling protocol, matched controls or likelihood model. Use qualitative updates; a repeated interview quotation and its narrative summary remain one source. The bands low/uncertain/high describe system judgment, not measured posterior probabilities. N/A norms don’t receive invented numerical confidence. Prompt 7 records actual updates after evaluation. **Worked denominator example:** 7/52 = 13.46% of applications. The next year’s 50% is a share of selected speakers, with no verified total. Their difference can’t estimate a workshop effect because the cohorts, selection mechanism and denominator change. Likewise, 19%→21% is two percentage points of sessions; it isn’t a two-percent increase in all women contributors. For C017, 35.4−32.7 = 2.7 percentage points of the stated website metric, not a measured Gutenberg effect. All arithmetic operates on native reported numbers; it doesn’t validate the source data. **Calibration risks:** high relevance — unknown denominators, selection, correlated testimony, survivor-only C016 and outcome proxies C019. Medium relevance — advocacy incentives and publication selection. Tiny sample risk applies to particular testimony, not a fabricated population N. Base-rate comparison is unavailable. No p-values, effect-size trial or statistical-significance claim appears in the selected route, so those audits are N/A. A later fact check can change evaluation; arithmetic can’t repair an undefined population. ## Prompt 6 — Analytical scaffold and evidence ledger The following reconstructs the selected route, not an author-written formal proof. Reader responses remain unknown. | Cluster | Purpose, thesis and method | Evidence/examples | Actual countervoices or concessions | Assumption / unanswered question / role | | --- | --- | --- | --- | --- | | A; Q01–03 | Narrate participation efforts; welcome needs concrete work. Interview/history synthesis. | Session counts; Binder workshops; grants, scholarship and release squad. | Gooding resists a diversity focus; Jin finds welcome insufficient; Nimmons finds leadership unrepresentative; cultural definitions differ. | Measures and causation remain open (O02–07). Supplies opportunity/power distinction. | | B; Q04–06 | Show preview standardization and resistance. Interface history plus quotations. | Menus screenshot; developers and designers explain different needs. | Author reports nonuse, uneven support and increasing variation; commenters challenge forced UI change. | Rule eligibility and interface scope matter (O10/13). Supplies technical conditions. | | C; Q07–09 | Reconstruct Gutenberg’s publishing goal and transition. Analogy, interviews and history. | Writers/developers/site owners face different disruptions; no-code design opportunities. | Writers see little benefit; concerns continue; Classic Editor sunset doesn’t occur as planned; Lister rejects absolute truth. | Continuing users exclude leavers (O16). Connects affordances to costs without resolving universal benefit. | | D; Q10–12 | Compare government deployments and political license values. Examples and secondary reports. | Foundation, campaign and government sites; claimed budget saving; White House screenshots. | Tadlock challenges value-neutral framing; software party affiliation and political values differ. No comparative security counterexample is supplied. | Deployment alone doesn’t test security (O19); budget comparability unknown. Weak bridge to platform superiority. | | E; Q13–15 | Invite future contributors and state philosophy. Prospective architecture plus role inventory. | Phase 3/4 proposal, translators/legal/design/community roles, freedoms list. | Author acknowledges unclear onboarding/retention and financing needs. No empirical counterexample to the proposed phase dependency is offered. | Plans need implemented evidence (O21). Closes with a value invitation, not a current roadmap audit. | | Evidence ID | Claims | Type/source | Independence | Quality and limit | Native IDs | | --- | --- | --- | --- | --- | --- | | N1 | C001–008 | Chapter 4 testimony and narrative | Multiple named voices, mediated through one edited history | Particular experiences; no independently acquired rosters, event counts or causal comparison | Q01–03; units 21–27 | | N2 | C009–013 | Chapter 6 narrative and screenshot | One native account | Visible interface; survey methods absent; no runtime execution | Q04–06; units 32–36 | | N3 | C014–017 | Chapter 8 analogy/interviews | Edited testimony, not independent outcome replication | Includes dissent and unfinished transition; reported website shares lack methods here | Q07–09; units 42–46 | | N4 | C018–020/024 | Chapter 9 report and screenshots | Secondary cost quotation; no acquired audit | Affiliation, UI and license values differ from performance/security measures | Q10–12; units 47–51 | | N5 | C021–023 | Chapter 16 prospective statements | Native edited quotations | Proposed dependency and role list; no implementation test | Q13–15; units 91–93 | | E1 | C010 | Primary 2015 policy article | External to Haden, within the same WordPress institution | Direct rule scope; no outcome comparison | Prompt 0 E1; Q04 | | E2 | C013 | Selected primary product documentation | External text within the same ecosystem | Terminological comparator; later context, no historical extension test | Prompt 0 E2; Q06 | Two external documents are actually read within declared scopes. E1 tells against C010’s unrestricted wording. E2 clarifies an ambiguity without establishing a categorical historical disproof. Neither is an independent trial of community outcomes. Underlying interviews, surveys, financial accounts, security evaluations and linked pages remain NE. **Argument spine, system reconstruction:** freedom as a goal → contributors build tools and institutions → interfaces/participation mechanisms change opportunities → experiences and constraints differ → wider contribution remains desirable. The leap from opportunity to universal success is uncertain. A goal can survive an ineffective mechanism, but it doesn’t validate that mechanism. **Completion gate before Prompt 7:** full selected text, matching inline context, selected pixels, accurate voices and definitions, explicit unread list, claim inventory and the two bounded primary comparisons are present. No whole-book completion is implied. For future reading, prioritize omitted chapters 3/11/12 for maintenance/economics and 14 for multilingual implementation only if those questions become the purpose; those suggestions infer purpose from headings. ## Prompt 7 — X-ray evaluation and fair criticism **Strongest reconstruction:** the project’s users and contributors can gain control when software interfaces and community procedures widen opportunities. Change brings costs that leaders should recognize; freedom needs people doing many kinds of work. This is a system-organized reconstruction of the source’s history and advocacy, not its formal thesis statement. It doesn’t require a claim that WordPress already gives every person equal influence or that all interface changes succeed. Grades: A direct independent support; B relevant but limited support; C suggestive/incomplete; D weak or mismatched support; F materially contradicted/misleading formulation; N/A nonempirical norm/interpretation/rule. A D here doesn’t prove the opposite. Each conclusion below repairs the particular claim without replacing it with an invented observed subset. | Claim / source | Author claim (P4) | Support | Grade | Objection / countercase | System conclusion and repair | | --- | --- | --- | --- | --- | --- | | C001; 21:e35–36; Q01 | WordPress and Automattic are different institutions. | Native distinction | C | A company can influence a project without equaling it. | Retain separate institutional labels; formal legal structure isn’t independently audited. | | C002; 21:e72–78 | Women present 19% of WordCamp sessions in 2012 and 21% in 2013. | Reported figures | C | Sessions aren’t people; original counts remain unread. | Keep the dated report and session denominator; withhold population-wide representation claims. | | C003; 22:e33–68 | Vancouver receives 7 women among 52 applications; after workshops the next year has 50% female speakers. | Local sequence | C | Different cohorts/selection; hypothetical other causes. | Keep the local sequence; remove causal effect-size inference and don’t compare applicant share with speaker share as one population. | | C004; 24:e13–24; Q02 | Welcoming language alone isn’t enough; intentional, consistent spaces and trust matter. | Named procedural argument | N/A | Any procedure can still exclude; intent isn’t outcome. | Adopt as a proposed inclusion standard, subject to actual access and participant checks, not a demonstrated success rate. | | C005; 23:e21–24 | A diverse community ensures long-term health and growth. | Asserted guarantee | D | A diverse group can still lose funding or decline (hypothetical). | Replace ensures with a goal and testable mechanisms; this costs the unconditional growth promise, preserves the value. | | C006; 25:e7–9; Q03 | Relevant diversity dimensions differ across cultures. | Explicit cultural qualification | N/A | Local categories can omit marginal participants. | Ask who defines local categories; preserve cross-cultural variation without treating any local definition as sufficient. | | C007; 24:e36–75 | Decision making remains U.S.-centered and leadership doesn’t reflect the global community. | Two named critical voices | C | No defined role/population comparison. | Retain attributed source-era imbalance testimony; request role/geography evidence before generalizing. | | C008; 27:e8–28; image16.jpeg | WordPress 5.6 has a women-and-nonbinary release squad in 2020. | Narrative and promotional image | C | One squad doesn’t establish global leadership parity. | Retain the 2020 release account; withhold broader distribution conclusions until roster evidence appears. | | C009; 32:e24–31; image10.png | The Customizer previews appearance changes and reduces switching between admin and front end. | Description and screenshot | C | Affordance isn’t measured task success. | Keep preview capability for supported settings; error reduction and user benefit need a task comparison. | | C010; 32:e41–58; Q04; E1 | In 2015 all themes must support the Customizer. | E1 scope contradicts all-theme shorthand | F | Repository custom settings and update timing bound the rule. | Correct the scope using E1; this removes the universal mandate, not the standardization rationale. | | C011; 32:e52–65 | Only 24% of directory themes support the Customizer in 2015; half of regular users never use it in a 2017 survey. | Methods absent in selected text | D | Ineligible/unupdated stock can remain outside obligations. | Withhold compliance inference and survey generalization; preserve figures only as attributed, unverified dated reports. | | C012; 35:e22–28 | Without a CMS owners can’t safely update phone numbers or staff biographies without technical specialists. | Explanatory assertion | D | Controlled static-site editing is a plausible countercase, not executed here. | Recast CMS as one way to separate routine edits from specialist work; drop technical necessity for every owner. | | C013; 35:e29–31; Q06; E2 | Some themes offer block-based full site editing through the Customizer. | Unspecified themes; E2 comparator | D | An extension could differ from the conventional interface. | Separate Customizer and Site Editor; leave the claimed integration unresolved until a named source-era theme is demonstrated. | | C014; 43:e34–51 | Publishing tools should work for people across languages, abilities, and incomes. | Stated aspiration | N/A | Money, connectivity, skills and access barriers remain. | Keep the access goal; don’t teach it as achieved universal availability. | | C015; 46:e14–19 | Breaking someone’s workflow counts as a problem alongside breaking a web page. | Explicit priority rule and workflow examples | N/A | Workflow and page failures can impose different measured costs. | Treat workflow disruption as a valid release concern without assuming equal cost or every complaint a veto. | | C016; 46:e5–13 | Users who persist find learning and compatibility concerns addressed. | Retrospective assurance | D | Unresolved users and leavers can be missing. | Withhold comprehensive resolution; retain that the narrative reports continued improvements alongside divided users. | | C017; 46:e37–42 | Website shares rise from 32.7% in 2018 to 35.4% in 2019. | Two reported percentages | C | Measurement provenance and other causes remain unverified. | Keep the dated descriptive comparison; no Gutenberg causal growth conclusion follows. | | C018; 49:e9–18; Q10 | The redesigned Trump-era White House website halves maintenance cost from $6m to $3m. | Quoted unnamed spokesperson via news report | D | Matched budgets and independent audit absent. | Retain the attributed claim; don’t present $3m as verified software savings or a deployment recommendation. | | C019; 51:e7–8; Q11 | Government popularity settles the idea that WordPress is less secure than traditional websites. | Government examples only | D | A popular platform can still have security defects (logical countercase). | Withdraw the adoption-to-security inference; platform comparison stays unresolved until relevant assessment. | | C020; 51:e17–39; Q12 | The license’s freedoms make open-source use a political choice. | Attributed freedoms interpretation | N/A | Political value doesn’t mean party identity. | Retain Tadlock’s interpretation beside cross-party deployment; these answer different questions. | | C021; 92:e7–22 | Collaboration infrastructure in phase 3 helps multilingual phase 4. | Prospective mechanism | D | Alternative architecture can help multilingual work without that exact phase sequence. | Keep the 2022 proposed benefit, not a proved necessity or a current shipping claim. | | C022; 92:e34–49; Q13 | Contribution needs translators, instructional designers, legal and community work as well as developers. | Explicit roles list | N/A | A task can have specialist requirements. | Invite role-specific contribution with support and authority; don’t assume every role fits every task. | | C023; 93:e46–61; Q14–15 | The four freedoms express WordPress’s software philosophy. | Stated four-item philosophy | N/A | License freedom doesn’t automatically supply resources or privacy. | Preserve the philosophy and separate compliance/social outcomes; no legal opinion about particular products follows. | | C024; 50:e9–17; image26.png | A visible accessibility feature doesn’t establish whole-site accessibility conformance. | RI methodological boundary | N/A | A control can exist while keyboard or task access fails. | Require a relevant audit before conformance claims; this is the reviewer’s rule, not Haden’s sentence. | **Distribution:** A 0, B 0, C 7, D 8, F 1, N/A 8. These grades concern the 24 inventory claims, not chapter scores. Particular dated reports dominate C; unsupported broad outcomes dominate D. The single F corrects policy wording, not the entire history. N/A preserves values without turning them into measured results. ### Actual retrospective updates These are judgment changes, not numerical Bayes calculations or preregistered predictions. Each row names the input driving the update. N/A claims have no empirical posterior. | Claim | Reconstructed prior | Evidence | Dependence | Updated judgment | Key reason | | --- | --- | --- | --- | --- | --- | | C002 | uncertain | N1 reported percentages | No independent counts | uncertain; no upgrade | The session denominator is known, dataset isn’t. | | C003 | uncertain | N1 cohort account | Same edited account | uncertain; causal confidence stays low | Changing denominator blocks effect estimate. | | C005 | low | N1 guarantee | Assertion, no outcome series | low; withheld | Undefined health makes guarantee weak. | | C007 | uncertain | N1 critics | Distinct voices, editorial selection | uncertain; credible lead | Named criticism supports investigation, not census. | | C009 | uncertain | N2 screenshot | One interface illustration | increases for affordance; outcome uncertain | Visible preview structure supports a narrow mechanism. | | C010 | uncertain | E1 primary policy | External text, same institution | decreases for unrestricted rule | Eligibility directly limits scope. | | C011 | low | N2 figures | Original methods unread | low; no upgrade | Stock, eligibility and sample differ. | | C016 | uncertain | N3 concession and assurance | Retrospective retainer framing | decreases for comprehensive resolution | Divided users and survival condition weaken generality. | | C018 | low | N4 secondary quotation | No acquired independent budget | low; no upgrade | The unnamed cost source drives uncertainty. | | C019 | high rejection of inference | N4 deployment examples | Popularity isn’t security assessment | high rejection of inference; security uncertain | Evidence and conclusion measure different properties. | ### Reasoning risks and author concessions **Genuine inference mismatch:** C019’s popularity appeal substitutes selection for threat assessment. **Overgeneralization:** C010’s all-theme rule fails eligibility; C012’s universal necessity lacks a defined comparison. **Selection risk:** C016 centers users who stay; C003 can become correlation-to-causation if exported. **Rhetorical weakness:** printing-press and open-source-antidote analogies offer orientation, not controlled causal evidence; this review doesn’t label every metaphor a fallacy. **Counter-observations in the author’s favor:** chapter 4 reports limited participation, U.S.-centered decisions and unreflective leadership; chapter 6 admits uneven adoption and standardization; chapter 8 gives writer/developer costs and unfinished work; chapter 16 recognizes retention and financing. These prevent an interpretation that Haden offers only an unqualified success narrative. **Strongest author reply:** an illustrated public history can preserve experiences and goals without conducting trials. The reply protects C003 as a local story, C004 as a norm and C021 as a proposal. It doesn’t convert government use into a security comparison or remove the need to state a rule accurately. The repair costs are explicit: lose universal guarantees, retain named experience, technical possibility and software values. ## Prompt 8 — Systems and historiography **Source-era context:** titleleaf and closing chapter mark twenty years of WordPress; the book covers its second decade through 2023. Core volunteers, release leaders, theme reviewers, businesses, event organizers and users occupy different roles. Companies can fund work without encompassing the project (C001). Repository standards distribute review costs while limiting extension choices (C010). Platform interfaces redistribute learning and compatibility burdens (C015/016). The selected method resembles institutional oral history: named participants, event chronology, screenshots and linked accounts. It gives participants agency and preserves disputes, but editorial selection and missing denominator records limit population inference. Government officials, security auditors, workshop nonparticipants, people leaving after changes and non-U.S. decision makers aren’t independently interviewed in this run. This is a limit of the selected source route, not proof that the complete volume excludes them. **Competing interpretations, system inference:** interface standardization can reduce review friction while narrowing developer discretion; code freedom can coexist with unequal money, time and authority; a shared publishing platform can carry opposing party uses while embodying license values. These comparisons converge with participatory-design and commons-governance concerns; no intellectual influence is established. Current E2 clarifies terminology, not a 2026 evaluation of every historical claim. No current market share, personnel or roadmap status is asserted. ## Prompt 9 — Inclusion, culture, access and reading demands **Structural strengths in the selected record:** workshops, travel scholarships, funded organizations and a deliberately constituted release squad go beyond welcome slogans. The text acknowledges local cultural definitions and nondeveloper roles. These are described mechanisms, not independently verified enforcement or retention outcomes. No guaranteed minority decision power, leadership succession protection or grievance effectiveness is verified here. **Omission risks:** speaker gender doesn’t measure every identity or leadership authority. Travel, unpaid time, language, access technology and resources can block participation despite public code. The attributed Courtney Robertson passage remains historical book testimony; don’t turn it into the reader’s current goals or agreement. Authorial description of designers/writers isn’t a fixed aptitude diagnosis. | Transfer setting | Source strength | System adaptation | Limit | | --- | --- | --- | --- | | Different countries/languages | Binder names cultural variation; contributors contest U.S. centrality | Ask local participants which categories and procedures matter | Don’t impose one U.S. demographic checklist | | Contributors with limited time/money | Scholarships and wider roles appear | Offer bounded asynchronous tasks, explicit support and paid/time costs | No assumption that everyone can volunteer | | Disabled users/contributors | Mission includes ability; site screenshots display controls | Provide keyboard/text routes, captions and task testing | UI controls aren’t conformance evidence (C024 RI) | | Nondeveloper participants | Named translation/design/legal/community roles | State decision authority as well as task invitations | Role visibility alone doesn’t guarantee influence | **Native format/accessibility:** fixed-layout pages split sentences across positioned XML elements, complicating reflow and quotation context. Selected images use generic alternatives; screenshots contain text that needs prose equivalents. No assistive-technology runtime test runs. This note uses headings, readable tables and complete map alternatives, but its rendered accessibility remains unverified. **Reading demand:** short explanatory sentences suggest an adult general reader can follow syntax; references to core, themes, CMS, REST, releases and named leaders increase prerequisite density. No readability score or diagnosis is inferred. Start with institution/interface vocabulary and the whole denominator example in Prompt 5. Supplement the source with actual participant feedback and task-specific access evidence if using it to make a decision; none is silently treated as read. ## Prompt 10 — Embedded notes pipeline Fleeting questions: find the original event counts (O02); identify the 2017 survey sample (O11); name the alleged Customizer/FSE integration (O13); include leavers (O16). These are open work, not new permanent files. ### LN1 — Participation and power Haden reports concrete inclusion efforts and continuing U.S./leadership imbalances (C002–008, Q01–03). Applicant and speaker percentages differ in population. The normative welcome/trust proposal doesn’t itself establish a measured participation effect. Supports [[#PN1 — Compare the same participation measure]]. ### PN1 — Compare the same participation measure **System transfer, not Haden’s sentence:** compare the same event population, stage and category before inferring progress. Link [[#LN1 — Participation and power]]. Confidence: high for denominator logic; uncertain for any real program’s effect. Scope/conditions: use when you have comparable definitions, dates and counts. Uncertainty: selection and missing participants can remain. Countercase: a qualitative account can establish one experience without a population comparison. Stop: don’t compute an effect when cohorts or selection stages differ. Candidate filename only: `Participation comparisons need matching denominators.md`. ### LN2 — Change and workflow Haden gives preview/design opportunities alongside writer/developer disruption and continuing disagreement (C009–016, Q04–09). Chomphosy explicitly treats workflow harm as a release concern. Supports [[#PN2 — Test the task behind a feature]]. ### PN2 — Test the task behind a feature **System transfer, not Haden’s sentence:** evaluate a feature through a defined user task, including transition and recovery, before claiming benefit. Link [[#LN2 — Change and workflow]]. Confidence: high for separating affordance from outcome; no measured benefit claimed. Scope/conditions: reversible local examples with stated theme/version and no live-site changes. Uncertainty: one task doesn’t represent all users. Countercase: a documentary screenshot can accurately show a button without a task trial. Stop: defer benefit claims if you can’t observe completion or preserve a safe baseline. Candidate filename: `Feature presence does not measure task success.md`. ### LN3 — Adoption and legitimacy Haden links government examples to security and sets party-neutral software beside Tadlock’s value interpretation (C018–020/024, Q10–12). Deployment, values and comparative performance need separate evidence. Supports [[#PN3 — Match evidence to the claimed property]]. ### PN3 — Match evidence to the claimed property **System transfer, not Haden’s sentence:** ask whether evidence measures deployment, cost, access or security before transferring its conclusion. Link [[#LN3 — Adoption and legitimacy]]. Confidence: high for the evidence rule; comparative WordPress security unknown. Scope/conditions: a precisely stated property and comparison. Uncertainty: adoption can encode informed choice but doesn’t reveal the decision’s evidence. Countercase: independently documented comparative assessment accompanying adoption can support the property. Stop: withhold assurance if the needed assessment remains unavailable. Candidate filename: `Adoption is not a comparative assessment.md`. **Embedded structure:** P0 sources → P4 claims → P7 verdicts → the three LN/PN pairs → P11 teaching/P12 private proposals. No separate PN files, MOC, visual sidecar or external reciprocal edits occur under the one-note instruction. Scoped adjacency check: the opening and review-to-atom routing in [[3. Resources/MOCs/Book Review Synthesis MOC]] (lines 10–30) treats a review as a source record and Prompt 10 drafts as candidates. It requires scope, counterpoint, source links and one primary MOC before promotion, with either multiple-source evidence or a changed live decision. This note retains its three PN candidates without promoting them; no MOC edit or corpus-wide adjacency claim occurs. These six heading links supply reciprocal links inside this note. **Don’t attribute to Haden:** C024 RI; all three PN transfers; the defined health/leadership/access operationalizations; hypothetical static editing and failed-adoption countercases; any current software inference; the proposed exercises. Q fragments retain their named speaker/context. E1/E2 are separate documents, not newly discovered sentences in the book. ## Prompt 11 — Teaching pack **Audience and objectives:** for an adult learner studying software/community history, distinguish a source-era event, a value, a technical affordance and an outcome claim; name the correct denominator; explain one scope repair. Prerequisites: project versus company, theme versus plugin, preview versus publish. Vocabulary: CMS, Customizer, block, Site Editor, participation, political and security (Prompt 3). **Whole example first:** use the 7/52 application share and next-year 50% speaker share from Prompt 5. Ask what each numerator and denominator counts. The worked conclusion is no controlled effect estimate; it doesn’t deny the workshop participants’ reported experience. **Lesson sequence:** (1) locate Q01–03 and read the surrounding page; (2) name institution and inclusion measure; (3) trace Q04 to the dated rule, keeping E1’s scope; (4) compare Q07–09’s transition experiences; (5) challenge Q11’s inference with the property test; (6) write a faithful, bounded claim and note the remaining question. Use short text blocks or map 1, with the full prose alternative available. **Discussion:** How can open code coexist with unequal influence (O07)? What should count as a breaking change (O15)? Which security evidence would change C019 (O19)? Does software freedom imply party identity (O20)? **Reflection:** which category of evidence did your own proposed sentence need, and which did it actually have? No learner response is invented. **Misconception checks:** 50% speakers doesn’t validate 50% applicants; a visible button doesn’t prove usability; a current documentation definition doesn’t exclude every historical extension; software political values don’t equal party affiliation. **Cases/activities:** compare the two cohort figures; annotate one interface screenshot with what it shows and doesn’t show; rewrite the government/security claim without turning it into the opposite assurance. For EX2, sort these six statements: (1) the menus screenshot lists Home/About/Blog/Contact; (2) it shows Save & Publish; (3) all users finish faster; (4) all themes have identical options; (5) chapter 6 reports mixed reactions; (6) the screenshot proves keyboard access. Source-key answers: 1–2 visible facts (image10.png), 5 reported experience (units 32–36), 3/4/6 unsupported outcomes or universal claims. This key doesn’t invent a learner response. **Assessment options:** a short source-located written repair; an oral explanation of denominator mismatch; a text-only claim/evidence matching exercise. Criteria: correct actor, date, scope, evidence property and unresolved question. A polished map or automated arithmetic doesn’t establish understanding. **Facilitator cautions:** don’t let printing-press or antidote analogies supply causal evidence. Disclose selected coverage and external reading limits. Discussion of exclusion or identity may involve personal experience; allow private reflection and declining to disclose. Don’t repeat Courtney Robertson’s historical quotation as the present reader’s view. Don’t teach this history as a current deployment, security or migration guide. **Accessibility adaptations:** provide text before images, pronounce abbreviations, offer keyboard-accessible written or spoken responses, captions if discussion uses audio, flexible pauses and complete map descriptions. Don’t infer a fixed learning style. **Multicultural adaptations:** let participants define locally relevant categories; include language, time and access constraints; don’t appoint one participant spokesperson for a population. If illustrating unnamed fictional learners later, preserve varied agency and access instead of assigning diagnoses from appearance. **Further reading:** E1 and the selected E2 scope in Prompt 0; native omitted chapters 3/11/12/14 by purpose; original counts, surveys and participant perspectives when retrieved. These are proposals, not claimed completed reading. ## Prompt 12 — Actions, PARA, private exercises and drift **Take:** when writing about this book, retain source-era dates, actual institutions and quotation voices; label any new transfer as a proposal. **Consider:** verify original event/survey records or a named interface case if a concrete decision needs them. **Avoid — most likely misuse:** turn a 2023 success narrative or government screenshot into current security, accessibility, inclusion or migration assurance. Avoid exporting the reader’s historical book quotation as a new personal belief. **Evidence-needed questions:** O11, O13, O18 and O19; they need methods, named implementation, matched budgets and a relevant assessment respectively. **PARA routing:** Archives holds this completed selected review. Resources can use embedded vocabulary/source keys; no extra file is created. Areas may use PN rules for documentation or community review if you choose. No Project is inferred or created because you haven’t named one. A new project must state its actual task and source requirements. All three exercises below are inactive private proposals. They test system transfers, not historical events, and don’t publish, recruit participants, change a live site or invent results. Review dates remain null until you choose to run one. | Exercise | Related transfer | Hypothesis | Private action | Measure | Duration | Stop condition | Review date | | --- | --- | --- | --- | --- | --- | --- | --- | | EX1 — Denominator labels | PN1 / C003 | Explicit labels prevent a false cohort comparison | Label numerator, denominator and selection stage in the worked example; then attempt one comparison | Correctly identify all three and withhold causal effect | One 15-minute proposed session | Stop if original cohort meaning isn’t available | null | | EX2 — Task/evidence sorting | PN2 / C009/015 | Separating affordance and outcome avoids premature benefit claims | Sort six statements about the native menus screenshot into visible fact, reported experience or unknown outcome | Count correct categories against source keys; record ambiguous items | One 15-minute proposed session | Stop if a claim needs live access or a real-site change | null | | EX3 — Property matching | PN3 / C019/024 | Naming the claimed property exposes evidence mismatch | Write one sentence each about deployment, security and accessibility using the same screenshot; mark unsupported ones | Three scope/evidence explanations, not a security score | One 15-minute proposed session | Stop before any assurance requiring an actual audit | null | **Decision rules:** adopt a transfer provisionally if the reasoning and source key survive the exercise; adapt wording if categories remain ambiguous; test another private example only after identifying the ambiguity; reject or defer when definitions/evidence are unavailable. Rejection revises PN1/PN2/PN3 for EX1/EX2/EX3 respectively. Historical claims stay distinct from exercise outcomes; no observation has occurred. **Drift plan, inactive:** review software interfaces/version-specific behavior against official documentation when you need to act, or at a proposed annual review; expire any operational application after a release affecting the task. Recheck organizational roles and site ownership before naming them current. Recheck market-share/survey methods before using rates; don’t carry 2018–2023 numbers forward. A relevant policy or documented interface change triggers early review. Historical source wording, native hash and the arithmetic identities don’t drift. New primary records can change their evaluation without changing what the book says. No reminder or monitoring automation is installed. ## Prompt 13 — Visual thinking pack Color palette: Russian violet #241c4a; periwinkle #bcb5e3; glaucous #647baf; sky blue #8ecae6; blue-green #219ebc; cerulean #126782; Prussian blue #023047; selective yellow #ffb703; UT orange #fb8500; light orange #fee2c3; light gray #ebebeb. Thesis nodes use blue-green, concepts sky blue, actions light orange, connections periwinkle; dark text/strokes carry contrast. No human likeness, identity or diagnosis is inferred. These are abstract source maps, not illustrated historical scenes. Dashed nodes/edges indicate unverified inference or unread material. Each map has a complete prose alternative; code/source/prose checks don’t establish rendered legibility, which remains unverified. ### Map 1 — Selected book route Purpose: orient the five full clusters without implying whole-book coverage. Layout: left-to-right conceptual reading path, not historical causation. Grouping: selected chapter nodes versus dashed unread chapters. Sources: C001/C004/C015/C020/C022, Q01–15. Uncertainty: the omitted chapters may alter the broader history. ```mermaid %%{init: {"theme":"base","themeVariables":{"background":"#ebebeb","primaryColor":"#8ecae6","primaryTextColor":"#023047","primaryBorderColor":"#126782","lineColor":"#126782","secondaryColor":"#bcb5e3","tertiaryColor":"#fee2c3","edgeLabelBackground":"#ebebeb","clusterBkg":"#ebebeb","clusterBorder":"#126782"}}}%% flowchart LR A["4: inclusion"] --> B["6: Customizer"] B --> C["8: Gutenberg"] C --> D["9: politics"] D --> E["16: future"] E --> T["Wider contribution is a goal"] U["11 other chapters: NE"] -. "whole history not assessed" .-> T class A,B,C,D,E concept; class T thesis; class U uncertain; classDef thesis fill:#219ebc,color:#023047,stroke:#126782; classDef concept fill:#8ecae6,color:#023047,stroke:#126782; classDef action fill:#fee2c3,color:#241c4a,stroke:#126782; classDef connection fill:#bcb5e3,color:#241c4a,stroke:#126782; classDef uncertain fill:#ebebeb,color:#241c4a,stroke:#126782,stroke-dasharray:5 5; ``` Alternative: the proposed reading route moves inclusion → Customizer → Gutenberg → politics → future → wider contribution as a goal. The eleven unread chapters connect to that goal only as a warning that the whole history isn’t assessed. The arrows order discussion, not causation. ### Map 2 — Evidence doesn’t automatically become an outcome Purpose: show two weak bridges and a separate value. Layout: top-to-bottom, independent adoption and participation branches. Grouping: evidence concepts, dashed inferred outcomes, license value connection. Sources: C003/C005/C019/C020, Q02/Q03/Q11/Q12. Uncertainty: neither outcomes claim receives a controlled/comparative test here. ```mermaid %%{init: {"theme":"base","themeVariables":{"background":"#ebebeb","primaryColor":"#8ecae6","primaryTextColor":"#023047","primaryBorderColor":"#126782","lineColor":"#126782","secondaryColor":"#bcb5e3","tertiaryColor":"#fee2c3","edgeLabelBackground":"#ebebeb","clusterBkg":"#ebebeb","clusterBorder":"#126782"}}}%% flowchart TD P["Workshops and reported cohorts"] -. "causal gap" .-> I["Program effect: unmeasured"] G["Government deployments"] -. "property mismatch" .-> S["Security parity: unresolved"] F["Software freedoms"] --> V["Political value interpretation"] I --> R["Ask for matched evidence"] S --> R V --> R class P,G,F concept; class I,S uncertain; class V connection; class R action; classDef thesis fill:#219ebc,color:#023047,stroke:#126782; classDef concept fill:#8ecae6,color:#023047,stroke:#126782; classDef action fill:#fee2c3,color:#241c4a,stroke:#126782; classDef connection fill:#bcb5e3,color:#241c4a,stroke:#126782; classDef uncertain fill:#ebebeb,color:#241c4a,stroke:#126782,stroke-dasharray:5 5; ``` Alternative: workshops and reported cohorts connect across a causal gap to an unmeasured program effect; government deployments connect across a property mismatch to unresolved security parity. Software freedoms support a political value interpretation. The unmeasured effect, unresolved security and value interpretation each lead to asking what matching evidence or reasoning is needed; a value isn’t a security outcome. ### Map 3 — Scope before transfer Purpose: implement the three PN review rules as a private decision path. Layout: top-to-bottom loop. Grouping: source concepts, missing-evidence warning and actions. Sources: C009/C010/C013/C019/024, Q04/Q06/Q09/Q11; C024/PN nodes are reviewer transfers, not author sentences. Uncertainty: missing evidence stops an assurance. ```mermaid %%{init: {"theme":"base","themeVariables":{"background":"#ebebeb","primaryColor":"#8ecae6","primaryTextColor":"#023047","primaryBorderColor":"#126782","lineColor":"#126782","secondaryColor":"#bcb5e3","tertiaryColor":"#fee2c3","edgeLabelBackground":"#ebebeb","clusterBkg":"#ebebeb","clusterBorder":"#126782"}}}%% flowchart TD S["Source sentence and actor"] --> D["Date, population and task"] D --> E["Evidence measures that property?"] E -->|"yes"| B["Bounded statement"] E -. "no or unknown" .-> W["Withhold assurance"] W --> Q["Retrieve relevant evidence"] Q --> D B --> P["Private transfer proposal"] class S,D,E concept; class B,P action; class W uncertain; class Q connection; classDef thesis fill:#219ebc,color:#023047,stroke:#126782; classDef concept fill:#8ecae6,color:#023047,stroke:#126782; classDef action fill:#fee2c3,color:#241c4a,stroke:#126782; classDef connection fill:#bcb5e3,color:#241c4a,stroke:#126782; classDef uncertain fill:#ebebeb,color:#241c4a,stroke:#126782,stroke-dasharray:5 5; ``` Alternative: start with a source sentence and its actor, then specify date, population and task. Ask whether the evidence measures that property. Yes leads to a bounded statement and then a private transfer proposal. No or unknown leads to withholding assurance, retrieving relevant evidence and returning to the date/population/task check. That loop doesn’t count proposed retrieval as completed reading. **Idea Compass:** Parents — software/community history and commons governance (comparison themes, not acquired books). Children — matching-denominator, task and property rules in PN1–3. Friends — participatory design and oral-history criticism (conceptual convergences, no influence claim). Competitors — adoption-as-security proxy, all-user success from retainers and representation-as-equal-authority interpretations. Internal navigation: P0 → P4 → P7 → LN/PN pairs → P12. **Omitted visuals and why:** no population pie chart because category denominators differ; no causal loop because mechanisms lack measured feedback; no complete timeline because eleven chapters remain unread; no full stakeholder network because missing roles/relationships would imply exhaustive coverage; no separate terminology graph or comparison matrix because Prompt 3/P7 tables provide the distinctions; no extra Excalidraw asset because the user requires one note. Maps 1–3 combine book, argument/evidence, dependency, concept and action functions without duplicating the prose. ## Session completion check Prompts 0–13 run in order and supply usable outputs for the declared selected route. No prompt is skipped; next_prompt is null. Adaptations: native EPUB replaces unavailable reader highlights; excerpts, literature/permanent-note candidates, teaching and visuals stay inside this one note. Full-book reading, personal reflection/ratings, current software tests, original statistics/interviews/budgets and external publication aren’t claimed. Missing material ranked by consequence: security/comparable cost evidence for assurance; original cohort/survey records for causal claims; named interface implementation for C013; unread chapters for a whole-history assessment. System contract, operational definitions and transfers remain labeled in their sections. Known session date is separate from unknown personal reading dates. The separate full quality reread covers the complete draft, with a recovered table span after output clipping. Fresh original XML checks verify all 15 excerpts; model fields, prompt order, tables, claim/grade parity and reciprocal headings pass. Diagram code and prose alternatives receive checks; rendered legibility remains unverified. Root audit and installation remain pending; no original or shared tracking changes occur. ## Vault installation record Root audit confirms the declared selected route and quoted locations before installation. Unread sections remain not evaluated. Reader rating and reading dates stay unknown. Live Obsidian rendering and Sync delivery remain unverified.