Skip to content

the organism/energy

08

the Metabolism.

Energy. Tokens are calories: it burns them to work, meters every one, and prices the whole ledger.

the challenge

79%

79% of enterprises overran their AI budget in the last 12 months, and only 15% can calculate their AI ROI.

DoiT, AI Spend Reality Check (Sapio Research), 2026

The AI bill keeps climbing, and no one can say what it bought.

Every model call costs money, but the cost arrives as one lump vendor invoice at the end of the month. There is no line-item, no way to tie a dollar to the work that spent it, and no early warning when a run goes hot. So budgets overrun and the return stays a guess.

95%

95% of organizations are getting zero return on their generative AI investment.

MIT Project NANDA, preliminary findings (not peer-reviewed), 2025

where today falls short

A vendor invoice is a total. It is not a meter.

Renting AI gives you a number at the end of the month, not visibility during it. You cannot see which model, which task, or which run spent the money, so you cannot catch a runaway before it lands or calculate the return after. And when a part of the system quietly drifts out of health, nothing is watching to notice.

The cell's power plant

Burn fuel, count every unit.

A mitochondrionThe cell's power plant: it burns fuel into ATP, the energy every other process spends. burns fuel into ATPATP (adenosine triphosphate): the molecule a cell spends as energy, made by burning fuel., the single unit of energy every other process spends, and nothing in the cell runs without drawing on it. The Metabolism runs the organism the same way. Every token is a calorie: spent to do work, counted as it burns, and priced per model, so the cost of the work is never a mystery on a monthly invoice. The diagram below meters a single burn.

Line-engraving of a mitochondrion in cross-section, showing the folded inner membrane (cristae); the cell's power plant

the answer

Tokens are calories. It meters every one and prices the whole ledger.

The organism treats compute as energy. Every unit of work burns tokens, and each token is counted the moment it is spent and priced at its own model rate into a running ledger. The bill is not a surprise at month end; it is a live meter you can read, trace to the exact work, and cap. And the same telemetry that watches the burn watches the organism, so a part that drifts out of health is healed before it becomes an outage.

One unit of work: burned, metered, and priced into the ledger.
🌶️burns tokensto do worktokensthe Metercountingcounts + pricesper model, per token$a priced ledgertriage inboxopus · $0.19summarizegpt-4o · $0.02review a PRsonnet · $0.05draft a replygemini · $0.03metered, on the record

A cell burns a burst of tokens to do a piece of work. Each token is counted as it is spent, priced at that model rate, and appended to a running ledger. The meter is live, not a monthly surprise. Token counts here are illustrative of the mechanism; the real totals are in the record below.

more than a bill

What a metered organism has that a monthly invoice does not.

A lump-sum invoice tells you what you spent. A metabolism tells you what you spent it on, watches it as it happens, and keeps itself healthy while it runs.

01

Every model is metered at its own rate.

!Today A lone vendor bill is one opaque total. You cannot see which model or which task spent what.

the cell Each call is counted at the token level and priced at that engine rate, then written as a ledger line tied to the work. Swap the model underneath and the meter tracks the new rate.

a priced usage ledger, per model and per token

one burn, charged per model🌶️a burngpt-4o$0.03opus$0.19same work, each model at its own rate
02

Everything it does is on the telemetry stream.

!Today A lone agent runs invisibly. You learn about a problem from the bill or from an outage, after the fact.

the cell Every command it runs streams into a partitioned store you can query, tied to the session that ran it. The runtime is observable, not a black box.

44,633 command-telemetry events, partitionedA real count from our own database, shown as proof rather than a claim. It is a dated snapshot, captured on the date shown on this page.

every command, on a queryable streameventst1t2t3
03

It notices when a part drifts, and heals it.

!Today Config drift and dead services sit unnoticed until something visibly breaks.

the cell Health checks watch every part. When a host drifts from its canonical state, it is detected and reconciled unattended, with no human in the loop.

17,320 health checks runA real count from our own database, shown as proof rather than a claim. It is a dated snapshot, captured on the date shown on this page.

health checks watch every parthost up?config matches?service alive?drift caught and reconciled, unattended

from our own systems

The metabolism, running today

These are not projections. They are the organism metering its own energy and watching its own health: a priced usage ledger per model and per token, a partitioned telemetry stream of every command it runs, and health checks that catch drift and reconcile it unattended.

Green is a real figure from our database, as of Jul 29, 2026; in the diagrams, a committed write.

44,633

command-telemetry events, partitioned

17,320

health checks run

priced

usage ledger, per model and per token

zoom in

Down to a single burn

One call, a known number of tokens, priced at this model rate, written as one line in the ledger and tied to the task that spent it. That is the smallest unit of the metabolism, and every one of them is on the record.

partitioned telemetry → the Meter, a priced ledger → drift, self-reconcile

talk to us

Curious how a layer like this would fit your own records?

Send a note

Telemetry-event and health-check counts rendered from the system's own database on Jul 29, 2026. The usage ledger is priced per model and per token. Market figures cited to their source above. Dated snapshot, restamped before publish.