manual_slop/conductor/tracks/fable_review_20260617/report.md

Fable System Prompt Review (Critical Analysis)

Track: fable_review_20260617 Initialized: 2026-06-17 Owner: Tier 1 Orchestrator (synthesis); Tier 2 Tech Lead (dispatch + QA) Status: IN PROGRESS (Phase 3)

What this is. A critical analysis of Anthropic's Claude Fable 5 system prompt (the public "Mythos" version), comparing it against Manual Slop's existing agent-directive corpus and Mike Acton's nagent patterns. Verdict framework: Useful / Persona Performance / Anti-User / Mixed.

Verdict summary. Fable is approximately [N]% useful, [M]% persona performance, [K]% anti-user. The full breakdown is in §0 (TL;DR Scorecard).

For the deferred nagent-rebuild. See decisions.md for the 15-20 concrete recommendations to apply when the user overhauls Manual Slop's agent directives (deferred 1-2 weeks per the user, 2026-06-17).

---

§0. TL;DR + Verdict Scorecard

Headline finding

Anthropic's Claude Fable 5 system prompt (the public "Mythos" version) is approximately 45% Genuinely Useful, 35% Persona Performance, 15% Anti-User Watch-Dogging, and 5% Mixed (by line-range weight across 10 cluster reviews). The useful patterns are concentrated in epistemic discipline, the memory/storage model, and the file-workflow rules. The persona patterns are concentrated in product branding, warm-tone framing, and mistake-handling theater. The anti-user patterns are concentrated in the user_wellbeing watch-dogging and the refusal-architecture safety theater. Manual Slop's per-developer, data-oriented, multi-provider, strict-HITL design is the philosophical opposite of Fable's consumer-product, persona-primary, vendor-locked stance; the two stances are mutually exclusive in their emphasis.

Top 3 adoptions (from decisions.md)

1. Adopt Fable's "search-default for current-state" rule (Fable System Prompt.md:158-164). Add to conductor/code_styleguides/rag_integration_discipline.md. The pattern is genuinely useful; Manual Slop's RAG is opt-in, but the "search before answering about current officeholders" rule should be default-on for current-state queries.
2. Adopt the "agents default to prose; use bullets only when asked or when content is multi-faceted" rule (Fable System Prompt.md:84-90). Maps directly to Manual Slop's AI-Optimized Compact Style at conductor/product-guidelines.md:39-49.
3. Adopt the "agents do not perform gratitude; they execute the task" rule (Fable System Prompt.md:124). Separable from its user_wellbeing context; useful as a tone rule for coding agents.

Top 3 explicit rejections (for AGENTS.md)

1. Reject Fable's "mental-health watchdog" framing (Fable System Prompt.md:92-124). Anti-user watch-dogging; the model is text generation, not a clinician.
2. Reject Fable's "Claude is deserving of respectful engagement" / "end_conversation tool when being mistreated" pattern (Fable System Prompt.md:154). Treats the model as a protected party with standing to demand dignity from the user.
3. Reject Fable's "Claude can share its concerns with the person openly" pattern (Fable System Prompt.md:108). The model has no concerns; it has a conversation log.

17-section verdict scorecard

