Bloat we refuse

Curation says what ships. This tab says what sucked so hard we documented the kill. Not vibes — operator sessions, uninstall pain, and architectural red flags.

genre diagnosis

Memorymancers → copromancers (real word: copromancy)

All that memorymancer marketing — continual learning, dialectic recall, dual queues, Workspace keys, gsync gravity — is not intelligence. It is specialist copromancy: read deuces, write shit. In, out, sludge. Same class: OpenClaw, Hermes/Nous, Honcho-shaped “statefulness solved.” Disgust is the correct operator response. Titanium does not host this.

literary kill · not a product review

Reading feces · curating shit sculptures

Copromancy is the real art: Rubem Fonseca energy — hard Brazilian prose that will look straight at the dung and not flinch. Then Oblivion: David Foster Wallace’s The Suffering Channel — the artist whose medium is shit, and the whole machine around curating feces as sculpture.

That collab is the product category: Nous Research × Honcho — memorymancers cosplaying neuromancers, actually specialist copromancers. Read deuces. Write shit. Dual-queue the gallery. Sell tickets to the sludge. XDDDD. Titanium does not hang that show.

killed · memory substrate

Honcho — the worst suck we have measured

KILLEDnot Phase-0not default memory

Honcho is the most elaborate way we have ever seen to not get durable, mission-scoped recall. Marketing: “statefulness solved,” “memory that reasons,” MCP for every client. Reality after stress + reaudit: probabilistic dialectic chat as “read path”, no real user metadata for structured axes, session semantics that fight multi-mission authority, and a design that begs you to client-patch around missing primitives.

That is peak suck: not “a bit slow,” but architecturally wrong for a judge stack. We did the primary-source work (schema, deriver, chat tool-loop). Verdict: R0 — no Honcho. SQLite-authoritative findings stay. FTS5 before you even think of reopening. If a tool needs you to rewrite your stack to host it, the tool is the bug.

Suck factor: max — worst “memory product” fit we tried for xbreed/xbgst
Use instead: local SQLite + scribe reports
Evidence: honcho-reaudit-closure-2026-04-18 (marketplace plugin docs)
Reopen: only named upstream schema/API changes — not a blog post

killed · hard no · pre-Hermes

OpenClaw — strong no already

KILLEDprior reject

OpenClaw was a strong no before Hermes ever got a dollar. Same autonomy-slime class: sticky runtime, not a thin job runner. Do not re-evaluate. The sequel (Hermes) only confirmed the genre is trash.

Use instead: sekhmet / Titanium pure sparks · xbgst
Reopen: None

killed · agent slime · nous research

Hermes agent — emoji bloatware that feels like a trojan

KILLEDNoushard to nuke

Hermes is not clever. It is literal bloatware — emoji control panels, sticky lifecycle, uninstall that makes you work for your own machine. Felt like a trojan (operator gut, not a legal filing). Ran it on a VPS: trash. Blamed the VPS. Ran it local: bigger mistake. Had ~$200 USD sitting on DigitalOcean after OpenClaw was already a hard no — figured why not. Then got so bothered by how shitty it was that every salvage path got tried. Could not. Literally. Garbage to the core. Cannot be salvaged. Host was never the bug. The product was.

Special circle of hell: Google Workspace API keys as a lifestyle, then “persistent memory” by duo-queuing the worst memory feature ever. On the date everything started going array — nice work, Hermes. Stack gravity toward gsync / rclone garbage as if sync daemons were consciousness. Utter trash. Fuck that default. Nous Research: do not pass go, do not collect a seat on Titanium.

Suck factor: extreme — bloat + emoji cosplay + sticky death
Memory: dual-queue cloud slime ≠ authority
Sync: gsync/rclone as agent substrate = credential sprawl
Use instead: sekhmet / Titanium pure sparks · xbgst · SQLite SSoT
If found: kill process + unit + user dirs; do not “disable”

killed · toolchain · enshittified PATH

mise — the most enshittified Node manager ever shipped

KILLEDnot fnmPATH occupancy

Imagine recommending mise for Node. XDDDD. It is not a version manager. It is a polyglot runtime religion wearing nvm’s coat: shims, activation hooks, plugin galaxies, “one tool to own PATH.” The job was pin Node. The product is occupy the shell.

Elegant shit: a kitchen sink that breaks everything it pretends to unify. Mystery node. Agent jobs that worked until the shim. CI that inherited a worldview. fnm does the one job — Fast Node Manager, no runtime theocracy. The glaze is earned: fnm multishell — eval "$(fnm env --shell bash)", fnm exec --using … — per-shell Node, no global shim occupation. Tools adapt to us. mise wants the reverse. Kill it as default. Do not “just try asdf again with a new name.”

Suck factor: peak — most enshittified Node manager in the drawer
Failure mode: PATH/shim occupancy, not “slow installs”
Use instead: fnm multishell + .node-version
Reopen: Node-only, no shims, one-command PATH restore — not “but Python too”

killed · config posture

MCP zoo on Titanium

KILLEDL3 pure-exec

“Connected” is not a feature. Twelve MCP servers on a Codex Titanium / sekhmet host is against policy. Context tax, auth flakes, wrong-tool bias. Even good research products do not get wired into L3 as default MCP.

Use instead: pure sparks; research on a separate host if needed
Exa praise: exa.html — product quality, not Titanium MCP mandate

Full kill table with reopen triggers: docs/ANTI-PATTERNS.md. Titanium stays clean. Curation stays sharp. Bloat stays named.