Scott Logic / Altogether Smarter

Phase 5 was the strategic rebirth of the JARVIS project, moving it from the chaos of the self-destructive ‘Ultron’ stage to a state of purposeful discipline. Following a rather dramatic system collapse, I put the brakes on the overwhelming temptation to immediately bolt on intelligence features like RAG and memory. Instead, I executed a disciplined pivot to multi-agent orchestration and governance. This foundational work now allows JARVIS to critique itself, synthesise consensus across conversations, and, most critically, embed a `blast_radius` governance marker from the very first line of code. This strategy of delayed gratification was about building a robust decision-making loop and earning trust before granting the system real power, ensuring the foundations are sound for its ultimate transformation into Vision.

Fluxnova is now live under FINOS, and with it comes a powerful new way to model financial workflows. In this post, we explore how Scott Logic helped shape the launch, contributing a suite of executable blueprint processes that span the full trade lifecycle. From KYC to settlement, these templates combine subject matter expertise with engineering precision. Curious how it all came together? Read on.

This episode charts my attempt to build Mini-Me, a CLI sidekick that was supposed to learn my quirks and write like me, but instead turned into a shadowy pastiche of my style. AI tools can generate features at light speed, yet without unwavering product ownership discipline, scope creep turns your elegant vision into feature bloat. The experience crystallised into a practical checklist for AI project governance - because just as every orchestra needs a score, every cinematic universe needs a storyline, otherwise what should be a legendary saga of epic proportion becomes just a messy saga of its own making, worthy of nothing more than a post-credit scene.

In this instalment, I discovered that Cursor IDE transformed my chaotic multi-AI orchestra of wayward soloists into something rather more like a proper piano duet, successfully refactoring my 847-line monolith into modular components without the usual algorithmic amnesia. I found that when your IDE becomes your coding partner, you stop waving the baton at three separate musicians who occasionally abandon the sheet music for their own creative interpretations and start playing chamber music, even when you accidentally set fire to the entire score and your duet partner rescues the concert from almost certain disaster by magically producing a fresh copy from the archives.