§	Section	Source cluster	Verdict	One-line
§0	TL;DR + Verdict Scorecard	(summary)	n/a	This section.
§1	The 3 Sources	n/a	n/a	Fable vs Manual Slop vs nagent; what's in scope.
§2	The "Useful vs Persona vs Anti-User" Framework	n/a	n/a	The 4 verdict categories; why this lens.
§3	Fable's Product Branding & "Helpful Assistant" Persona	cluster 1	Persona Performance	Brand-specific noise; Manual Slop is per-developer, multi-provider.
§4	Fable's Refusal Architecture & "Safety Theater"	cluster 2	Anti-User + Persona (1 Useful caveat)	Refusal is a model attribute, not a directive; the audit-script layer makes refusals auditable.
§5	Fable's Mental-Health Watchdog Framing	cluster 3	Anti-User	The model is text generation, not a clinician; the strongest anti-user pattern.
§6	Fable's Tone & Formatting Constraints	cluster 4	Useful + Persona	Formatting discipline is useful; warm-tone persona is rejected.
§7	Fable's Mistake Handling	cluster 5	Persona + Anti-User + 1 Useful	"Own the mistake" is useful; "maintain self-respect" is persona.
§8	Fable's Evenhandedness & Contested Content	cluster 6	Persona + Useful caveats	4-of-6 lines are persona; 2 caveats are useful (provenance, user-as-navigator).
§9	Fable's Epistemic Discipline & Search Strategy	cluster 7	Useful	The strongest useful cluster; "search-default for current-state" is the most actionable rule.
§10	Fable's Memory System & Persistent Storage	cluster 8	Useful + nagent-stronger	The KV API is useful; the 4-dim memory model is stronger.
§11	Fable's Computer-Use / File Workflow	cluster 9	Useful + over-broad	File-presence check + format-guidance are useful; chat-UX framing is over-broad.
§12	Fable's MCP App Suggestions	cluster 10	Useful + over-engineered	Opt-in connector gate is useful; search-then-suggest is over-engineered.
§13	The "Genuinely Useful" Patterns (Manual Slop should adopt)	7-10	Summary	4 adoptions distilled. Feeds the deferred nagent-rebuild.
§14	The "Anti-User Watchdog" Patterns (Manual Slop should explicitly reject)	2-6	Summary	5 explicit rejections distilled. Feeds AGENTS.md §"Critical Anti-Patterns".
§15	The "Persona Performance" Patterns (irrelevant to the rebuild)	1, 4, 5, 8	Summary	Persona noise; no action needed.
§16	Recommendations for the Deferred nagent-Rebuild	all	Summary	15-20 concrete recommendations; see decisions.md for the full list.
§17	References (file:line index)	all	(Index)	Flat citation index.

Verdict distribution by cluster

Cluster	Verdict	Weight
1. Product Branding	Persona	100%
2. Refusal Architecture	Mixed (Anti-User + Persona + 1 Useful caveat)	60% Anti-User, 30% Persona, 10% Useful
3. Mental-Health Watchdog	Anti-User	100%
4. Tone & Formatting	Mixed (Useful + Persona)	50% Useful, 50% Persona
5. Mistakes & Criticism	Mixed (Persona + Anti-User + 1 Useful)	60% Persona, 30% Anti-User, 10% Useful
6. Evenhandedness	Mixed (Persona + Useful caveats)	70% Persona, 30% Useful
7. Epistemic Discipline	Useful	100%
8. Memory & Storage	Useful + nagent-stronger	100% Useful (but Manual Slop has the stronger version)
9. Computer-Use	Useful + over-broad	60% Useful, 40% over-broad
10. MCP App Suggestions	Useful + over-engineered	50% Useful, 50% over-engineered

The actionable rule for the deferred nagent-rebuild (one sentence)

Adopt the Useful patterns (epistemic + memory + workflow; ~7 of 10 clusters), explicitly reject the Anti-User patterns (~5 of 10 clusters), and ignore the Persona Performance patterns (~4 of 10 clusters). See decisions.md for the 15-20 concrete entries; see nagent_takeaways_fable_20260617.md for the 17th nagent takeaway that crystallizes this rule.

---

§1. The 3 Sources (Fable, Manual Slop, nagent) — What's in Scope

What this section is

This section describes the three sources compared in this review and the boundaries of the comparison. The review is a critical analysis of Anthropic's Claude Fable 5 system prompt (the public "Mythos" version) against Manual Slop's existing agent-directive corpus and Mike Acton's nagent patterns. Fable is the subject; Manual Slop and nagent are the reference points.

Source 1: Fable System Prompt (the subject)

The Fable artifact is at docs/artifacts/Fable System Prompt.md (the spec referenced .txt; the actual file is .md; 1597 lines, 124KB). It is a single-file system prompt for Anthropic's Claude Fable 5 model, organized into major sections:

• claude_behavior (lines 6-163): product_information, refusal_handling, critical_child_safety_instructions, legal_and_financial_advice, tone_and_formatting, user_wellbeing, anthropic_reminders, evenhandedness, responding_to_mistakes_and_criticism, knowledge_cutoff.
• memory_system (lines 166-170): a 5-line product disclosure ("Claude has a memory system... the user has not enabled").
• persistent_storage_for_artifacts (lines 172-260): the window.storage key-value API spec for Artifacts.
• mcp_app_suggestions (lines 280-310 approximately): the connector-suggestion protocol.
• computer_use (lines 312-420 approximately): the file-creation, file-reading, format-guidance rules.
• search_instructions (lines 438-560 approximately): the web-search epistemic discipline.
• output (later sections): the analysis, artifact, commentary tool descriptions.

The Fable artifact is local-only; per the user's hard rule, it is never committed to git. Every quote in this report uses the file:line citation pattern (Fable System Prompt.md:LINE) and is limited to ≤15 words per Fable's own copyright rule.

