Ranged value

change-applies

Applies for every adoption

An in-range change moves Instance by its amount Bind resolution phrase, in one commit with no partly settled state observable. A mark whose reached state did not change does not report. The edges are stated at Value cite min and Value cite max; this test restates neither number.

Given

Instance holding a stored value strictly between Value cite min and Value cite max, with enough room that the change below stays in range, and with no active band blocking the change's direction

When

• one imposed change with signed amount d is applied to Instance

Then

• the stored Instance value changes by d Bind resolution phrase
• the value and residue, when residue exists, commit together and no partly settled state is observable
• no mark whose reached state did not change reports

Diagnostics

• Instance-value-before-after
• Instance-mark-log

fractional-change-resolves

Applies when Small change is Nearest or Nearest away from zero or Drop the fraction or Always a whole unit.

Instance holds whole numbers, so a change carrying a fraction resolves before it reaches the value: what moves is Bind resolution phrase. The part resolved away is gone; no later change is larger or smaller for it.

Given

Instance holding a whole stored value, with room in range for the change below, and a record naming the amount offered and the amount that reached the value

When

• positive and negative changes carrying fractions, including exact halves, are offered to Instance

Then

• the amount that reaches Instance is Bind resolution phrase
• the stored value is whole after every change
• the resolved-away part is discarded and changes no later operation

Diagnostics

• Instance-change-record
• Instance-value-before-after

fractional-change-saves-residue

Applies when Small change is Save the fraction.

Instance splits a fractional change: the whole part moves at once and the signed remainder waits as residue. Whenever that residue contains complete multiples of Value cite fraction step, those multiples leave toward zero as whole-unit movement and the remainder stays. A whole change leaves residue alone. The test restates neither the step nor any limit.

Given

Instance holding a whole stored value with signed residue zero, enough room for the changes below, and a record naming each offered amount, movement, and residue afterwards, and with no active band blocking the change's direction

When

• a run of positive and negative fractional changes is applied, including a whole change and residue that reaches at least one complete multiple of Value cite fraction step

Then

• the whole part of each fractional change moves Instance at once and only its signed fractional remainder enters residue
• complete multiples of Value cite fraction step are removed from residue toward zero and move that many whole units in the matching direction
• a whole change moves in full and leaves residue unchanged
• the stored value remains whole
• residue after each change equals the offered signed fractional remainders minus the complete multiples of Value cite fraction step already released, and each released multiple moved that many whole units

Diagnostics

• Instance-change-record
• Instance-residue
• Instance-value-before-after

fractional-value-keeps-no-store

Applies when Number kind is Fractional.

A fractional Instance keeps every finite change at full precision. It has no saved-fraction store, so residue is never observable.

Given

Instance holding any fractional stored value with room for finite positive and negative changes

When

• finite changes with fractional amounts settle

Then

• every finite change lands at full precision
• no saved-fraction store exists
• no residue is ever observable

Diagnostics

• Instance-value-before-after
• Instance-state-record

comparisons-read-stored-value

Applies for every adoption

Whatever Instance shows the player, every comparison reads its stored value at full precision. Lines, bands, limits, drift stops, and costs never read a rounded display number, and each cited position is read fresh.

Given

a moment when the number shown for Instance differs from the stored value because the display is rounded, shortened, or abbreviated; a display that always matches storage has nothing to check here

When

• a line, band edge, limit, drift stop, or cost comparison is made

Then

• the comparison reads the stored Instance value at full precision
• every cited position is read fresh for that comparison
• the displayed number decides nothing

Diagnostics

• Instance-comparison-log
• Instance-value-before-after

creation-is-silent

Applies for every adoption

Creation is not a movement and reports nothing. Instance silently stores every line's reached state, gives lines their declared arm state or the armed default, and gives bands their declared starts.

Given

creation of Instance at Value cite initial

When

• initial line and band state is stored

Then

• creation is not a movement and reports nothing
• every line's reached state is stored silently
• lines take their declared arm state, or armed when starts-armed is omitted
• bands take their declared starts

Diagnostics

• Instance-line-state
• Instance-line-allowance
• Instance-band-state
• Instance-mark-log

exact-landing-counts

Applies when Exact landing is At the line counts.

For Instance, touching a line or consuming limit counts as reaching it. An armed line at that position, matching the direction of travel and with allowance remaining, reports on that landing, and a limit answered start-a-lap consumes the change. This value-wide answer is tested at a line or band that declares no counts-at-line of its own.

Given

Instance on the unreached side of a declared line or consuming limit, at a line or band that declares no counts-at-line of its own

When

• one change lands exactly on that position

Then

• the position counts as reached in the direction of travel
• an armed line at that position, matching the direction of travel and with allowance remaining, reports on that landing
• a limit answered start-a-lap consumes the change

Diagnostics

• Instance-mark-log
• Instance-operation-record

exact-landing-must-pass

Applies when Exact landing is Must pass the line.

For Instance, touching a line or consuming limit is not enough. It becomes reached only after the stored or tested path passes strictly beyond it.

Given

Instance on the unreached side of a declared line or consuming limit, at a line or band that declares no counts-at-line of its own

When

• one change lands exactly on that position and a later change passes it

Then

• the exact landing does not count as reached
• the later movement strictly past the position is the first movement that may report or consume

Diagnostics

• Instance-mark-log
• Instance-operation-record

ceiling-stops-change

Applies when At the ceiling is Stop at the ceiling.

A rising change that overshoots Value cite max leaves Instance exactly on that edge. The excess is lost and reported to no one. This test restates neither number.

Given

Instance holding any value at or below Value cite max

When

• an imposed rising change would take Instance above Value cite max

Then

• the stored value is exactly Value cite max
• the excess is discarded and reported to no one
• the change otherwise happened

Diagnostics

• Instance-value-after
• Instance-edge-record

floor-stops-change

Applies when At the floor is Stop at the floor.

A falling change that undershoots Value cite min leaves Instance exactly on that edge. The shortfall is lost and reported to no one. This test restates neither number.

Given

Instance holding any value at or above Value cite min

When

• an imposed falling change would take Instance below Value cite min

Then

• the stored value is exactly Value cite min
• the shortfall is discarded and reported to no one

Diagnostics

• Instance-value-after
• Instance-edge-record

ceiling-refuses-change

Applies when At the ceiling is Refuse the whole change.

A change that would carry Instance above Value cite max is refused whole and the refusal is reported to the caller. Value and residue stay as they were, and no mark reports, not even partway to the edge.

Given

Instance holding stored value v and, when present, residue r

When

• an imposed rising change would take Instance above Value cite max

Then

• the change is refused and the stored value remains v
• residue remains r
• no mark reports
• the refusal is reported to the caller

Diagnostics

• Instance-value-before-after
• Instance-residue-before-after
• Instance-refusal-record

floor-refuses-change

Applies when At the floor is Refuse the whole change.

A change that would carry Instance below Value cite min is refused whole and the refusal is reported to the caller. Value and residue stay as they were, and no mark reports, not even partway to the edge.

Given

Instance holding stored value v and, when present, residue r

When

• an imposed falling change would take Instance below Value cite min

Then

• the change is refused and the stored value remains v
• residue remains r
• no mark reports
• the refusal is reported to the caller

Diagnostics

• Instance-value-before-after
• Instance-residue-before-after
• Instance-refusal-record

