Proof
Numbers you can check yourself
Every figure on this page comes from two verifiable sources: the git history of the public canon repo, and the artefact manifest this site is generated from. Clone the repo and count — the point of the page is that you can.
From the canon repo
The system, by the numbers
128
days in production
388
pull requests merged into the canon repo — most opened by Forge, reviewed by Prism
436
commits since the first on the repo
154
canon artefacts published
62
skills
34
scheduled tasks and routines
16
agents and operators
38
governance artefacts
Repo history from assoc-one/claude-ops, first commit 2026-06-03, last published 2026-10-09. Counts regenerated on every site build — nothing on this page is typed in by hand.
Across the estate
The whole system, not just its rulebook
The canon repo above is where the system improves itself. These numbers add the delivery repos — the products, sites, and storefronts the agents build against. Agent-built work is counted by the documented convention: pull requests opened from claude/ branches.
870
commits across the estate
729
pull requests merged
687
of them opened by agents
claude-ops
canon — the operating layer
436
421
416
careeros-web
delivery
98
2
2
meirionpritchard-com
delivery
227
216
210
aledpritchard-com
delivery
39
35
6
assoc-one
delivery
8
7
7
mbn-theme
delivery
28
25
23
fitness
delivery
29
19
19
luna
delivery
5
4
4
Where the effort goes
Running the system vs shipping the work
Each bar splits a month's merged pull requests between the operating layer (the system tightening its own rules) and delivery (software shipped). Early months lean heavily towards the system building itself — that is what standing something up looks like. The number to watch is the balance shifting towards delivery as the rules stop needing repair. It is published either way.
The scheduled layer
What runs without being asked
The cadence of a team, reproduced on a clock. Morning briefs, triage passes, pipeline sweeps, weekly planning, a retro that drains observed friction into system improvements — each one a thin scheduled loader over a canon artefact you can read.
task-a1-operator-loop
Weekly thin loader that runs skill-operating-loop in the context of the A1 vertical — the Association of One practice plus its live client engagements — on behalf of operator-a1
.mdtask-a1-operator-standup
Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the A1 vertical on behalf of operator-a1, feeding Aled's 09:00 stand-up
.mdtask-aide-loop
Weekly thin loader that runs Aide's attention loop on behalf of agent-aide — sweep the committed cycle for what needs Aled, allocate the week, and propose calendar holds inside his declared hold windows
.mdtask-apps-operator-loop
Weekly thin loader that runs the operating loop for the Apps accelerator on behalf of operator-apps — a portfolio, so the decide-step is allocation across bets (skill-portfolio-allocation), not driving one goal
.mdtask-apps-operator-standup
Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the Apps accelerator on behalf of operator-apps, feeding Aled's 09:00 stand-up
.mdtask-bara-operator-loop
Weekly thin loader that runs skill-operating-loop in the context of the BARA vertical, on behalf of operator-bara
.mdtask-bara-operator-standup
Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the BARA vertical on behalf of operator-bara, feeding Aled's 09:00 stand-up
.mdtask-bottrader-operator-loop
Weekly thin loader that runs skill-operating-loop in the context of the bot.Trader vertical, on behalf of operator-bottrader
.mdtask-bottrader-operator-standup
Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the bot.Trader vertical on behalf of operator-bottrader, feeding Aled's 09:00 stand-up
.mdtask-bottrader-watch
Daily sensor for the bot.Trader runtime, on behalf of operator-bottrader — reads the health digest the GitHub Actions decision cycle publishes outbound (heartbeat outcome and the guard's own last-write timestamp, dail…
.mdtask-content-drain
Weekly Mr Pritchard content qualify pass — works through the new captures (decisions, moments, breakthroughs, opinions) and asks of each "what is this, and is it worth publishing?" Worth it → flesh into a stated posit…
.mdtask-content-review
Monthly Mr Pritchard capture review — sweeps the parked captures the weekly qualify pass set aside and asks whether they now cluster, by theme, into something shareable that no single one was on its own
.mdtask-coordinate
Scheduled deployment of skill-coordinate — the Relay (R3-LAY) cross-board PM coordination pass
.mdtask-cycle-planning
The cycle-boundary ceremony, run as a scheduled task — retro the closing cycle, roll over incomplete work, and propose the next cycle's commit and its one goal, with Aled the gate on cycle membership and goal
.mdtask-daily-report
Morning brief on delivery work — an agnostic status-and-progress report over active work only, posted as one short Linear project status update per live project with an explicit health flag, so projects carry the dail…
.mdtask-fleet-dispatch
Scheduled deployment of skill-fleet-dispatch — sweeps Todo across delivery projects for tickets owned by the connector-surface fleet (Pixel, Reach, Sonar, Scout, Aide) and runs each via skill-dispatch-run
.mdtask-goal-review
Scheduled deployment of skill-goal-review — the periodic read of progress against the outcome-initiatives and their KPIs across every venture
.mdtask-health
Scheduled deployment of skill-task-health — the Pulse health check on the scheduled layer (behaviour, deployment parity, config parity)
.mdtask-mrp-operator-loop
Weekly thin loader that runs skill-operating-loop in the context of the Mr Pritchard editorial vertical, on behalf of operator-mrp
.mdtask-mrp-operator-standup
Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the Mr Pritchard editorial vertical on behalf of operator-mrp, feeding Aled's 09:00 stand-up
.mdtask-optimisation-review
Scheduled deployment of skill-optimisation-review — the periodic Pulse review of tooling conventions, operating shape, and the model-and-schedule efficiency of the scheduled layer
.mdtask-owner-standup
Relay's weekday consolidation of the five operator stand-ups into the one 09:00–09:30 stand-up Aled attends
.mdtask-pipeline-graduation
Pipeline graduation (Scout) — promote surfaced:* Network contacts into the right opportunity funnel (Roles/Advisory/Pitches), link back, mark surfaced:done
.mdtask-pipeline-qualify
Scheduled deployment of skill-pipeline-qualify (Scout) — qualify Pipeline Backlog tickets to Ready
.mdtask-pipeline-sweep
Scheduled deployment of the Gmail→Pipeline sweep (Scout) — runs skill-pipeline-sweep once per intake (network, recruiters, roles, advisory)
.mdtask-platform-watch
Monthly Pulse scan for newly-shipped platform capability the fleet could adopt — Claude Code and Agent SDK release notes only — filing a propose-only FRICTION note to the Pulse queue for each feature worth assessing,…
.mdtask-pulse-refine
Scheduled deployment of skill-ops-retro's refine pass — the first of the two daily Pulse-retro passes, and the one that owns every read and judgement call
.mdtask-pulse-retro
Scheduled deployment of skill-ops-retro's author pass — the second of the two daily Pulse-retro passes, and the one that only produces and presents
.mdtask-strategy-review
Weekly Atlas strategy review — sweeps every venture's outcome-initiative for a complete strategy (purpose, objectives, KPI tree with baselines and targets) and for drift, and raises a surfaced gap ticket to Aled for e…
.mdroutine-feasibility-loop
Driver routine for bot.Trader Mandate A's feasibility pipeline — grinds every ready Phase-2b feasibility-study ticket in one operator-triggered batch, composing skill-feasibility-study per ticket: fetch real venue dat…
.mdHonesty note
What these numbers do and don't say
The canon repo is public — those numbers you can verify commit by commit. The delivery repos are private client and product codebases, so their counts are summarised here, pulled from the GitHub API on every build rather than typed in. The artefact counts include work at every status: most is in use, some is drafted, a little is proposed and says so on its card.
One number that matters isn't on this page: the hours of operator attention the system frees each week. It isn't measured precisely yet, so it isn't claimed. When it is, it will be.