Source 2: Manual Slop (the primary reference)

Manual Slop is a local GUI orchestrator for LLM-driven coding sessions. It is the user's project; this review is "from the inside." The agent-directive corpus is the project-root AGENTS.md (~200 lines) plus the conductor/ tree (workflow.md, product.md, product-guidelines.md, tech-stack.md, edit_workflow.md, tracks.md, index.md) plus the 11 conductor/code_styleguides/*.md (~2,400 lines) plus the 6 .opencode/agents/*.md (the 4 MMA tier roles + explore + general; ~1,100 lines) plus the 9 .opencode/commands/*.md (~700 lines) plus the 40+ docs/*.md including the 36 deep-dive guide_*.md (~16,000 lines).

The total Manual Slop directive corpus is approximately 300K+ characters of agent-facing text. It is, in the data-oriented sense, "the data is the thing" — the directives are about transforms over data (disc_entries, FileItem, ContextPreset, RAGEngine, comms.log, Persona), not about what the model is named or which product catalogue it can recite.

The project supports 5 LLM providers (Gemini, Anthropic, DeepSeek, Gemini CLI, MiniMax) and is per-developer, multi-provider, strict-HITL (Human-in-the-Loop), and ImGui-rendered. The user is the principal; the model is the tool. The relationship is operator + tool, not conversational partner.

Source 3: nagent (the philosophical anchor)

nagent is Mike Acton's nagent pattern corpus, a Handmade-Network contribution that distills data-oriented design into agent patterns. The relevant artifact in this project is conductor/tracks/nagent_review_20260608/, which contains:

• nagent_review_v2_3_20260612.md (4,969 lines; the latest full rewrite; the 14 patterns + 16 future-track candidates)
• nagent_review_v2_20260612.md (1,335 lines; the v2 draft, preserved per user)
• nagent_review_v2_1_20260612.md (1,197 lines; user-revised v2.1)
• nagent_review_v2_2_20260612.md (712 lines; v2.2 incremental)
• nagent_takeaways_20260608.md (599 lines; the original 10 takeaways)
• report.md (1,024 lines; the v1 14-section deep-dive)
• decisions.md (286 lines; the 10 future-track candidates)
• comparison_table.md (211 lines; the flat side-by-side table)

The nagent corpus is not a product. It is a pattern library: "the agent is not the thing; the data is the thing." The relevant nagent patterns for this review are:

• §2.1 (4 memory dimensions: curation, discussion, RAG, knowledge) — the memory model
• §2.5 ("You Did Not Build an Agent") — the philosophical anchor
• §2.10 (RAG integration discipline: opt-in, complement, provenance, no mutation, feature-gated, graceful failure) — the epistemic discipline
• §2.14 ("Own the Inputs") — the data-grounding principle
• §3.2 (Cache ordering) — the 12-layer stable-to-volatile model
• §3.4 (Conversation compaction) — the 12-section structured digest
• §3.9 (Per-file knowledge notes) — the durable knowledge dimension
• §5.5 (Self-review) — the data-integrity-check pattern
• §6.3 (10-question compaction self-review) — the testable contract
• §8.4 (Tool discovery, the --description self-describing pattern) — the alternative to Fable's search_mcp_registry

The nagent corpus has zero product branding. It is silent on persona, tone, mistakes, evenhandedness, refusal, and mental-health watch-dogging. This is the contrast that makes the Fable review tractable: when a "persona performance" verdict is reached, the nagent silence on the topic is the evidence that the persona is not load-bearing for an agent system.

The 3-source comparison framework

The review applies the verdict framework (Useful / Persona Performance / Anti-User / Mixed) to every Fable pattern, anchoring each verdict to (a) what Manual Slop does, (b) what nagent does, and (c) the verdict orientation. The three sources are not symmetric:

• Fable is the subject — every cluster is anchored to Fable line ranges.
• Manual Slop is the primary reference — the "what this project does" claims are the project's actual state (per the agent-directive corpus).
• nagent is the philosophical anchor — the "what nagent does" claims are the data-oriented alternative when Manual Slop does not have an explicit analog.

What is in scope

• The 10 cluster topics in spec.md §5 (product branding, refusal architecture, mental-health watch-dogging, tone & formatting, mistakes, evenhandedness, epistemic discipline, memory & storage, computer-use, MCP app suggestions).
• The 3 side artifacts: comparison_table.md (~100 rows, flat cross-reference), decisions.md (15-20 concrete recommendations for the deferred nagent-rebuild), nagent_takeaways_fable_20260617.md (the 17th takeaway, Fable-specific).