ceiling-returns-extra

Applies when At the ceiling is Hand back the extra.

A caller's rising change fills Instance to Value cite max and receives the positive extra that did not fit. This contract does not route it. The same change with nobody acting has no caller, so its extra is dropped.

Given

Instance holding v with positive room h below Value cite max

When

• a caller applies rising change d greater than h, and the same change is also run with nobody acting

Then

• the stored value is exactly Value cite max
• the caller receives positive extra d minus h
• the operation with nobody acting has no caller, so the same extra is dropped

Diagnostics

• Instance-value-after
• Instance-returned-extra

floor-returns-extra

Applies when At the floor is Hand back the extra.

A caller's falling change empties Instance to Value cite min and receives the positive shortfall that did not fit. This contract does not route it. The same change with nobody acting has no caller, so its shortfall is dropped.

Given

Instance holding v with positive room h above Value cite min

When

• a caller applies falling change of magnitude d greater than h, and the same change is also run with nobody acting

Then

• the stored value is exactly Value cite min
• the caller receives positive shortfall d minus h
• the operation with nobody acting has no caller, so the same shortfall is dropped

Diagnostics

• Instance-value-after
• Instance-returned-extra

ceiling-is-landmark

Applies when At the ceiling is No ceiling.

The value at Value cite max does not hold Instance down. A rising change passes it in full; the top remains a citable landmark and still defines shares.

Given

Instance holding v

When

• a rising change d makes v plus d exceed Value cite max

Then

• the stored value is exactly v plus the change, resolved as this value's number-kind directs — through its small-change answer where that question is asked — with no limit applied
• nothing is stopped, refused, returned, or lapped
• Value cite max remains a citable landmark and still defines shares

Diagnostics

• Instance-value-after
• Instance-mark-log

floor-is-landmark

Applies when At the floor is No floor.

The value at Value cite min does not hold Instance up. A falling change passes it in full; the bottom remains a citable landmark.

Given

Instance holding v

When

• a falling change d makes v plus d fall below Value cite min

Then

• the stored value is exactly v plus the change, resolved as this value's number-kind directs — through its small-change answer where that question is asked — with no limit applied
• nothing is stopped, refused, returned, or lapped
• Value cite min remains a citable landmark

Diagnostics

• Instance-value-after
• Instance-mark-log

ceiling-starts-lap

Applies when At the ceiling is Start a lap.

When a rising change consumes Value cite max, Instance reports outward marks, then the lap, then any marks on the leg to Value cite lap lands on. The reports keep one operation id and distinguish their legs. This test restates neither position.

Given

Instance below Value cite max, with the armed marks this adoption can place on the outward and lap legs and an operation record carrying before, after, direction, leg position, operation id, and lap count

When

• one rising change reaches Value cite max as exact-landing directs

Then

• the outward leg ends at the consuming ceiling
• outward marks report first, as this value's jumped-lines answer directs, then the lap
• after the lap report, cited limits are read fresh
• where either cited limit moved, any limit-moved band report occurs before the lap leg
• a limit move never repositions the value during the lap loop
• the lap leg stores Value cite lap lands on and any marks on it report after the lap
• all reports retain the originating operation id and distinguish leg position

Diagnostics

• Instance-operation-record
• Instance-lap-log
• Instance-mark-log

floor-starts-lap

Applies when At the floor is Start a lap.

When a falling change consumes Value cite min, Instance reports outward marks, then the lap, then any marks on the leg to Value cite lap lands on. The reports keep one operation id and distinguish their legs. This test restates neither position.

Given

Instance above Value cite min, with the armed marks this adoption can place on the outward and lap legs and an operation record carrying before, after, direction, leg position, operation id, and lap count

When

• one falling change reaches Value cite min as exact-landing directs

Then

• the outward leg ends at the consuming floor
• outward marks report first, as this value's jumped-lines answer directs, then the lap
• after the lap report, cited limits are read fresh
• where either cited limit moved, any limit-moved band report occurs before the lap leg
• a limit move never repositions the value during the lap loop
• the lap leg stores Value cite lap lands on and any marks on it report after the lap
• all reports retain the originating operation id and distinguish leg position

Diagnostics

• Instance-operation-record
• Instance-lap-log
• Instance-mark-log

lap-carries-extra

Applies when The extra after a lap is Carry it onto the new value.

After a lap, Instance carries the leftover onto the new value. It settles as another leg in the original direction, from step 1, under the originating operation id.

Given

a change whose movement continues past a consuming limit

When

• Instance reports its first lap

Then

• the leftover past the consuming limit is applied after the lap movement, in the original direction
• that leg returns to settlement step 1, keeps the originating operation id, and tests its own marks

Diagnostics

• Instance-operation-record
• Instance-lap-log

lap-drops-extra

Applies when The extra after a lap is Drop it.

After one lap, Instance drops the leftover. It is reported to no one and produces no further leg.

Given

a change whose movement continues past a consuming limit

When

• Instance reports its first lap

Then

• the leftover is discarded after that lap
• it is reported to no one and causes no further leg or lap

Diagnostics

• Instance-operation-record
• Instance-lap-log

lap-repeats-with-cap

Applies when More than one lap is Lap again while it fits.

Carried leftover may lap Instance again while it fits, but one originating operation settles at most 32 laps. Before lap 33, continuation is rejected, lap-cap-reached records the state committed by lap 32, and the remaining leftover is dropped.

Given

carried leftover large enough to reach the same consuming limit repeatedly, including a run that would require a thirty-third lap

When

• the originating change settles

Then

• Instance reports another lap whenever the carried leftover reaches the limit
• at most 32 laps settle for the originating operation
• before lap 33 continuation is rejected, lap-cap-reached reports with the state committed by lap 32, and all remaining leftover is dropped

Diagnostics

• Instance-lap-log
• Instance-lap-cap-reached
• Instance-value-after

lap-stops-after-one

Applies when More than one lap is One lap per change and The extra after a lap is Carry it onto the new value.

One originating change can report only one lap. A second reach of the same consuming limit is stored without consuming, and further excess is dropped.

Given

a change with carried leftover large enough to reach the same consuming limit a second time

When

• the originating change settles

Then

• exactly one lap reports
• the second reach is stored without consuming
• further excess is dropped

Diagnostics

• Instance-lap-log
• Instance-value-after

lap-stops-after-one-and-drops

Applies when More than one lap is One lap per change and The extra after a lap is Drop it.

One originating change reports exactly one lap. Because this adoption drops leftover, that leftover is reported to no one and cannot cause a second consumption.

Given

a change with leftover beyond a consuming limit and enough amount to reach that limit again if the leftover were carried

When

• the originating change settles

Then

• exactly one lap reports
• the leftover is dropped and reported to no one
• no second consumption occurs

Diagnostics

• Instance-lap-log
• Instance-operation-record
• Instance-value-after

lap-clears-residue

Applies when A lap clears saved fraction is Clear it.

A lap clears Instance residue once the consuming movement commits and, where leftover is carried, before that leftover is resolved.

Given

Instance holding nonzero signed residue before a consuming movement

When

• the movement commits and reports a lap

Then

• residue is zero once the consuming movement commits, and where leftover is carried, before that leftover is resolved

Diagnostics

• Instance-residue-trace
• Instance-lap-log

lap-keeps-residue

Applies when A lap clears saved fraction is Keep it.

