--- title: "FeedTheJoe Library: Playbooks" shelf: Playbooks url: https://library.feedthejoe.com/playbooks/ volumes: 9 release: 2026.09.12-g40 rights: © 2026 THATDEVELOPERGUY LLC. All rights reserved. --- # Shelf III: Playbooks End to end procedures that cross several charters, with the evidence each step must leave behind. * * * # Cross discipline playbooks Source: https://library.feedthejoe.com/playbooks/library-playbooks/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 Use these dependency oriented workflows with the [routing protocol](https://library.feedthejoe.com/operating-model/01-master-router/). They coordinate specialist work without merging distinct evidence states or granting production permissions. * [Bubbles: outside in availability and public reachability](https://library.feedthejoe.com/playbooks/01-bubbles-public-reachability/) * [Contact form to actual mailbox: an end to end evidence chain](https://library.feedthejoe.com/playbooks/02-contact-to-mailbox/) * [From public delivery to useful answers and observed AI citations](https://library.feedthejoe.com/playbooks/03-discovery-to-ai-citations/) * [Browser and accessibility regressions across a complete task](https://library.feedthejoe.com/playbooks/04-browser-accessibility/) * [Improve measured performance without damaging the website](https://library.feedthejoe.com/playbooks/05-performance-without-regressions/) * [Turn verified work into a public expertise asset](https://library.feedthejoe.com/playbooks/06-evidence-to-public-expertise/) * [Coordinate hostname, URL and content migrations](https://library.feedthejoe.com/playbooks/07-migration-and-url-changes/) * [Preflight, controlled release and fresh acceptance](https://library.feedthejoe.com/playbooks/08-release-and-independent-acceptance/) * * * # Bubbles: outside in availability and public reachability Source: https://library.feedthejoe.com/playbooks/01-bubbles-public-reachability/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R02 when public/private behavior differs; R01 when service/proxy failure is established. **Consulted roles:** R01, R02, R03, R08, R20, R24, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition An intended public customer journey fails, or works only on a private/Tailscale connection. Bubbles is a host label, not evidence of its OS, addresses or service names. ## Sequence and ownership ### 1\. Define exposure Record intended public hostnames and private services. Confirm authorization and obtain an independent public test vantage. Do not publish a private service merely to make a test pass. ### 2\. Split the path R02 compares authoritative/recursive DNS, IPv4/IPv6 and TLS hostname behavior. R01 checks actual ingress/listeners/proxy/upstream with bounded redacted logs. Preserve timestamps. ### 3\. Locate the failing layer Compare external response with origin side response and correlated application evidence. A live process alone cannot prove the journey. A tailnet connection alone cannot prove public crawlability. ### 4\. Reconcile repair R24 assigns one writer for the affected DNS/config path. R20 reviews exposure changes. R08 reviews public host/canonical implications. R25 prepares a scoped authorized change and rollback. ### 5\. Accept from outside R26 repeats the critical public journey using fresh inputs on the declared build. Record each published address family and disclose unavailable vantages. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Intended public journey succeeds from an independent public vantage * Advertised IPv4/IPv6 paths meet the contract * Private services remain private; no fabricated host configuration ## Stop or block If public vantage or host access is missing, keep the corresponding check BLOCKED and provide only the observations actually available. Do not remove AAAA records or enable public tunneling without owner approved diagnosis. ## Role and source references * [R01 · Site Reliability Engineer](https://library.feedthejoe.com/disciplines/r01-site-reliability/) * [R02 · Network/DNS Engineer](https://library.feedthejoe.com/disciplines/r02-network-dns/) Primary source IDs: D01, D02, D04, D06. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Contact form to actual mailbox: an end to end evidence chain Source: https://library.feedthejoe.com/playbooks/02-contact-to-mailbox/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R03 until application/provider handoff is established, then R17 for downstream delivery. **Consulted roles:** R03, R04, R05, R07, R16, R17, R20, R21, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition A user sees form success but there is no confirmed inquiry. Use synthetic data and an authorized controlled recipient; this playbook grants no permission to email real customers. ## Sequence and ownership ### 1\. Define success states Agree which states the system can observe: request received, validated, durably accepted, provider accepted, mailbox observed and business qualified. Do not promise later states from earlier evidence. ### 2\. Trace the application R04 records the UI/request; R03 validates server handling, persistence, retries, queue and provider outcomes using one correlation ID. Exercise failure cases in a safe environment. ### 3\. Trace delivery R17 uses the same message/provider ID to inspect bounce/queue and actual authorized mailbox evidence. Review SPF/DKIM/DMARC alignment and legitimate sending streams before proposing a DNS change through R02. ### 4\. Check cross cutting behavior R05 tests required actual browsers; R07 tests keyboard, labels and error recovery; R16 compares emitted events with real states. R20 checks sensitive data handling and abuse controls. ### 5\. Verify the repair R21 retains negative and duplicate request cases. R25 sequences the approved change. R26 reexecutes the inquiry with fresh data and reports actual mailbox observation or BLOCKED. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * User messages match observed application states * The scoped synthetic inquiry is durably handled as contracted * Required mailbox receipt is directly observed * Analytics does not count failed/duplicate submissions as qualified inquiries ## Stop or block Provider acceptance without mailbox access supports only provider acceptance. Do not falsify a receipt record, publish customer messages, or enforce a mail policy that has not been reviewed against legitimate senders. ## Role and source references * [R03 · Backend Web Engineer](https://library.feedthejoe.com/disciplines/r03-backend-web/) * [R16 · Analytics/Measurement Engineer](https://library.feedthejoe.com/disciplines/r16-analytics-measurement/) * [R17 · Email Deliverability Engineer](https://library.feedthejoe.com/disciplines/r17-email-deliverability/) Primary source IDs: D07, D28, D32, D33, D36. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # From public delivery to useful answers and observed AI citations Source: https://library.feedthejoe.com/playbooks/03-discovery-to-ai-citations/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R12 for a named AI surface, with R08 owning general crawl/index contracts. **Consulted roles:** R02, R08, R09, R10, R11, R12, R13, R14, R16, R20, R23. **Mode:** read only diagnosis until actual authorization. ## Entry condition The business wants relevant search/AI visibility, or a particular named surface does not show its content. No position or citation can be guaranteed by completing the checklist. ## Sequence and ownership ### 1\. Name the observation Record the engine/surface, exact query, locale, timestamp and exposed model state. Different products may not share crawler policies, indexes or reporting. ### 2\. Verify delivery and eligibility R02 establishes public reachability; R08 checks response/directive/canonical/link contracts and available engine reports. R12 checks search/training/user fetch controls with current provider documentation. ### 3\. Evaluate answer value R10 judges query to page relevance; R13 adds distinct useful explanations and genuine proof. R14 approves factual claims. R09 prevents orphan/duplicate pages and R11 keeps identity markup truthful. ### 4\. Observe selection separately R12 records citations and counterexamples with the original source URL and method. Do not infer model training or memory from a citation or a crawl log. ### 5\. Reconcile business outcomes R16 reports available search exposure, referrals and qualified inquiries with compatible scopes. R23 checks whether the questions correspond to real buyer problems. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Each asserted outcome has the correct source and observation context * Crawler access, indexing, citations, referrals and leads are not conflated * No special file or formatting guarantee replaces useful content ## Stop or block Unavailable dashboards or model identifiers remain unavailable. Do not create synthetic testimonials, low value query variant pages or guaranteed inclusion promises to fill a measurement gap. ## Role and source references * [R08 · Technical SEO Engineer](https://library.feedthejoe.com/disciplines/r08-technical-seo/) * [R10 · Search Relevance/IR Engineer](https://library.feedthejoe.com/disciplines/r10-search-relevance-ir/) * [R12 · AEO/AIO/GEO Engineer](https://library.feedthejoe.com/disciplines/r12-aeo-aio-geo/) Primary source IDs: D13, D20, D21, D22, D23, D24, D29, D31. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Browser and accessibility regressions across a complete task Source: https://library.feedthejoe.com/playbooks/04-browser-accessibility/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R05 for environment specific behavior; R07 for accessibility assessment. **Consulted roles:** R03, R04, R05, R07, R21, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition A critical task fails in a browser/device or cannot be completed with keyboard/screen reader operation. The acceptance matrix must identify actual versus emulated environments. ## Sequence and ownership ### 1\. Record the environment Capture OS, device, browser/version, input mode and assistive technology. State whether the test uses a branded product, engine build, emulation or actual device. ### 2\. Map the complete process Include discovery, navigation, form entry, validation, error recovery and confirmation. A homepage screenshot is not task coverage. ### 3\. Isolate and repair R05 produces a minimal reproduction; R07 maps access failures to criteria and process impact; R04 proposes a semantic/behavioral repair with R03 contract review. ### 4\. Retest interactions Run appropriate automated regression checks through R21, but retain manual keyboard/screen reader and actual device requirements. Check zoom/reflow and affected alternate states. ### 5\. Accept honestly R26 verifies required matrix rows. Report real environments unavailable for testing as BLOCKED rather than substituting WebKit for Safari or a desktop resize for an iPhone. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Required environment rows identify exactly what was run * Critical process works under agreed keyboard/assistive workflows * Automation and manual assessment scopes remain distinct ## Stop or block No automated score is a complete WCAG conformance verdict. Missing real device coverage cannot be silently relabeled. Avoid changing a UI based only on one screenshot without a reproducible behavior. ## Role and source references * [R04 · Frontend Web Engineer](https://library.feedthejoe.com/disciplines/r04-frontend-web/) * [R05 · Browser Compatibility Engineer](https://library.feedthejoe.com/disciplines/r05-browser-compatibility/) * [R07 · Accessibility Specialist](https://library.feedthejoe.com/disciplines/r07-accessibility/) Primary source IDs: D07, D08, D11, D12. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Improve measured performance without damaging the website Source: https://library.feedthejoe.com/playbooks/05-performance-without-regressions/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R06. **Consulted roles:** R01, R03, R04, R05, R06, R07, R08, R16, R20, R21, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition A measured field or lab bottleneck affects representative customer journeys. The goal is not an isolated score improvement at any cost. ## Sequence and ownership ### 1\. Define the baseline R06 separates field and lab data, records routes/templates, windows, devices and tool versions. Missing field data is unknown, not a passing metric. ### 2\. Find the dominant cause Inspect primary content delivery, interaction blocking, layout movement, fonts, images, scripts and cache behavior using actual traces. ### 3\. Review interfaces R01 reviews runtime/cache changes; R20 checks private response exposure; R08 checks meaningful content and directives; R04/R07/R05 protect actual interactions. ### 4\. Change one controlled unit Use a minimal reversible proposal. Record baseline and candidate under comparable conditions. R21 executes critical journey regressions; R16 checks event integrity. ### 5\. Release and observe R25 sequences the authorized change; R26 checks the declared build. Report immediate lab results separately from later sufficiently sampled field results. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * The claimed improvement matches a reproducible method * No inquiry, accessibility, privacy, browser or URL policy regression * Field claims use available appropriate field evidence ## Stop or block Do not cache personal API responses, remove essential content, defer critical behavior or claim conversion uplift from a lab score. If the historical field window is incomplete, state that explicitly. ## Role and source references * [R01 · Site Reliability Engineer](https://library.feedthejoe.com/disciplines/r01-site-reliability/) * [R06 · Web Performance Engineer](https://library.feedthejoe.com/disciplines/r06-web-performance/) * [R20 · Application Security/Privacy Engineer](https://library.feedthejoe.com/disciplines/r20-application-security-privacy/) Primary source IDs: D09, D10, D05, D11. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Turn verified work into a public expertise asset Source: https://library.feedthejoe.com/playbooks/06-evidence-to-public-expertise/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R13. **Consulted roles:** R08, R09, R10, R11, R12, R13, R14, R16, R19, R20, R23, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition A documented method or actual authorized engagement can answer a distinct buyer question. This is a publication workflow, not an instruction to declare expertise without proof. ## Sequence and ownership ### 1\. Choose the reader problem R23 validates audience and demand evidence; R10 judges query relevance; R09 checks existing content so the article adds a distinct answer. ### 2\. Collect and classify proof Separate a sourced methodology article from a real case study. R14 checks exact claims, denominators, dates, credentials and permissions; R20 redacts sensitive artifacts. ### 3\. Write and attribute truthfully R13 builds a useful answer with original explanation and limitations. Joseph must actually review and approve a byline or experience claim. R11 models only verified person/business/document facts. ### 4\. Approve a canonical publication Choose the actual host/route; R08 checks directives and links. R25 obtains owner authorization and controls publication. Do not upload the private library or duplicate the same article across both brands. ### 5\. Observe and earn corroboration R12/R16 measure named surface citations, referrals and qualified outcomes separately. R19 pursues relevant independent coverage of useful work, disclosing paid/owned relationships. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Distinct useful answer and truthful approved authorship * Material claims have sufficient traceable evidence * Public artifacts contain no secrets or unauthorized personal data * Actual publication is owner authorized and technically checked ## Stop or block No fabricated results, client logos, certifications, independent reviewers or Wikidata identities. A planning brief and keyword list are not a completed case study or measured demand. ## Role and source references * [R13 · Content Strategist/SEO Editor](https://library.feedthejoe.com/disciplines/r13-content-strategy-seo-editor/) * [R14 · Fact Checker/Claims Auditor](https://library.feedthejoe.com/disciplines/r14-claims-auditor/) * [R23 · Product Marketing/Market Researcher](https://library.feedthejoe.com/disciplines/r23-product-marketing-research/) Primary source IDs: D20, D21, D25, D26, D19, D40. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Coordinate hostname, URL and content migrations Source: https://library.feedthejoe.com/playbooks/07-migration-and-url-changes/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R25 for release sequencing; R24 for integrated architecture. **Consulted roles:** R01, R02, R03, R08, R09, R11, R12, R16, R17, R20, R21, R24, R25, R26. **Mode:** read only diagnosis until actual authorization. ## Entry condition An approved migration changes hosting, hostname, routes, content relationships or identity references. Do not initiate a domain consolidation merely because two brands exist. ## Sequence and ownership ### 1\. Inventory the current state Preserve route/status/canonical maps, important entry points, forms, mail/DNS dependencies, tracking identities and recoverable configuration. ### 2\. Design target contracts R09 establishes page purposes; R08 owns URL/redirect policy; R11 updates entity IDs consistently; R02 reviews hostname/DNS/TLS; R03/R17 preserve inquiry handling. ### 3\. Plan rollback and sequence R24 resolves dependencies. R01 verifies recovery readiness. R25 records exact steps, owners and abort criteria, including forward repair for nonreversible data changes. ### 4\. Test before exposure R21 checks representative redirects, loops, content, forms and analytics on the declared candidate. R20 reviews exposure and sensitive data. No blanket redirect to homepage shortcut. ### 5\. Accept and monitor R26 repeats critical public journeys; R16 records measurement annotations; R08/R12 monitor engine outcomes over their actual reporting windows without guaranteeing instant indexing. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Approved old to new URL contracts are implemented * Inquiry and identity/measurement dependencies remain valid * Recovery and postchange critical journeys are observed ## Stop or block Do not rewrite both brand domains or delete legacy routes without a real inventory and authorization. A sitemap submission cannot substitute for functional migration acceptance. ## Role and source references * [R08 · Technical SEO Engineer](https://library.feedthejoe.com/disciplines/r08-technical-seo/) * [R24 · Solutions Architect/Integrator](https://library.feedthejoe.com/disciplines/r24-solutions-architecture/) * [R25 · Release/Change Manager](https://library.feedthejoe.com/disciplines/r25-release-change-management/) Primary source IDs: D04, D13, D14, D19, D45. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. * * * # Preflight, controlled release and fresh acceptance Source: https://library.feedthejoe.com/playbooks/08-release-and-independent-acceptance/ Shelf: Playbooks · Status: Expansion · Published 2026-09-09 · Release 2026.09.12-g40 **Lead:** R25. **Consulted roles:** R01, R20, R21, R22, R24, R25, R26 plus affected domain owners. **Mode:** read only diagnosis until actual authorization. ## Entry condition An actual owner authorized change has a defined build/environment and predeclared acceptance contract. The library itself performs no deployment. ## Sequence and ownership ### 1\. Freeze the contract Record project/build/environment, exact change scope, required checks, allowed exceptions and required independence. Preserve the contract hash before collecting acceptance records. ### 2\. Verify readiness R01 demonstrates recovery readiness, R21 runs preflight regressions, R22 challenges approved assumptions and R20 reviews critical exposure. R24 resolves conflicts. ### 3\. Authorize execution R25 confirms the actual operator, sequence, stop thresholds and rollback owner. A JSON pass or role prompt cannot grant permission. ### 4\. Observe the deployed result Collect timestamped raw evidence for the actual build. R26 executes fresh required journeys, discloses reviewer relationship and does not accept builder summaries on trust. ### 5\. Record the bounded verdict Validate the record structure and artifact hashes with the offline gate, then have the responsible owner inspect truth and independence. Report failed/blocked requirements, residual risk and actual rollback if performed. ## Evidence package Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. ## Acceptance * Required checks have fresh scoped evidence and match the declared build * Independence satisfies the agreed policy and is truthfully disclosed * A responsible owner, not the tool, makes the release decision ## Stop or block Never create a fake second reviewer identity or modify a failed requirement after testing to obtain a pass. The offline evidence gate checks consistency, not truth or authority. ## Role and source references * [R21 · QA/SDET Engineer](https://library.feedthejoe.com/disciplines/r21-qa-sdet/) * [R25 · Release/Change Manager](https://library.feedthejoe.com/disciplines/r25-release-change-management/) * [R26 · Independent Acceptance Engineer](https://library.feedthejoe.com/disciplines/r26-independent-acceptance/) Primary source IDs: D44, D45, D46. See the [source register](https://library.feedthejoe.com/operating-model/discipline-source-register/) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause.