DAP Standard Changeset 02: assumption A6, what would break it

Date: 27 August 2026. Author: Dartmouth Advisory Partners. Status: approved by Brendan Sibeth, 27 August 2026 ("approved"). Applied to the 2026.2 source on 28 August 2026 before publication.

Target: dap-standard-2026.2.md, Part 1.3, assumption A6. One clause. Additive in effect: no code moves, no code retires, no definition of any leaf changes.

1. Why

Changeset 01 added K.04.05 (compute capacity as a traded unit) and stated assumption A6 with a break clause that named the listed contracts: withdrawal or non-approval of the announced futures would retire the leaf. That tied a structural leaf to a single exchange's decision.

The decision of 27 August 2026 is that DAP tracks compute as a traded unit regardless of any one listing. The unit rests on the observed market: daily published capacity benchmarks, spot venues trading standardised accelerator-hours, and tokenised claims on capacity, of which a cleared futures contract is one expression. The break clause is corrected to match.

2. Versioning

Version 2026.2 is not yet published. Apply this changeset to the 2026.2 source before publication and record it in the 2026.2 change log as a pre-publication amendment. If 2026.2 has already been published when this is applied, ship it instead as 2026.3, a minor release, with the same text.

3. The change

3.1 Replace assumption A6 (Part 1.3)

Current text (the A6 paragraph in full, as merged on 18 August 2026):

A6. Compute is becoming a commodity with an independent, referenceable price. We assume standardised accelerator capacity trades as a fungible unit whose price is observable independently of any single provider's contract terms, and that the unit is durable enough to carry its own leaf. If this reverses, K.04.05 is retired with a forward map to K.04.01 and T-COMPUTEMKT retires with a forward map to T-AICOMPUTE. What would break it: withdrawal or non-approval of the listed contracts, sustained absence of liquidity in them, or a return to capacity sold only inside bundled, bespoke, non-transferable supply agreements with no fungible unit behind them. A6 is weaker than A1 to A5 and should be read that way: K.04.05 was added on a publicly announced listing rather than on an observed market, which is a deliberate and stated risk.

Replacement:

A6. Compute is becoming a commodity with an independent, referenceable price. We assume standardised accelerator capacity trades as a fungible unit whose price is observable independently of any single provider's contract terms, and that the unit is durable enough to carry its own leaf. The leaf rests on the unit, not on any one venue, contract, or administrator. If this reverses, K.04.05 is retired with a forward map to K.04.01 and T-COMPUTEMKT retires with a forward map to T-AICOMPUTE. What would break it: the disappearance of every independently published capacity price and every venue trading a fungible unit, or a return to capacity sold only inside bundled, bespoke, non-transferable supply agreements. The withdrawal, non-approval, or illiquidity of any single listed contract does not break it; such an event is recorded against the affected contracts in deriv_attrs and in the review log, and the leaf stands. A6 is weaker than A1 to A5 and should be read that way: K.04.05 was added on published daily benchmarks, spot venues, and announced listings rather than on a deep observed market, which is a deliberate and stated risk.

3.2 Add a review-log entry (Part 7.6)

Append to section 7.6:

Changeset 02, 27 August 2026. Assumption A6's break clause corrected so that the leaf K.04.05 rests on the observed compute unit rather than on any single exchange listing. No code moved or retired. Applied before publication of 2026.2.

4. What this changeset does not do

It does not change the definition of K.04.05, Module E, rule C.6, or worked example 20. It does not claim any contract has listed or been approved. It does not weaken A6's own standard of evidence: the unit still has to be observable and fungible, and the retirement path with forward maps is unchanged.

5. Applying it

Run apply-changeset-02.py against the 2026.2 source. The script replaces the single line that begins with **A6., appends the 7.6 entry, and refuses to write if it cannot find exactly one A6 line or the 7.6 heading. It prints a diff and writes nothing on failure.