Skip to content

Add Fugu orchestration evaluation and design rationale#8

Open
jhave wants to merge 2 commits into
mainfrom
claude/narracode-fugu-optimization-5zid2g
Open

Add Fugu orchestration evaluation and design rationale#8
jhave wants to merge 2 commits into
mainfrom
claude/narracode-fugu-optimization-5zid2g

Conversation

@jhave

@jhave jhave commented Jun 28, 2026

Copy link
Copy Markdown
Owner

Summary

This PR adds two new documents to the Narracode project: a detailed technical evaluation of Sakana AI's Fugu orchestration model and an accompanying essay explaining why Fugu-style enhancements would not improve Narracode's literary harness.

Changes

  • plans/2026-06-28_fugu-orchestration-evaluation-and-routing-proposal.md: A comprehensive technical proposal evaluating Fugu's applicability to Narracode. The document:

    • Explains what Fugu is (a learned orchestrator that routes tasks across frontier models)
    • Identifies the structural rhyme between Fugu's Thinker/Worker/Verifier roles and Narracode's existing Initiator/Compositional/Reflexive passes
    • Separates what transfers (routing tables, role vocabulary, multi-model draft forks, recursive verification) from what must be refused (output synthesis, learned-reward coordination, emergent scaffolds)
    • Proposes concrete, minimal edits to narracode.md to formalize routing as a first-class, auditable decision
    • Recommends adopting Fugu's routing discipline while explicitly refusing its synthesis and optimization mechanisms
  • 2026-06-28_fugu-orchestration-consideration.html: A public-facing essay articulating the design philosophy behind the rejection. The essay:

    • Argues that Fugu's headline features (synthesis, learned coordination) are precisely what Narracode must refuse to preserve literary voice
    • Explains that model choice is an irreducibly subjective aesthetic judgment, not a reward function
    • Warns that routing tables become maintenance liabilities as models change seasonally
    • Identifies context rot as the cost of orchestration complexity
    • Concludes that the enhancement is restraint—declining to enhance is the most literary choice

Notable Details

The evaluation is grounded in the principle that Fugu optimizes against verifiable objectives (SWE-Bench, GPQA) while Narracode exists precisely because prose that scores highest on automatic metrics is the failure mode. The proposal preserves Narracode's core commitment: keeping the human prompter's aesthetic judgment as the irreducible decision point, while making routing transparent and auditable rather than hidden or learned.

The HTML essay is styled for publication on glia.ca and includes proper attribution, funding acknowledgments, and Creative Commons licensing.

https://claude.ai/code/session_01Mxqax7CCW9RZ59pHEshZvq

claude added 2 commits June 28, 2026 13:55
Evaluate Sakana Fugu's orchestration-as-a-model against Narracode's
harness. Maps Fugu's Thinker/Worker/Verifier triad and swappable
multi-provider routing onto Narracode's existing AUTO_MODE model
assignment, and proposes a "local Fugu" dispatcher that routes each
pass to Claude/Gemini/GPT via API. Critically refuses Fugu's output
synthesis and learned-reward coordination as median-collapse hazards,
following the house "what transfers / what doesn't" pattern.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mxqax7CCW9RZ59pHEshZvq
…rracode

Standalone Glia-styled page (Narracode logo + Glia footer/bio/funding/
license) arguing against bolting Fugu-style orchestration onto the
harness: routing tables rot as models churn; model choice is an
irreducibly subjective aesthetic judgment, not a reward function;
orchestration adds complexity and worsens context rot; and platforms
already enhance prompts toward the median the harness exists to refuse.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mxqax7CCW9RZ59pHEshZvq
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants