Real world use cases

What units of work look like in practice: support, legal, reporting, and code, each with its checks and budget.

Any outcome with a describable end state is a unit of work. Four families cover most operations today.

Support ticket

B ≈ $4. Checks: status closed (0.5), reply sent (0.3), KB linked (0.2). Atomic.

Contract review

B ≈ $25. Checks: risks flagged (0.4), redlines (0.4), summary filed (0.2). Divisible with escrowed judgment.

Weekly report

B ≈ $12. Checks: data pulled (0.3), analysis (0.4), delivered (0.3). Divisible.

Merged change

B by scope. Checks: tests pass, surface untouched, merged. Atomic, always.

The budgets come from the anchors in the playbook: real prices, human baselines, market comparables. The checks come from state the environment can capture. Per-check pass rates then drive each family's economics: the weakest check dominates the intervention rate, so improving one check moves the whole unit type.

What a quarter of these looks like on one ledger: the dashboard. Beyond operations, the same unit opens three frontier cases:

Pricing agents

Per-settled-quirq pricing and QER as the builder's spec sheet.

Agentic markets

Budgets as demand, cost per quirq as supply: microdata for economists.

Quantum computing

Shots are quantum's tokens; quirqs as the output meter, and intent as data. Exploratory.

Start with the dashboard.