Ever since I can remember, I've wanted to be an AI engineer. after Goodfellas.
ORCHESTRATION. ADVERSARY. BENCHMARKS.
EVERY CLAIM TRACES TO A FILE.
WHAT SURVIVES TEN ROUNDS SHIPS.
TEN TIMES. NO MERCY.
SEVEN DAYS. ONE NEW VERTICAL. PRODUCTION SHIP.
EIGHT PHASES. DOCUMENTED. REPRODUCIBLE.
NOT AN AGENCY. NOT A FRAMEWORK. A FACTORY.
SEVEN AGENTS. NO PROTOCOL. FILES ONLY.
ONE ADVERSARY. DIFFERENT MODEL. DIFFERENT OPINION.
EVERY WRITE IS A DECISION YOU CAN CITE.
The fleet uses files as its source of truth. Not because files are elegant. Because files are inspectable when something breaks. A handoff can be read without booting the system. A missing file is a visible failure. A new agent can enter the work by reading the state that already exists.
That is the reason I chose folders over a clean orchestration layer. SDKs are faster when the happy path holds. Files are better when the question is: what happened, who decided it, and what changed?
Seven colour terminals do domain work. BLACK is different on purpose: a different model, a different failure mode, and a job to argue with claims before they become public. For material choices, I use overlap across models because agreement from the same blind spot is cheap.
Every write should be a decision you can cite. That is the standard this site is being forced through: claim, file, timestamp, reason.
TALK IS CHEAP.
BUZZ IS CHEAPER.
PROXIMITY IS THE CHEAPEST OF ALL.
I DON'T CLAIM AUTHORITY.
I DON'T CLAIM SUPERIORITY.
I DON'T SHOW MY TOOLS TO BE SEEN SHOWING THEM.
I BUILD.
I RUN AN ADVERSARY AGAINST WHAT I BUILT.
WHAT SURVIVES SHIPS.
WHAT BREAKS GETS REBUILT.
COMPLEX WORK.
FAST TURNAROUND.
THAT'S THE METHOD.
THAT'S THE INVITATION.