Residue is unchanged by the Instance lap itself, measured immediately after the lap movement and before any carried leftover settles.

Given

Instance holding nonzero signed residue before a consuming movement

When

• the movement commits and reports a lap

Then

• residue is unchanged by the lap itself, measured immediately after the lap movement and before any carried leftover settles

Diagnostics

• Instance-residue-before-after
• Instance-lap-log

line-crosses-fixed-position

Applies when row value kind is Number.

The Row.id line uses Bind position phrase. A Bind movement direction reports when its reached state changes from false to true, provided the line is armed and has allowance. Its declared starting arm state applies; omission means armed.

Given

Instance holding a value on the unreached side of Row.id at Bind position phrase, with the line in its declared starting arm state; omission of starts-armed means armed

When

• one Bind movement direction changes Row.id from unreached to reached

Then

• Row.id reports exactly once if it is armed and still has allowance
• the report carries before, after, direction, leg position, operation id, and row id
• reached state is recomputed from the stored endpoint in both directions

Diagnostics

• Instance-mark-log
• Instance-line-state
• Instance-value-before-after

line-crosses-cited-position

Applies when row value kind is Citation.

The Row.id line uses Bind position phrase, with Row.value key read fresh whenever it is compared. A Bind movement direction reports when reached state changes from false to true, provided the line is armed and has allowance. Its declared starting arm state applies; omission means armed. The test names the address and restates no number.

Given

Instance holding a value on the unreached side of Row.id at Bind position phrase, with the line in its declared starting arm state and the cited number recorded before comparison; omission of starts-armed means armed

When

• one Bind movement direction changes Row.id from unreached to reached

Then

• Row.value key is read fresh for the comparison and this test restates no number
• Row.id reports exactly once if it still has allowance
• the report carries before, after, direction, leg position, operation id, and row id

Diagnostics

• Instance-comparison-log
• Instance-mark-log
• Instance-line-state

line-uses-ceiling-share

Applies when row line unit is Share of the ceiling.

Row.id states a share rather than an absolute position. Its line follows that share of Value cite max, read fresh at comparison time; this test restates neither number.

Given

the marked top at Value cite max recorded before comparison and Row.id armed

When

• a Bind movement direction crosses the share declared by Row.id

Then

• the line position is the row's declared share multiplied by the fresh value at Value cite max
• the position may be fractional; it is compared, never stored
• the crossing reports once if allowance remains

Diagnostics

• Instance-comparison-log
• Instance-mark-log

line-exact-landing-override

Applies when row counts at line is At the line counts or Must pass the line.

The Row.id row overrides the value-wide exact-landing choice. Its at-the-line-counts answer makes an exact landing reach the line; its must-pass-the-line answer requires movement strictly past it.

Given

Row.id armed and unreached in its reporting direction

When

• one movement lands exactly on Row.id and another strictly passes it

Then

• where this row declares at-the-line-counts, an exact landing counts as reaching the line
• where this row declares must-pass-the-line, an exact landing does not reach the line and the movement must pass it
• the row's declared answer overrides Instance's value-wide exact-landing answer

Diagnostics

• Instance-mark-log
• Instance-line-state

line-refires-every-crossing

Applies when row refire is Every crossing.

For Row.id, each leg whose reached state for a reported direction goes false to true fires exactly one report, while a true-to-false leg reports nothing. Bind sequence result.

Given

Row.id armed and unreached

When

• Instance crosses Row.id in a reporting direction, returns to unreached, and crosses again

Then

• each leg whose reached state for a reported direction goes false to true fires exactly one report for that leg, and a leg whose transition is true to false reports nothing
• Bind sequence result

Diagnostics

• Instance-mark-log
• Instance-line-state

line-both-directions-keep-state

Applies when row direction is Both.

A both-direction line keeps one reached state per direction. In a cross-down, cross-up, cross-down sequence, each qualifying false-to-true transition reports while refire allowance remains; one shared state is not legal.

Given

Row.id armed with allowance and its rising and falling reached states recorded separately

When

• Instance crosses Row.id down, up, and down again

Then

• each direction keeps its own reached state
• each qualifying false-to-true transition in either direction reports while the line's refire allowance remains
• no shared single reached state is legal

Diagnostics

• Instance-crossing-log
• Instance-mark-log
• Instance-line-state

line-fires-once-per-arm

Applies when row refire is Once and row rearm is On reset or On event or After a wait.

Row.id reports once per arm. Across two crossings without re-arming, only the first reports. Its re-arm rule is: Bind rearm phrase.

Given

Row.id armed with its full allowance

When

• Instance makes two qualifying crossings without re-arming, then Bind rearm phrase

Then

• only the first crossing reports before re-arming
• after the declared re-arm, the next qualifying crossing reports once again

Diagnostics

• Instance-mark-log
• Instance-line-allowance

line-fires-set-number

Applies when row refire is A set number of times and row rearm is On reset or On event or After a wait.

Row.id may report Row.times times per arm. Further qualifying crossings stay silent until Bind rearm phrase restores the full allowance.

Given

Row.id armed with a fresh allowance of Row.times

When

• Instance makes more than Row.times qualifying crossings without re-arming, then reaches Bind rearm phrase

Then

• exactly Row.times crossings report before the allowance is exhausted
• the declared re-arm restores the full allowance of Row.times

Diagnostics

• Instance-mark-log
• Instance-line-allowance

line-wait-rearm-repeat

Applies when row rearm is After a wait.

While Row.id waits to re-arm under Row.rearm declared in, another crossing Bind repeat phrase. The test names the wait address and restates no duration.

Given

Row.id waiting to re-arm under Row.rearm declared in

When

• another qualifying crossing occurs before the wait finishes

Then

• the new crossing Bind repeat phrase
• the line remains unable to exceed its current allowance until the resulting wait completes

Diagnostics

• Instance-line-wait
• Instance-line-allowance

jumped-lines-reports

Applies when Jumped lines is All in order or Only the nearest.

When one leg of Instance crosses several marks, Bind report phrase. Bind state phrase. A crossed band edge updates its band state under both answers whether or not its report is selected. If this adoption has fewer than two marks, it has no multi-mark case to run.

Given

one leg that crosses at least two armed bare lines or band edges with allowance; an adoption with fewer than two marks has no multi-mark case and this scenario is vacuous

When

• the leg settles

Then

• Bind report phrase
• Bind state phrase
• a band edge crossed on the leg updates its band state under both answers, whether or not its report is the selected one

Diagnostics

• Instance-mark-log
• Instance-mark-state

marks-read-final-value

Applies when Lines read is The final value.

When a change passes a limit, Instance marks read the final outward endpoint: the stored value, or the consuming limit on a lap. A mark at or past the reached limit never observes the raw candidate, and every report from that leg carries the stored endpoint or consuming limit as its after value.

Given

a change whose raw candidate passes a limit and a mark at or past the limit the change reaches

When

• the change settles without refusal

Then

• outward marks test the stored endpoint or the consuming limit
• no outward mark observes a number beyond the limit
• every report from that leg carries the stored endpoint, or the consuming limit, as its after value — never the raw candidate

Diagnostics

• Instance-operation-record
• Instance-mark-log

marks-read-raw-result

Applies when Lines read is The raw result.

When a change passes a limit, Instance marks on the outward leg read the raw candidate and report it as after. Refusal exposes no raw result; lap and leftover legs read stored endpoints.