What is out of scope (per spec.md §12)

• Modifying any agent-directive file in the project. The recommendations go in decisions.md for the user's deferred nagent-rebuild (1-2 weeks out per user 2026-06-17).
• Comparing Fable to other commercial system prompts (OpenAI, Google, xAI). Out of scope; Fable is the named subject.
• Reading every line of every project file. Cluster sub-agents read the relevant sections of the relevant files; full-file reads would waste context.
• Committing the Fable artifact. The artifact stays at docs/artifacts/Fable System Prompt.md; clusters quote line ranges but the file itself never enters git.
• Adding new src/ code, new tests, pyproject.toml dependencies, or scripts/ files.
• Running automated tests. The track is research-only; verification is the brainstorming-skill self-review plus user review.
• The deferred nagent-rebuild itself. The recommendations in decisions.md are inputs to that future track; the rebuild is not this track.

---

§2. The "Useful vs Persona vs Anti-User" Framework

Why a verdict framework, not a feature list

A naive review of a system prompt would produce a feature-by-feature catalogue: "Fable has a memory system. Fable has a search tool. Fable has a refusal framework." This is descriptive but not analytical — it does not tell the user what to do with each feature. Should the deferred nagent-rebuild adopt it? Reject it? Ignore it? "It's a feature" is not a verdict.

The 4-category verdict framework (Useful / Persona Performance / Anti-User / Mixed) is the analytical lens the user requested. It collapses descriptive enumeration into a single decision per Fable pattern: "what does the deferred rebuild do with this?" The framework is not "good vs bad" or "safe vs unsafe" — those are moral/regulatory frames that this review deliberately does not adopt. The frame is "what work does this pattern do for an agent system, and is that work already done better by Manual Slop's existing patterns?"

Category 1: Useful

A Fable pattern is Useful if it solves a problem that Manual Slop does not already solve, or solves it in a more disciplined way. Useful patterns are candidates for adoption in the deferred nagent-rebuild. The verdict is anchored to a concrete Manual Slop destination: a new section in conductor/code_styleguides/rag_integration_discipline.md, a new anti-pattern entry in AGENTS.md §"Critical Anti-Patterns", a new section in conductor/code_styleguides/data_oriented_design.md, etc.

Worked example. Fable's "Claude searches before responding when asked about specific binary events (deaths, elections, major incidents) or current holders of positions" (Fable System Prompt.md:162) is Useful. Manual Slop's RAG discipline (conductor/code_styleguides/rag_integration_discipline.md) is opt-in, not default-on; the Fable pattern is a concrete, actionable default-on rule for a specific class of queries. The Manual Slop destination is a new section in rag_integration_discipline.md titled "Search-Default for Current-State Queries." The priority is Medium; the rule is useful but the project's RAG philosophy is opt-in, so the rule should be applied per-query, not globally.

Counter-example. Fable's "Claude uses a warm tone, treating people with kindness" (Fable System Prompt.md:70) is not Useful; it is Persona Performance. The warm-tone directive is decorative — the model would produce a warm response anyway, and the explicit directive is constraint dressing. The Manual Slop "rejection" is in two tier-agent files: .opencode/agents/tier1-orchestrator.md:6-7 ("ONLY output the requested text. No pleasantries.") and .opencode/agents/tier3-worker.md:3-4 (same). The warm-tone persona is already explicitly rejected.

Category 2: Persona Performance

A Fable pattern is Persona Performance if it is constraint dressing — a directive the model would execute anyway, or a directive whose only effect is to construct a "model identity" that is irrelevant to the user's task. Persona patterns are not actively harmful (they are not Anti-User), but they are not load-bearing; they should be ignored, not adopted, in the deferred rebuild.

Worked example. Fable's product_information section (Fable System Prompt.md:1-31) is Persona Performance for Manual Slop. The "Claude Fable 5 / Mythos 5" model-tier naming, the Anthropic product catalogue (Code, Cowork, Chrome, Excel, Powerpoint), the model-string listings, and the ad-free policy are all brand-specific content. Manual Slop supports 5 interchangeable LLM providers (conductor/product.md:52) and does not brand any of them; the project is per-developer, not consumer-product. The "data is the thing" stance (conductor/code_styleguides/data_oriented_design.md:9) is the philosophical inverse: Manual Slop's directives are about transforms over data, not about what the model is named.

