The Fifth Ledger

The Four Token Ledgers established that compute, billing, entitlement, and authority are four incompatible denominations that do not convert to one another, and that the session is the only bounded event capable of settling all four simultaneously.

There is a fifth ledger. The carbon ledger.

Every AI session has an energy cost. The industry measures it at the data center level. The IEA measures it nationally and globally. Nobody is measuring it at the level of interaction because the interaction has no boundary. No start event. No scope definition. No close event. No authority record. The accounting is done at the facility level, offset at the portfolio level, and attributed to nobody in particular.

The session is the place that attribution requires and currently lacks.

This essay extends the four-ledger framework to environmental settlement: the same boundary that closes the economic books closes the carbon books, and the architecture capable of supporting an avoided-emissions methodology for AI coordination overhead is now in the public record.

The Four Token Ledgers established that a token performs four distinct jobs simultaneously, and the field has been debating the cost direction while using a single word to describe four incompatible currencies.

Compute is denominated in floating-point operations. Billing is denominated in dollars per million units. Entitlement is denominated in plan quotas. Authority is not denominated at all. The four denominations do not convert against each other. There is no clearinghouse where they jointly resolve.

The session is what closes that gap. The bounded unit that can say: this inference was admitted here, authorized here, allocated here, computed here, billed here, and terminated here. When the session closes, all four

Abstract

ledgers settle simultaneously. Without the session, the enterprise has receipts. With it, the enterprise has cost control.

That essay ended with four ledgers.

There is a fifth.

The carbon ledger.

Every AI session has an energy cost. That cost is distributed across compute, cooling, infrastructure depreciation, and grid draw. The industry has been measuring the aggregate at the data center level for years. The IEA measures it at the national and global level. The GHG Protocol provides the accounting framework. ISO 14064 provides the organizational reporting standard.

What none of those frameworks can currently do is attribute an energy cost to a specific interaction, because the interaction has no boundary. There is no start event, no scope definition, no close event, and no authority record. The session that would make attribution possible does not architecturally exist. The meters run. The watts accumulate. The carbon is emitted. The accounting is done at the facility level, reported at the organizational level, and offset at the portfolio level.

Nobody is tracking the carbon ledger at the interaction level because there's nowhere to put it.

The session is that place.

At a minimum, any serious avoided-emissions methodology must satisfy three threshold questions: is the reduction measurable, is it additional, and can it be attributed without double-counting? Session governance addresses all three in principle, but the important word is principle. The

The Ledger Nobody Opened

What the Session Makes Possible

following section explains what the architecture enables and where the work still needs to be done.

The reduction is real. Collapsing the coordination product to a sum eliminates a measurable fraction of the energy load per session. The floor that Part One described is not a theoretical construct. It is watts consumed on identity reconciliation, policy evaluation, authority negotiation, and cross-boundary synchronization before useful work begins. A session boundary established once and held across the full interaction eliminates the redundant firings of those surfaces. The watts not burned are not offset. They are not balanced. They are not produced.

The reduction is additional. The baseline is a fragmented architecture: the product function runs independently at every surface, for every trace, for every interaction. Session-scoped architecture produces the delta. The delta is the difference between the product and the sum, per session, at whatever scale the deployment runs. That delta would not exist without the architectural intervention.

The reduction is attributable. The session has a start, a scope, and a close. The authority record exists. The compute scope is bounded. The billing scope is bounded. The entitlement scope is bounded. The carbon scope is bounded by the same boundary that bounds all four economic ledgers. One interaction, one delta, one owner.

No methodology currently exists in any voluntary carbon market registry for crediting avoided AI coordination overhead. Verra does not have it. Gold Standard does not have it. The GHG Protocol’s Scope 2 guidance, extended through public consultation into early 2026, does not reach it. The EU’s Data Centre Energy Efficiency Package, active and still being drafted, does not yet have vocabulary for coordination overhead as a distinct category.

A carbon market practitioner will push on this correctly: without a verified baseline, there is no additionality, and without additionality, there is no credit. That objection is right, and it points to the correct sequence. The session boundary is not a carbon credit. It is the precondition for measuring whether a creditable delta exists. No methodology can establish a baseline for a reduction that cannot be bounded. No reduction can be bounded without a session. The boundary makes the before-and-after comparison possible. The methodology cannot be written until the architecture that enables the measurement is in place. That is not a weakness of the argument. It is the order of operations.

The architecture capable of supporting that methodology is now in the public record.

That is the sequence. The session creates the preconditions for measurement. Measurement creates the preconditions for methodology. The market frameworks are mature enough to receive a new methodology built on session-bounded avoided emissions once the measurement infrastructure exists. The methodology follows the architecture, not the other way around.

The implementor who establishes the session boundary produces the delta. That is the platform deploying session-scoped architecture, the enterprise deployer running governed interactions, or the infrastructure operator whose stack binds the five coordination dimensions to a single persistent identity.

They produced the avoided overhead. The session record identifies the ledger entry. Ownership can then be assigned by contract, policy, or registry methodology, depending on how the deployment is structured and which party the governing framework designates as the claimant.

Who Holds the Credit

That is a new asset class sitting inside an architecture decision. Not a financial instrument layered on top of the system. Not a renewable energy purchase attached to the facility. Not a carbon removal credit purchased from a third party to offset emissions that were produced anyway. An avoided emission, per session, attributable to a specific architectural choice, with a bounded record identifying where it occurred.

The distinction matters. The hyperscaler buying carbon removal credits is cleaning the fuel after it burns. The implementor establishing session governance is preventing the burn. A facility running on renewable power that also runs fragmented coordination infrastructure is consuming clean watts on reconciliation that a session boundary would have eliminated. The renewable purchase addresses carbon intensity. It does not address the watts. Session governance addresses the watts. Those are not substitutes. They are different layers of the same problem, and the one nobody is currently addressing is the one that compounds as inference complexity grows.

The carbon market has been watching hyperscalers spend toward $70 billion on credits to offset emissions they cannot yet eliminate. Microsoft remains the world’s largest carbon removal buyer. Google increased CDR purchases 14-fold from 2023 to 2024. The gap between climate commitments and operational reality is widening because the mitigation is happening at the portfolio level while the production is happening at the interaction level.

Session governance is mitigation at the interaction level. Every session that runs on session-scoped infrastructure instead of fragmented infrastructure produces a real delta. Aggregated across the scale of a platform deployment, that delta is not a rounding error.

The Four Token Ledgers piece closed with this:

The Five Ledgers, Settled

A token meter counts consumption. A session defines the economic event.

The fifth ledger adds one line:

The session also defines the environmental event.

When the session terminates, compute stops, billing closes, entitlement restores, and the authority chain dies. Those are the four economic ledgers settling simultaneously. The carbon ledger settles at the same moment. The avoided coordination overhead is fixed at session close. It is attributable to that session, to that architecture, to that deployment.

The industry is building better engines. The public is resisting bigger garages. Neither conversation has reached the floor.

The floor is where the watts go before the answer starts. The session is what exposes it, measures it, and lowers it.

Five ledgers. One boundary. One close.

The carbon ledger is not separate from the economic argument. It is the same argument, expressed in a currency the market is actively seeking and the architecture is uniquely positioned to supply. The methodology that turns the delta into a creditable accounting object does not yet exist. Building it requires the bounded event first. The bounded event is what session governance provides.