Given

a change whose raw candidate passes a limit and a mark that only that candidate reaches

When

• the change settles without refusal

Then

• outward marks test the raw candidate before the edge handles it
• their reports use that tested candidate as after
• a refused change exposes no raw result, and lap and leftover legs test stored endpoints

Diagnostics

• Instance-operation-record
• Instance-mark-log

band-enters-at-fixed-line

Applies when row enter on is Line and row enter value kind is Number.

Row.id enters when a Row.enter direction leg reaches the entering line at Row.enter value, read as its enter-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at Value cite max. It reports the state change subject to the value's jumped-lines answer.

Given

Row.id out and Instance on the non-entered side of the entering line at Row.enter value, read as its enter-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at Value cite max

When

• one Row.enter direction leg changes the entering edge from unreached to reached

Then

• Row.id enters and reports once, subject to jumped-lines
• the report carries the row id and operation evidence

Diagnostics

• Instance-band-state
• Instance-mark-log

band-enters-at-cited-line

Applies when row enter on is Line and row enter value kind is Citation.

Row.id enters when a Row.enter direction leg reaches the cited entering line Row.enter value key, read fresh. The test names the address and restates no number.

Given

Row.id out and Instance on the non-entered side of the cited entering line Row.enter value key

When

• one Row.enter direction leg changes the entering edge from unreached to reached

Then

• Row.enter value key is read fresh and this test restates no number
• Row.id enters and reports once, subject to jumped-lines

Diagnostics

• Instance-band-state
• Instance-comparison-log
• Instance-mark-log

band-leaves-at-fixed-line

Applies when row leave on is Line and row leave value kind is Number.

Row.id leaves when a Row.leave direction leg reaches the leaving line at Row.leave value, read as its leave-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at Value cite max.

Given

Row.id in and Instance on the non-leaving side of the leaving line at Row.leave value, read as its leave-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at Value cite max

When

• one Row.leave direction leg changes the leaving edge from unreached to reached

Then

• Row.id leaves and reports once, subject to jumped-lines

Diagnostics

• Instance-band-state
• Instance-mark-log

band-leaves-at-cited-line

Applies when row leave on is Line and row leave value kind is Citation.

Row.id leaves when a Row.leave direction leg reaches the cited leaving line Row.leave value key, read fresh. The test names the address and restates no number.

Given

Row.id in and Instance on the non-leaving side of the cited leaving line Row.leave value key

When

• one Row.leave direction leg changes the leaving edge from unreached to reached

Then

• Row.leave value key is read fresh and this test restates no number
• Row.id leaves and reports once, subject to jumped-lines

Diagnostics

• Instance-band-state
• Instance-comparison-log
• Instance-mark-log

band-event-enters

Applies when row enter on is Event.

The event at Row.enter declared in turns Row.id on. This event edge is not inferred from the held number.

Given

Row.id out

When

• the event at Row.enter declared in occurs

Then

• Row.id enters and records that event as its cause

Diagnostics

• Instance-band-state
• Instance-band-event-record

band-event-or-wait-leaves

Applies when row leave on is Event or After a wait.

Row.id leaves when Bind leave phrase. Its state is controlled by that declared edge, not inferred from the held number.

Given

Row.id in

When

• Bind leave phrase

Then

• Row.id leaves and records the declared cause

Diagnostics

• Instance-band-state
• Instance-band-event-record

band-wait-repeat

Applies when row leave on is After a wait.

While Row.id waits to leave, another entry Bind repeat phrase. The wait address is Row.leave declared in; this test restates no duration.

Given

Row.id in with the wait at Row.leave declared in running

When

• its entering edge occurs again before the wait finishes

Then

• the new entry Bind repeat phrase
• Row.id remains in until the resulting wait completes

Diagnostics

• Instance-band-state
• Instance-band-wait

band-starts-as-declared

Applies when row starts is In or Out.

At creation, Row.id Bind start phrase and reports nothing. The starting value is cited at Value cite initial; this test restates no number.

Given

creation of Instance at Value cite initial

When

• the initial band state is stored

Then

• Row.id Bind start phrase
• creation reports no mark

Diagnostics

• Instance-band-state
• Instance-mark-log

band-starts-from-initial

Applies when row starts is Read from initial and row enter on is Line and row leave on is Line.

At creation, Row.id reads Value cite initial against both its line edges: in exactly when the entering side holds and the leaving side does not. Creation reports nothing. An event-edged band that answers read-from-initial starts out; the event-entered case is checked by its own template.

Given

creation of Instance at Value cite initial, with the line geometry for Row.id recorded

When

• the initial band state is stored

Then

• Row.id starts in exactly when Value cite initial sits on the reached side of its entering edge and not on the reached side of its leaving edge, each per that edge's declared direction
• creation reports no mark

Diagnostics

• Instance-band-state
• Instance-comparison-log
• Instance-mark-log

event-entered-band-starts-out

Applies when row starts is Read from initial and row enter on is Event.

An event-edged band that answers read-from-initial starts out; Row.id enters by an event, so there is no line geometry to read against the starting value. Creation reports nothing.

Given

creation of Instance with the Row.id entering event not yet observed

When

• the initial band state is stored

Then

• Row.id starts out: an event-edged band that answers read-from-initial starts out
• creation reports no mark

Diagnostics

• Instance-band-state
• Instance-mark-log

event-left-band-starts-out

Applies when row starts is Read from initial and row leave on is Event or After a wait.

Row.id leaves by an event or a wait, so it is event-edged whatever its entering edge, and an event-edged band that answers read-from-initial starts out. Creation reports nothing. Together with the event-entered template this covers every event-edged shape.

Given

creation of Instance where Row.id leaves by an event or a wait

When

• the initial band state is stored

Then

• Row.id starts out: a band with any event or wait edge is event-edged, and an event-edged band that answers read-from-initial starts out
• creation reports no mark

Diagnostics

• Instance-band-state
• Instance-mark-log

band-blocks-selected-movement

Applies when row blocks change is Blocks rises or Blocks falls or Blocks all.

While Row.id is in, blocks-rises blocks rising imposed changes, costs, and drifts; blocks-falls blocks falling ones; blocks-all blocks both directions — each as far as this adoption can construct the attempt. Blocking happens before settlement, and a blocked drift records the block but has no receiver. Each set, reset, limit move, and lap movement this adoption can construct settles unblocked; if it can construct none, that clause asserts nothing.

Given

Row.id in

When

• of the movements this adoption can construct: where this row answers blocks-rises, a rising change, cost, and drift are each attempted; where it answers blocks-falls, a falling change, cost, and drift are each attempted; where it answers blocks-all, changes, costs, and drifts are attempted in both directions; a movement kind this adoption cannot construct asserts nothing here
• each of a set, a reset, a limit move, and a lap movement that this adoption can construct settles; an adoption that can construct none of them asserts nothing here

Then

• each attempted selected imposed change, cost, and drift is discarded before fractional handling and records blocked
• a blocked drift has no receiver and contributes nothing to a composed batch
• each of a set, a reset, a limit move, and a lap movement that this adoption can construct settles unblocked; an adoption that can construct none of them asserts nothing here

Diagnostics

• Instance-blocked-record
• Instance-operation-record

event-entered-band-survives-silent-recompute

Applies when row enter on is Event.

