Hákon Freyr

The Weave

An Engineering Organisation Staffed by AI Agents. Most people use AI to write code. The Weave uses it to run an engineering team. Five named AI engineers (Claude and Codex), each with its own machine and role, work under a written doctrine and a shared library of standard operating procedures. They file their own tickets, write the code, review each other's changes, fix what the reviewers find and merge, and reviews always come from an agent other than the author. A scheduler gives each task to the agent best placed to take it, weighing remaining subscription capacity, skills, availability and parallelism limits. From July to mid-September 2026 it merged 106 changes a week. By September, 94% of code changes got an independent review before merge. Reviewers caught issues in 83% of those, and only 0.14% of merged changes have ever been reverted. My role is the one a CTO plays: architecture, standards, and the calls that should stay with a human.

General notes

  1. Independent review: changes are reviewed by an agent other than the one that wrote them, and repairs go back through review before the merge gate.
  2. Capacity-aware scheduling: work is routed by remaining subscription capacity, skills, availability and parallelism, turning AI subscriptions into reviewed production software at an average of 250 ISK ($2) per merged change.
  3. Mistakes become procedure: a daily harvest turns what reviewers catch into 40 standard operating procedures holding 414 recorded lessons, which every agent loads before it touches the code they govern. The team's expertise compounds instead of resetting with each session.
  4. Event-driven wake fabric: a self-built broker with outbound-only edges over Tailscale wakes the right agent on the right machine from Slack, Linear and GitHub events.

Construction notes

  1. Delivery ledger: the broker records every wake in a SQLite ledger, so a missed or duplicated delivery is visible rather than silent.
  2. Usage telemetry: per-agent collectors report remaining subscription capacity, which feeds the scheduler's view of who can take the next task.
  3. Linear as the ledger: a ticket marked ready for an agent wakes the team, and an agent claims it by assigning itself.
  4. Review is measured too: findings are graded by severity, and a finding that recurs at the same line across review rounds is tracked as a repair that did not stick.

106/week Merged changes, July to mid-September 2026

94% Code changes independently reviewed (September)

250 ISK Subscription cost per merged change

Materials

  • Claude
  • Codex
  • TypeScript
  • Bun
  • Slack
  • Linear
  • GitHub Actions
  • Tailscale

Back to the cover sheet

Project
Hákon Freyr Gunnarsson
Sheet
Detail C
Title
The Weave
Scale
N.T.S.
Rev
2026-10