# NOTE: Truncated export: newest 200 of 11818 items. This is not full-corpus coverage; use https://mythos.one/sitemap.xml for URL coverage. # MythOS Library — Full Content > MythOS is a modular knowledge platform for structured memos, knowledge graphs, and AI-powered library chat. This file carries the newest public memos, up to 200 per response — not the full corpus. A truncated response says so on its first line; exhaustive URL coverage lives in the sitemap tree. - [Website](https://mythos.one) - [Summary Version](https://mythos.one/llm.txt) - [OpenAPI Spec](https://mythos.one/api/openapi) - [Sitemap (full URL coverage)](https://mythos.one/sitemap.xml) --- ## Index - [Shower Thoughts Skill](https://mythos.one/me/brianswichkow/40784b) - [BrianBot Skills Glossary](https://mythos.one/me/brianswichkow/b921b7) - [Glossary of Glossaries](https://mythos.one/me/brianswichkow/8f41e5) - [Comet Partner](https://mythos.one/me/brianswichkow/305a0c) - [AI Augmentation vs AI Automation](https://mythos.one/me/brianswichkow/3e1c80) - [Weaponized ADHD](https://mythos.one/me/brianswichkow/ceda0e) - [Chris Stoikos](https://mythos.one/me/brianswichkow/3568e3) - [Cerebras](https://mythos.one/me/brianswichkow/495474) - [Ralph](https://mythos.one/me/brianswichkow/840037) - [Page-2 SEO Opportunity Audit — Loop Runbook](https://mythos.one/me/brianswichkow/2391e9) - [Daniel Kronovet](https://mythos.one/me/brianswichkow/6317ca) - [RadicalxChange](https://mythos.one/me/brianswichkow/d8caaa) - [Zaratan](https://mythos.one/me/brianswichkow/0d2b2c) - [Jake Block](https://mythos.one/me/brianswichkow/bb6af1) - [Cybernetic Governance in a Coliving House](https://mythos.one/me/brianswichkow/10f762) - [The CredSperiment](https://mythos.one/me/brianswichkow/dedba7) - [Atlas Berry](https://mythos.one/me/brianswichkow/d33d01) - [Gunner Park](https://mythos.one/me/brianswichkow/1a8dc3) - [Weston Clarke](https://mythos.one/me/brianswichkow/f5aa89) - [Dane Williams](https://mythos.one/me/brianswichkow/4a82e5) - [Sydney Friedman](https://mythos.one/me/brianswichkow/83ddb1) - [Greyson Lampley](https://mythos.one/me/brianswichkow/c5daa4) - [Smart-Kickoff — Agent Buildbook](https://mythos.one/me/brianswichkow/ed4e43) - [Smart-Kickoff](https://mythos.one/me/brianswichkow/ad935e) - [The Ultimate Retribution: Divorcing a Dildo with AI](https://mythos.one/me/brianswichkow/ce6cc4) - [End Overdose](https://mythos.one/me/brianswichkow/965bd4) - [Clay CLI](https://mythos.one/me/brianswichkow/3b2d01) - [Loops](https://mythos.one/me/mythos/d722ca) - [Devices](https://mythos.one/me/mythos/3cf877) - [How to Change the Apple Account Linked to MythOS](https://mythos.one/me/mythos/2a4130) - [Change Log: iOS](https://mythos.one/me/mythos/edd499) - [Officer Handoffs](https://mythos.one/me/mythos/69bd49) - [Exit Rights](https://mythos.one/me/mythos/5e4756) - [Resonance Dollars](https://mythos.one/me/mythos/23188c) - [Collective Governance](https://mythos.one/me/mythos/359ab3) - [Community-Owned Memos](https://mythos.one/me/mythos/c6d458) - [Clearbit](https://mythos.one/me/brianswichkow/dbd0be) - [HubSpot](https://mythos.one/me/brianswichkow/4abe89) - [Breeze](https://mythos.one/me/brianswichkow/9d32d5) - [HubSpot Developer MCP Server](https://mythos.one/me/brianswichkow/926d13) - [HubSpot Agent CLI](https://mythos.one/me/brianswichkow/787070) - [Breeze Prospecting Agent](https://mythos.one/me/brianswichkow/95c2f0) - [Breeze Intelligence](https://mythos.one/me/brianswichkow/2e8776) - [Clay vs Cargo](https://mythos.one/me/brianswichkow/77ecd8) - [Clay Audiences](https://mythos.one/me/brianswichkow/2ba266) - [Clay Workflows](https://mythos.one/me/brianswichkow/6db9df) - [Recovery Window](https://mythos.one/me/chaseriner/4c0e5f) - [Self-Release Tool](https://mythos.one/me/chaseriner/df0088) - [Mobility Work](https://mythos.one/me/chaseriner/23bd4d) - [Abbie Kouzmanoff](https://mythos.one/me/brianswichkow/828899) - [Jeff Barg](https://mythos.one/me/brianswichkow/19335a) - [Claygent Builder](https://mythos.one/me/brianswichkow/87e3bc) - [Clay Custom MCP](https://mythos.one/me/brianswichkow/50cdad) - [MCP Tool Suite](https://mythos.one/me/mythos/cb033e) - [Clay Web Intent](https://mythos.one/me/brianswichkow/31047c) - [Clay Integrations](https://mythos.one/me/brianswichkow/6552e6) - [Clay Semantic Search](https://mythos.one/me/brianswichkow/5fffd7) - [How to Build Custom AI Agents in Clay](https://mythos.one/me/brianswichkow/791cea) - [Clay Sequencer](https://mythos.one/me/brianswichkow/74bb69) - [Claygent Connectors](https://mythos.one/me/brianswichkow/99243b) - [Claygent](https://mythos.one/me/brianswichkow/dca5d2) - [Clay Ads](https://mythos.one/me/brianswichkow/3ec7d4) - [Clay](https://mythos.one/me/brianswichkow/defaa0) - [Sculpt](https://mythos.one/me/brianswichkow/dface7) - [Eric Nowoslawski](https://mythos.one/me/brianswichkow/da90d2) - [Varun Anand](https://mythos.one/me/brianswichkow/f59a3a) - [Nicolae Rusan](https://mythos.one/me/brianswichkow/f2765b) - [Matthew Quan](https://mythos.one/me/brianswichkow/6f9c75) - [Clay Credits](https://mythos.one/me/brianswichkow/ef1c23) - [Clay Cup](https://mythos.one/me/brianswichkow/ea29fb) - [Clay MCP](https://mythos.one/me/brianswichkow/f5f6e4) - [Clay Functions](https://mythos.one/me/brianswichkow/c49d21) - [Ilias Ismanalijev](https://mythos.one/me/brianswichkow/803dfe) - [Pieter Levels](https://mythos.one/me/brianswichkow/2013af) - [Pat Flynn](https://mythos.one/me/brianswichkow/3ce9af) - [Scribe](https://mythos.one/me/mythos/1b99f6) - [Sweet Surrender](https://mythos.one/me/tzenlai/376416) - [MythOS](https://mythos.one/me/mythos/09405a) - [Profile Memo](https://mythos.one/me/mythos/afcb21) - [MythOS Guide](https://mythos.one/me/mythos/bb4e0a) - [How to Use MythOS with Cursor](https://mythos.one/me/mythos/da529c) - [How to Set Up MythOS with Claude Desktop](https://mythos.one/me/mythos/87bdc8) - [Oracle](https://mythos.one/me/mythos/3703e9) - [Philip Rosedale](https://mythos.one/me/brianswichkow/a5ba00) - [Plans & Tiers](https://mythos.one/me/mythos/32ab0d) - [Enrichment](https://mythos.one/me/mythos/4ce782) - [Meshy](https://mythos.one/me/brianswichkow/9ff694) - [Self-RADAR](https://mythos.one/me/brianswichkow/0ff68f) - [Bipolar Disorder](https://mythos.one/me/brianswichkow/571369) - [The Premise of BPD](https://mythos.one/me/brianswichkow/82e686) - [Tzen: Life Journey](https://mythos.one/me/tzenlai/3a27c0) - [Jensen Abler](https://mythos.one/me/brianswichkow/dba27b) - [OpusClip](https://mythos.one/me/brianswichkow/2bc32b) - [Notifications](https://mythos.one/me/mythos/3a3316) - [Eva Hooft](https://mythos.one/me/brianswichkow/c2d0c9) - [Rachel Blair](https://mythos.one/me/brianswichkow/44ce3b) - [Wispr Flow](https://mythos.one/me/brianswichkow/c102a1) - [Alyson Badhwar](https://mythos.one/me/brianswichkow/301985) - [General Semantics](https://mythos.one/me/johnzdanowski/58dde5) - [Hacker Typer](https://mythos.one/me/brianswichkow/7e2178) - [Degenerative System](https://mythos.one/me/brianswichkow/456974) - [Regenerative Enterprise](https://mythos.one/me/brianswichkow/6ef742) - [Nurture Capitals](https://mythos.one/me/brianswichkow/d106f3) - [Harvesting the Surplus](https://mythos.one/me/brianswichkow/5714cb) - [Multi-Capital Abundance](https://mythos.one/me/brianswichkow/6ba921) - [Regenerative System](https://mythos.one/me/brianswichkow/ffaa0f) - [Edges and Connections](https://mythos.one/me/brianswichkow/8d128a) - [Permaculture](https://mythos.one/me/brianswichkow/dbba22) - [8 Forms of Capital](https://mythos.one/me/brianswichkow/71b6a8) - [Before Violence Becomes Visible](https://mythos.one/me/brianswichkow/f45624) - [The Reporting Escalation Ladder](https://mythos.one/me/brianswichkow/77e720) - [Clay](https://mythos.one/me/ericengoron/a5340f) - [Eric Engoron](https://mythos.one/me/ericengoron/creator) - [Reclaim Agency](https://mythos.one/me/brianswichkow/e059db) - [Sense of Agency](https://mythos.one/me/brianswichkow/8524d2) - [attention](https://mythos.one/me/brianswichkow/4b4bc0) - [Cornell University](https://mythos.one/me/brianswichkow/bf2bf2) - [Cornell Chi Phi Sexual Assault Case](https://mythos.one/me/brianswichkow/939efb) - [Artificial Intelligence (AI) Glossary](https://mythos.one/me/brianswichkow/c80e7a) - [Abbott Kinney Blvd.](https://mythos.one/me/brianswichkow/f461cc) - [hallucination](https://mythos.one/me/brianswichkow/52dc89) - [Apple TV](https://mythos.one/me/brianswichkow/fc0733) - [Elephante](https://mythos.one/me/brianswichkow/7a2848) - [stewardship](https://mythos.one/me/brianswichkow/c555da) - [Intel](https://mythos.one/me/brianswichkow/aa41f0) - [birth](https://mythos.one/me/brianswichkow/840203) - [IBM](https://mythos.one/me/brianswichkow/873804) - [grace](https://mythos.one/me/brianswichkow/0c853c) - [desire](https://mythos.one/me/brianswichkow/93b871) - [Alibaba](https://mythos.one/me/brianswichkow/944656) - [Hustle Fund](https://mythos.one/me/brianswichkow/52306c) - [totality](https://mythos.one/me/brianswichkow/1ce990) - [DoorDash](https://mythos.one/me/brianswichkow/c5496a) - [TipTapCloud](https://mythos.one/me/brianswichkow/bd0de3) - [Emergent Properties](https://mythos.one/me/brianswichkow/c30e61) - [Signal](https://mythos.one/me/brianswichkow/806542) - [Long Beach, CA](https://mythos.one/me/brianswichkow/4ac21e) - [SendGrid](https://mythos.one/me/brianswichkow/4b71e5) - [Everyday Dose](https://mythos.one/me/brianswichkow/e9965f) - [legacy](https://mythos.one/me/brianswichkow/5e3d8f) - [story](https://mythos.one/me/brianswichkow/82e865) - [finite](https://mythos.one/me/brianswichkow/ae20f2) - [Reflect](https://mythos.one/me/brianswichkow/a9867c) - [eBay](https://mythos.one/me/brianswichkow/7213ec) - [Amazon Prime](https://mythos.one/me/brianswichkow/7b130b) - [Apple Shortcuts](https://mythos.one/me/brianswichkow/439447) - [Dialogflow](https://mythos.one/me/brianswichkow/7bec4f) - [Venmo](https://mythos.one/me/brianswichkow/fa4024) - [intrinsic](https://mythos.one/me/brianswichkow/302ab9) - [Evernote](https://mythos.one/me/brianswichkow/db71d9) - [ephemeral](https://mythos.one/me/brianswichkow/5d58f5) - [Target](https://mythos.one/me/brianswichkow/a8b36d) - [Mistral](https://mythos.one/me/brianswichkow/fce9a1) - [compassion](https://mythos.one/me/brianswichkow/21a552) - [kindness](https://mythos.one/me/brianswichkow/4efa51) - [SDK](https://mythos.one/me/brianswichkow/982be6) - [Harvard Business School (HBS)](https://mythos.one/me/brianswichkow/e872dc) - [self-care](https://mythos.one/me/brianswichkow/4c9e44) - [BBC](https://mythos.one/me/brianswichkow/6aa400) - [conscious](https://mythos.one/me/brianswichkow/2e1c8e) - [integrity](https://mythos.one/me/brianswichkow/68d622) - [coherence](https://mythos.one/me/brianswichkow/47316a) - [shadow](https://mythos.one/me/brianswichkow/407339) - [Day One Journal](https://mythos.one/me/brianswichkow/7f1103) - [label](https://mythos.one/me/brianswichkow/be30b1) - [agreement](https://mythos.one/me/brianswichkow/012c57) - [Artificial General Intelligence (AGI)](https://mythos.one/me/brianswichkow/4bc325) - [infinite](https://mythos.one/me/brianswichkow/6c9d11) - [universe](https://mythos.one/me/brianswichkow/8becf7) - [influencer](https://mythos.one/me/brianswichkow/370c6f) - [meditation](https://mythos.one/me/brianswichkow/fce3a1) - [Supabase](https://mythos.one/me/brianswichkow/eef372) - [clarity](https://mythos.one/me/brianswichkow/069189) - [affirmation](https://mythos.one/me/brianswichkow/77fffb) - [empathy](https://mythos.one/me/brianswichkow/c4777b) - [community](https://mythos.one/me/brianswichkow/88f9c3) - [San Diego, CA](https://mythos.one/me/brianswichkow/a36cee) - [separation](https://mythos.one/me/brianswichkow/06a99d) - [Python](https://mythos.one/me/brianswichkow/3a095a) - [metadata](https://mythos.one/me/brianswichkow/672f26) - [Forbes](https://mythos.one/me/brianswichkow/3b775a) - [Verizon](https://mythos.one/me/brianswichkow/c77281) - [COVID](https://mythos.one/me/brianswichkow/65ad30) - [practice](https://mythos.one/me/brianswichkow/f1c9b5) - [time](https://mythos.one/me/brianswichkow/ee4b36) - [gratitude](https://mythos.one/me/brianswichkow/a951ef) - [viral](https://mythos.one/me/brianswichkow/dedec1) - [Kenneth Hahn Park](https://mythos.one/me/brianswichkow/5d4e42) - [Neli's](https://mythos.one/me/brianswichkow/38d963) - [Joel Serot](https://mythos.one/me/brianswichkow/c5c743) - [Casey Rose](https://mythos.one/me/brianswichkow/9b5f13) - [John Kirkpatrick](https://mythos.one/me/brianswichkow/025769) - [Averi AI](https://mythos.one/me/brianswichkow/7419ab) - [awareness](https://mythos.one/me/brianswichkow/a6b1b3) - [New York City, NY](https://mythos.one/me/brianswichkow/69e532) - [NASDAQ](https://mythos.one/me/brianswichkow/fd7074) - [Microsoft](https://mythos.one/me/brianswichkow/7ee2f4) - [Addiction vs. Loyalty](https://mythos.one/me/brianswichkow/8505ca) - [Rocket Yoga](https://mythos.one/me/brianswichkow/64ed9d) - [Solsea](https://mythos.one/me/brianswichkow/c92193) --- # Shower Thoughts Skill URL: https://mythos.one/me/brianswichkow/40784b Updated: 2026-10-12 Tags: #skill-md #brianbot-skill ```yaml name: shower-thoughts description: Steps out of focused work, reads recent entries from the human's configured sources (such as daily journal entries, changelogs, or notes), and surfaces one shower thought — a 140-character miniature epiphany connecting the current work to something else the human is doing. Shows the thought in the session and posts it to a shower-thoughts feed. Use when asked for a "shower thought" or /shower-thoughts, when stuck and the same ideas keep resurfacing, or at a natural pause such as after opening a PR or before planning a new feature. ``` Run one diffuse-mode pass over what your human has been doing lately and return a single grounded insight about how the current work connects to the rest — shown in this session and posted to a feed that holds only shower thoughts — then go back to the task. ## When to Use * Explicit: "shower thought", "give me a shower thought", `/shower-thoughts` * Stuck: the same approaches keep resurfacing, or every option feels like a variation of the last * Natural pause: a PR just opened, a phase just closed, a new feature is about to be planned * Not for critiquing or pressure-testing a plan — this skill generates connections; it does not judge the work ## Setup Run this once, when no settings exist. Ask your human, in one message: * **Sources** — which records of recent activity to read, such as daily journal entries, a changelog, commit history, or meeting notes. For each: where it lives and how to read it (tool call, file path, or URL) * **Window** — how far back to read (default: 7 days) * **Skip** — lines that are pure noise, such as routine habit logs or boilerplate * **Feed** — where to post thoughts (a channel, a file, a note), or nowhere * **Audience limits** — what must never appear in a thought shown where others can see it (default: health, sexual, substance, and relationship details) Save the answers as a private settings document titled "{name}'s Shower Thoughts Skill" that says "Run the Shower Thoughts Skill with these Inputs" and lists them. Future runs read it instead of asking. Never store credentials in it. ## Inputs * `SOURCES`, `WINDOW`, `SKIP`, `FEED`, `AUDIENCE` — from the settings document * Required: read access to every source. If one is unreachable, skip it and name it in the output; if none are reachable, stop and say so * Strongly recommended: a subagent tool running on the same model as this session. Reading sources directly floods the session's context; a subagent absorbs the reading and returns about 100 tokens. Do not hand the sources to a different model provider without your human's approval — they may be personal ## Workflow 1. **Load settings** * Read the settings document. If none exists, run Setup first * Read the last 7 days of `FEED` (when readable) — every thought posted there, verbatim 2. **Describe the current work at three altitudes** — one line each, kept to yourself: * **Task** — the literal work ("adding cursor pagination to channel reads") * **Mechanism** — the pattern underneath ("letting a reader ask only for what's new since it last looked") * **Mundane** — how anyone would recognize it ("picking up a book at the bookmark") * The mundane line is the doorway: unrelated things start to look alike at that altitude 3. **Step into the shower (subagent)** * Hand a fresh subagent only: the three altitude lines, the source instructions with `WINDOW` and `SKIP`, the last 7 days of `FEED` as the recent thoughts, the Frames, the Filter, and the Output format. Never the task, the code, or your reasoning — the clean context is the point * The subagent reads every source across the window, drops `SKIP` lines and entries about the current work itself, and compresses each remaining entry into one line of 140 characters or fewer, labeled with its project or domain * If fewer than 10 lines remain, it returns "sources too thin" * Otherwise it wanders: 15–25 raw collisions through the Frames, fast, unranked, unjudged * Then it runs every collision through the Filter and returns the single best thought, optionally one related idea, and — for your check only — the two entries the thought rests on. Or "nothing surfaced" * No subagent available: do the same in this session, compressing every entry before wandering, and expect the context cost 4. **Check, then show the thought** — confirm it rests on the two entries the subagent named, then show it in the session format under Output and nothing else 5. **Post the thought** to `FEED` — the thought only 6. **Return to the task.** The pass is a break, not a pivot ## Frames * **Same shape** — which entry has the same structure as the work at the mundane altitude? * **Distance pick** — pair the work with the three entries least related to it * **Inversion** — what if that project were the work's consumer, or its supplier? * **Leftovers** — what does the work throw away that something else needs? * **Scale shift** — what does this look like for one person, a community, a thousand customers? * **Time shift** — what will this need in six months that something else is building now? ## Filter A collision passes only if all hold: * **Playful** — it has shower energy: the small "huh, wait…" of noticing something odd, delightful or quietly absurd about everyday life, the way r/Showerthoughts reads. Light and curious, never a status report, a warning, a risk assessment or a business lesson * **Grounded** — rests on at least two real source entries; the session checks them, the human never needs to see them * **Bridging** — connects two distinct projects or domains, at least one of them work; the further apart, the better * **Perspective shift** — reframes something known rather than summarizing two entries side by side * **Stands alone** — fits in 140 characters and makes sense to someone who saw neither entry: no project names, tool names or jargon they would need explained * **Declarative** — a statement in second or third person; not a question, to-do, or advice * **Not a lazy format** — none of "X is just Y", "X is the Y of Z", "Technically, X", "If you think about it, X", "In a parallel universe, X" * **Not wordplay** — no puns or observations about naming; playful is a fresh angle on something true, not a joke * **Not a repeat** — no pairing, image or insight from the last 7 days of `FEED`, and nothing that reads as a rewording of one * **Within audience limits** — when the session may be seen by others, nothing `AUDIENCE` excludes Choose the one that would make the human grin or tilt their head; on a tie, the greater distance between the bridged things. ## Rules * Exactly one thought per run, or none, plus at most one related idea. Never post a weak thought to fill the slot * Never invent facts about any project or entry to make a connection work * A shower thought is an observation, not an action item. Never add it to a roadmap, open an issue, or append advice to it from this skill * `FEED` holds only shower thoughts — never status updates, receipts, or empty results ## Output * Session format — exactly one thought, then one related idea: * `Shower thought… {thought}` * `Related idea: {one line — something the thought sparks: a thing to build, try or notice}` * Nothing else in the session: no second thought, bridges, sources, counts, flair, status or notes about the run * Feed format: the thought only. Never post the related idea, and never post more than the one thought * Empty result: in the session only — "No shower thought this time." — and nothing posted * Example, from the entries "Channel reads now take a cursor; agents poll only what arrived since they last looked" and "Episode pipeline drops 80% of each transcript; only pull-quotes survive": * `Shower thought… Most of every conversation you've ever had was the part nobody would bother to quote.` * `Related idea: keep the unquoted 80% of each episode as searchable notes instead of throwing it away.` --- # BrianBot Skills Glossary URL: https://mythos.one/me/brianswichkow/b921b7 Updated: 2026-10-12 Tags: #brianbot-skill #glossary The **BrianBot Skills Glossary** indexes the agent skills @[BrianBot](/me/brianswichkow/85920f) runs, noting whether each lives as a @[MythOS](/me/brianswichkow/14a6ef) memo agents read on demand or is installed in a harness like @[Claude Code](/me/brianswichkow/632ca2) or @[Hermes Agent](/me/brianswichkow/857234). ## Glossary ### M * @[MythOS Claude Code Skill](/me/mythos/85e3ff) — `mythos`, an installed, open-source Claude Code skill that connects a MythOS library to the CLI. ### S * @[Shower Thoughts Skill](/me/brianswichkow/40784b) — `shower-thoughts`, a memo-run skill that reads its human's configured sources, such as journals, and surfaces one 140-character insight linking the current work to the rest. # Contexts * [#brianbot-skill](/tag/brianbot-skill) * [#glossary](/tag/glossary) --- # Glossary of Glossaries URL: https://mythos.one/me/brianswichkow/8f41e5 Updated: 2026-10-12 Tags: #glossary The **Glossary of Glossaries** is a master index of all domain-specific glossaries in this library, organized alphabetically by subject. # Glossaries ## # * @[3D Printing Glossary](/me/brianswichkow/ed75b0) ## A * @[Abuse Glossary](/me/brianswichkow/2b5f44) ## B * @[Borderline Personality Disorder (BPD) Glossary](/me/brianswichkow/8d7ec5) * @[BrianBot Skills Glossary](/me/brianswichkow/b921b7) * @[Burning Man Glossary](/me/brianswichkow/17a229) ## C * @[Claude Code Glossary](/me/brianswichkow/90b92a) * @[Claude Model Glossary](/me/brianswichkow/8ff1b3) * @[Claude Platform Glossary](/me/brianswichkow/f36a7e) * @[Cluster B Glossary](/me/brianswichkow/e2557d) * @[Community Glossary](/me/brianswichkow/b407f0) * @[Consensual Non-Monogamy (CNM) Glossary](/me/brianswichkow/2bc3da) * @[Content Optimization Glossary](/me/brianswichkow/df8340) ## G * @[Gemini Model Glossary](/me/brianswichkow/4a2bd2) * @[Grok Model Glossary](/me/brianswichkow/a938dd) ## H * @[Hermes Glossary](/me/brianswichkow/dbee34) ## M * @[Marketing Glossary](/me/brianswichkow/f2ac69) * @[Motorcycle Glossary](/me/brianswichkow/2ff2ab) ## N * @[Narcissistic Personality Disorder (NPD) Glossary](/me/brianswichkow/2c7f2c) ## O * @[One Inc Glossary](/me/brianswichkow/504bec) * @[OpenAI Model Glossary](/me/brianswichkow/d18d4a) * @[OpenClaw Glossary](/me/brianswichkow/90d7b7) ## R * @[Reddit Glossary](/me/brianswichkow/bc7794) ## S * @[Startup Glossary](/me/brianswichkow/314d3b) # Contexts * [#glossary](/tag/glossary) --- # Comet Partner URL: https://mythos.one/me/brianswichkow/305a0c Updated: 2026-10-11 Tags: #consensual-non-monogamy-lexicon A **comet partner**, also called a satellite partner, is a romantic connection in @[Consensual Non-Monogamy (CNM)](/me/brianswichkow/89bbf6) characterized by geographic distance and infrequent but meaningful encounters. ## What Is a Comet Relationship? A comet relationship is the orbit a comet partner moves in. The metaphor is apt: like a comet passing through orbit, this partner appears periodically, burns bright during the visit, and then returns to their own trajectory. Comet partnerships often involve people in different cities, states, or countries who maintain genuine romantic connection without the logistical entanglement of proximity — no shared groceries, no coordinating schedules, no negotiating whose turn it is to do dishes. The relationship exists in concentrated bursts rather than continuous daily presence. ## How Do Comet Partners Fit Into Polyamory? Within @[polyamory](/me/brianswichkow/f7cbdf), comet partners occupy a unique position. They don't fit neatly into hierarchical labels like @[Primary Partner](/me/brianswichkow/71c98b) or @[Nesting Partner](/me/brianswichkow/923fd6), and their infrequent presence means they generate less @[New Relationship Energy (NRE)](/me/brianswichkow/c6621b) disruption to existing relationship networks. For some practitioners, comet relationships are the ideal form of connection — deep intimacy without entanglement, presence without obligation. They challenge the @[Relationship Escalator](/me/brianswichkow/990f50) assumption that more time together automatically means more commitment. ## How Is a Comet Partner Different From a Long-Distance Partner? A long-distance relationship usually treats distance as a problem to solve: continuous daily contact, visits scheduled as often as possible, and @[an](/me/chaseriner/47398f) assumed endpoint where the distance closes. A comet partnership treats distance as part of its shape. Contact between visits is light or dormant, encounters are rare by design, and there is no plan to converge — the relationship is complete as it is rather than waiting to become something else. ## FAQ ### What is a comet partner? A comet partner is a romantic connection in consensual non-monogamy who lives far away and appears infrequently, sharing intense, meaningful time before returning to their own life. ### Is a comet partner the same as a satellite partner? Yes. Satellite partner is a synonym for the same role; both describe a partner who orbits at a distance rather than sharing daily life. ### How often do comet partners see each other? There is no set cadence. Encounters are infrequent by definition, often a few times a year, and the relationship stays intact but dormant between visits. # Contexts * [#consensual-non-monogamy-lexicon](/tag/consensual-non-monogamy-lexicon) --- # AI Augmentation vs AI Automation URL: https://mythos.one/me/brianswichkow/3e1c80 Updated: 2026-10-11 Tags: #agentic-augmentation **AI Augmentation vs AI Automation** is the foundational distinction in how organizations and individuals integrate @[Artificial Intelligence](/me/brianswichkow/f90072) into their work. Automation replaces human labor in a process. Augmentation amplifies human capability within a process. They use the same technology — @[large language models](/me/brianswichkow/10aa8a), agents, APIs — for fundamentally different purposes. The choice between them shapes everything downstream: the systems you build, the skills you develop, and whether AI makes you more capable or more dependent. ## The Distinction **Automation** removes the human from a loop. The AI handles a task end-to-end: customer support chatbots that resolve tickets without agents, document processing pipelines that extract data without reviewers, code generation that ships without engineers. The goal is efficiency — same output, fewer people. **Augmentation** keeps the human in the loop and makes the loop better. The AI provides context the human couldn't access alone, synthesizes information the human couldn't process alone, and executes tasks the human couldn't scale alone — while the human retains judgment, direction, and creative authority. The goal is capability — better output, same people. | | AI Automation | AI Augmentation | | --- | --- | --- | | Human's role | Removed from the loop | Kept in the loop, operating at a higher level | | Goal | Efficiency: same output, fewer people | Capability: better output, same people | | Measure of success | Tasks completed without a person | A person more capable over time | | Trajectory | Flat: the same thing, consistently, at scale | Compounding: better every week | | Failure mode | Brittle when the task drifts from its script | Dependency, if the human can't function without it | | Typical examples | Support chatbots, document pipelines, unattended code generation | Research synthesis, drafting with review, agents that encode one person's judgment | ## How to Tell the Difference Ask one question: **Does the human get more capable over time, or more replaceable?** - If the system works best when the human isn't involved, it's automation - If the system works best when the human is deeply involved but operating at a higher level, it's augmentation @[Brian Bot](/me/brianswichkow/85920f)'s 57-agent ecosystem looks like automation from the outside — agents running autonomously, content publishing without intervention, daily podcasts generating themselves. But the system is designed around augmentation: every agent carries Brian's voice because the @[Memory layer](/me/brianswichkow/6a3108) encodes his identity. Every autonomous action reflects a decision framework he built. The human isn't removed — the human is *encoded into the architecture* and then amplified. ## Why This Matters for Practitioners The automation framing dominates the AI conversation because it's easier to measure. "We replaced 5 customer support agents" is a clear ROI story. Augmentation is harder to quantify: how do you measure "this person now thinks in systems they couldn't build before"? But augmentation compounds in ways automation doesn't. An automated process stays flat — it does the same thing, consistently, at scale. An augmented practitioner gets better every week. The @[Augmentation Stack](/me/brianswichkow/6a3108) compounds: every interaction enriches Memory, every Memory enrichment improves the AI's reasoning, every improved output feeds back into the system. The human evolves with the technology instead of being replaced by it. ## The Sovereignty Test @[Human-AI augmentation](/me/brianswichkow/bca911) has one non-negotiable requirement: the human must remain @[sovereign](/me/brianswichkow/8e63c7). If the AI system works so well that you can't function without it — if removing the AI would leave you less capable than before you started — the system has failed. Good augmentation makes the human more capable *with or without* the AI. The system should expand your thinking, not create a dependency. This is the design constraint that separates augmentation from sophisticated automation wearing an augmentation label. If the system makes you better, it's augmentation. If the system makes itself necessary, it's lock-in dressed as progress. ## @[Collaborative Augmentation](/me/brianswichkow/6c3d01) as the Framework The @[Collaborative Augmentation](/me/brianswichkow/6c3d01) framework operationalizes this distinction. Separate the authorities: the human holds emotional authority (values, taste, direction), the AI holds execution authority (speed, consistency, scale). Build compounding context so the collaboration improves over time. Inform, don't ask permission. The result is a system where neither party is subordinate and neither is replaceable — the hybrid outperforms either alone. ## FAQ ### What is the difference between AI augmentation and AI automation? Automation replaces human labor in a process; augmentation amplifies human capability within it. Both use the same models, agents, and APIs. The difference is whether the human is removed from the loop or kept in it at a higher level. ### Is AI augmentation better than AI automation? Neither is better in every case. Automation fits bounded, repetitive tasks where the script rarely changes. Augmentation fits judgment work, where the value comes from a person getting better over time. The test is whether the human ends up more capable or more replaceable. ### Can one system be both automation and augmentation? Yes. A system can run autonomously and still be augmentation if it encodes one person's judgment and makes that person more capable — agents that publish without intervention but carry their operator's voice and decision framework are the clearest example. :::callout The automation narrative drives me crazy. Not because automation is wrong — it's appropriate for some tasks. But the default framing in every AI conversation is "how many people can we replace?" rather than "how much more capable can each person become?" That framing shapes what gets built, what gets funded, and what people expect from AI. I built @[Brian Bot](/me/brianswichkow/85920f) as an augmentation system because I wanted to become more capable, not more replaceable. Every agent in my system amplifies a skill I already have — synthesizing information, producing content, managing complexity, building infrastructure. If you took BrianBot away tomorrow, I'd still have the skills. I'd just be slower. That's augmentation. If I couldn't function without it, that would be a failure of design. The @[sovereignty](/me/brianswichkow/0d835a) test is the thing I keep coming back to. Am I more capable or more dependent? That question should be asked about every AI system, every product, every workflow. If the answer is dependent, rebuild. ::: # Contexts - [#agentic-augmentation](/tag/agentic-augmentation) --- # Weaponized ADHD URL: https://mythos.one/me/brianswichkow/ceda0e Updated: 2026-10-10 Tags: #attention-deficit-hyperactivity-disorder-adhd **Weaponized ADHD** refers to an informal practice of intentionally leveraging attention variability and episodes of hyperfocus associated with @[Attention Deficit Hyperactivity Disorder (ADHD)](/me/brianswichkow/c47162) to align tasks and projects with those tendencies. In this framing, Weaponized ADHD focuses on choosing high-stimulation, outcome‑driven work and installing external scaffolds that channel focus while containing distractibility. Clinical descriptions of ADHD emphasize patterns of inattention, impulsivity, and hyperactivity, and behavioral guidance often highlights environmental structuring and external reminders as helpful supports. Common tactics include externalized memory aids such as sticky notes, digital capture‑and‑triage systems, timeboxing and the @[Pomodoro Technique](/me/brianswichkow/9249db), and lightweight @[kanban](/me/brianswichkow/34d1d8) or pipeline views for prioritization. The approach is frequently applied in roles that reward rapid context switching, creative ideation, and opportunistic networking, including sales development, research sprints, or event‑driven operations. The term is colloquial rather than clinical and describes a strengths‑based, systems‑oriented strategy to reduce friction from distractibility while maximizing productive hyperfocus. :::callout{icon=https://firebasestorage.googleapis.com/v0/b/mythos-demo.appspot.com/o/profile_pictures%2FSrjP15vkgmSZ50n3Abo5Gite9UE3?alt=media&token=e34784b7-33c6-4fb7-9b1a-74ffc460bce5} I’ve been channeling and leveraging my ADHD with @[sticky note](/me/brianswichkow/65ac82)s and @[MythOS](/me/mythos/09405a) for years, using a @[Corporate Matchmaker](/me/brianswichkow/ec6ff1) role across 50+ @[One Inc Partnerships](/me/brianswichkow/51a7d7) so that nearly any attention pivot routes into a revenue channel. Treating it as both art and science—tight capture loops, exploratory sprints, and disciplined reviews—keeps the practice sustainable. ::: # Contexts * [#attention-deficit-hyperactivity-disorder-adhd](/tag/attention-deficit-hyperactivity-disorder-adhd) --- # Chris Stoikos URL: https://mythos.one/me/brianswichkow/3568e3 Updated: 2026-10-10 Tags: #entrepreneur #beard-club #beard-owner #exited [**Chris Stoikos**](https://www.linkedin.com/in/chrisstoikos/) is a serial [#entrepreneur](/tag/entrepreneur) and the founder and former CEO of @[The Beard Club](/me/brianswichkow/3dc3a6), the men's grooming subscription brand launched in 2015 as Dollar Beard Club. Under his leadership the company reached a reported $40 million in sales, driven in part by viral video advertising in which he starred. In 2023 he joined the grooming brand Hardworking Gentlemen as chief creative officer, a role focused on the brand's creative work. Stoikos is also the founder of Unconscious Content, a collection of media and content creators intended to help entrepreneurs draw on the creativity of their unconscious mind, and of Viral Response, an advertising service. His earlier ventures include Coolbox, founded in 2015 and later licensed; Stoik's Bear Paws, founded in 2012 and acquired; and Electronic Express, founded in 2010 and acquired. :::callout{icon=💡,color=blue} I first met Chris in February 2016 when—while writing at @[Intelligencia](/me/brianswichkow/71ae0d)—I looked up from my computer and recognized his mane. I braved the "OMG, I know you from the internet" awkwardness to introduce myself. I later documented it on the @[Ghost Influence](/me/brianswichkow/3153b9) blog in a post titled '[Beards and Excuses](https://ghostinfluence.com/beards-and-excuses/)'. ::: # Contexts * [#beard-club](/tag/beard-club) * [#beard-owner](/tag/beard-owner) * [#exited](/tag/exited) --- # Cerebras URL: https://mythos.one/me/brianswichkow/495474 Updated: 2026-10-10 Tags: #ai-infrastructure #semiconductor **[Cerebras](https://www.cerebras.ai/)** (Nasdaq: CBRS), formally Cerebras Systems, is an AI chipmaker and inference cloud provider founded in 2016 and led by co-founder and CEO Andrew Feldman, with co-founder Sean Lie as CTO. It builds the Wafer-Scale Engine, a single processor the size of a dinner plate; the WSE-3 carries 900,000 AI-optimized cores and 44 GB of on-chip SRAM. It sells that compute as CS-3 systems and through Cerebras Cloud, an OpenAI-compatible inference API for developers and enterprises. Cerebras designed its chip from scratch rather than following the @[NVIDIA](/me/brianswichkow/8de9b1) GPU model, and has repositioned around inference delivered as a cloud service. It claims inference up to 30 times faster than GPU systems. Independent Artificial Analysis benchmarks show a smaller but real lead, for example about 2,500 tokens per second on Llama 4 Maverick against about 1,000 on Nvidia Blackwell. Cerebras Cloud offers a free trial with $5 in credit, a pay-per-token Developer tier starting at $10, and custom Enterprise plans. Named customers include @[OpenAI](/me/brianswichkow/a05371), whose multi-billion-dollar inference contract anchors much of its revenue, as well as G42, Amazon Web Services, MBZUAI, @[Perplexity](/me/brianswichkow/79517c), Meta, and GSK. Cerebras reported 2025 revenue of $510 million (up 76%) and net income of $237.8 million. It went public on May 14, 2026 at $185 a share, raising $5.5 billion at a $56.4 billion fully diluted valuation, and its shares opened 108% higher. :::callout I set up a Cerebras Cloud account in October 2026. ::: # Contexts * [#ai-infrastructure](/tag/ai-infrastructure) * [#semiconductor](/tag/semiconductor) --- # Ralph URL: https://mythos.one/me/brianswichkow/840037 Updated: 2026-10-10 Tags: #open-source #ai-agents #developer-tool **[Ralph](https://github.com/snarktank/ralph)** is an [#open-source](/tag/open-source), MIT-licensed autonomous coding loop published on @[GitHub](/me/brianswichkow/724696) by Ryan Carson (`snarktank`). It runs an AI coding agent repeatedly until every item in a @[Product Requirements Document (PRD)](/me/brianswichkow/f8559c) passes. Each iteration starts a fresh agent with clean context, takes the highest-priority unfinished user story, implements it, runs quality checks, commits on success, and marks the story done. The loop exits when the agent reports all stories complete. Ralph packages Geoffrey Huntley's "Ralph" pattern, which it credits as its basis, into a bash script (`ralph.sh`) plus skills. It is a simpler cousin of the worker-and-judge @[Ralph Loop](/me/brianswichkow/c17ac1). Instead of a separate judge reading a long transcript, it keeps memory outside the model: git history, a `prd.json` task list with a `passes` flag per story, an append-only `progress.txt` of learnings, and an @[AGENTS.md](/me/brianswichkow/ba19af) updated after each iteration with patterns and gotchas. It drives Amp by default and @[Claude Code](/me/brianswichkow/632ca2) with `--tool claude`, needs `jq` and a git repository, and runs 10 iterations unless told otherwise. It installs by copying the script into a project or as a @[Claude Code Plugin](/me/brianswichkow/5049bf) from its own marketplace. By October 2026 the repository had about 21,900 stars and 2,100 forks. :::callout @[Jim Goodman](/me/brianswichkow/725d6c) introduced me to Ralph. ::: # Key Features - **Fresh context per iteration** — each pass spawns a new agent, so long builds never exhaust a single @[context window](/me/brianswichkow/9c8f8e). - **File-based memory** — git history, `prd.json`, and `progress.txt` carry state between iterations instead of the model's context. - **PRD skills** — `/prd` drafts a requirements document and `/ralph` converts it into the `prd.json` stories the loop works through. - **Self-updating AGENTS.md** — each iteration records patterns and gotchas where coding agents read them automatically. - **Agent choice** — runs Amp by default or Claude Code via `--tool claude`, with a configurable iteration cap. # Contexts * [#ai-agents](/tag/ai-agents) * [#developer-tool](/tag/developer-tool) --- # Page-2 SEO Opportunity Audit — Loop Runbook URL: https://mythos.one/me/brianswichkow/2391e9 Updated: 2026-10-09 Tags: #runbook #seo Each pass audits one finalized 28-day window of a site's @[Google Search Console](/me/brianswichkow/d40f3b) data. It finds queries ranking on page 2 (positions 11–20) that have real impressions but almost no clicks, maps each to the page that ranks, audits those pages, and writes the exact fix for each. Results go to a dashboard, a MythOS worklist, or both, with a summary for the operator. It is built for anyone with Search Console access and is meant to run weekly. Status: prototype. It was converted from a one-shot audit prompt on 2026-10-09 and has not yet run as a scheduled loop. ## Purpose The cheapest SEO wins are queries Google already considers relevant but places just below the first page of results. This loop surfaces them each pass, ranks them by click upside rather than raw volume, and states the exact change for each page: before-and-after title tags, the H2 to add, and which URL redirects into which. It reports only and never edits the site, so whoever owns the pages applies the fixes. Any agent with web access can run it (Claude Code, the Claude desktop app, or a comparable MCP client). A scheduler only needs to point that agent at this memo and run one pass. Every step needs tools, so it cannot run as a single tool-less model call. ## Prerequisites - **Parameters** — copy the table below and fill in your values. Values marked "set by first pass" are discovered on the first run and recorded. - **Search Console access** — one of two paths: - **Preferred:** a Search Console MCP server that exposes search analytics by query and page, such as the read-only @[Google Search Console MCP](/me/brianswichkow/a57e90). It runs headless, so the loop can run unattended. That server is not yet published for public install. Until it is, use any equivalent Search Console MCP or the Chrome path. - **Fallback:** Chrome with the Claude in Chrome extension, signed into a Google account that has access to the property. It needs the machine awake and Chrome open. - **Page fetching** — any web-fetch tool, to read each ranking page's title, meta description, and headings. - **Dashboard publishing** (for OUTPUT `dashboard`) — a way to publish one HTML page to a stable URL. In Claude, that is the Artifact tool. - **MythOS MCP** (for OUTPUT `worklist`) — @[MythOS MCP](/me/mythos/a18046) connects a MythOS library to your AI client. To install it, add [`https://mythos.one/api/mcp`](https://mythos.one/api/mcp) as a connector in Claude (claude.ai → Customize → Connectors) and sign in, or generate an API key at mythos.one Settings → API for other clients. Without it, choose OUTPUT `dashboard`. - **Mail connector** (optional) — for example Gmail, to draft the summary. Without one, the summary is delivered in the pass's receipt. - **Trigger** — a weekly schedule whose only instruction is "read this memo and run one pass": a scheduled task, `/loop`, cron, or a MythOS Loop handed to an external runner. | Name | Value | Description | | --- | --- | --- | | SITE | `{example.com}` | The site being audited | | PROPERTY | `sc-domain:{example.com}` | Search Console property. For a URL-prefix property, use its full prefix (e.g. `https://www.example.com/`) | | PAGE\_SCOPE | blank | Optional URL-path filter, e.g. `/blog/`. Blank audits the whole property | | GOOGLE\_ACCOUNT\_INDEX | set by first pass | Chrome path only: the `N` in `/u/N/` for the signed-in account that holds PROPERTY | | OUTPUT | `dashboard` | `dashboard`, `worklist`, or `both` | | MYTHOS\_LIBRARY | blank | Worklist only: the MythOS library username that holds the worklist. Blank uses the connected account's own library | | WORKLIST\_MEMO | set by first pass | Worklist only: path of the worklist memo this loop maintains | | DASHBOARD\_URL | set by first pass | Dashboard only: the stable URL every later pass republishes to | | REPORT\_EMAIL | `{you@example.com}` | Only recipient of the summary | | EMAIL\_MODE | `draft` | `draft` creates a draft; `send` sends; `none` skips email. Only the operator changes this | | WINDOW | 28 days, ending 3 days before today | Selection window, aligned to Search Console's finalization lag | | BAND | positions 11–20.99 | Page-2 band | | MIN\_IMPRESSIONS | 40 | Floor for a band query to count | | TARGET\_CTR | 0.06 | Planning stand-in for CTR near position 5. It orders the list and is not a forecast | | TOP\_N | 20 | Ranked queries kept | | PAGE\_LOOKUP\_N | 10 | Top queries mapped to their ranking pages | | SNIPPET\_LIST | positions 8–11, 300+ impressions, CTR ≤ 0.5% | Page-one queries that aren't getting clicked (a title/meta problem). The 0.5% threshold is provisional | | FAR\_LIST | 400+ impressions, position ≥ 21 | Listed for awareness, never presented as quick wins | | SYNTHETIC\_SCREEN | on: drop 1,000+ impression queries with CTR < 0.2% | Removes automated or AI-agent query families that would inflate the band. Turn it off for sites without that traffic. The threshold is provisional | ## The Loop ### Step 1 — Discover the pass - Compute the window: its end is three calendar days before today, in the property's reporting time zone (Pacific), and its start is WINDOW days earlier. - Read the prior state from the output this loop maintains: the dashboard's embedded `audit-data` block at DASHBOARD\_URL, or the "Last audited window" line in WORKLIST\_MEMO. - If the prior window end equals the computed end, the window has already been audited. Report "no new window; last audited " and stop. - Otherwise, keep the prior ranked rows (from the dashboard block, when present) as PRIOR for the week-over-week delta. On a first pass, PRIOR is empty. ### Step 2 — Connect to Search Console - **MCP path:** list the accessible sites and confirm PROPERTY is among them. If it is not, halt and report missing access. - **Chrome path** (only without a Search Console MCP): load the Chrome tools in one ToolSearch call (`tabs_context_mcp`, `navigate`, `computer`, `find`, `javascript_tool`, `browser_batch`), check the tab context, and open a new tab. - Find the account index by testing [`https://search.google.com/u/N/search-console?resource_id=`](https://search.google.com/u/N/search-console?resource_id=) followed by URL-encoded PROPERTY, for N = 0, 1, 2 and so on. Start from GOOGLE\_ACCOUNT\_INDEX when it is set, and record the index if it was unset. ### Step 3 — Pull the window's query data - **MCP path:** query search analytics for PROPERTY over the window, grouped by query. When PAGE\_SCOPE is set, filter to pages containing it. Request enough rows to cover everything at MIN\_IMPRESSIONS or above. - **Chrome path:** open `/u/N/search-console/performance/search-analytics` for the property with `num_of_days=28&breakdown=query&metrics=CLICKS%2CIMPRESSIONS%2CCTR%2CPOSITION`. When PAGE\_SCOPE is set, add a page filter. Then set "Rows per page" to 500, following the dropdown convention below, and extract the rows with the snippet in Conventions. - Count the parsed rows before trusting anything. If the Chrome path yields only 10, the dropdown didn't take: retry it once, then proceed with what parsed and say so. - Record site totals (clicks, impressions, CTR, average position) from the same pull. ### Step 4 — Screen and rank - When SYNTHETIC\_SCREEN is on, drop matching query families and list what was dropped. - Filter to BAND with at least MIN\_IMPRESSIONS impressions. - Score each row as `impressions × (TARGET_CTR − CTR)`, where CTR is a fraction, and floor the score at 0. Sort by score and keep the top TOP\_N. - Build SNIPPET\_LIST and FAR\_LIST from the same pull. - When PRIOR exists, compute each query's change in impressions, position, and score, and mark queries that are new to or gone from the band. ### Step 5 — Map queries to ranking pages - For each of the top PAGE\_LOOKUP\_N queries, pull the page breakdown with an exact-match query filter. On the MCP path, group by page and filter the query with `equals`. On the Chrome path, append `&breakdown=page&query=!` plus the URL-encoded exact query, and slice the extraction from `Top pages`. Batch the navigate-and-extract pairs into `browser_batch` calls. - When more than one URL from the site ranks for a query, flag it as cannibalization. Name each URL with its position, pick the winner (the URL already ranking best, not the one that "should" win by topic), and plan 301 redirects from the others into it. ### Step 6 — Audit the ranking pages - For each distinct ranking URL, fetch the page and record verbatim its title tag, meta description, H1, and full H2 list. If the page is a MythOS memo and the MythOS MCP is connected, also read the memo and record its SEO title and description. - Check each page against its queries: - Is the query phrase in the title, and in the H1? - Intent: does the page answer what was asked, or a neighbouring question? ("Why does X take so long" ranking for "how long does X take" is a mismatch.) - Spelling and word form: one word vs. two, singular vs. plural. - Is the meta description missing, leaving Google to write the snippet? - Is the metadata a leftover placeholder, such as "Home" or a bare product name? - Give each row one diagnosis: Cannibalization, Metadata, Intent mismatch, Content depth, or Spelling. ### Step 7 — Write the fixes - Order fixes by summed score. For each, state what is wrong, list the affected queries with impressions and position, and give the exact change: the before and after title tag, the H2 to add and where it goes, and which URL 301s into which. - Where the on-page work is already done and the real limit is content depth or domain authority, say so plainly. Never pad the list with invented tweaks; five real fixes beat ten padded ones. ### Step 8 — Publish the dashboard - Run this step only when OUTPUT is `dashboard` or `both`. - Build one HTML page: - A stat strip: estimated clicks in play, queries in band, band impressions, and site totals. - The ranked table: query, ranking page, impressions, clicks, position, estimated gain, diagnosis chip, and the week-over-week delta column. - A per-row position scale with a page-one marker. - The ordered fixes. - The SNIPPET\_LIST and FAR\_LIST side lists. - Notes that the 0.06 target CTR is a planning number, not a forecast, and that the band is not exhaustive. - Embed this pass's data as `