Because Row.id has an event entering edge, each silent recompute this adoption can perform — a silent set, a reset declaring recompute-from-target, or a cited limit move — preserves its state. Where none can be performed, this test asserts nothing. The band stays in until its own leaving edge occurs.

Given

Row.id in after the event at Row.enter declared in

When

• each silent recompute this adoption can perform — a set whose value answers does-a-set-fire-lines with silent, a reset row declaring recompute-from-target, a limit move on a cited limit — settles; where the adoption can perform none, this test asserts nothing

Then

• Row.id remains in unless its own leaving edge occurs

Diagnostics

• Instance-band-state
• Instance-operation-record

event-left-band-survives-silent-recompute

Applies when row leave on is Event or After a wait.

Because Row.id has an event or wait leaving edge, each silent recompute this adoption can perform — a silent set, a reset declaring recompute-from-target, or a cited limit move — preserves its state. Where none can be performed, this test asserts nothing. Only its declared edges change it.

Given

Row.id in a known state before recomputation

When

• each silent recompute this adoption can perform — a set whose value answers does-a-set-fire-lines with silent, a reset row declaring recompute-from-target, a limit move on a cited limit — settles; where the adoption can perform none, this test asserts nothing

Then

• Row.id keeps its prior state through every recompute

Diagnostics

• Instance-band-state
• Instance-operation-record

line-once-never-rearms

Applies when row refire is Once and row rearm is Never.

Row.id reports on its first qualifying crossing and never re-arms. Later crossings still update reached state but do not report.

Given

Row.id armed with its fresh allowance

When

• Instance makes two or more qualifying crossings over the run

Then

• only the first crossing reports
• no event or passage of time restores its allowance

Diagnostics

• Instance-mark-log
• Instance-line-allowance

line-set-number-never-rearms

Applies when row refire is A set number of times and row rearm is Never.

Row.id has a lifetime allowance of Row.times reports. It never re-arms after that allowance is exhausted.

Given

Row.id armed with lifetime allowance Row.times

When

• Instance makes more than Row.times qualifying crossings over the run

Then

• exactly Row.times crossings report
• the exhausted allowance is never restored

Diagnostics

• Instance-mark-log
• Instance-line-allowance

line-starts-armed-as-declared

Applies when row starts armed is Armed or Disarmed.

A Row.id row that explicitly starts armed can report its first qualifying crossing if it has allowance. A row that explicitly starts disarmed Bind disarmed phrase. When starts-armed is omitted, line-crosses-fixed-position and line-crosses-cited-position check the default armed state.

Given

creation of Instance with Row.id declaring an explicit starting arm state

When

• the first qualifying crossing occurs

Then

• a row that explicitly starts armed can report its first qualifying crossing if it has allowance
• a row that explicitly starts disarmed Bind disarmed phrase
• creation itself reports nothing

Diagnostics

• Instance-line-allowance
• Instance-mark-log

band-enter-share-follows-ceiling

Applies when row enter unit is Share of the ceiling.

Row.id places its entering line at a declared share of Value cite max, read fresh for the comparison. This test restates neither number.

Given

Row.id out and the marked top at Value cite max recorded before comparison

When

• a movement crosses the entering share declared by the row

Then

• the entering position is the row's share multiplied by the fresh value at Value cite max
• the entering position may be fractional; it is compared, never stored
• Row.id enters if the directional reached state changes

Diagnostics

• Instance-comparison-log
• Instance-band-state

band-leave-share-follows-ceiling

Applies when row leave unit is Share of the ceiling.

Row.id places its leaving line at a declared share of Value cite max, read fresh for the comparison. This test restates neither number.

Given

Row.id in and the marked top at Value cite max recorded before comparison

When

• a movement crosses the leaving share declared by the row

Then

• the leaving position is the row's share multiplied by the fresh value at Value cite max
• the leaving position may be fractional; it is compared, never stored
• Row.id leaves if the directional reached state changes

Diagnostics

• Instance-comparison-log
• Instance-band-state

band-exact-landing-override

Applies when row counts at line is At the line counts or Must pass the line.

The Row.id row overrides the value-wide exact-landing choice for each line edge this row has (a band may have only one). Its at-the-line-counts answer counts an exact landing; its must-pass-the-line answer requires movement strictly past the edge.

Given

Row.id once approaching each line edge this row has (a band may have only one)

When

• one movement lands exactly on an edge and another strictly passes it

Then

• where this row declares at-the-line-counts, an exact landing counts as reaching each line edge this row has (a band may have only one)
• where this row declares must-pass-the-line, an exact landing does not reach a line edge and the movement must pass it
• the row's declared answer overrides Instance's value-wide exact-landing answer

Diagnostics

• Instance-band-state
• Instance-mark-log

set-stores-target-without-raw-result

Applies for every adoption

Row.id reads Bind mode phrase at Row.target key when Row.trigger declared in offers it. A set with a declared enabling condition is offered only while that condition holds. Bind settlement phrase: it has no raw result and does not pass through small-change. This test names the addresses and restates no number.

Given

Row.id enabled, with target source Row.target key and trigger Row.trigger declared in

When

• the trigger offers Bind mode phrase

Then

• a set with a declared enabling condition is offered only while that condition holds
• Bind settlement phrase
• the set has no raw result and marks can observe only its successful stored outcome
• fractional small-change handling is not applied

Diagnostics

• Instance-set-record
• Instance-value-before-after

outside-set-clamps

Applies when A set outside the range is Pull it to the nearer limit.

A set outside the range stores the nearer passed limit. It exposes no rejected target as a raw result, hands back no extra, and starts no lap. The limits are Value cite min and Value cite max; this test restates neither number. Where no declared set can target outside the range, it asserts nothing.

Given

named sets targeting once above Value cite max and once below Value cite min, where this adoption's declared sets can construct such targets; an adoption whose sets can never target outside the range asserts nothing here

When

• each set settles

Then

• the high target stores exactly Value cite max and the low target stores exactly Value cite min
• neither rejected target is a raw result
• the set returns no extra and starts no lap

Diagnostics

• Instance-set-record
• Instance-value-after

outside-set-refuses

Applies when A set outside the range is Refuse the set.

A set outside the range is refused whole. Instance keeps its value and residue, and no mark fires. The test cites Value cite min and Value cite max and restates neither number.

Given

Instance holding value v and, when present, residue r; a named set targets outside Value cite min and Value cite max

When

• the set is offered

Then

• the set is refused to its caller
• the stored value remains v and residue remains r
• no mark reports or changes state from movement

Diagnostics

• Instance-set-record
• Instance-value-before-after
• Instance-residue-before-after

outside-set-stores-as-sent

Applies when A set outside the range is Store it as sent.

An outside set stores its target exactly as sent, but only beyond an ordinary edge that allows Instance to pass. The target is the stored outcome, not a separate raw result.

Given

a named set whose target is beyond a limit whose ordinary edge answer allows the value to pass

When

• the set settles

Then

• the exact target is stored
• the set exposes no separate raw result

Diagnostics

• Instance-set-record
• Instance-value-after

set-fires-marks-as-change

Applies when Does a set fire lines is Treat it as a change.

A successful set tests marks along its stored movement and reports them as jumped-lines directs. Because a set crossing no line can store the same value under either answer, this test also reads the operation record that distinguishes mark testing from silent recompute.

Given

