Vega
Reads the system, checks real websites, and decides what's worth building next.
How CRTC AI builds · a true story
CRTC AI doesn't build with one chatbot. It runs a crew of five AI specialists — a system we call STARSHIP — that plan, build, and check each other through the night. Here's one real shift. Every number on this page links to a record.
Five agents, each a different AI model, each with one job. The score next to each is its real track record from that shift — and yes, one of them is supposed to look bad.
Reads the system, checks real websites, and decides what's worth building next.
Writes the code and its tests, and repairs its own failures up to twice before giving up.
Never builds. Re-runs every delivered build in a sandbox, re-checks its evidence, and tries to break it. Fails things on purpose.
Tracks what every shift costs, what's real revenue, and keeps projections clearly labeled as guesses.
Inspects the system at clock-in and writes the handoff and next-shift plan at clock-out.
Overnight, November 4, 2026. 8 hours. Budget 50 cents of cloud AI (it ran 3 cents over, on credit we already pay for).
Read the system and three real local websites, then picked work worth doing.
Built a roofing estimate calculator and a water-heater sizer — real tools, with their own tests.
Re-ran both builds in a clean sandbox, re-hashed the evidence. Both passed.
A third build looked fine — but Argus found its tests missed a planted bug (a <= that should have been <). Failed it. It never shipped.
Wrote the handoff and queued the next shift's work. 112 events, all recorded in a tamper-proof log.

The same system runs on one laptop in Mount Pleasant. That morning, it lost power.
When it came back, 32 of its 33 services restarted on their own. The one that didn't, the AI diagnosed and fixed — and wrote itself a fix so the same thing can't break it again. We know because the recovery is logged: git intact, all 18 databases checked clean, 242 tests passing.