> Each rule below is enforced mechanically by the skill, not left to vibes.
> R1. Repo docs are the memory; not in HANDOFF.md = didn't happen
SKILL.md:
> Not in docs/HANDOFF.md = didn't happen. Refuse to judge results that exist only in conversation or builder chat output.
"Mechnical enforcement" just means "prompting the LLM a bit extra" these days? It (still) amazes me how much effort and tokens we expend on what could and should be a two line script...
Denvercoder9
Reduce Fable tokens by 80%, simply by not using it!
> I am fairly convinced this is the shape serious agent work keeps converging toward.
"this" being "plan with expensive model, implement with cheap model".
Anyone who follows HN would be hard-pressed to disagree; this architecture is re-invented twice monthly.
> Not because it is aesthetically pleasing. Because every other shape eventually runs into the same boring failures: context rot, self-grading, goalpost drift, and merge chaos.
Actual failure isn't boring. But struggling through a generated software project that celebrates its own genius and doesn't have a single self-critical or genuinely reflective thing to say...at least watching paint dry I might get giddy off the fumes.
I'm not interested in critiquing the project itself, either, you'll just run that through a model, too.
mpalmer
> freezes the gates
LLM-written readmes love to use inscrutable jargon that means nothing outside of the context window that birthed it.
Retr0id
US Govt reduces Fable Tokens by 100%.
Teknomadix
I actually just started doing this by having Fable roleplay as Jeff Dean and to use Codex as Sanjay driving the implementation and have them go back and forth. Works really well and it’s cool to see AI pair program
rockwotj
Fable will do this itself, by spawning Opus/Sonnet subagents to do easy work.
felixgallo
@DanMcInerney Thank you for sharing this! Using a larger model for planning and a cheaper, smaller model for execution is a smart way to save tokens and seems like the way to go in general.
I wanted to see what would happen if Claude delegated work to pi wiht a model like Deepseek, so I forked your repo and tried it out. It's working really well so far.
https://github.com/pcomans/architect-loop-pi
You can use any agent and/or model for each step and share context between them.
cohix
yes I'm using Fable to inspect, generate plan and architectural docs then using Gemini to implement then have Fable review, find bugs. saving lots of usage.
comments (10)
> Each rule below is enforced mechanically by the skill, not left to vibes.
> R1. Repo docs are the memory; not in HANDOFF.md = didn't happen
SKILL.md:
> Not in docs/HANDOFF.md = didn't happen. Refuse to judge results that exist only in conversation or builder chat output.
"Mechnical enforcement" just means "prompting the LLM a bit extra" these days? It (still) amazes me how much effort and tokens we expend on what could and should be a two line script...
Denvercoder9
> I am fairly convinced this is the shape serious agent work keeps converging toward.
"this" being "plan with expensive model, implement with cheap model".
Anyone who follows HN would be hard-pressed to disagree; this architecture is re-invented twice monthly.
https://www.facebook.com/groups/vibecodinglife/posts/1946207... https://github.com/openai/codex/discussions/10628 https://build5nines.com/stop-burning-premium-requests-how-to...
> Not because it is aesthetically pleasing. Because every other shape eventually runs into the same boring failures: context rot, self-grading, goalpost drift, and merge chaos.
Actual failure isn't boring. But struggling through a generated software project that celebrates its own genius and doesn't have a single self-critical or genuinely reflective thing to say...at least watching paint dry I might get giddy off the fumes.
I'm not interested in critiquing the project itself, either, you'll just run that through a model, too.
mpalmer
LLM-written readmes love to use inscrutable jargon that means nothing outside of the context window that birthed it.
Retr0id
Teknomadix
rockwotj
felixgallo
I wanted to see what would happen if Claude delegated work to pi wiht a model like Deepseek, so I forked your repo and tried it out. It's working really well so far. https://github.com/pcomans/architect-loop-pi
phpp
corvad
You can use any agent and/or model for each step and share context between them.
cohix
diavelguru