About
I ship with agents, and I answer for the code produced.
I design and ship production applications by orchestrating coding agents: specification, parallelisation, review and hardening.
Background
I design and ship production applications by orchestrating coding agents. The work runs in four stages: specify, orchestrate, verify, ship. Agents speed up execution; the specification and the review stay mine.
The method comes from the tooling I built for myself: SupraCortex, local-first project memory for coding agents; SupraSpace, a local command centre for coding CLIs; FlowFactory, an experiment in generating n8n workflows.
The base remains production: the Procure-to-Pay module of SEMS at E-Solution since August 2024, with Laravel, GitLab CI/CD and Docker, after an internship on fleet-management submodules from February to July 2024. I use Laravel, Node.js or React when they are the right tool, never as an argument in themselves.
Method
Specify, orchestrate, verify, ship.
Specify
Contracts, acceptance criteria and edge cases are written before the first line. The spec serves both the agents and the review.
Orchestrate
Agents work in parallel on disjoint scopes, with shared project memory and a review at every step.
Verify
Architecture, security and data integrity are reviewed, and tests pass in CI before every integration.
Ship
CI/CD pipelines, Docker environments and handover documentation, so another team can carry on.
Why this is different
Why this is different
- One spec that both agents and humans follow.
- Agents parallelised on disjoint scopes.
- Every merge is reviewed and tested.
- Specification
- Contracts · acceptance criteria · edge cases
- Orchestration
- Claude Code · Codex · OpenCode · MCP
- Review
- Architecture · security · tests · CI
- Shipping
- GitLab CI/CD · Docker · observability
StackLaravel · PHP · Node.js · React · Next.js · TypeScript · Tailwind · Supabase · SQLite · Docker · GitLab CI
The CV details experience, education and technical skills.