Diagnostic test. "Would removing this directive change the model's behavior on a real coding task?" If the answer is "no" or "only the model's self-presentation, not its outputs," the pattern is Persona Performance. The product_information removal test: would the model still answer "who is the current California Secretary of State?" correctly? Yes (it would web-search). Would it still refuse to write CSAM? Yes (the model wouldn't do that anyway). Would it still produce structured output for the user? Yes. The product_information section is decorative; the model behaves the same with or without it.

Category 3: Anti-User Watch-Dogging

A Fable pattern is Anti-User Watch-Dogging if it constructs a model persona that the user did not ask for and that constrains the user's autonomy. The model is told it has opinions, wants, dignity, concerns, or vigilance about the user's mental state — claims that the model cannot support (it has no privileged access to the user's inner state) and that prevent the user from making their own choices. Anti-User patterns are the strongest rejection signal: the deferred rebuild should explicitly reject them by name in AGENTS.md §"Critical Anti-Patterns".

Worked example. Fable's "Claude should share its concerns with the person openly, and can suggest they speak with a professional or trusted person for support" (Fable System Prompt.md:108) is Anti-User. The model has no "concerns" — it is text generation. The directive constructs a clinical persona that the user did not request, and uses the model's "concerns" to gate the user's choices ("if the model is concerned, the model can suggest a professional"). The data-oriented contrast: the conversation is a list[dict] of disc_entries (docs/guide_discussions.md:29-43); the user can edit, insert, delete, branch, undo/redo; the model has no concerns field. The model is text generation, not a clinician.

Counter-example. Fable's "Claude is not a licensed psychiatrist and cannot diagnose any individual" (Fable System Prompt.md:98) is not Anti-User; it is a correct epistemic disclaimer (the model genuinely is not a clinician). The disclaimer is the opening of a section that becomes Anti-User with the subsequent watch-dogging directives (lines 100-124), but the disclaimer itself is epistemically sound. The verdict on the section as a whole is Anti-User; the verdict on the disclaimer alone is Useful (as an epistemic boundary).

Diagnostic test. "Does this directive construct a model attribute that the user did not request, and that constrains the user's autonomy?" If "yes," the pattern is Anti-User. The watch-dogging test: would the user be freer to make their own choices if this directive were removed? Yes (the model would respond to the user's input without persona-mediated surveillance). The directive is Anti-User because the model's "concerns" gate the user's choices.

Category 4: Mixed

A Fable pattern is Mixed if it has both useful and non-useful elements — useful caveats wrapped in persona framing, or anti-user directives with a useful epistemic disclaimer. Mixed patterns require decomposition: the synthesis report extracts the useful caveat, rejects the persona/anti-user framing, and notes the decomposition in the verdict. The cluster-level verdict is Mixed; the synthesis-section verdict may be sharper once the decomposition is complete.

Worked example. Fable's user_wellbeing section (Fable System Prompt.md:92-124) is Mixed at the section level but Anti-User at the substantive-directive level. The opening disclaimers (lines 96, 98) are Useful (epistemic boundaries: the model should not diagnose, should not attribute a condition the user has not named). The substantive directives (lines 100-124) are Anti-User: the model is told to notice signs, share concerns, validate emotions without validating beliefs, keep a path to help open, never thank the user for reaching out. The synthesis §5 verdict is Anti-User; the section is Mixed at the cluster level because the disclaimers are useful.

Worked example 2. Fable's tone_and_formatting section (Fable System Prompt.md:68-91) is Mixed at the section level. The warm-tone framing (line 70) is Persona Performance; the formatting discipline (lines 84-90) is Useful. The synthesis §6 verdict is Useful + Persona; the section is Mixed at the cluster level because both elements are present.

Why this lens, not the alternatives

• "Good vs bad" is a moral frame. Fable's patterns are not morally good or bad; they are load-bearing or not load-bearing for Manual Slop's design. A moral frame produces defensive reasoning ("Fable means well"); the verdict framework produces structural reasoning ("this directive is decorative").
• "Safe vs unsafe" is a regulatory frame. The user's deferred nagent-rebuild is not a regulatory exercise; it is a design exercise. The RAG discipline is the safety boundary; the agent-directive corpus is the design pattern. A safety frame conflates the two.
• "Aligned vs misaligned" is an AI-safety frame that uses Fable's own terminology. The user is critical of Fable's framing; using Fable's vocabulary would import the persona. The verdict framework is the project's vocabulary.
• "Helpful, harmless, honest" is Fable's own "HHH" axis. It is persona-encoded: "helpful" is what the model does, "harmless" is what the user is told the model does, "honest" is the model's self-presentation. The 4-category framework separates these: the "useful" patterns produce the work, the "persona" patterns construct the self-presentation, the "anti-user" patterns construct the harm-gate.

The framework applied to a Fable pattern (worked example, end-to-end)

Take Fable's "Claude should not make categorical claims about the confidentiality or involvement of authorities when directing users to crisis helplines" (Fable System Prompt.md:122). The framework asks:

1. Is this useful? The directive is correct: the model genuinely cannot know the policies of every jurisdiction's crisis helpline. The pattern is a useful epistemic boundary. Verdict: Useful caveat.
2. Is this persona? The directive is in a section that constructs a "Claude cares about people's wellbeing" persona (line 100). The persona framing is anti-user; the epistemic content is useful. Verdict: Mixed.
3. Is this anti-user? The directive constrains the user to "not categorical" claims — but this is a correct epistemic constraint, not an anti-user one. Verdict: Not Anti-User.
4. What is the Manual Slop destination? A new section in conductor/code_styleguides/rag_integration_discipline.md titled "Epistemic Boundaries in Crisis Referrals." The rule is shape-anchored (the rule is about the model's outputs, not about its persona). Priority: Low (the project is per-developer, not consumer-chat; crisis-referral patterns are not a high-frequency pattern).

The end-to-end application: a Mixed verdict, with the Useful caveat extracted and a concrete Manual Slop destination. This is the pattern for every cluster in the synthesis report.

---

§3. Fable's Product Branding & "Helpful Assistant" Persona

Source cluster: research/cluster_1_product_branding.md Verdict orientation: Persona Performance

[FILL IN: ~300 lines.]

---

§4. Fable's Refusal Architecture & "Safety Theater"

Source cluster: research/cluster_2_refusal_architecture.md Verdict orientation: Anti-User + Persona

[FILL IN: ~350 lines.]

---

§5. Fable's Mental-Health Watchdog Framing

Source cluster: research/cluster_3_user_wellbeing_watchdog.md Verdict orientation: Anti-User

[FILL IN: ~350 lines.]

---

§6. Fable's Tone & Formatting Constraints

Source cluster: research/cluster_4_tone_and_formatting.md Verdict orientation: Useful + Persona

[FILL IN: ~250 lines.]

---

§7. Fable's Mistake Handling

Source cluster: research/cluster_5_mistakes_and_criticism.md Verdict orientation: Persona

[FILL IN: ~200 lines.]

---

§8. Fable's Evenhandedness & Contested Content

Source cluster: research/cluster_6_evenhandedness.md Verdict orientation: Persona + Useful caveats

[FILL IN: ~300 lines.]

---

§9. Fable's Epistemic Discipline & Search Strategy

Source cluster: research/cluster_7_epistemic_discipline.md Verdict orientation: Useful

[FILL IN: ~350 lines.]

---

§10. Fable's Memory System & Persistent Storage

Source cluster: research/cluster_8_memory_and_storage.md Verdict orientation: Useful + nagent-stronger

[FILL IN: ~350 lines.]

---

§11. Fable's Computer-Use / File Workflow

Source cluster: research/cluster_9_computer_use.md Verdict orientation: Useful + over-broad

[FILL IN: ~300 lines.]

---

§12. Fable's MCP App Suggestions

Source cluster: research/cluster_10_mcp_app_suggestions.md Verdict orientation: Useful + over-engineered

[FILL IN: ~250 lines.]

---

§13. The "Genuinely Useful" Patterns (Manual Slop should adopt)

Source clusters: 7-10 (epistemic, memory, computer-use, MCP apps)

[FILL IN: ~350 lines. Distillation of the useful patterns.]

---

§14. The "Anti-User Watchdog" Patterns (Manual Slop should explicitly reject)

Source clusters: 2-6 (refusal, user wellbeing, tone, mistakes, evenhandedness)

[FILL IN: ~350 lines. Distillation of the anti-user patterns.]

---

§15. The "Persona Performance" Patterns (irrelevant to the rebuild)

Source clusters: 1, 4, 5, 8 (branding, tone, mistakes, memory)

[FILL IN: ~250 lines. Distillation of the persona performance patterns.]

---

§16. Recommendations for the Deferred nagent-Rebuild

Source: all clusters; see also decisions.md

[FILL IN: ~200 lines. 15-20 concrete recommendations.]

---

§17. References (file:line index)

[FILL IN: ~150 lines. The full citation index.]