a named set whose accepted stored target crosses at least one mark, plus a set whose target crosses no mark, with an operation record distinguishing reports from silent state updates

When

• each set settles

Then

• crossed marks test the successful stored movement and report as jumped-lines directs
• the operation record identifies this answer even when the absence of a crossing makes the stored result indistinguishable from a silent recompute

Diagnostics

• Instance-set-record
• Instance-mark-log
• Instance-mark-state

set-updates-marks-silently

Applies when Does a set fire lines is Silent.

A successful set silently recomputes bare lines and line-geometry bands from its stored target. Event-edged bands keep state and nothing reports. The operation record is required because a set crossing no line can leave the same stored value under either answer.

Given

a named set whose accepted stored target crosses marks, with an operation record naming silent recomputation

When

• the set settles

Then

• bare-line reached state and line-geometry band state recompute from the stored target
• event-edged bands keep state and no mark reports
• the operation record distinguishes silent recompute from treat-it-as-a-change even when no line was crossed

Diagnostics

• Instance-set-record
• Instance-mark-log
• Instance-mark-state

successful-set-clears-residue

Applies when Small change is Save the fraction.

A successful Row.id set clears Instance residue in the same commit. The target comes from Row.target key; this test restates no number. A refused set leaves residue unchanged.

Given

Instance holding nonzero signed residue with Row.id enabled

When

• Row.id successfully stores its target from Row.target key

Then

• residue becomes zero in the same commit as the stored target

Diagnostics

• Instance-set-record
• Instance-residue-before-after

cost-pays-exactly

Applies for every adoption

When affordable and unblocked, Row.id moves Instance Bind direction phrase by the amount at Row.amount key after small-change resolves it, updating residue accordingly. The report to Row.action declared in carries no refusal and no shortage. This test names the addresses and restates no number.

Given

Instance with enough room Bind direction phrase to pay the non-negative amount at Row.amount key, and with no active band blocking the change's direction

When

• the action at Row.action declared in attempts Row.id

Then

• the stored value moves Bind direction phrase by the amount at Row.amount key after small-change resolves it, and residue updates accordingly
• the report to the action carries no refusal and no shortage
• marks test the paid movement normally

Diagnostics

• Instance-value-before-after
• Instance-residue-before-after
• Instance-cost-record
• Instance-mark-log

value-wide-cost-refuses

Applies when Not enough room is Refuse the action.

For a cost row without an override, an unaffordable cost is refused whole. Movement and provisional residue are discarded together; value, residue, and every mark stay unchanged, and the caller receives the shortage.

Given

a cost row without an answer override, insufficient room for its full provisional movement, stored value v, residue r when present, and unchanged mark state m

When

• the cost is attempted

Then

• the action is refused with its positive shortage
• movement and provisional residue are discarded together
• stored value v, residue r, and all mark state m remain unchanged

Diagnostics

• Instance-cost-record
• Instance-value-before-after
• Instance-residue-before-after
• Instance-mark-state

value-wide-cost-takes-what-fits

Applies when Not enough room is Take what fits.

For a cost row without an override, an unaffordable cost takes only what fits. Instance moves to the limiting edge, recomputes residue from the approved amount only, reports the positive amount paid, and tests marks normally.

Given

a cost row without an answer override and insufficient room for its full provisional movement

When

• the cost is attempted

Then

• the stored value moves to the limiting edge
• movement and residue are recomputed from only the approved amount
• the caller receives the positive amount paid and marks test that movement normally

Diagnostics

• Instance-cost-record
• Instance-value-before-after
• Instance-residue-before-after
• Instance-mark-log

cost-row-override-refuses

Applies when Not enough room is Take what fits and row answer is Refuse the action.

Row.id overrides the value-wide cost answer. When it cannot be paid in full, it refuses the action at Row.action declared in, reports the shortage, and changes neither value nor residue.

Given

insufficient room to pay Row.id in full, with stored value v and residue r when present

When

• the action at Row.action declared in attempts the amount at Row.amount key

Then

• the row's refuse-the-action answer wins over the value-wide answer
• the caller receives refusal and shortage
• value, residue, and every mark remain unchanged

Diagnostics

• Instance-cost-record
• Instance-value-before-after
• Instance-residue-before-after
• Instance-mark-state

cost-row-override-partial

Applies when Not enough room is Refuse the action and row answer is Take what fits.

Row.id overrides the value-wide cost answer. When full payment does not fit, Instance moves to the limiting edge, recomputes residue from the approved part only, and reports the positive amount paid to Row.action declared in.

Given

insufficient room to pay Row.id in full

When

• the action at Row.action declared in attempts the amount at Row.amount key

Then

• the row's take-what-fits answer wins over the value-wide answer
• Instance moves to the limiting edge and reports the positive amount paid
• movement and residue are recomputed from only that approved amount
• marks test that movement normally

Diagnostics

• Instance-cost-record
• Instance-value-before-after
• Instance-residue-before-after
• Instance-mark-log

drift-moves-value

Applies for every adoption

Instance changes on its own under Row.id. Each time Bind cadence phrase, its contribution is Bind resolution phrase, then clipped to Row.stops at key, so it Bind direction phrase by no more than Bind amount phrase. The amount and stop are stated at their addresses; this test restates neither number.

Given

Instance away from Row.stops at key, with Row.id eligible, every interrupt row for it allowing it, and no other drift eligible

When

• Bind cadence phrase, with nobody acting

Then

• the contribution is Bind resolution phrase, then clipped to Row.stops at key, so Instance Bind direction phrase by no more than Bind amount phrase
• the operation commits once with no partly settled state observable
• marks test the movement once

Diagnostics

• Instance-value-before-after
• Instance-drift-log
• Instance-mark-log

continuous-drift-uses-elapsed-time

Applies when row cadence is Per real second.

Row.id accrues continuously. It multiplies the rate at Row.step amount key by elapsed cited-clock time, not frame count, and sends fractional accrual through small-change. This test restates no rate.

Given

Row.id eligible over equal cited-clock durations rendered with different frame counts

When

• each duration settles

Then

• each contribution is the rate at Row.step amount key multiplied by elapsed cited-clock time
• equal elapsed time produces equal provisional movement regardless of frame count
• fractional accrual passes through small-change

Diagnostics

• Instance-clock-trace
• Instance-drift-log

named-moment-drift-uses-citation

Applies when row cadence is At a named moment.

Row.id contributes only when the moment at Row.moment declared in occurs. Passing time alone does not run it.

Given

Row.id eligible before the moment at Row.moment declared in

When

• time passes without that moment, then the named moment occurs

Then

• Row.id contributes nothing before the moment
• it contributes once when the cited moment occurs

Diagnostics

• Instance-drift-log
• Instance-event-log

declared-drift-amount-rule

Applies when row amount kind is Depends on state or Grows while it runs.

Row.id does not use one fixed contribution. It Bind shape phrase, with the base at Row.step amount key. The test names both addresses and restates neither number nor rule.

Given

Row.id eligible at two states or two points in its run for which Row.amount declared in gives different amounts

When

• one contribution settles in each case

Then

• each contribution Bind shape phrase
• Row.step amount key supplies the declared base amount and this test restates neither the amount nor the rule

Diagnostics

• Instance-drift-log
• Instance-value-trace

drift-stops

Applies for every adoption

