Measure phase

Measure

Phase 01 of 03

The measure phase turns the token-metering layer engineers already run into an auditable nexus of cost. It establishes which token spend is capitalisable, tags it to a specific build, proves it can be measured reliably at the individual-request level IAS 38 §54-62, and posts it across the token ledger to general ledger bridge. Everything the carry phase amortises is created here.

What this phase establishes

Recognition of an internally generated intangible turns on evidence. The measure phase builds that evidence before a single figure reaches the balance sheet. It answers three questions in order: what data does the metering layer emit, how is that data attributed to a specific build, and which of it may be capitalised at all. Get these right and the carry and report phases become bookkeeping; get them wrong and the whole asset is exposed at audit.

The pages in this phase

Token metering

The request-level data engineers already emit, and the fields the ledger needs.

AI-gateway tagging

Project and resource identifiers that attribute token spend to a specific build.

Nexus of cost

The evidence chain connecting tagged tokens to a recognised asset.

Reliable measurement

Satisfying IAS 38's measurement criterion at the individual-request level.

Token ledger to general ledger

The signature bridge: mapping ledger rows to GL intangible entries.

Inference as a period cost

Why metered third-party inference is almost always expensed.

Research vs development

Which token spend crosses into the capitalisable development phase.

Probable-to-complete threshold

The ASU 2025-06 threshold and what it changes for US GAAP measurement.