Governance

The game page reads the gold layer to ask what happened in the game. This page reads the same layer to ask a different question. Who decided what a value means, and would anyone notice if that decision moved?

1. What is under version control

The gold dimensions that keep their history are named below. Each version carries the dates its source file declares, so every rebuild shows the same history.

SELECT members,
       members_in_force,
       versions,
       superseded,
       deepest_history,
       last_change
FROM reference_governance
WHERE dimension = 'every dimension'

Every version is still current, because no reference value has changed since its source declared it. The history exists so that the first change leaves a record, and tests/test_versioned_dimensions.py declares a second version to prove that it does.

2. One policy per dimension

A character or a boss dates from the first game commit that names it. A contract cap dates from the commit that put it in the contract.

SELECT dimension,
       members,
       versions,
       superseded,
       first_valid_from
FROM reference_governance
WHERE dimension <> 'every dimension'
ORDER BY dimension

Modes have no dimension, and that is a decision rather than an omission. Nothing published names a mode, so a history would hold rows nobody reads. ADR 0002 carries the argument.

3. What the playbook says today

The table below gives each version the date it took effect. A rewritten description closes the row you see here and opens the next one.

SELECT dimension,
       member_key,
       version_seq,
       description,
       valid_from,
       status
FROM reference_history
ORDER BY dimension, member_key, version_seq

A run state carries two flags rather than a description, so it keeps its own table. is_run_state decides which pulses count as play time, and every run reads the version in force while it ran. A state reclassified tomorrow changes the runs after tomorrow and no run before it.

SELECT state_key,
       version_seq,
       is_run_state,
       in_run,
       valid_from,
       status
FROM app_state_history
ORDER BY state_key, version_seq

4. What the contract allowed

Each quarantine decision depends on the cap in force at the time. The contract keeps every value a cap has held, with its dates, so a reader can still check an old decision against its cap.

SELECT cap_key,
       cap_value::INTEGER AS cap_value,
       valid_from,
       status
FROM contract_cap_history
ORDER BY cap_key, valid_from

5. What nobody exercised

A documented value that never appears in the data is a governance question, not a bug. It means the reference and the telemetry disagree about what the game can do, and one of the two needs a look.

SELECT dimension,
       documented::INTEGER AS documented,
       exercised::INTEGER  AS exercised,
       array_to_string(never_seen, ', ') AS never_seen
FROM dimension_coverage
ORDER BY dimension

The never seen column names every documented value the data does not show. A narrow capture from one player produces that, and a wider one would close most of the gap.

What this page cannot tell you

Each date answers one narrow question.