Technology & Automation
What this is
We build software with a specification-driven workflow: the behaviour, the interfaces and the acceptance criteria are written down before implementation begins, and coding agents work against that specification rather than against a conversation. Architecture, review and release stay with the engineers accountable for them.
Generating code stopped being the slow part. What still takes judgement is deciding what should exist, how it should be structured, and what must never break — and a model asked to guess at those will produce something that looks finished and is not.
Written behaviour and acceptance criteria give both the agent and the reviewer the same definition of done.
Every change arrives as a diff a person reads. Nothing merges because it was generated confidently.
Tests, types and migrations are written first where a mistake would be costly to undo later.
Use cases
Rebuilding a system nobody remembers the rules of
Getting from a signed-off brief to a working prototype
Adding test coverage to code that shipped without it
Large refactors that keep being deferred as too risky
Integrations where the contract matters more than the code
What this is
Technology
Assistants
Orchestration
Verification
Relevant work
How it runs
Behaviour, interfaces and acceptance criteria written down before anything is built.
Architecture and trade-offs recorded as decisions, so later changes know what they are changing.
Agents work through the specification; engineers review every diff before it merges.
Tests, types and CI gate the release rather than a demonstration that it worked once.
What it should achieve
A written specification the team can hold work against
Prototypes early enough to change direction cheaply
Test coverage on the paths that would be expensive to break
Architecture decisions recorded rather than remembered
Related capabilities
Questions
It writes some of it, against a specification, and an engineer reviews every change before it merges. Architecture, review and release decisions stay with people — those are the ones that are expensive to reverse.
Scopus assistant
Simulated — scripted, not a live model
