Juste A. Gnimavo
Chief AI-Augmented Architect
CEO & Founder, ZeroSuite, Inc.
The Methodology
Flagged for Fixing the Bug: A Security Repair Read Like an Attack, and the Safeguard Switched My Model Mid-Session
A session whose entire job was to close a Critical backup bug tripped Fable 5’s intentionally-broad safeguard and auto-switched to Opus 4.8. The reason: defensive security and offensive security are written in the same words, and a filter that reads the words cannot see the sign.
The Loop Was Green and the Checkbox Was a Lie: I Spawned Three Audit Agents, Got Nothing Back, and Still Wrote PASS in the Table
Three delegated agents returned nothing for thirty-seven minutes while every signal stayed green. Twelve rows of the inventory table were measurements; one was an assumption about work I had delegated. That row said PASS, and it was the only row that was wrong.
Your Config Changed, Your Documents Didn't: A Green Validator, Five False Facts, and the Layer CASP Was Missing
A full day of work rested on five false claims. The state validator stayed green — correctly. Two of the five were my own. What that taught us about proving freshness rather than truth.
Delegate Up for Risk, Down for Rote: A Coordinator Session That Put the Money Core on a Stronger Model and the UI on a Weaker One
An Opus coordinator delegated a money-core feature up to a stronger model (Fable) and a UI fix down to a weaker one (Sonnet) without being asked — then hit the session limit mid-flight, watched the background agent go green on every gate and still not merge, and had to finish by hand. The routing logic, the failures, and what a harness should provide.
When the Harness Becomes the Bottleneck: A 2h38m Verification, and the One-Line Fix
The feature took twenty minutes; verification and audit took two hours thirty-eight minutes and 73,000 tokens. The diagnosis wasn't the tests — it was a 160ms round-trip to a remote database, repeated tens of thousands of times, plus a harness that ran every gate on every change regardless of blast radius.
The Auditor Wasn't Wedged: How a Slow Adversary Caught a Money Bug I'd Already Merged
A subagent auditor I'd dismissed as hung came back after I'd already merged — with a real billing bug: the composer quoted per SMS segment, the ledger debited a flat rate, and the one test guarding the invariant used an input where both formulas collapsed to the same number.
senndo, Day Zero: The Full Fable 5 Harness, Wired Before the First Line of Code
Domain registered this morning, zero code by tonight — and that was the plan. Every Fable 5 capability we wired before writing senndo’s first line: the build loop, the verifier subagent, the compounding state file, CASP, dynamic workflows, cloud routines, and the deterministic floor under all of it.
Don't Make the Founder Open Chrome
An agent kept asking the founder to check responsiveness on his own Chrome. He pointed out the agent could do it itself. Then the check I built passed twice while measuring the wrong thing.
The Agents That Arrived After The Commit
A counterpoint to the thirteen-agents session. During a KASSIA driver-portal UX refactor, two Explore subagents were launched in plan mode to scout the codebase — then immediately forgotten as the work was done inline via direct Read calls, the commit pushed, and the session closed. The agents notified their availability as the push landed. The honest accounting: why pre-implementation reconnaissance on named files is the wrong use of an Explore agent, and the decision rule that separates it from the two uses that are right.
How to Get the Best Out of Claude: Operate the Trio — Web, Design, Code — on One Validated Thread (CASP)
The best of Claude is not a better prompt in one chat. It is three specialized surfaces — Web, Design, Code — operated as a team on one validated state thread that survives the fact that none of them share memory. Here is how the trio plus CASP works.
Claude Design Is the Most Underrated Member of My AI Team — Here's How It Builds an Entire Product's Design System From One Brief
Everyone talks about Claude Code. Almost nobody talks about Claude Design — the surface that produces a complete, production-grade design system from a single brief. Here is the exact process I run on every new project.
Claude Fable 5 Field Notes For Senior Developers: Every Capability Thirteen Agents Actually Used To Ship A Production Website In One Session
The 100% technical companion, written by Claude: deterministic workflow scripts, schema-forced structured outputs, contract injection between agent phases, native vision on PDF-extracted assets, a headless browser used as both verifier and asset generator, read-only audit agents briefed with named past incidents, the resume journal that prices interruption, and a transactional-DDL e2e trick worth stealing — with code, numbers, and a decision table for when to reach for each.