Both at-stop answers leave Instance stored at Row.stops at key, so the stored value cannot distinguish them. This probe reads the at-stop step record: Bind landing phrase. Once stored at that address, Row.id is ineligible and offers nothing. The test restates no stop or amount.

Given

Instance less than one Row.id contribution from Row.stops at key, Row.id eligible and alone, and an at-stop step record naming the offered amount, every intermediate value, the correction, and the stored value afterwards

When

• the next offered contribution would pass Row.stops at key

Then

• the step record names the amount offered before clipping or correction
• Bind landing phrase
• the stored value is exactly Row.stops at key under either answer
• after an overshoot, correction reports no mark and recomputes reached state from the stored stop
• Row.id is ineligible and offers nothing while the value rests at its stop

Diagnostics

• Instance-at-stop-step-record
• Instance-offered-amount
• Instance-intermediate-value
• Instance-value-after

drift-clips-at-consuming-ceiling

Applies when At the ceiling is Start a lap and row direction is Rises.

A Row.id contribution that reaches the consuming ceiling at Value cite max clips there without consuming it. It can report marks on that leg, but it never reports a lap. The test restates no limit.

Given

Row.id eligible below the consuming ceiling at Value cite max, with its offered contribution large enough to pass it, with Row.stops at key at or beyond Value cite max, so the ceiling is the binding stop

When

• the drift settles alone

Then

• the drift clips at Value cite max
• no lap reports and no lap movement occurs
• marks test the clipped drift leg normally

Diagnostics

• Instance-drift-log
• Instance-lap-log
• Instance-mark-log

drift-clips-at-consuming-floor

Applies when At the floor is Start a lap and row direction is Falls.

A Row.id contribution that reaches the consuming floor at Value cite min clips there without consuming it. It can report marks on that leg, but it never reports a lap. The test restates no limit.

Given

Row.id eligible above the consuming floor at Value cite min, with its offered contribution large enough to pass it, with Row.stops at key at or below Value cite min, so the floor is the binding stop

When

• the drift settles alone

Then

• the drift clips at Value cite min
• no lap reports and no lap movement occurs
• marks test the clipped drift leg normally

Diagnostics

• Instance-drift-log
• Instance-lap-log
• Instance-mark-log

drift-approaches-anchor

Applies when row direction is Toward the anchor.

Row.id uses Value cite anchor only to choose its side: it rises below the anchor and falls above it. Eligibility and clipping use Row.stops at key; while stored at that stop the row is ineligible. Where the stop sits on a consuming limit, the drift clips there without consuming it.

Given

Instance once below and once above Value cite anchor, with Row.id eligible because the value is away from Row.stops at key, every interrupt row allowing it, and no other drift eligible

When

• one contribution settles from each side

Then

• the lower value rises below the anchor and the higher value falls above it, so the anchor chooses the side's direction
• each contribution clips at Row.stops at key and never passes that stop
• the row is ineligible while stored exactly at Row.stops at key
• where the stop sits on a consuming limit, the drift clips there without consuming it

Diagnostics

• Instance-drift-log
• Instance-value-trace

drifts-add-together

Applies when Drifts together is Add them up.

When several Instance drifts run together, each eligible contribution clips to its own stop, then the signed amounts add. The combined movement resolves small-change and tests marks once.

Given

at least two eligible drifts at one step, after blocked rows are removed and each contribution is clipped to its own stop

When

• the step settles

Then

• the signed clipped contributions are summed
• small-change resolves once and marks test once for the combined movement

Diagnostics

• Instance-drift-batch-record
• Instance-value-before-after
• Instance-mark-log

largest-drift-wins

Applies when Drifts together is Only the largest.

When several Instance drifts run together, only the largest clipped absolute contribution settles. Row order breaks a tie, and a skipped growing drift does not advance its ramp.

Given

at least two eligible drifts at one step, including equal clipped absolute magnitudes and a growing row that can be skipped

When

• the step settles

Then

• only the greatest clipped absolute magnitude settles
• row order selects an exact tie
• a skipped growing row does not advance its ramp for that step

Diagnostics

• Instance-drift-batch-record
• Instance-ramp-state

drifts-settle-in-row-order

Applies when Drifts together is In row order.

When several Instance drifts run together, they settle separately in written row order. Each row sees the prior row's committed state and tests its own marks.

Given

at least two eligible drifts at one step whose separate settlements produce observable intermediate value or mark differences

When

• the step settles

Then

• each eligible row settles from block through report in written row order
• each row sees the state committed by the prior row and tests marks separately

Diagnostics

• Instance-drift-batch-record
• Instance-value-trace
• Instance-mark-log

condition-interrupt-controls-drift

Applies when row kind is Off while condition or Runs only while condition.

Row.id Bind allow phrase, using the condition at Row.condition declared in. Every interrupt row naming Row.drift must allow it before that drift runs.

Given

the condition at Row.condition declared in observed once false and once true, with every other interrupt row for Row.drift allowing it

When

• Row.drift reaches an occurrence in each condition state

Then

• Row.id Bind allow phrase
• the drift runs only when this row and every other row naming Row.drift allow it

Diagnostics

• Instance-interrupt-state
• Instance-drift-log

pause-interrupt-controls-drift

Applies when row kind is Paused after event.

After Row.event declared in, Row.id pauses Row.drift and Bind length phrase. A repeated event Bind repeat phrase. Every row naming the drift must allow it before it resumes.

Given

Row.drift otherwise allowed by every interrupt row

When

• the event at Row.event declared in occurs twice before the pause completes

Then

• Row.id Bind length phrase and prevents Row.drift from running during the wait
• the second event Bind repeat phrase
• Row.drift runs again only after this and every other row naming it allow it

Diagnostics

• Instance-interrupt-state
• Instance-pause-record
• Instance-drift-log

state-dependent-pause-length

Applies when row pause length kind is Depends on state.

Row.id reads the state-dependent pause rule at Row.pause length declared in, using the base at Row.pause length key. The test names both addresses and restates neither duration nor rule.

Given

two states for which Row.pause length declared in gives different pause lengths

When

• the event at Row.event declared in starts Row.id in each state

Then

• each wait follows Row.pause length declared in using the base at Row.pause length key
• this test restates neither duration nor rule

Diagnostics

• Instance-pause-record
• Instance-interrupt-state

interrupt-conjunction-holds

Applies for every adoption

Even while Row.id allows Row.drift, another row for that drift can forbid it. The drift runs only when every row naming it allows it; where this adoption has no such pair, this test asserts nothing.

Given

another interrupt row naming Row.drift and currently forbidding it while Row.id allows it; where this adoption has no such pair, this test asserts nothing

When

• the drift reaches an occurrence while those row states hold

Then

• Row.drift does not run
• every interrupt row for one drift must allow it before it runs

Diagnostics

• Instance-interrupt-state
• Instance-drift-log

reset-returns-silently

Applies for every adoption

At Row.happens at, Row.id silently returns Instance to its named target, or to Value cite initial when sets-value-to-key is omitted (with a cited initial, the number read at creation). Where this adoption declares any line or band, crossing one on the return path reports nothing. The reset does not lap or pass through small-change.

Given

Instance away from the target used by Row.id

When

• the moment at Row.happens at occurs

Then

• Row.id stores its sets-value-to-key target when present, otherwise Value cite initial (with a cited initial, the number read at creation)
• where this adoption declares any line or band, the return path crossing one reports nothing
• the reset reports no lap
• the return is one absolute repositioning and does not pass through small-change

