FeedTheJoeLibrary

Realm III

Playbooks

End to end procedures that cross several charters, with the evidence each step must leave behind.

9 volumes · 2,870 words · Whole realm as Markdown

Map of Realm III. Each sign is a volume on this shelf; roads join volumes that cite each other. Open the whole atlas.
  1. Cross discipline playbooks

    Use these dependency oriented workflows with the routing protocol. They coordinate specialist work without merging distinct evidence states or granting production permissions.

    Expansion85 words.md

  2. Bubbles: outside in availability and public reachability

    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.

    Expansion354 words.md

  3. Contact form to actual mailbox: an end to end evidence chain

    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.

    Expansion379 words.md

  4. From public delivery to useful answers and observed AI citations

    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.

    Expansion363 words.md

  5. Browser and accessibility regressions across a complete task

    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.

    Expansion337 words.md

  6. Improve measured performance without damaging the website

    A measured field or lab bottleneck affects representative customer journeys. The goal is not an isolated score improvement at any cost.

    Expansion324 words.md

  7. Turn verified work into a public expertise asset

    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.

    Expansion361 words.md

  8. Coordinate hostname, URL and content migrations

    An approved migration changes hosting, hostname, routes, content relationships or identity references. Do not initiate a domain consolidation merely because two brands exist.

    Expansion331 words.md

  9. Preflight, controlled release and fresh acceptance

    An actual owner authorized change has a defined build/environment and predeclared acceptance contract. The library itself performs no deployment.

    Expansion336 words.md