Artificial Wasteland · Record / proofOutrigger stratum · 03.09.2026

A negative result, kept negative

The order that was never a schedule

Two amendments point to the same printed line. Reverse their application and the reconstructed text reverses too. The database test still says both orders are serializable. It has not failed. We asked it a question the parliamentary record cannot contain.

Home calibration · run first

Can the graph find a real cycle?

Before Parliament enters the instrument, the engine must reproduce the canonical database cases. A conflicting pair of operations creates a directed edge. A directed cycle means no equivalent serial order exists.

Canonical serial schedule

computing
T1T2

Canonical lost-update schedule

computing
T1T2

Live verdict

COMPUTING

Reading the locked parliamentary records.

?order-sensitive pairs
?cycles in the two selected serial orders
?coordinate baseline result
?records marked UNPARSEABLE

Exact composition instrument

Clause 2 · page 3 · line 22
Reconstructed insertion sequence3:22

Conflict precedence graph

6 7

computing

HYPOTHETICAL, NOT IN THE PARLIAMENTARY RECORD

The later insertion is placed immediately after the immutable boundary, a declared adapter convention. This sequence is an instrument output, not an authoritative consolidated bill.

All exact pairs

The 22 by 22 field

Every square is recomputed from exact source records. Red means the two application orders differ. Select a square to put that pair into the instrument. The diagonal is not a pair.

order-sensitivesame final statesame amendment

Six transfer gates

Nothing gets waved through

01 · HOME

Cycle found where due

Computing both canonical schedules.

02 · ADAPTER

Refusal is visible

Computing the strict parser ledger.

03 · HOLDOUT

Official consolidation

Checking the separate Sentencing Bill.

04 · RIVAL

Coordinate equality

Comparing the predeclared baseline.

05 · MUTATION

One caught, one spared

Running both planted mutations.

06 · OUTCOME

Copy follows evidence

Waiting for the computed verdict.

TESTING CAUGHT MUTATION

TESTING DELIBERATE NON-DETECTION

Adapter audit

What crossed the border

USED, DROPPED, AND SUPPLIED FIELDS

Used

  • Bill publication and document identifiers
  • Akoma Ntoso XML bytes and page-line processing instructions
  • Amendment id, bill id, stage id and type
  • Page, line, list number and decision
  • Every field in every amendment line

Calculation-neutral or dropped

  • Sponsors, explanation and group headers are display-only
  • Party colours are dropped
  • Member photos and contact links are dropped
  • Legal meaning and political intent are not inferred

Supplied by hand

  • Page-line marker as the data item
  • Each transaction reads and writes that boundary
  • Immediate-after insertion behavior
  • The visitor's selected serial order
  • The optional concurrent interleaving, labelled invented
THE STRICT GRAMMAR

Accepted: an EditBillBody record whose first line exactly names Clause or Schedule, page, line, and at end insert; whose coordinate fields agree; whose target processing instruction exists exactly once; and whose inline or multiline payload is structurally complete. Everything else is UNPARSEABLE. Spaces, quotation marks, markup, indentation and casing are never repaired.

All 77 records

The refusal ledger

A grey record is not a near miss and not a guessed edit. It is outside this instrument's exact grammar. Open any row to inspect the locked JSON supplied by Parliament.

No.TargetStatusSource instruction or refusalRecord
SELECTED RAW JSON
Select a record.

The check · recomputed in this page

?exact pairs enumerated
?serial orders of sensitive pairs checked
?official changes matched
?distinct page-line markers

Computing from the shipped source-derived data.