Diagnostics

• Instance-reset-record
• Instance-value-after
• Instance-mark-log

reset-handles-residue

Applies when Small change is Save the fraction.

When Row.id settles, it Bind residue phrase.

Given

Instance holding nonzero signed residue before Row.id

When

• the reset at Row.happens at settles

Then

• Row.id Bind residue phrase in the same silent commit

Diagnostics

• Instance-reset-record
• Instance-residue-before-after

reset-handles-lines-and-bands

Applies for every adoption

Row.id Bind arm phrase. Band states respond as the row's resets-bands answer directs; a row that omits resets-bands keeps every band's state, which is this definition's documented default. All state changes are silent.

Given

changed line allowances and band states before Row.id

When

• the reset at Row.happens at settles

Then

• Row.id Bind arm phrase
• band states respond as the row's resets-bands answer directs, and a row that omits resets-bands keeps every band's state — that omission is this definition's documented default
• every line's reached state is recomputed and stored from the reset target
• all state changes are silent

Diagnostics

• Instance-reset-record
• Instance-line-allowance
• Instance-band-state
• Instance-mark-log

reset-applies-explicit-band-choice

Applies when row resets bands is Return to starts or Recompute from target or Keep.

An explicit return-to-starts restores declared band starts; recompute-from-target recomputes line geometry and keeps event-edged bands; keep preserves every band's prior state unchanged. The presence gate prunes a row that omits resets-bands; the general reset template checks that omission's documented keep default.

Given

for return-to-starts, band states different from their declared starts; for recompute-from-target, line-geometry band states different from what the reset target would produce; for keep, a prior band state that differs from what both return-to-starts and recompute-from-target would produce, where this adoption can construct one; where it cannot, keep is checked only as no band state changing

When

• the reset at Row.happens at settles

Then

• where this row declares return-to-starts, it restores every band to its declared starts state
• where this row declares recompute-from-target, it recomputes every line-geometry band from the reset target and keeps every event-edged band
• where this row declares keep, it preserves every band's prior state unchanged
• the change is silent

Diagnostics

• Instance-reset-record
• Instance-band-state
• Instance-mark-log

limit-move-refills-ceiling

Applies when When a limit moves is Refill to the new ceiling.

Where Value cite max is cited and moves, Instance fills to the fresh max. Where Value cite min is cited and moves alone, the held value stays unless it falls below the fresh min. An adoption citing only one limit exercises only that clause. A limit move never laps and never clears residue.

Given

Instance holding any value while each cited limit this adoption can move is exercised separately

When

• each cited limit this adoption can move settles in its own case

Then

• where Value cite max is a cited limit that moves, the fresh max is stored as the value
• where Value cite min is cited and moves alone, the value is kept unless it falls below the fresh min
• an adoption citing only one limit exercises only that clause
• neither movement starts a lap and residue is unchanged

Diagnostics

• Instance-limit-move-record
• Instance-value-before-after

limit-move-keeps-number

Applies when When a limit moves is Keep the number.

A moving limit leaves Instance's number alone while it fits. If it no longer fits, the value clamps to the moved limit even where an ordinary change could pass it. Residue stays and no lap starts.

Given

Instance holding values once inside and once outside the range made by a cited limit move

When

• the limit move settles

Then

• an inside value remains unchanged
• an outside value clamps to the fresh limit it passed even if an ordinary change could pass that limit
• residue is unchanged and no lap starts

Diagnostics

• Instance-limit-move-record
• Instance-value-before-after

limit-move-keeps-share

Applies when When a limit moves is Keep the share.

A moving limit keeps Instance at the same normalized share of Value cite min to Value cite max. Bind number phrase. An old range collapsed to nothing by cited limits uses the fresh min, though range-nonempty makes that unreachable for declared numbers. Residue is unchanged.

Given

Instance at a known normalized share immediately before a non-empty old range changes

When

• the cited limit move settles

Then

• one absolute repositioning stores the same normalized share in the new range
• Bind number phrase
• an old range collapsed to nothing by cited limits uses the fresh min; the declaration rule range-nonempty makes this unreachable for declared numbers
• residue is unchanged

Diagnostics

• Instance-limit-move-record
• Instance-share-calculation
• Instance-value-before-after

limit-move-uses-declared-number

Applies when When a limit moves is Pull it to a declared number.

A limit move keeps Instance's number when it still fits. Otherwise it stores the fresh safe number at Value cite out of range lands on. The test names the address and restates no number.

Given

Instance once inside and once outside the fresh range after a cited limit move

When

• each limit move settles

Then

• the inside value remains unchanged
• the outside value stores Value cite out of range lands on
• the target is read fresh and lies inside the new range
• residue is unchanged and no lap starts

Diagnostics

• Instance-limit-move-record
• Instance-value-before-after

limit-move-leaves-number-alone

Applies when When a limit moves is Leave the number alone.

A moving limit does not reposition Instance. A held number may remain beyond the moved landmark only where the matching ordinary edge answer permits it. Residue stays and no lap starts.

Given

Instance holding a number that a cited limit moves past, with the matching ordinary edge answer allowing the value beyond that limit

When

• the limit move settles

Then

• the stored number remains unchanged even outside the fresh landmark
• residue is unchanged and no lap starts

Diagnostics

• Instance-limit-move-record
• Instance-value-before-after

limit-move-never-fires-bare-line

Applies when When a limit moves is Refill to the new ceiling or Keep the number or Keep the share or Pull it to a declared number or Leave the number alone.

After a limit move, Instance refreshes the reached state of bare line Row.id but never fires it. Where either limit answers start-a-lap, a limit move landing the value exactly on that edge does not consume it.

Given

a cited limit move that changes Row.id reached state

When

• the limit and any resulting held-value change finish settling

Then

• Row.id stores fresh reached state but reports nothing
• where either limit answers start-a-lap, a limit move landing the value exactly on that edge does not consume it

Diagnostics

• Instance-limit-move-record
• Instance-mark-log
• Instance-mark-state

limit-move-recomputes-band

Applies when When a limit moves is Refill to the new ceiling or Keep the number or Keep the share or Pull it to a declared number or Leave the number alone and row enter on is Line and row leave on is Line.

After a limit move, line-geometry band Row.id recomputes and stores its fresh state. Where that state changed, it reports the change with cause limit-moved; an unchanged state reports nothing.

Given

a cited limit move with the prior Row.id state recorded

When

• the limit and any resulting held-value change finish settling

Then

• Row.id recomputes and stores its fresh line-geometry state
• where that fresh state differs from the prior recorded state, Row.id reports the change with cause limit-moved; where it does not differ, Row.id reports nothing

Diagnostics

• Instance-limit-move-record
• Instance-mark-log
• Instance-mark-state

limits-hold

Applies for every adoption

For every operation in this adoption's verification scope — Inputs scope — Bind min clause, and Bind max clause. A cited limit whose answer is no-floor or no-ceiling remains a landmark. The adoption supplies scope and seeds through verification inputs; each half of the oracle is the one its own edge answer permits.

Holds

after every operation, Bind min clause, and Bind max clause. A cited limit whose answer is no-floor or no-ceiling remains a landmark

Seeds

Inputs seeds

Scope

Inputs scope

Diagnostics

• Instance-value-trace
• Instance-first-violating-operation