tokenfabrikker/CHANGELOG.md
Kjell Tore Guttormsen b4aa608d6d
docs: enter the project owner's decisions on clarifications 98, 102 and 103
Clarifications 18 to 20 of the pre-registration, approved 2026-11-13
before anything is computed: part II has no verdict when no step can
be built, a single facility cannot be the 25 % step (clarification 104
of the specification, not coded yet), and the paths the ownership
forms are compared on.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-13 17:35:18 +01:00

151 lines
14 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Changelog
All notable changes to this project will be documented in this file.
## Unreleased
- Pre-registration of what is tested and what it takes for the hypothesis to hold (`FORHANDSREGISTRERING.md`).
- Source bank: 948 entries in 21 areas, each checked against its primary source (`kilder/`). The second round
(areas 13–21) covers the parameters that lacked a source when the model was specified.
- Model specification, draft 3 (47 equations), after a pre-read of draft 2, two independent reviews of draft 3
and a control of the corrections (`modell/`).
- Parameters frozen before anything is computed: 124 parameters in 2025 kroner, one distribution each, with the
source entries they rest on (`modell/parametere.json`). The checksum is recorded in the pre-registration.
No code and no results yet.
- Eight clarifications of the pre-registered criteria, approved by the project owner after the parameter freeze
and before anything is computed (`FORHANDSREGISTRERING.md`, «Presiseringer»). The parameter file is unchanged.
- First code (`src/tokenfabrikker/`): one function per equation for the power plant, the data centre and the
revenue (S1–S21, S36, S43–S47), a strict reader for the frozen parameter file with unit conversion, and the
10 000 Monte Carlo draws stored in `data/`. Python with pinned numpy and scipy, pytest, ruff `ALL` and mypy strict.
No result for the hypothesis has been computed.
- An independent reader coded the key equations from the specification alone. The two implementations agree on
all 23 functions. The 19 ambiguities the reader found are settled in a new, dated chapter 16 of the
specification (`modell/`); the parameter file and the pre-registration are unchanged.
- Known-answer tests against Argonne, NOU 2026: 4, Epoch and NVE with the sources' own assumptions
(`tests/test_fasit.py`). The misses are kept as documented expected failures: wind on land and offshore wind
come out 5–6 % below NVE, and three rows of Argonne's table depend on a reading the source does not settle.
- Build-out, power system and cash flow in code (`src/tokenfabrikker/`): when each facility starts and which
vintages of IT hardware it gets (S22, S33), the export rule with its own stored stream of random numbers
(`data/aarshendelser.npy`), the fitted price lines and the power and capacity balances (S23–S25, S38), and the
yearly cash flows with residual value, the additionality rule and net present value for Norway (S26, S34, S35,
S40, S45). Tested on made-up numbers only; no result for the hypothesis has been computed.
- A second independent reader coded these equations from the specification alone and found 28 ambiguities. They
are settled in clarifications 21–40 in chapter 16 of the specification. With the readings aligned, the two
implementations agree on 10 000 made-up build-out paths. The clarifications that are choices are marked and put
to the project owner (`modell/fagfellevurdering-utkast-2-og-3.md`, part 5).
- The price lines of S38 are held against NVE's twelve scenarios: within 5 % for Norway and three price areas,
6.0 % and 7.7 % off in one scenario for NO3 and NO4, kept as documented expected failures.
- Business economics, ownership, scale, environment and verdicts in code (`nivaaisert.py`, `eierskap.py`,
`skala.py`, `miljo.py`, `dommer.py`; S15, S19, S27 to S32, S37, S42), tested on made-up numbers only. A third
independent reader coded the same chapters from the specification alone and found 60 points, 14 of them
objections to the economics; a new reader then recoded from the clarifications in four more rounds (17, 5, 1
and 0 new points). The readings stand in clarifications 41–61 in chapter 16; the two implementations agree on
1 000 made-up paths. Corrected after the readers: the accident cost stays when the additionality rule binds,
tax depreciation loses real value with price growth, and the special tax only meets return above the cost of
capital. Weaknesses in the comparison of ownership forms that are not corrected are listed in clarification 61
and put to the project owner (`modell/fagfellevurdering-utkast-2-og-3.md`, part 6). No result for the
hypothesis has been computed.
- The comparison of ownership forms corrected before anything is computed (clarifications 62–67 in chapter 16):
a residual value at the final year as a taxable sale, the electricity tax as the state's only levy with what
displaced private data centres would have paid deducted, private owners who pay what their share is worth in
expectation, the state's cash flow valued with the required return for compute, and the cost of capital before
tax. An independent reader coded the corrections from the text alone in three rounds; its first-round finding
that the private owners and the state were priced with different rates changed the correction. With it every
ownership form has the same expected value in the main run, and they differ in risk and capital. The two
implementations agree to within one krone on 1 500 made-up paths. The project owner approved the corrections
before anything is computed.
- The direction of the project extended by the project owner (what can start quickly, a stepwise build-up, and
compute on the users' own machines), and four more clarifications of the pre-registered criteria (9–12), all
before anything is computed (`FORHANDSREGISTRERING.md`). The sources' figures for the emissions test M5 (i)
are set up and checked against the primary sources (clarification 68). The parameter file is unchanged.
- Source bank extended with areas 22–26 for the addition to the direction (188 entries: fast start on the grid,
power with short lead time, stepwise build-up, compute on the users' own machines, avoided emissions and
cooling water), each checked against its primary source by an independent controller (`kilder/`).
- The addition to the direction written into the specification as chapter 17 (equations S48–S54) and into the
pre-registration, before anything is computed: a new solution T, "stepwise", in two versions (modules of
100 MW on the grid with new renewable power, and the same with grid-connected nuclear power from when it can
come), which A must also beat; no gas power; a threshold and two labelled scenarios for compute on the users'
own machines; the calculation of emissions with a deduction; cooling water; and a timeline of megawatts in
operation per solution. An independent reader coded the chapter from the text alone in three rounds; its findings
changed the chip rule and the condition for nuclear power in the second version, the cap on early grid
connections and the lead time. The parameter file is unchanged; the new quantities are candidates until the
deviation from the freeze.
- One deviation from the parameter freeze, before anything is computed (`modell/parametere.json` version 1.1,
new checksum in the pre-registration): thirteen new quantities for the addition to the direction, seven new
sensitivities and three corrected lines in the list of sensitivities. None of the 124 frozen parameters got a
new value, range or distribution. 137 parameters, 91 drawn quantities, new draws in `data/`. Before the
deviation the project itself looked up the 30 source entries behind the new quantities in the primary
sources; four things changed from the candidates (see chapter 17.8 of the specification).
- The build-out of solution T in code (`src/tokenfabrikker/utbygging.py`, chapter 17.1): when each module of
100 MW starts in T-F and T-K, with the grid balance of the first stage, the condition for nuclear power (S49)
and the two stocks of chips, and the timeline of megawatts in operation per type of power (S50). The equations
S48–S54 are pure functions, and the new quantities are read into the input data. Written from the text
before the independent reader's code was opened, then run against it: 42 000 made-up build-outs and 20 000
made-up sets for S51–S54 without a difference. Six clarifications (70–75) in chapter 16 of the specification
say how chapter 17 is read where the text was silent. Solution T is not taken through the cash flow or the
verdicts yet, and no result for the hypothesis has been computed.
- Solution T through the power system and the cash flow (`kontantstrom.py`): everything per module, renewable
modules with their own portfolio as in C, the nuclear modules of T-K on shared units as in B, and the fixed
cost of a new nuclear country counted to the first unit. The loss of demand of chapter 17.3 enters the
revenue and the disconnection arm of S47 (`regn_program(..., bortfall=...)`); without a loss every figure is
unchanged. Emissions "with deduction" (S53) and cooling water (S54) are put together over a programme for
all seven solutions (`miljo.py`). A new independent reader coded the same from the specification alone:
1 778 made-up paths through both codes without a difference, and the two sensitivities that are switches in
both. Six clarifications (76–81) in chapter 16 settle what the text left open
(`modell/fagfellevurdering-utkast-2-og-3.md`, part 11). The levelised cost, ownership, scale and verdicts
refuse solution T and a loss of demand until chapter 17 is taken through them. No result has been computed.
- Present values are now exactly rounded sums. As dot products the same computation did not give the same last
digit every time, for every solution. A test runs the same computation six times and requires equal numbers.
- Solution T and the loss of demand through the levelised cost, the business economics, the ownership forms
and scale (`nivaaisert.py`, `eierskap.py`, `skala.py`): the power cost per module, with a renewable module's
own portfolio as in C and the nuclear modules of T-K on shared units as in B; tariff, building, IT hardware
and residual value per module; and the factor of S51 per vintage in S19, S27, S31 and S42. For the five
solutions of chapters 0 to 16 without a loss every figure is unchanged to the last digit. A new independent
reader coded the same from the specification alone: 1 760 made-up paths through both codes, 6.6 million
figures compared, without a difference. Six clarifications (82–87) in chapter 16 say how the text is read
and name one property the reader found that is in favour of nuclear power on the grid in the business
economics (`modell/fagfellevurdering-utkast-2-og-3.md`, part 12). M5 and the verdicts do not know solution T yet. No
result has been computed.
- The technologies of a facility are kept in a fixed order. As a set of names their order differed from run to
run, and the last digit of the figures for solution C with it.
- M5 and the verdicts for five solutions (`miljo.py`, `dommer.py`): T-F meets M5 (i) and (ii) by definition
and T-K is judged as nuclear power; the ladder, part I and M7 cover A, B, C, T-F and T-K, and in M7 A must
beat each of the four others that can be built. Three sensitivities of chapter 17.8 are switches: full
displacement in the first stage (`regn_program(..., full_fortrengning_i_forste_trinn=True)`), new renewable
power first from 2031 for C and T (`lag_plan(..., ny_kraft_fra=2031)`), and modules of 50 and 200 MW
(`Inndata.med`). Next to S54 the withdrawal of water is also given with sea water only for the nuclear
production the data centres themselves use. With the switches off every figure for all seven solutions is
unchanged to the last digit. A new independent reader coded the same from the specification alone: about
400 000 comparisons of M5 and the verdicts on invented outcomes per draw, and 2 523 made-up paths with
10.1 million figures through both codes for the sensitivities, without a difference. Seven clarifications
(88–94) in chapter 16 say how the text is read (`modell/fagfellevurdering-utkast-2-og-3.md`, part 13). No
result has been computed.
- Clarification 17 of the pre-registration, approved by the project owner 2026-11-13 before anything is
computed: the conditions of a power solution can be named when every target it holds under conditions in
has a condition that can be named, and when M5 holds under conditions the condition is that the sources in
which nuclear power is not higher are the ones relied on, written out with the source. The independent
reader found that the text did not say this. The project owner also decided that the grid connection of a
nuclear plant stays out of the business economics, as the text says, and that the report states it
(clarification 87).
- The run over the draws (`kjoring.py`): for every draw the seven solutions on every step of the ladder in six
scenarios (three price scenarios and the three marked scenarios for AI use on the users' own machines), with
the outcomes the verdicts need; the verdicts per target with the shares they are set from, the step they
are read on, part I and part II; the timeline (S50) as median, percentiles and shares over the draws; and
the ownership forms on that step. Clarifications 95–103 in chapter 16 settle what the text did not say: what
is computed per draw, that a path that cannot be built has no outcome while a set of values the build-out
rejects stops the run, that the step is set once in «normalisering» and used in every scenario, which paths
the ownership forms are compared on, how the percentiles are computed, and that part II has no verdict when
no step can be built. The run gives the same figures to the last digit on one, three and four processes,
with five different hash seeds and with solutions, steps and scenarios in reverse order (2 240 made-up
paths). A new independent reader coded the same from the specification alone: 120 made-up draws through
both codes (3 360 paths, 373 000 figures) and 600 runs of invented outcomes per draw (1.9 million figures
and 545 000 verdicts, steps and years) without a difference
(`modell/fagfellevurdering-utkast-2-og-3.md`, part 14). The run has only been given made-up draws. No
result has been computed.
- Clarifications 18 to 20 of the pre-registration, approved by the project owner 2026-11-13 before anything is
computed: part II gets no verdict when no step of the ladder can be built, and the report says so; the step
with a single facility cannot be the 25 % step, because the independent reader found that the rule let a
weaker single facility give a better verdict (this makes part I easier to meet in that one case, and is
changed now because it could not be changed credibly once the figures exist); and the ownership forms are
compared for each of the five solutions on the step the verdicts are read on. The change of the step rule
(clarification 104 of the specification) is not coded yet.