Pools & meters

Boss stagger

boss-stagger · an adoption of Ranged value, version 1

Tests included

Use in your game

Opens the authoring tool with these answers and settings already filled in. You still add your game's own rules and tuning.

What is in the ZIP

The ZIP holds the adoption and its acceptance tests. In the authoring tool, choose Add contract and pick this ZIP. If you keep your design as files, put them in contracts/.

The contract behind it

Covers health, stamina, oxygen, XP and other values with a marked bottom and top. It decides how changes meet those limits, how named lines fire, how costs are paid, and how the value can move on its own. Sources, rates, display and effects belong to the game's own rules.

Read the full Ranged value contract →

Questions

The supplied answer is marked on each question. Pick other answers to see what changes. Nothing is saved here: the ZIP and the authoring tool use the supplied answers.

Can this value hold a fraction, or is it always a whole number?

Choices for Can this value hold a fraction, or is it always a whole number?
Supplied answer The stored value is always whole. A health bar can show 7 or 8, never 7.5.

A change with a fractional part passes through small-change before any limit or mark reads it. Every absolute stored target and mark must resolve to a whole number.

Fractions stay exactly as sent. An oxygen meter can rest at 7.5.

Every finite change lands at full precision. No saved-fraction store exists.

Why this is asked

Whole and fractional values handle small changes differently. A health bar may show only whole points while oxygen keeps decimals.

A change contains part of a point. What happens to that part?

Asked when
Number kind is Whole number.
If not asked
This value keeps fractional changes exactly as sent.
Choices for A change contains part of a point. What happens to that part?
Use the nearer whole change, with an exact half going up the scale. A health gain of 2.5 becomes 3.

Round the signed change to the nearest integer; ties go toward positive infinity. Discard the difference.

Use the nearer whole change, with an exact half going away from zero. A karma loss of 2.5 becomes −3.

Round to the nearest integer; ties choose the integer with the greater absolute magnitude. Discard the difference.

Drop the fractional part toward zero. A poison drain of 0.7 health does nothing that step.

Remove the signed fractional part toward zero and discard it.

Every nonzero change moves at least one whole point. Chip damage of 0.1 removes 1 health.

Round every non-integer signed change away from zero and discard the difference.

Supplied answer Save leftover fractions until they make a whole point. Two hits worth 0.5 poise each add 1 poise together.

Move the whole part now. Add only the signed fractional remainder to one saved-fraction store. Remove complete multiples of fraction-step toward zero, move by that many whole units, and keep the remainder. Sets always clear the store; named resets and starting over at a limit use their own clearing choices.

Landing exactly on a line or limit: does that count as reached?

Choices for Landing exactly on a line or limit: does that count as reached?
Supplied answer Yes, touching it counts. Health falling to exactly 25 fires a warning set at 25.

A rising mark at t is reached at value greater than or equal to t; a falling mark is reached at value less than or equal to t. An exact landing may consume a limit.

No, the value must pass it. Health must fall below 25 before a warning set at 25 fires.

A rising mark at t is reached only above t; a falling mark is reached only below t. An exact landing does not consume a limit.

Starting again at a limit is a lap. What happens when a change would push this value above its marked top?

Choices for Starting again at a limit is a lap. What happens when a change would push this value above its marked top?
Stop at the top and lose the extra. A large health pickup fills the bar and wastes the surplus.

Store max, discard the excess, and report it to no one. The change otherwise happened.

Refuse the whole gain. A health pickup that would overfill the bar adds no health.

Leave the value and saved fraction unchanged and report the refusal. Fire no mark.

Fill to the top and return the extra. A healing rule can pass unused healing to a shield.

Store max and report the positive excess to the caller. This contract does not route it. A change with nobody acting has no caller, so its extra is dropped.

The marked top is only a landmark. A score can keep rising after it passes its goal.

Store the complete result above max. The declared top remains citable and still defines shares.

Supplied answer Start a lap at the top. Filling an XP bar reports a level and returns the bar to its lap target.

Reaching is decided by exact-landing. Report a lap and move to lap-lands-on. Section 3 alone defines leftover handling and report order.

A change would pull this value below its marked bottom. What happens?

Choices for A change would pull this value below its marked bottom. What happens?
Supplied answer Stop at the bottom and lose the extra. A lethal hit leaves health at zero.

Store min, discard the excess, and report it to no one.

Refuse the whole loss. A hit that would cross the bottom deals no damage.

Leave the value and saved fraction unchanged and report the refusal. Fire no mark.

Empty to the bottom and return the shortfall. A shield can report how much damage still needs another rule.

Store min and report the positive shortfall to the caller. This contract does not route it. A change with nobody acting has no caller, so the shortfall is dropped.

The marked bottom is only a landmark. A debt meter can keep falling below zero.

Store the complete result below min. The declared bottom remains citable.

Start a lap at the bottom. Losing the last combo point can report a break and refill the meter.

Reaching is decided by exact-landing. Report a lap and move to lap-lands-on. Section 3 alone defines leftover handling and report order.

One move passes more than one mark (a line or a band edge). Which marks report?

Asked when
the lines list has at least one row, or the bands list has at least one row.
If not asked
No mark exists, so no move can pass one.
Choices for One move passes more than one mark (a line or a band edge). Which marks report?
Supplied answer Report every crossed mark in travel order. One large hit can report wounded, critical, then empty health.

Report every armed line and band edge whose reached state changes in its direction. Order by position along the path; row order breaks ties. Update all mark state.

Report only the crossed mark nearest the landing value. One large hit can report empty health and suppress earlier warnings.

Bare lines and band edges compete by distance to the landing value; row order breaks ties. Report only the winner, but update every reached, arm, and band state along the full path.

The bottom or top moves while this value holds a number. What happens to the value?

Asked when
the min value is supplied as a reference, or the max value is supplied as a reference.
If not asked
The bottom and top are fixed numbers, so neither limit moves.
Choices for The bottom or top moves while this value holds a number. What happens to the value?
Follow a moving top by filling to it. Raising maximum health from 100 to 120 also raises current health to 120.

A max change stores the new max. A min-only change keeps the value unless it falls below the new min, then stores that min.

Keep the current number while it still fits. Raising maximum health from 100 to 120 leaves current health at 70.

Preserve the value inside the new range; otherwise clamp it to the limit it is outside, even if an ordinary change may pass that limit.

Keep the same share of the range. Raising a half-full health bar from 100 to 200 moves its health from 50 to 100.

Compute the old normalized share immediately before the limit move and store the same share of the new range. An empty old range uses the new min. Whole-number targets round to nearest with ties away from zero. Saved fraction is unchanged.

Keep the number if it fits; otherwise move to a named safe number. A lowered stamina cap can move an outside value to 80.

Preserve the value inside the new range. Otherwise store out-of-range-lands-on, which must resolve inside the new range.

Do not move the held number now. Lowering a score's marked top to 100 can leave a held score of 120 unchanged.

A held number outside a moved limit is legal only where the matching ordinary edge answer lets the value pass that limit.

Something sets this value to a number outside its range. What happens?

Asked when
the sets list has at least one row.
If not asked
No named set puts this value directly at a target number.
Choices for Something sets this value to a number outside its range. What happens?
Move to the limit the target passed. A refill aimed at 120 leaves a 100-point health bar at 100.

Above max store max; below min store min. The rejected target is not a raw result. A set does not hand back extra or start a lap.

Refuse the set and keep the old number. An invalid checkpoint refill leaves health unchanged.

Leave the value and saved fraction unchanged, fire no mark, and report refusal to the caller.

Store the target even outside the range. A score set to 120 can stay above its marked top of 100.

Store the target exactly. It is legal beyond a limit only where the matching ordinary edge answer lets the value pass that limit.

A set jumps across one or more marks. Do they report?

Asked when
the sets list has at least one row.
If not asked
No named set crosses a line or changes a band.
Choices for A set jumps across one or more marks. Do they report?
Report crossed marks after a successful set. Refilling oxygen to full can clear the low-air warnings on the way up.

After storing the accepted target, test lines and band edges along the movement. jumped-lines selects reports. A rejected or clamped target is never a raw result.

Update mark state without reports. Respawning at full health does not replay every health warning.

Recompute line reached state and line-geometry band state from the stored target. Event-edged bands keep their state. Report nothing.

Starting over at a limit is a lap. After a lap, what happens to the extra?

Asked when
At the ceiling is Start a lap, or At the floor is Start a lap.
If not asked
Neither limit starts this value over, so no lap leaves extra.
Choices for Starting over at a limit is a lap. After a lap, what happens to the extra?
Keep using the extra after the lap. An XP award of 120 can fill a 100-point bar and put 20 into the next level.

Keep the amount past the consuming limit and apply it in the same direction after the lap movement. Section 3 defines the sequence.

Supplied answer Throw the extra away after the lap. A 120-point stagger hit fills one 100-point meter and loses the remaining 20.

Discard the leftover after one lap and report it to no one (see the settlement order).

After a lap, the extra can reach the same limit again. Can one change cause more than one lap?

Asked when
At the ceiling is Start a lap, or At the floor is Start a lap.
If not asked
Neither limit starts this value over, so one change cannot lap it.
Choices for After a lap, the extra can reach the same limit again. Can one change cause more than one lap?
Start over again while enough extra remains. A 250-point XP award can report two levels on a 100-point bar.

Repeat while carried leftover reaches the limit, subject to the 32-lap cap in section 3. This requires carrying the extra.

Supplied answer Allow at most one lap from each change. A 250-point combo gain reports one lap even if more would fit.

The originating change causes at most one lap (see the settlement order).

Does a lap clear any saved fraction?

Asked when
Small change is Save the fraction and At the ceiling is Start a lap, or Small change is Save the fraction and At the floor is Start a lap.
If not asked
No lap can clear saved fractions; either this value does not lap or it does not save fractions.
Choices for Does a lap clear any saved fraction?
Supplied answer Clear the saved fraction after every lap. Breaking a stagger meter removes the 0.4 poise still waiting.

A lap clears the saved fraction.

Keep the saved fraction across a lap. Leveling up keeps the 0.4 XP still waiting.

A lap leaves the signed saved-fraction store unchanged.

This value cannot pay the full cost of an action. What happens?

Asked when
the costs list has at least one row.
If not asked
No cost checks this value before changing it; every change simply happens, and bands and limits still apply.
Choices for This value cannot pay the full cost of an action. What happens?
Refuse the action and spend nothing. A tired player cannot dodge without the full stamina cost.

Report refusal and shortage to the caller. Leave the value, saved fraction, and every mark unchanged.

Spend what remains and report the amount paid. A tired player can use the last stamina for a weaker dodge.

Move to the limiting edge, test marks normally, and report the approved positive magnitude. The game's rule decides the partial action.

A drift is a change that happens with nobody acting. Two or more drifts can run in the same step. How do they combine?

Asked when
the drifts list has at least two rows.
If not asked
Fewer than two drifts can run together, so no combination choice applies.
Choices for A drift is a change that happens with nobody acting. Two or more drifts can run in the same step. How do they combine?
Add the drifts' signed amounts and move once. Oxygen drain of 3 and recovery of 1 produce one loss of 2.

Clip each eligible contribution to its own stop, sum the clipped amounts, resolve small-change once, and test marks once.

Run only the largest drift. Health regeneration of 4 beats poison damage of 2 for that step.

Compare clipped absolute magnitudes; row order breaks a tie. A skipped ramp does not advance for that step.

Run each drift in written order. Poison can damage health before regeneration heals it in the same step.

Settle every eligible row separately in row order. Each row follows section 3 from start to finish.

A change would pass a limit. Do marks read the result before or after the limit handles it?

Asked when
the lines list has at least one row, or the bands list has at least one row.
If not asked
No line or band exists, so nothing reads a result beyond a limit.
Choices for A change would pass a limit. Do marks read the result before or after the limit handles it?
Supplied answer Marks read the number the value keeps. A hit aimed at −20 leaves health at 0, so warnings read 0.

The outward part of the move tests its stored endpoint, or the consuming limit on a lap. It never tests beyond a limit.

Marks read the result before the limit fixes it. A hit aimed at −20 lets health warnings read −20 before health returns to 0.

The outward part of the move tests the raw candidate. It may observe a number the value never stores. A refused change has no observable raw result.

Numbers7 numbers

Each value is either a number set here or a reference to one of your tuning keys.

Min = 0

fixed as written

min

This value's marked bottom. Keep it even when the value may fall lower.

Max = 100

fixed as written

max

This value's marked top. Keep it even when the value may rise higher.

Initial = 0

fixed as written

initial

The number held when this value is created, or a citation read at creation. Later resets are listed separately.

Fraction step = 1

fixed as written

fraction-step

How much saved fraction releases one whole point.

Anchor

anchor

The resting point a drift approaches from either side.

Not used by this adoption. It applies when some drifts row has direction Toward the anchor.

Lap lands on = 0

fixed as written

lap-lands-on

Where the value lands during a lap.

Out of range lands on

out-of-range-lands-on

Where the value lands when a moved limit leaves it outside the new range.

Not used by this adoption. It applies when When a limit moves is Pull it to a declared number.

Rules13 rules

A rule is a check between the numbers. Validation reports a rule that fails.

  • max > min
  • initial >= min
  • initial <= max
  • fraction-step > 0
  • anchor >= min
  • anchor <= max
  • lap-lands-on >= min
  • lap-lands-on <= max
  • out-of-range-lands-on >= min
  • out-of-range-lands-on <= max
  • Keeping the same share needs a real floor and ceiling; close both limits or choose another response to a moving limit.

    Forbidden when When a limit moves is Keep the share and At the ceiling is No ceiling, or When a limit moves is Keep the share and At the floor is No floor.

  • This moving-limit answer can place the value directly on either consuming edge, but a limit move never starts a lap; change the moving-limit or lap answer.

    Forbidden when When a limit moves is Refill to the new ceiling and At the ceiling is Start a lap, or When a limit moves is Refill to the new ceiling and At the floor is Start a lap.

  • Another lap needs leftover from the first; carry it forward or allow only one lap.

    Forbidden when More than one lap is Lap again while it fits and The extra after a lap is Drop it.

Lists9 lists

Each list holds the rows this adoption supplies. A list can be empty.

Reading notes

reading-notes

This adoption declares no reading notes.

Quantity unit

quantity-unit

This adoption declares no quantity unit.

Lines

lines

IdValue kindValueValue keyLine unitDirectionRefireTimesRearmRearm declared inRepeatCounts at lineStarts armed
stagger-warningnumber70risingevery-crossing
stagger-breakcitationcontracts.boss-stagger.maxrisingevery-crossing
poise-settlednumber0fallingevery-crossing

Sets

sets

This adoption declares no sets.

Bands

bands

IdEnter onEnter value kindEnter valueEnter value keyEnter unitEnter directionEnter declared inLeave onLeave value kindLeave valueLeave value keyLeave unitLeave directionLeave declared inRepeatStartsBlocks changeCounts at line
stagger-lockoutlinenumber100numberrisingafter-a-waittuning.stagger.lockout-secondsrestart-the-waitoutblocks-rises

Costs

costs

This adoption declares no costs.

Drifts

drifts

IdDirectionCadenceMoment declared inStep amount keyAmount kindAmount declared inStops at keyAt stop
poise-decayfallsper-real-secondtuning.stagger.poise-decay-rategrows-while-it-runs02-mechanics.md#poise-decay-rampcontracts.boss-stagger.minlands-exactly

Interrupts

interrupts

IdDriftKindCondition declared inEvent declared inPause length keyPause length kindPause length declared inRepeat event
after-a-hitpoise-decaypaused-after-event02-mechanics.md#poise-hit-landedtuning.stagger.poise-decay-delayfixedrestart-the-wait
while-lockedpoise-decayoff-while-condition02-mechanics.md#stagger-lockout-band

Resets

resets

This adoption declares no resets.

Test inputsscope and seeds

Some tests need a scope or seeds from the adoption before they can run.

This adoption supplies none; every test uses its defaults.

Acceptance tests33 tests apply

The contract comes with 96 tests. A test that runs once per row is counted once for each row. Tests that do not apply to these answers are still listed, with the reason.

change-applies

an in-range change applies exactly

scenarioonce

Applies to boss-stagger.

An in-range change moves boss-stagger by its amount, resolved to whole units as this value's small-change answer directs, 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 min = 0 and max = 100; this test restates neither number.

Test steps and diagnostics
Given

boss-stagger holding a stored value strictly between min = 0 and max = 100, 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 boss-stagger
Then
  • the stored boss-stagger value changes by d, resolved to whole units as this value's small-change answer directs
  • 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
  • boss-stagger-value-before-after
  • boss-stagger-mark-log

fractional-change-resolves

a fractional change resolves as declared

scenarioonce

Does not apply to boss-stagger: small change is save the fraction, not nearest or nearest away from zero or drop the fraction or always a whole unit.

fractional-change-saves-residue

saved fractions release whole multiples toward zero

scenarioonce

Applies to boss-stagger.

boss-stagger splits a fractional change: the whole part moves at once and the signed remainder waits as residue. Whenever that residue contains complete multiples of fraction-step = 1, 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.

Test steps and diagnostics
Given

boss-stagger 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 fraction-step = 1
Then
  • the whole part of each fractional change moves boss-stagger at once and only its signed fractional remainder enters residue
  • complete multiples of fraction-step = 1 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 fraction-step = 1 already released, and each released multiple moved that many whole units
Diagnostics
  • boss-stagger-change-record
  • boss-stagger-residue
  • boss-stagger-value-before-after

fractional-value-keeps-no-store

a fractional value has no saved-fraction store

scenarioonce

Does not apply to boss-stagger: number kind is whole number, not fractional.

comparisons-read-stored-value

every comparison reads the stored value

scenarioonce

Applies to boss-stagger.

Whatever boss-stagger 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.

Test steps and diagnostics
Given

a moment when the number shown for boss-stagger 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 boss-stagger value at full precision
  • every cited position is read fresh for that comparison
  • the displayed number decides nothing
Diagnostics
  • boss-stagger-comparison-log
  • boss-stagger-value-before-after

creation-is-silent

creation stores mark state silently

scenarioonce

Applies to boss-stagger.

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

Test steps and diagnostics
Given

creation of boss-stagger at initial = 0

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
  • boss-stagger-line-state
  • boss-stagger-line-allowance
  • boss-stagger-band-state
  • boss-stagger-mark-log

exact-landing-counts

an exact landing counts as reached

scenarioonce

Applies to boss-stagger.

For boss-stagger, 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.

Test steps and diagnostics
Given

boss-stagger 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
  • boss-stagger-mark-log
  • boss-stagger-operation-record

exact-landing-must-pass

an exact landing does not count as reached

scenarioonce

Does not apply to boss-stagger: exact landing is at the line counts, not must pass the line.

ceiling-stops-change

excess stops at the ceiling

scenarioonce

Does not apply to boss-stagger: at the ceiling is start a lap, not stop at the ceiling.

floor-stops-change

excess stops at the floor

scenarioonce

Applies to boss-stagger.

A falling change that undershoots min = 0 leaves boss-stagger exactly on that edge. The shortfall is lost and reported to no one. This test restates neither number.

Test steps and diagnostics
Given

boss-stagger holding any value at or above min = 0

When
  • an imposed falling change would take boss-stagger below min = 0
Then
  • the stored value is exactly min = 0
  • the shortfall is discarded and reported to no one
Diagnostics
  • boss-stagger-value-after
  • boss-stagger-edge-record

ceiling-refuses-change

an overshooting change is refused whole at the ceiling

scenarioonce

Does not apply to boss-stagger: at the ceiling is start a lap, not refuse the whole change.

floor-refuses-change

an undershooting change is refused whole at the floor

scenarioonce

Does not apply to boss-stagger: at the floor is stop at the floor, not refuse the whole change.

ceiling-returns-extra

ceiling excess is handed back

scenarioonce

Does not apply to boss-stagger: at the ceiling is start a lap, not hand back the extra.

floor-returns-extra

floor shortfall is handed back

scenarioonce

Does not apply to boss-stagger: at the floor is stop at the floor, not hand back the extra.

ceiling-is-landmark

the ceiling does not hold the value down

scenarioonce

Does not apply to boss-stagger: at the ceiling is start a lap, not no ceiling.

floor-is-landmark

the floor does not hold the value up

scenarioonce

Does not apply to boss-stagger: at the floor is stop at the floor, not no floor.

ceiling-starts-lap

reaching the ceiling starts a lap

scenarioonce

Applies to boss-stagger.

When a rising change consumes max = 100, boss-stagger reports outward marks, then the lap, then any marks on the leg to lap-lands-on = 0. The reports keep one operation id and distinguish their legs. This test restates neither position.

Test steps and diagnostics
Given

boss-stagger below max = 100, 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 max = 100 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 lap-lands-on = 0 and any marks on it report after the lap
  • all reports retain the originating operation id and distinguish leg position
Diagnostics
  • boss-stagger-operation-record
  • boss-stagger-lap-log
  • boss-stagger-mark-log

floor-starts-lap

reaching the floor starts a lap

scenarioonce

Does not apply to boss-stagger: at the floor is stop at the floor, not start a lap.

lap-carries-extra

extra continues after a lap

scenarioonce

Does not apply to boss-stagger: the extra after a lap is drop it, not carry it onto the new value.

lap-drops-extra

extra is dropped after a lap

scenarioonce

Applies to boss-stagger.

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

Test steps and diagnostics
Given

a change whose movement continues past a consuming limit

When
  • boss-stagger 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
  • boss-stagger-operation-record
  • boss-stagger-lap-log

lap-repeats-with-cap

carried extra laps again up to the runtime cap

scenarioonce

Does not apply to boss-stagger: more than one lap is one lap per change, not lap again while it fits.

lap-stops-after-one

one change causes at most one lap

scenarioonce

Does not apply to boss-stagger: the extra after a lap is drop it, not carry it onto the new value.

lap-stops-after-one-and-drops

one change drops leftover after its only lap

scenarioonce

Applies to boss-stagger.

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.

Test steps and diagnostics
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
  • boss-stagger-lap-log
  • boss-stagger-operation-record
  • boss-stagger-value-after

lap-clears-residue

a lap clears saved residue

scenarioonce

Applies to boss-stagger.

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

Test steps and diagnostics
Given

boss-stagger 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
  • boss-stagger-residue-trace
  • boss-stagger-lap-log

lap-keeps-residue

a lap keeps saved residue

scenarioonce

Does not apply to boss-stagger: a lap clears saved fraction is clear it, not keep it.

line-crosses-fixed-position · stagger-warning

the stagger-warning line fires on crossing

scenarioper lines row

Applies to the stagger-warning row.

The stagger-warning line uses the position the row declares, read as its line-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100. A rising movement 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.

Test steps and diagnostics
Given

boss-stagger holding a value on the unreached side of stagger-warning at the position the row declares, read as its line-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100, with the line in its declared starting arm state; omission of starts-armed means armed

When
  • one rising movement changes stagger-warning from unreached to reached
Then
  • stagger-warning 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
  • boss-stagger-mark-log
  • boss-stagger-line-state
  • boss-stagger-value-before-after

line-crosses-fixed-position · poise-settled

the poise-settled line fires on crossing

scenarioper lines row

Applies to the poise-settled row.

The poise-settled line uses the position the row declares, read as its line-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100. A falling movement 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.

Test steps and diagnostics
Given

boss-stagger holding a value on the unreached side of poise-settled at the position the row declares, read as its line-unit directs — the declared number itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100, with the line in its declared starting arm state; omission of starts-armed means armed

When
  • one falling movement changes poise-settled from unreached to reached
Then
  • poise-settled 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
  • boss-stagger-mark-log
  • boss-stagger-line-state
  • boss-stagger-value-before-after

line-crosses-cited-position · stagger-break

the stagger-break line follows and fires at its cited position

scenarioper lines row

Applies to the stagger-break row.

The stagger-break line uses the position read fresh from contracts.boss-stagger.max, interpreted as its line-unit directs — the number at that address itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100, with contracts.boss-stagger.max read fresh whenever it is compared. A rising movement 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.

Test steps and diagnostics
Given

boss-stagger holding a value on the unreached side of stagger-break at the position read fresh from contracts.boss-stagger.max, interpreted as its line-unit directs — the number at that address itself unless the row declares share-of-the-ceiling, where it is that share of the fresh value at max = 100, with the line in its declared starting arm state and the cited number recorded before comparison; omission of starts-armed means armed

When
  • one rising movement changes stagger-break from unreached to reached
Then
  • contracts.boss-stagger.max is read fresh for the comparison and this test restates no number
  • stagger-break reports exactly once if it still has allowance
  • the report carries before, after, direction, leg position, operation id, and row id
Diagnostics
  • boss-stagger-comparison-log
  • boss-stagger-mark-log
  • boss-stagger-line-state

line-uses-ceiling-share

the Row.id line is a share of the ceiling

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches line-unit share of the ceiling.

line-exact-landing-override

Row.id uses its own exact-landing answer

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches counts-at-line at the line counts or must pass the line.

line-refires-every-crossing · stagger-warning

stagger-warning fires again on each crossing

scenarioper lines row

Applies to the stagger-warning row.

For stagger-warning, 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. the described cross, return, cross sequence therefore reports twice, and the return leg is silent.

Test steps and diagnostics
Given

stagger-warning armed and unreached

When
  • boss-stagger crosses stagger-warning 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
  • the described cross, return, cross sequence therefore reports twice, and the return leg is silent
Diagnostics
  • boss-stagger-mark-log
  • boss-stagger-line-state

line-refires-every-crossing · stagger-break

stagger-break fires again on each crossing

scenarioper lines row

Applies to the stagger-break row.

For stagger-break, 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. the described cross, return, cross sequence therefore reports twice, and the return leg is silent.

Test steps and diagnostics
Given

stagger-break armed and unreached

When
  • boss-stagger crosses stagger-break 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
  • the described cross, return, cross sequence therefore reports twice, and the return leg is silent
Diagnostics
  • boss-stagger-mark-log
  • boss-stagger-line-state

line-refires-every-crossing · poise-settled

poise-settled fires again on each crossing

scenarioper lines row

Applies to the poise-settled row.

For poise-settled, 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. the described cross, return, cross sequence therefore reports twice, and the return leg is silent.

Test steps and diagnostics
Given

poise-settled armed and unreached

When
  • boss-stagger crosses poise-settled 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
  • the described cross, return, cross sequence therefore reports twice, and the return leg is silent
Diagnostics
  • boss-stagger-mark-log
  • boss-stagger-line-state

line-both-directions-keep-state

Row.id keeps separate reached state for both directions

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches direction both.

line-fires-once-per-arm

Row.id fires once, then waits to re-arm

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches refire once and rearm on reset or on event or after a wait.

line-fires-set-number

Row.id fires its declared number of times per arm

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches refire a set number of times and rearm on reset or on event or after a wait.

line-wait-rearm-repeat

Row.id handles another crossing during its re-arm wait

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches rearm after a wait.

jumped-lines-reports

a move crossing several marks reports as declared

scenarioonce

Applies to boss-stagger.

When one leg of boss-stagger crosses several marks, every crossed armed mark reports in travel order, with row order breaking ties. every crossed mark updates all its state. 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.

Test steps and diagnostics
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
  • every crossed armed mark reports in travel order, with row order breaking ties
  • every crossed mark updates all its state
  • a band edge crossed on the leg updates its band state under both answers, whether or not its report is the selected one
Diagnostics
  • boss-stagger-mark-log
  • boss-stagger-mark-state

marks-read-final-value

marks read the final value at an edge

scenarioonce

Applies to boss-stagger.

When a change passes a limit, boss-stagger 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.

Test steps and diagnostics
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
  • boss-stagger-operation-record
  • boss-stagger-mark-log

marks-read-raw-result

marks read the raw result at an edge

scenarioonce

Does not apply to boss-stagger: lines read is the final value, not the raw result.

band-enters-at-fixed-line · stagger-lockout

the stagger-lockout band enters at its fixed line

scenarioper bands row

Applies to the stagger-lockout row.

stagger-lockout enters when a rising leg reaches the entering line at 100, 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 max = 100. It reports the state change subject to the value's jumped-lines answer.

Test steps and diagnostics
Given

stagger-lockout out and boss-stagger on the non-entered side of the entering line at 100, 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 max = 100

When
  • one rising leg changes the entering edge from unreached to reached
Then
  • stagger-lockout enters and reports once, subject to jumped-lines
  • the report carries the row id and operation evidence
Diagnostics
  • boss-stagger-band-state
  • boss-stagger-mark-log

band-enters-at-cited-line

the Row.id band enters at its cited line

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches enter-on line and enter-value-kind citation.

band-leaves-at-fixed-line

the Row.id band leaves at its fixed line

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches leave-on line and leave-value-kind number.

band-leaves-at-cited-line

the Row.id band leaves at its cited line

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches leave-on line and leave-value-kind citation.

band-event-enters

the Row.id band enters on its event

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches enter-on event.

band-event-or-wait-leaves · stagger-lockout

the stagger-lockout band leaves on its declared event or wait

scenarioper bands row

Applies to the stagger-lockout row.

stagger-lockout leaves when the wait at tuning.stagger.lockout-seconds completes. Its state is controlled by that declared edge, not inferred from the held number.

Test steps and diagnostics
Given

stagger-lockout in

When
  • the wait at tuning.stagger.lockout-seconds completes
Then
  • stagger-lockout leaves and records the declared cause
Diagnostics
  • boss-stagger-band-state
  • boss-stagger-band-event-record

band-wait-repeat · stagger-lockout

the stagger-lockout band handles another entry during its wait

scenarioper bands row

Applies to the stagger-lockout row.

While stagger-lockout waits to leave, another entry restarts the wait from that entry. The wait address is tuning.stagger.lockout-seconds; this test restates no duration.

Test steps and diagnostics
Given

stagger-lockout in with the wait at tuning.stagger.lockout-seconds running

When
  • its entering edge occurs again before the wait finishes
Then
  • the new entry restarts the wait from that entry
  • stagger-lockout remains in until the resulting wait completes
Diagnostics
  • boss-stagger-band-state
  • boss-stagger-band-wait

band-starts-as-declared · stagger-lockout

the stagger-lockout band starts as declared

scenarioper bands row

Applies to the stagger-lockout row.

At creation, stagger-lockout starts out and reports nothing. The starting value is cited at initial = 0; this test restates no number.

Test steps and diagnostics
Given

creation of boss-stagger at initial = 0

When
  • the initial band state is stored
Then
  • stagger-lockout starts out
  • creation reports no mark
Diagnostics
  • boss-stagger-band-state
  • boss-stagger-mark-log

band-starts-from-initial

the Row.id band reads its starting state from the initial value

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches starts read from initial and enter-on line and leave-on line.

event-entered-band-starts-out

the event-entered Row.id band starts out

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches starts read from initial and enter-on event.

event-left-band-starts-out

the event-left Row.id band starts out

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches starts read from initial and leave-on event or after a wait.

band-blocks-selected-movement · stagger-lockout

the stagger-lockout band blocks its selected movements

scenarioper bands row

Applies to the stagger-lockout row.

While stagger-lockout 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.

Test steps and diagnostics
Given

stagger-lockout 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
  • boss-stagger-blocked-record
  • boss-stagger-operation-record

event-entered-band-survives-silent-recompute

the event-entered Row.id band keeps state through silent recomputes

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches enter-on event.

event-left-band-survives-silent-recompute · stagger-lockout

the event-edged stagger-lockout band keeps state through silent recomputes

scenarioper bands row

Applies to the stagger-lockout row.

Because stagger-lockout 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.

Test steps and diagnostics
Given

stagger-lockout 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
  • stagger-lockout keeps its prior state through every recompute
Diagnostics
  • boss-stagger-band-state
  • boss-stagger-operation-record

line-once-never-rearms

Row.id fires once and never re-arms

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches refire once and rearm never.

line-set-number-never-rearms

Row.id has one fixed lifetime allowance

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches refire a set number of times and rearm never.

line-starts-armed-as-declared

Row.id uses its explicit starting arm state

scenarioper lines row

Does not apply to boss-stagger: no row in lines matches starts-armed armed or disarmed.

band-enter-share-follows-ceiling

the Row.id entering line is a share of the ceiling

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches enter-unit share of the ceiling.

band-leave-share-follows-ceiling

the Row.id leaving line is a share of the ceiling

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches leave-unit share of the ceiling.

band-exact-landing-override

Row.id uses its own exact-landing answer

scenarioper bands row

Does not apply to boss-stagger: no row in bands matches counts-at-line at the line counts or must pass the line.

set-stores-target-without-raw-result

the Row.id set stores its target without a raw result

scenarioper sets row

Does not apply to boss-stagger: sets has no rows.

outside-set-clamps

an outside set stores the nearer limit

scenarioonce

Does not apply to boss-stagger: a set outside the range is not asked for boss-stagger.

outside-set-refuses

an outside set is refused whole

scenarioonce

Does not apply to boss-stagger: a set outside the range is not asked for boss-stagger.

outside-set-stores-as-sent

an outside set stores its target as sent

scenarioonce

Does not apply to boss-stagger: a set outside the range is not asked for boss-stagger.

set-fires-marks-as-change

a successful set reports crossed marks

scenarioonce

Does not apply to boss-stagger: does a set fire lines is not asked for boss-stagger.

set-updates-marks-silently

a successful set recomputes marks without reports

scenarioonce

Does not apply to boss-stagger: does a set fire lines is not asked for boss-stagger.

successful-set-clears-residue

the Row.id set clears residue when it succeeds

scenarioper sets row

Does not apply to boss-stagger: sets has no rows.

cost-pays-exactly

the affordable Row.id cost pays exactly

scenarioper costs row

Does not apply to boss-stagger: costs has no rows.

value-wide-cost-refuses

the value-wide cost answer refuses an unaffordable action

scenarioonce

Does not apply to boss-stagger: not enough room is not asked for boss-stagger.

value-wide-cost-takes-what-fits

the value-wide cost answer takes what fits

scenarioonce

Does not apply to boss-stagger: not enough room is not asked for boss-stagger.

cost-row-override-refuses

the Row.id override refuses an unaffordable action

scenarioper costs row

Does not apply to boss-stagger: not enough room is not asked for boss-stagger.

cost-row-override-partial

the Row.id override takes what fits

scenarioper costs row

Does not apply to boss-stagger: not enough room is not asked for boss-stagger.

drift-moves-value · poise-decay

poise-decay moves the value on its own

scenarioper drifts row

Applies to the poise-decay row.

boss-stagger changes on its own under poise-decay. Each time cited-clock time passes, its contribution is resolved through small-change into a provisional movement, then clipped to contracts.boss-stagger.min, so it falls by no more than the positive amount at tuning.stagger.poise-decay-rate, grown by the row's growth rule at 02-mechanics.md#poise-decay-ramp. The amount and stop are stated at their addresses; this test restates neither number.

Test steps and diagnostics
Given

boss-stagger away from contracts.boss-stagger.min, with poise-decay eligible, every interrupt row for it allowing it, and no other drift eligible

When
  • cited-clock time passes, with nobody acting
Then
  • the contribution is resolved through small-change into a provisional movement, then clipped to contracts.boss-stagger.min, so boss-stagger falls by no more than the positive amount at tuning.stagger.poise-decay-rate, grown by the row's growth rule at 02-mechanics.md#poise-decay-ramp
  • the operation commits once with no partly settled state observable
  • marks test the movement once
Diagnostics
  • boss-stagger-value-before-after
  • boss-stagger-drift-log
  • boss-stagger-mark-log

continuous-drift-uses-elapsed-time · poise-decay

poise-decay accrues continuously from elapsed clock time

scenarioper drifts row

Applies to the poise-decay row.

poise-decay accrues continuously. It multiplies the rate at tuning.stagger.poise-decay-rate by elapsed cited-clock time, not frame count, and sends fractional accrual through small-change. This test restates no rate.

Test steps and diagnostics
Given

poise-decay eligible over equal cited-clock durations rendered with different frame counts

When
  • each duration settles
Then
  • each contribution is the rate at tuning.stagger.poise-decay-rate multiplied by elapsed cited-clock time
  • equal elapsed time produces equal provisional movement regardless of frame count
  • fractional accrual passes through small-change
Diagnostics
  • boss-stagger-clock-trace
  • boss-stagger-drift-log

named-moment-drift-uses-citation

Row.id runs only at its named moment

scenarioper drifts row

Does not apply to boss-stagger: no row in drifts matches cadence at a named moment.

declared-drift-amount-rule · poise-decay

poise-decay uses its declared changing amount rule

scenarioper drifts row

Applies to the poise-decay row.

poise-decay does not use one fixed contribution. It is grown by the row's growth rule at 02-mechanics.md#poise-decay-ramp, with the base at tuning.stagger.poise-decay-rate. The test names both addresses and restates neither number nor rule.

Test steps and diagnostics
Given

poise-decay eligible at two states or two points in its run for which 02-mechanics.md#poise-decay-ramp gives different amounts

When
  • one contribution settles in each case
Then
  • each contribution is grown by the row's growth rule at 02-mechanics.md#poise-decay-ramp
  • tuning.stagger.poise-decay-rate supplies the declared base amount and this test restates neither the amount nor the rule
Diagnostics
  • boss-stagger-drift-log
  • boss-stagger-value-trace

drift-stops · poise-decay

poise-decay stops where its row says it stops

scenarioper drifts row

Applies to the poise-decay row.

Both at-stop answers leave boss-stagger stored at contracts.boss-stagger.min, so the stored value cannot distinguish them. This probe reads the at-stop step record: the offered contribution is clipped so no value beyond contracts.boss-stagger.min exists in the step record. Once stored at that address, poise-decay is ineligible and offers nothing. The test restates no stop or amount.

Test steps and diagnostics
Given

boss-stagger less than one poise-decay contribution from contracts.boss-stagger.min, poise-decay 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 contracts.boss-stagger.min
Then
  • the step record names the amount offered before clipping or correction
  • the offered contribution is clipped so no value beyond contracts.boss-stagger.min exists in the step record
  • the stored value is exactly contracts.boss-stagger.min under either answer
  • after an overshoot, correction reports no mark and recomputes reached state from the stored stop
  • poise-decay is ineligible and offers nothing while the value rests at its stop
Diagnostics
  • boss-stagger-at-stop-step-record
  • boss-stagger-offered-amount
  • boss-stagger-intermediate-value
  • boss-stagger-value-after

drift-clips-at-consuming-ceiling

Row.id clips at the consuming ceiling without lapping

scenarioper drifts row

Does not apply to boss-stagger: no row in drifts matches direction rises.

drift-clips-at-consuming-floor

Row.id clips at the consuming floor without lapping

scenarioper drifts row

Does not apply to boss-stagger: at the floor is stop at the floor, not start a lap.

drift-approaches-anchor

Row.id approaches the anchor from either side

scenarioper drifts row

Does not apply to boss-stagger: anchor is not in use for boss-stagger.

drifts-add-together

eligible drifts add before one settlement

scenarioonce

Does not apply to boss-stagger: drifts together is not asked for boss-stagger.

largest-drift-wins

only the largest eligible drift settles

scenarioonce

Does not apply to boss-stagger: drifts together is not asked for boss-stagger.

drifts-settle-in-row-order

eligible drifts settle separately in row order

scenarioonce

Does not apply to boss-stagger: drifts together is not asked for boss-stagger.

condition-interrupt-controls-drift · while-locked

while-locked controls its drift through a condition

scenarioper interrupts row

Applies to the while-locked row.

while-locked allows poise-decay only while the condition is false, using the condition at 02-mechanics.md#stagger-lockout-band. Every interrupt row naming poise-decay must allow it before that drift runs.

Test steps and diagnostics
Given

the condition at 02-mechanics.md#stagger-lockout-band observed once false and once true, with every other interrupt row for poise-decay allowing it

When
  • poise-decay reaches an occurrence in each condition state
Then
  • while-locked allows poise-decay only while the condition is false
  • the drift runs only when this row and every other row naming poise-decay allow it
Diagnostics
  • boss-stagger-interrupt-state
  • boss-stagger-drift-log

pause-interrupt-controls-drift · after-a-hit

after-a-hit pauses its drift after an event

scenarioper interrupts row

Applies to the after-a-hit row.

After 02-mechanics.md#poise-hit-landed, after-a-hit pauses poise-decay and uses the fixed pause at tuning.stagger.poise-decay-delay. A repeated event restarts the wait from the repeated event. Every row naming the drift must allow it before it resumes.

Test steps and diagnostics
Given

poise-decay otherwise allowed by every interrupt row

When
  • the event at 02-mechanics.md#poise-hit-landed occurs twice before the pause completes
Then
  • after-a-hit uses the fixed pause at tuning.stagger.poise-decay-delay and prevents poise-decay from running during the wait
  • the second event restarts the wait from the repeated event
  • poise-decay runs again only after this and every other row naming it allow it
Diagnostics
  • boss-stagger-interrupt-state
  • boss-stagger-pause-record
  • boss-stagger-drift-log

state-dependent-pause-length

Row.id reads its state-dependent pause rule

scenarioper interrupts row

Does not apply to boss-stagger: no row in interrupts matches pause-length-kind depends on state.

interrupt-conjunction-holds · after-a-hit

after-a-hit combines with every interrupt on its drift

scenarioper interrupts row

Applies to the after-a-hit row.

Even while after-a-hit allows poise-decay, 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.

Test steps and diagnostics
Given

another interrupt row naming poise-decay and currently forbidding it while after-a-hit 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
  • poise-decay does not run
  • every interrupt row for one drift must allow it before it runs
Diagnostics
  • boss-stagger-interrupt-state
  • boss-stagger-drift-log

interrupt-conjunction-holds · while-locked

while-locked combines with every interrupt on its drift

scenarioper interrupts row

Applies to the while-locked row.

Even while while-locked allows poise-decay, 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.

Test steps and diagnostics
Given

another interrupt row naming poise-decay and currently forbidding it while while-locked 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
  • poise-decay does not run
  • every interrupt row for one drift must allow it before it runs
Diagnostics
  • boss-stagger-interrupt-state
  • boss-stagger-drift-log

reset-returns-silently

the Row.id reset returns the value silently

scenarioper resets row

Does not apply to boss-stagger: resets has no rows.

reset-handles-residue

the Row.id reset handles residue as declared

scenarioper resets row

Does not apply to boss-stagger: resets has no rows.

reset-handles-lines-and-bands

the Row.id reset restores mark state as declared

scenarioper resets row

Does not apply to boss-stagger: resets has no rows.

reset-applies-explicit-band-choice

the Row.id reset applies its explicit band choice

scenarioper resets row

Does not apply to boss-stagger: resets has no rows.

limit-move-refills-ceiling

a moving ceiling refills the value

scenarioonce

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-keeps-number

a moving limit keeps the held number when it fits

scenarioonce

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-keeps-share

a moving limit preserves the value's share

scenarioonce

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-uses-declared-number

an outside value moves to its declared safe number

scenarioonce

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-leaves-number-alone

a moving limit leaves the held number alone

scenarioonce

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-never-fires-bare-line

a limit move never fires the Row.id bare line

scenarioper lines row

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limit-move-recomputes-band

a limit move recomputes the Row.id band as its edge kind directs

scenarioper bands row

Does not apply to boss-stagger: when a limit moves is not asked for boss-stagger.

limits-hold

the limits hold after every operation

generalonce

Applies to boss-stagger.

For every operation in this adoption's verification scope — sequences of legal imposed changes, costs, sets, drift steps and batches, laps, resets, and limit moves over one run — the boss-stagger value is greater than or equal to min = 0, and the boss-stagger value is less than or equal to max = 100. 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.

Test steps and diagnostics
Holds

after every operation, the boss-stagger value is greater than or equal to min = 0, and the boss-stagger value is less than or equal to max = 100. A cited limit whose answer is no-floor or no-ceiling remains a landmark

Seeds

["audit-a","audit-b"]

Scope

sequences of legal imposed changes, costs, sets, drift steps and batches, laps, resets, and limit moves over one run

Diagnostics
  • boss-stagger-value-trace
  • boss-stagger-first-violating-operation
JSONthe adoption as one file

The adoption file as supplied. Answers you try on this page are not written into it; to change an adoption, open it in the authoring tool.

{
  "contract": "ranged-value",
  "version": 1,
  "summary": "Covers health, stamina, oxygen, XP and other values with a marked bottom and top. It decides how changes meet those limits, how named lines fire, how costs are paid, and how the value can move on its own. Sources, rates, display and effects belong to the game's own rules.",
  "questions": {
    "number-kind": {
      "asks": "Can this value hold a fraction, or is it always a whole number?",
      "rationale": "Whole and fractional values handle small changes differently. A health bar may show only whole points while oxygen keeps decimals.",
      "options": {
        "whole-number": {
          "meaning": "The stored value is always whole. A health bar can show 7 or 8, never 7.5.",
          "semantics": "A change with a fractional part passes through small-change before any limit or mark reads it. Every absolute stored target and mark must resolve to a whole number."
        },
        "fractional": {
          "meaning": "Fractions stay exactly as sent. An oxygen meter can rest at 7.5.",
          "semantics": "Every finite change lands at full precision. No saved-fraction store exists."
        }
      }
    },
    "small-change": {
      "asks": "A change contains part of a point. What happens to that part?",
      "when": {
        "flag": {
          "number-kind": [
            "whole-number"
          ]
        }
      },
      "otherwise": "This value keeps fractional changes exactly as sent.",
      "options": {
        "nearest": {
          "meaning": "Use the nearer whole change, with an exact half going up the scale. A health gain of 2.5 becomes 3.",
          "semantics": "Round the signed change to the nearest integer; ties go toward positive infinity. Discard the difference."
        },
        "nearest-away-from-zero": {
          "meaning": "Use the nearer whole change, with an exact half going away from zero. A karma loss of 2.5 becomes −3.",
          "semantics": "Round to the nearest integer; ties choose the integer with the greater absolute magnitude. Discard the difference."
        },
        "drop-the-fraction": {
          "meaning": "Drop the fractional part toward zero. A poison drain of 0.7 health does nothing that step.",
          "semantics": "Remove the signed fractional part toward zero and discard it."
        },
        "always-a-whole-unit": {
          "meaning": "Every nonzero change moves at least one whole point. Chip damage of 0.1 removes 1 health.",
          "semantics": "Round every non-integer signed change away from zero and discard the difference."
        },
        "save-the-fraction": {
          "meaning": "Save leftover fractions until they make a whole point. Two hits worth 0.5 poise each add 1 poise together.",
          "semantics": "Move the whole part now. Add only the signed fractional remainder to one saved-fraction store. Remove complete multiples of fraction-step toward zero, move by that many whole units, and keep the remainder. Sets always clear the store; named resets and starting over at a limit use their own clearing choices."
        }
      }
    },
    "exact-landing": {
      "asks": "Landing exactly on a line or limit: does that count as reached?",
      "options": {
        "at-the-line-counts": {
          "meaning": "Yes, touching it counts. Health falling to exactly 25 fires a warning set at 25.",
          "semantics": "A rising mark at t is reached at value greater than or equal to t; a falling mark is reached at value less than or equal to t. An exact landing may consume a limit."
        },
        "must-pass-the-line": {
          "meaning": "No, the value must pass it. Health must fall below 25 before a warning set at 25 fires.",
          "semantics": "A rising mark at t is reached only above t; a falling mark is reached only below t. An exact landing does not consume a limit."
        }
      }
    },
    "at-the-ceiling": {
      "asks": "Starting again at a limit is a lap. What happens when a change would push this value above its marked top?",
      "options": {
        "stop-at-the-ceiling": {
          "meaning": "Stop at the top and lose the extra. A large health pickup fills the bar and wastes the surplus.",
          "semantics": "Store max, discard the excess, and report it to no one. The change otherwise happened."
        },
        "refuse-the-whole-change": {
          "meaning": "Refuse the whole gain. A health pickup that would overfill the bar adds no health.",
          "semantics": "Leave the value and saved fraction unchanged and report the refusal. Fire no mark."
        },
        "hand-back-the-extra": {
          "meaning": "Fill to the top and return the extra. A healing rule can pass unused healing to a shield.",
          "semantics": "Store max and report the positive excess to the caller. This contract does not route it. A change with nobody acting has no caller, so its extra is dropped."
        },
        "no-ceiling": {
          "meaning": "The marked top is only a landmark. A score can keep rising after it passes its goal.",
          "semantics": "Store the complete result above max. The declared top remains citable and still defines shares."
        },
        "start-a-lap": {
          "meaning": "Start a lap at the top. Filling an XP bar reports a level and returns the bar to its lap target.",
          "semantics": "Reaching is decided by exact-landing. Report a lap and move to lap-lands-on. Section 3 alone defines leftover handling and report order."
        }
      }
    },
    "at-the-floor": {
      "asks": "A change would pull this value below its marked bottom. What happens?",
      "options": {
        "stop-at-the-floor": {
          "meaning": "Stop at the bottom and lose the extra. A lethal hit leaves health at zero.",
          "semantics": "Store min, discard the excess, and report it to no one."
        },
        "refuse-the-whole-change": {
          "meaning": "Refuse the whole loss. A hit that would cross the bottom deals no damage.",
          "semantics": "Leave the value and saved fraction unchanged and report the refusal. Fire no mark."
        },
        "hand-back-the-extra": {
          "meaning": "Empty to the bottom and return the shortfall. A shield can report how much damage still needs another rule.",
          "semantics": "Store min and report the positive shortfall to the caller. This contract does not route it. A change with nobody acting has no caller, so the shortfall is dropped."
        },
        "no-floor": {
          "meaning": "The marked bottom is only a landmark. A debt meter can keep falling below zero.",
          "semantics": "Store the complete result below min. The declared bottom remains citable."
        },
        "start-a-lap": {
          "meaning": "Start a lap at the bottom. Losing the last combo point can report a break and refill the meter.",
          "semantics": "Reaching is decided by exact-landing. Report a lap and move to lap-lands-on. Section 3 alone defines leftover handling and report order."
        }
      }
    },
    "jumped-lines": {
      "asks": "One move passes more than one mark (a line or a band edge). Which marks report?",
      "when": {
        "any": [
          {
            "row-count": {
              "lines": "non-empty"
            }
          },
          {
            "row-count": {
              "bands": "non-empty"
            }
          }
        ]
      },
      "otherwise": "No mark exists, so no move can pass one.",
      "options": {
        "all-in-order": {
          "meaning": "Report every crossed mark in travel order. One large hit can report wounded, critical, then empty health.",
          "semantics": "Report every armed line and band edge whose reached state changes in its direction. Order by position along the path; row order breaks ties. Update all mark state."
        },
        "only-the-nearest": {
          "meaning": "Report only the crossed mark nearest the landing value. One large hit can report empty health and suppress earlier warnings.",
          "semantics": "Bare lines and band edges compete by distance to the landing value; row order breaks ties. Report only the winner, but update every reached, arm, and band state along the full path."
        }
      }
    },
    "when-a-limit-moves": {
      "asks": "The bottom or top moves while this value holds a number. What happens to the value?",
      "when": {
        "any": [
          {
            "value-form": {
              "min": [
                "citation"
              ]
            }
          },
          {
            "value-form": {
              "max": [
                "citation"
              ]
            }
          }
        ]
      },
      "otherwise": "The bottom and top are fixed numbers, so neither limit moves.",
      "options": {
        "refill-to-the-new-ceiling": {
          "meaning": "Follow a moving top by filling to it. Raising maximum health from 100 to 120 also raises current health to 120.",
          "semantics": "A max change stores the new max. A min-only change keeps the value unless it falls below the new min, then stores that min."
        },
        "keep-the-number": {
          "meaning": "Keep the current number while it still fits. Raising maximum health from 100 to 120 leaves current health at 70.",
          "semantics": "Preserve the value inside the new range; otherwise clamp it to the limit it is outside, even if an ordinary change may pass that limit."
        },
        "keep-the-share": {
          "meaning": "Keep the same share of the range. Raising a half-full health bar from 100 to 200 moves its health from 50 to 100.",
          "semantics": "Compute the old normalized share immediately before the limit move and store the same share of the new range. An empty old range uses the new min. Whole-number targets round to nearest with ties away from zero. Saved fraction is unchanged."
        },
        "pull-it-to-a-declared-number": {
          "meaning": "Keep the number if it fits; otherwise move to a named safe number. A lowered stamina cap can move an outside value to 80.",
          "semantics": "Preserve the value inside the new range. Otherwise store out-of-range-lands-on, which must resolve inside the new range."
        },
        "leave-the-number-alone": {
          "meaning": "Do not move the held number now. Lowering a score's marked top to 100 can leave a held score of 120 unchanged.",
          "semantics": "A held number outside a moved limit is legal only where the matching ordinary edge answer lets the value pass that limit."
        }
      }
    },
    "a-set-outside-the-range": {
      "asks": "Something sets this value to a number outside its range. What happens?",
      "when": {
        "row-count": {
          "sets": "non-empty"
        }
      },
      "otherwise": "No named set puts this value directly at a target number.",
      "options": {
        "pull-it-to-the-nearer-limit": {
          "meaning": "Move to the limit the target passed. A refill aimed at 120 leaves a 100-point health bar at 100.",
          "semantics": "Above max store max; below min store min. The rejected target is not a raw result. A set does not hand back extra or start a lap."
        },
        "refuse-the-set": {
          "meaning": "Refuse the set and keep the old number. An invalid checkpoint refill leaves health unchanged.",
          "semantics": "Leave the value and saved fraction unchanged, fire no mark, and report refusal to the caller."
        },
        "store-it-as-sent": {
          "meaning": "Store the target even outside the range. A score set to 120 can stay above its marked top of 100.",
          "semantics": "Store the target exactly. It is legal beyond a limit only where the matching ordinary edge answer lets the value pass that limit."
        }
      }
    },
    "does-a-set-fire-lines": {
      "asks": "A set jumps across one or more marks. Do they report?",
      "when": {
        "row-count": {
          "sets": "non-empty"
        }
      },
      "otherwise": "No named set crosses a line or changes a band.",
      "options": {
        "treat-it-as-a-change": {
          "meaning": "Report crossed marks after a successful set. Refilling oxygen to full can clear the low-air warnings on the way up.",
          "semantics": "After storing the accepted target, test lines and band edges along the movement. jumped-lines selects reports. A rejected or clamped target is never a raw result."
        },
        "silent": {
          "meaning": "Update mark state without reports. Respawning at full health does not replay every health warning.",
          "semantics": "Recompute line reached state and line-geometry band state from the stored target. Event-edged bands keep their state. Report nothing."
        }
      }
    },
    "the-extra-after-a-lap": {
      "asks": "Starting over at a limit is a lap. After a lap, what happens to the extra?",
      "when": {
        "any": [
          {
            "flag": {
              "at-the-ceiling": [
                "start-a-lap"
              ]
            }
          },
          {
            "flag": {
              "at-the-floor": [
                "start-a-lap"
              ]
            }
          }
        ]
      },
      "otherwise": "Neither limit starts this value over, so no lap leaves extra.",
      "options": {
        "carry-it-onto-the-new-value": {
          "meaning": "Keep using the extra after the lap. An XP award of 120 can fill a 100-point bar and put 20 into the next level.",
          "semantics": "Keep the amount past the consuming limit and apply it in the same direction after the lap movement. Section 3 defines the sequence."
        },
        "drop-it": {
          "meaning": "Throw the extra away after the lap. A 120-point stagger hit fills one 100-point meter and loses the remaining 20.",
          "semantics": "Discard the leftover after one lap and report it to no one (see the settlement order)."
        }
      }
    },
    "more-than-one-lap": {
      "asks": "After a lap, the extra can reach the same limit again. Can one change cause more than one lap?",
      "when": {
        "any": [
          {
            "flag": {
              "at-the-ceiling": [
                "start-a-lap"
              ]
            }
          },
          {
            "flag": {
              "at-the-floor": [
                "start-a-lap"
              ]
            }
          }
        ]
      },
      "otherwise": "Neither limit starts this value over, so one change cannot lap it.",
      "options": {
        "lap-again-while-it-fits": {
          "meaning": "Start over again while enough extra remains. A 250-point XP award can report two levels on a 100-point bar.",
          "semantics": "Repeat while carried leftover reaches the limit, subject to the 32-lap cap in section 3. This requires carrying the extra."
        },
        "one-lap-per-change": {
          "meaning": "Allow at most one lap from each change. A 250-point combo gain reports one lap even if more would fit.",
          "semantics": "The originating change causes at most one lap (see the settlement order)."
        }
      }
    },
    "a-lap-clears-saved-fraction": {
      "asks": "Does a lap clear any saved fraction?",
      "when": {
        "any": [
          {
            "flag": {
              "small-change": [
                "save-the-fraction"
              ],
              "at-the-ceiling": [
                "start-a-lap"
              ]
            }
          },
          {
            "flag": {
              "small-change": [
                "save-the-fraction"
              ],
              "at-the-floor": [
                "start-a-lap"
              ]
            }
          }
        ]
      },
      "otherwise": "No lap can clear saved fractions; either this value does not lap or it does not save fractions.",
      "options": {
        "clear-it": {
          "meaning": "Clear the saved fraction after every lap. Breaking a stagger meter removes the 0.4 poise still waiting.",
          "semantics": "A lap clears the saved fraction."
        },
        "keep-it": {
          "meaning": "Keep the saved fraction across a lap. Leveling up keeps the 0.4 XP still waiting.",
          "semantics": "A lap leaves the signed saved-fraction store unchanged."
        }
      }
    },
    "not-enough-room": {
      "asks": "This value cannot pay the full cost of an action. What happens?",
      "when": {
        "row-count": {
          "costs": "non-empty"
        }
      },
      "otherwise": "No cost checks this value before changing it; every change simply happens, and bands and limits still apply.",
      "options": {
        "refuse-the-action": {
          "meaning": "Refuse the action and spend nothing. A tired player cannot dodge without the full stamina cost.",
          "semantics": "Report refusal and shortage to the caller. Leave the value, saved fraction, and every mark unchanged."
        },
        "take-what-fits": {
          "meaning": "Spend what remains and report the amount paid. A tired player can use the last stamina for a weaker dodge.",
          "semantics": "Move to the limiting edge, test marks normally, and report the approved positive magnitude. The game's rule decides the partial action."
        }
      }
    },
    "drifts-together": {
      "asks": "A drift is a change that happens with nobody acting. Two or more drifts can run in the same step. How do they combine?",
      "when": {
        "row-count": {
          "drifts": "at-least-two"
        }
      },
      "otherwise": "Fewer than two drifts can run together, so no combination choice applies.",
      "options": {
        "add-them-up": {
          "meaning": "Add the drifts' signed amounts and move once. Oxygen drain of 3 and recovery of 1 produce one loss of 2.",
          "semantics": "Clip each eligible contribution to its own stop, sum the clipped amounts, resolve small-change once, and test marks once."
        },
        "only-the-largest": {
          "meaning": "Run only the largest drift. Health regeneration of 4 beats poison damage of 2 for that step.",
          "semantics": "Compare clipped absolute magnitudes; row order breaks a tie. A skipped ramp does not advance for that step."
        },
        "in-row-order": {
          "meaning": "Run each drift in written order. Poison can damage health before regeneration heals it in the same step.",
          "semantics": "Settle every eligible row separately in row order. Each row follows section 3 from start to finish."
        }
      }
    },
    "lines-read": {
      "asks": "A change would pass a limit. Do marks read the result before or after the limit handles it?",
      "when": {
        "any": [
          {
            "row-count": {
              "lines": "non-empty"
            }
          },
          {
            "row-count": {
              "bands": "non-empty"
            }
          }
        ]
      },
      "otherwise": "No line or band exists, so nothing reads a result beyond a limit.",
      "options": {
        "the-final-value": {
          "meaning": "Marks read the number the value keeps. A hit aimed at −20 leaves health at 0, so warnings read 0.",
          "semantics": "The outward part of the move tests its stored endpoint, or the consuming limit on a lap. It never tests beyond a limit."
        },
        "the-raw-result": {
          "meaning": "Marks read the result before the limit fixes it. A hit aimed at −20 lets health warnings read −20 before health returns to 0.",
          "semantics": "The outward part of the move tests the raw candidate. It may observe a number the value never stores. A refused change has no observable raw result."
        }
      }
    }
  },
  "declares": {
    "values": {
      "min": {
        "description": "This value's marked bottom. Keep it even when the value may fall lower.",
        "forms": [
          "number",
          "citation"
        ]
      },
      "max": {
        "description": "This value's marked top. Keep it even when the value may rise higher.",
        "forms": [
          "number",
          "citation"
        ]
      },
      "initial": {
        "description": "The number held when this value is created, or a citation read at creation. Later resets are listed separately.",
        "forms": [
          "number",
          "citation"
        ]
      },
      "fraction-step": {
        "description": "How much saved fraction releases one whole point.",
        "when": {
          "flag": {
            "small-change": [
              "save-the-fraction"
            ]
          }
        }
      },
      "anchor": {
        "description": "The resting point a drift approaches from either side.",
        "forms": [
          "number",
          "citation"
        ],
        "when": {
          "row-has": {
            "drifts": {
              "direction": [
                "toward-the-anchor"
              ]
            }
          }
        }
      },
      "lap-lands-on": {
        "description": "Where the value lands during a lap.",
        "forms": [
          "number",
          "citation"
        ],
        "when": {
          "any": [
            {
              "flag": {
                "at-the-ceiling": [
                  "start-a-lap"
                ]
              }
            },
            {
              "flag": {
                "at-the-floor": [
                  "start-a-lap"
                ]
              }
            }
          ]
        }
      },
      "out-of-range-lands-on": {
        "description": "Where the value lands when a moved limit leaves it outside the new range.",
        "forms": [
          "number",
          "citation"
        ],
        "when": {
          "flag": {
            "when-a-limit-moves": [
              "pull-it-to-a-declared-number"
            ]
          }
        }
      }
    },
    "rows": {
      "reading-notes": {
        "description": "List the game prose a reader needs before trusting this adoption. Use at most one row.",
        "when-empty": "No advance reading is required.",
        "record": {
          "read-first": {
            "type": "citation",
            "required": true,
            "description": "Point to the game prose a reader needs first, such as which of a soft and hard ceiling the game calls full."
          }
        }
      },
      "quantity-unit": {
        "description": "Name the game-owned unit used by absolute values. Use at most one row.",
        "when-empty": "This contract gives the quantity no named unit.",
        "record": {
          "unit": {
            "type": "string",
            "required": true,
            "description": "The unit for every absolute number and citation, such as kg or XP. This contract neither interprets nor converts it."
          }
        }
      },
      "lines": {
        "description": "List the named marks this value reports crossing.",
        "when-empty": "No crossing is reported.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this mark in the game's words, such as low-health or full."
          },
          "value-kind": {
            "type": "string",
            "required": true,
            "options": [
              "number",
              "citation"
            ],
            "description": "Whether this mark uses a fixed number or points to a number the mark follows wherever it goes."
          },
          "value": {
            "type": "number",
            "when": {
              "row": {
                "value-kind": [
                  "number"
                ]
              }
            },
            "description": "The fixed number where this mark sits."
          },
          "value-key": {
            "type": "citation",
            "when": {
              "row": {
                "value-kind": [
                  "citation"
                ]
              }
            },
            "description": "Point to the number where this mark sits. Read it fresh at each comparison."
          },
          "line-unit": {
            "type": "string",
            "options": [
              "number",
              "share-of-the-ceiling"
            ],
            "description": "Use a fixed number or a share of the marked top. A share sits at that share of the fresh top; it can fall between whole points and is only compared, never stored. Omitting this field means number."
          },
          "direction": {
            "type": "string",
            "required": true,
            "options": [
              "rising",
              "falling",
              "both"
            ],
            "description": "Which direction may report this crossing."
          },
          "refire": {
            "type": "string",
            "required": true,
            "options": [
              "every-crossing",
              "once",
              "a-set-number-of-times"
            ],
            "description": "Report every crossing, once per arm, or a fixed number of times per arm."
          },
          "times": {
            "type": "integer",
            "within": [
              1,
              2147483647
            ],
            "when": {
              "row": {
                "refire": [
                  "a-set-number-of-times"
                ]
              }
            },
            "description": "The positive whole number of reports allowed per arm."
          },
          "rearm": {
            "type": "string",
            "when": {
              "row": {
                "refire": [
                  "once",
                  "a-set-number-of-times"
                ]
              }
            },
            "options": [
              "on-reset",
              "on-event",
              "after-a-wait",
              "never"
            ],
            "description": "What restores this line's full allowance."
          },
          "rearm-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "rearm": [
                  "on-reset",
                  "on-event",
                  "after-a-wait"
                ]
              }
            },
            "description": "Point to the reset, event, or wait that restores the line."
          },
          "repeat": {
            "type": "string",
            "when": {
              "row": {
                "rearm": [
                  "after-a-wait"
                ]
              }
            },
            "options": [
              "restart-the-wait",
              "keep-the-first-wait",
              "add-to-the-wait"
            ],
            "description": "Choose what another crossing does while the wait is running."
          },
          "counts-at-line": {
            "type": "string",
            "options": [
              "at-the-line-counts",
              "must-pass-the-line"
            ],
            "description": "Override the value-wide exact-landing answer for this line."
          },
          "starts-armed": {
            "type": "string",
            "options": [
              "armed",
              "disarmed"
            ],
            "description": "Whether this line starts able to report. Omission means armed."
          }
        }
      },
      "sets": {
        "description": "List each refill, direct assignment, or recomputed total. Use a set when the movement should be audible to lines and bands.",
        "when-empty": "Nothing sets the value outright; laps, resets and limit moves remain their own movements.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name the set, such as surface-refill or inventory-total."
          },
          "mode": {
            "type": "string",
            "required": true,
            "options": [
              "set-to-target",
              "recompute"
            ],
            "description": "Use a named target or a rule's computed result."
          },
          "target-key": {
            "type": "citation",
            "required": true,
            "description": "Point to the target number or the rule that computes it."
          },
          "trigger-declared-in": {
            "type": "citation",
            "required": true,
            "description": "Point to the event or rule that offers this set."
          },
          "enabled-while": {
            "type": "citation",
            "description": "Point to an optional condition that allows this set."
          }
        }
      },
      "bands": {
        "description": "List named on-or-off states between marks, such as overheated or low-warning.",
        "when-empty": "This value keeps no named state.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this state in the game's words."
          },
          "enter-on": {
            "type": "string",
            "required": true,
            "options": [
              "line",
              "event"
            ],
            "description": "Whether a line or named event turns the state on."
          },
          "enter-value-kind": {
            "type": "string",
            "when": {
              "row": {
                "enter-on": [
                  "line"
                ]
              }
            },
            "options": [
              "number",
              "citation"
            ],
            "description": "Whether the entering line uses a fixed number or points to a number the mark follows wherever it goes."
          },
          "enter-value": {
            "type": "number",
            "when": {
              "row": {
                "enter-value-kind": [
                  "number"
                ]
              }
            },
            "description": "The fixed entering line."
          },
          "enter-value-key": {
            "type": "citation",
            "when": {
              "row": {
                "enter-value-kind": [
                  "citation"
                ]
              }
            },
            "description": "Point to the entering line. Read it fresh at each comparison."
          },
          "enter-unit": {
            "type": "string",
            "when": {
              "row": {
                "enter-on": [
                  "line"
                ]
              }
            },
            "options": [
              "number",
              "share-of-the-ceiling"
            ],
            "description": "Use a fixed number or a share of the marked top. A share sits at that share of the fresh top; it can fall between whole points and is only compared, never stored."
          },
          "enter-direction": {
            "type": "string",
            "when": {
              "row": {
                "enter-on": [
                  "line"
                ]
              }
            },
            "options": [
              "rising",
              "falling"
            ],
            "description": "The direction that turns the state on."
          },
          "enter-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "enter-on": [
                  "event"
                ]
              }
            },
            "description": "Point to the event that turns the state on."
          },
          "leave-on": {
            "type": "string",
            "required": true,
            "options": [
              "line",
              "event",
              "after-a-wait"
            ],
            "description": "Whether a line, event, or wait turns the state off."
          },
          "leave-value-kind": {
            "type": "string",
            "when": {
              "row": {
                "leave-on": [
                  "line"
                ]
              }
            },
            "options": [
              "number",
              "citation"
            ],
            "description": "Whether the leaving line uses a fixed number or points to a number the mark follows wherever it goes."
          },
          "leave-value": {
            "type": "number",
            "when": {
              "row": {
                "leave-value-kind": [
                  "number"
                ]
              }
            },
            "description": "The fixed leaving line."
          },
          "leave-value-key": {
            "type": "citation",
            "when": {
              "row": {
                "leave-value-kind": [
                  "citation"
                ]
              }
            },
            "description": "Point to the leaving line. Read it fresh at each comparison."
          },
          "leave-unit": {
            "type": "string",
            "when": {
              "row": {
                "leave-on": [
                  "line"
                ]
              }
            },
            "options": [
              "number",
              "share-of-the-ceiling"
            ],
            "description": "Use a fixed number or a share of the marked top. A share sits at that share of the fresh top; it can fall between whole points and is only compared, never stored."
          },
          "leave-direction": {
            "type": "string",
            "when": {
              "row": {
                "leave-on": [
                  "line"
                ]
              }
            },
            "options": [
              "rising",
              "falling"
            ],
            "description": "The direction that turns the state off."
          },
          "leave-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "leave-on": [
                  "event",
                  "after-a-wait"
                ]
              }
            },
            "description": "Point to the leaving event or wait length."
          },
          "repeat": {
            "type": "string",
            "when": {
              "row": {
                "leave-on": [
                  "after-a-wait"
                ]
              }
            },
            "options": [
              "restart-the-wait",
              "keep-the-first-wait",
              "add-to-the-wait"
            ],
            "description": "Choose what another entry does while the wait is running."
          },
          "starts": {
            "type": "string",
            "required": true,
            "options": [
              "in",
              "out",
              "read-from-initial"
            ],
            "description": "Whether this state starts on, off, or follows the starting value."
          },
          "blocks-change": {
            "type": "string",
            "options": [
              "none",
              "blocks-rises",
              "blocks-falls",
              "blocks-all"
            ],
            "description": "Which incoming plain changes, costs, or drifts are blocked while this state is on. Omission means none."
          },
          "counts-at-line": {
            "type": "string",
            "options": [
              "at-the-line-counts",
              "must-pass-the-line"
            ],
            "description": "Override exact-landing for both line edges."
          }
        }
      },
      "costs": {
        "description": "List each action that checks whether this value can pay before it changes.",
        "when-empty": "No action checks this value before it changes; every change simply happens, and bands and limits still apply.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this cost in the game's words, such as dodge or cast-spell."
          },
          "direction": {
            "type": "string",
            "required": true,
            "options": [
              "rising",
              "falling"
            ],
            "description": "Whether paying moves toward the top or bottom."
          },
          "amount-key": {
            "type": "citation",
            "required": true,
            "description": "Point to the non-negative cost."
          },
          "action-declared-in": {
            "type": "citation",
            "required": true,
            "description": "Point to the action that receives refusal, shortage, or paid-amount reports."
          },
          "answer": {
            "type": "string",
            "options": [
              "refuse-the-action",
              "take-what-fits"
            ],
            "description": "Override the value-wide cost answer for this action."
          }
        }
      },
      "drifts": {
        "description": "List each drift, such as draining, recovery, or cooling.",
        "when-empty": "This value never changes on its own.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this drift in the game's words."
          },
          "direction": {
            "type": "string",
            "required": true,
            "options": [
              "rises",
              "falls",
              "toward-the-anchor"
            ],
            "description": "Move upward, downward, or toward the shared resting point."
          },
          "cadence": {
            "type": "string",
            "required": true,
            "options": [
              "per-game-step",
              "per-real-second",
              "per-turn",
              "at-a-named-moment"
            ],
            "description": "Choose when one contribution is made."
          },
          "moment-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "cadence": [
                  "at-a-named-moment"
                ]
              }
            },
            "description": "Point to the named moment."
          },
          "step-amount-key": {
            "type": "citation",
            "required": true,
            "description": "Point to the positive amount per occurrence."
          },
          "amount-kind": {
            "type": "string",
            "required": true,
            "options": [
              "fixed",
              "depends-on-state",
              "grows-while-it-runs"
            ],
            "description": "Whether the amount stays fixed, reads state, or grows while running."
          },
          "amount-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "amount-kind": [
                  "depends-on-state",
                  "grows-while-it-runs"
                ]
              }
            },
            "description": "Point to the state mapping or growth rule."
          },
          "stops-at-key": {
            "type": "citation",
            "required": true,
            "description": "Point to the number where this drift stops."
          },
          "at-stop": {
            "type": "string",
            "required": true,
            "options": [
              "lands-exactly",
              "overshoots-then-returns"
            ],
            "description": "Land exactly, or briefly pass the stop before returning when the row runs alone."
          }
        }
      },
      "interrupts": {
        "description": "List the conditions and pauses that control a drift. Every row for one drift must allow it before it runs.",
        "when-empty": "No listed condition or pause controls a drift.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this interruption."
          },
          "drift": {
            "type": "string",
            "required": true,
            "description": "Name the drift this row controls."
          },
          "kind": {
            "type": "string",
            "required": true,
            "options": [
              "off-while-condition",
              "runs-only-while-condition",
              "paused-after-event"
            ],
            "description": "Stay off during a condition, run only during it, or pause after an event."
          },
          "condition-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "kind": [
                  "off-while-condition",
                  "runs-only-while-condition"
                ]
              }
            },
            "description": "Point to the condition or to a band on this value."
          },
          "event-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "kind": [
                  "paused-after-event"
                ]
              }
            },
            "description": "Point to the event that starts the pause."
          },
          "pause-length-key": {
            "type": "citation",
            "when": {
              "row": {
                "kind": [
                  "paused-after-event"
                ]
              }
            },
            "description": "Point to the pause length."
          },
          "pause-length-kind": {
            "type": "string",
            "when": {
              "row": {
                "kind": [
                  "paused-after-event"
                ]
              }
            },
            "options": [
              "fixed",
              "depends-on-state"
            ],
            "description": "Whether the pause stays fixed or reads state."
          },
          "pause-length-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "pause-length-kind": [
                  "depends-on-state"
                ]
              }
            },
            "description": "Point to the rule for the changing pause."
          },
          "repeat-event": {
            "type": "string",
            "when": {
              "row": {
                "kind": [
                  "paused-after-event"
                ]
              }
            },
            "options": [
              "restart-the-wait",
              "keep-the-first-wait",
              "add-to-the-wait"
            ],
            "description": "Choose what another event does while the pause is running."
          }
        }
      },
      "resets": {
        "description": "List named moments that put this value back, such as respawn, a new day, or turn start. Use a reset when this return must always stay silent.",
        "when-empty": "Only creation applies the starting value.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this reset moment in the game's words."
          },
          "happens-at": {
            "type": "citation",
            "required": true,
            "description": "Point to the rule naming the moment."
          },
          "sets-value-to-key": {
            "type": "citation",
            "description": "Point to the stored target. Omission uses the starting value — with a cited initial, the number read at creation."
          },
          "clears-saved-fraction": {
            "type": "string",
            "when": {
              "flag": {
                "small-change": [
                  "save-the-fraction"
                ]
              }
            },
            "options": [
              "yes",
              "no"
            ],
            "description": "Whether this reset clears the saved fraction."
          },
          "re-arms-lines": {
            "type": "string",
            "required": true,
            "options": [
              "yes",
              "no"
            ],
            "description": "Whether cited lines regain their full allowance."
          },
          "resets-bands": {
            "type": "string",
            "options": [
              "return-to-starts",
              "recompute-from-target",
              "keep"
            ],
            "description": "Choose how named states respond. return-to-starts silently restores every band's declared start; recompute-from-target silently recomputes every line-geometry band against the reset target; keep preserves every band's state. Event-edged bands keep their state under both recompute-from-target and keep. Omission means keep; that is this definition's chosen default, not a forced choice."
          }
        }
      }
    }
  },
  "rules": {
    "range-nonempty": "max > min",
    "initial-not-below-min": "initial >= min",
    "initial-not-above-max": "initial <= max",
    "fraction-step-positive": "fraction-step > 0",
    "anchor-not-below-min": "anchor >= min",
    "anchor-not-above-max": "anchor <= max",
    "lap-lands-not-below-min": "lap-lands-on >= min",
    "lap-lands-not-above-max": "lap-lands-on <= max",
    "out-of-range-lands-not-below-min": "out-of-range-lands-on >= min",
    "out-of-range-lands-not-above-max": "out-of-range-lands-on <= max",
    "share-needs-two-walls": {
      "forbid": {
        "any": [
          {
            "flag": {
              "when-a-limit-moves": [
                "keep-the-share"
              ],
              "at-the-ceiling": [
                "no-ceiling"
              ]
            }
          },
          {
            "flag": {
              "when-a-limit-moves": [
                "keep-the-share"
              ],
              "at-the-floor": [
                "no-floor"
              ]
            }
          }
        ]
      },
      "message": "Keeping the same share needs a real floor and ceiling; close both limits or choose another response to a moving limit."
    },
    "moving-refill-cannot-lap": {
      "forbid": {
        "any": [
          {
            "flag": {
              "when-a-limit-moves": [
                "refill-to-the-new-ceiling"
              ],
              "at-the-ceiling": [
                "start-a-lap"
              ]
            }
          },
          {
            "flag": {
              "when-a-limit-moves": [
                "refill-to-the-new-ceiling"
              ],
              "at-the-floor": [
                "start-a-lap"
              ]
            }
          }
        ]
      },
      "message": "This moving-limit answer can place the value directly on either consuming edge, but a limit move never starts a lap; change the moving-limit or lap answer."
    },
    "another-lap-needs-extra": {
      "forbid": {
        "flag": {
          "more-than-one-lap": [
            "lap-again-while-it-fits"
          ],
          "the-extra-after-a-lap": [
            "drop-it"
          ]
        }
      },
      "message": "Another lap needs leftover from the first; carry it forward or allow only one lap."
    }
  },
  "origin": "https://opengdd.org/contracts/ranged-value-1",
  "mechanism": [
    "This is the one normative authority for event order. Questions describe choices; they do not redefine this sequence.",
    "An **operation** is one change the machine settles from start to finish: a plain change, cost, set, drift step or composed drift batch, lap movement, limit move, or reset. An **imposed change** is a plain change that happens without checking whether the value can pay it. **Residue** is the signed fraction saved for later. A **mark** is a line or one edge of a band. A **leg** is one visible stretch of movement with its own start and end. Each operation has an id supplied by its row or cited game rule and settles fully before the next begins. A lap sequence's outward, reset, and leftover legs retain their originating operation id; leg position and lap count distinguish their reports.",
    "A band is **line-geometry** only when both its edges are lines. A band with any event or wait edge is **event-edged**. An event-edged band keeps its state under every silent recompute (a set, a reset, or a limit move). A reset's explicit `return-to-starts` is a restore, not a recompute, and applies to every band.",
    "1. **Block.** If an active band blocks the operation's direction and the operation is an imposed change, cost, or drift, discard it. Report `blocked` to its source; a drift records the block but has no receiver. Stop this operation. Remove a blocked drift before several drifts combine. Blocks never stop sets, resets, limit moves, or lap movements. 2. **Resolve provisionally.** Fractional handling computes a provisional movement and new residue without committing either. A whole change leaves residue untouched. An absolute repositioning computes its destination and applies its own clearing rule; it does not pass through `small-change`. 3. **Check capacity for a cost.** Compare provisional movement with the room toward the named limit. Refusal discards movement and residue together. `take-what-fits` recomputes both from the approved amount and never keeps a fraction from the refused part. 4. **Find the raw candidate.** A change adds provisional movement to the held value. A set uses its accepted or clamped stored target. A lap movement, limit move, or reset uses its own absolute destination. 5. **Apply the edge.** A raw candidate strictly past a limit uses that limit's answer. Exact landing is ordinary unless `start-a-lap` applies, in which case `exact-landing` decides whether it consumes. Refusing the whole change discards provisional movement and residue, leaves the store untouched, reports refusal, and stops. Sets, resets, and limit moves use their own target rules. Drifts use the clipping exception below. 6. **Commit.** Store the final value and new residue together. No partly settled state is visible. 7. **Test marks for each leg.** The outward leg ends at the final value or consuming limit. A lap then has a lap leg, followed by each carried leftover as a new lap operation returning to step 1. Test lines and band edges on every leg. Recompute reached state from each stored endpoint in both directions; only a false-to-true transition in the row's direction reports. A `both` line keeps one reached state per direction. With raw reading, only the outward leg tests the raw candidate; reset and leftover legs test stored values. At a consuming limit, report outward marks, including a line on the limit, then the lap, then lap-leg marks. Apply `jumped-lines` separately to every leg. 8. **Report.** Every report carries before, after, direction, leg position, and operation id. A crossing or band transition also carries its row id. A lap carries its count. `lap-cap-reached` carries committed state. Returned extra carries its amount. A cost or block carries refusal, shortage, approved amount, or `blocked` as applicable. Raw-reading reports use the tested raw candidate as `after`; other reports use the stored endpoint. Direction is `rising`, `falling`, or `unchanged`.",
    "Every comparison reads the stored value at full precision, never a rounded display number. Every cited limit, mark and stop is read fresh at each comparison. Creation is not a movement or report. At creation, line and band-edge reached state is stored without reporting; lines use their declared arm state, and bands use their declared starting state. A share mark sits at the declared share multiplied by the fresh value at `max`; that position may be fractional and is compared, never stored. A line-geometry band that answers `read-from-initial` starts in exactly when the initial value sits on the reached side of its entering edge and not on the reached side of its leaving edge, each side read per that edge's declared direction, with an exact landing counted as this value's `exact-landing` answer or the row's `counts-at-line` override directs. An event-edged band that answers `read-from-initial` starts out. A silent recompute of a line-geometry band's state (a set, a limit move, or `recompute-from-target`) applies the same two-sided test against the value it recomputes from.",
    "**Lap loop.** A single originating operation may settle at most 32 laps. Before lap 33, reject the continuation, report `lap-cap-reached`, drop the remaining leftover, and keep the state committed by lap 32. A statically provable repeated lap state is a package error, but the runtime cap remains the termination guard. After each lap report, re-read either cited limit and check the lap target against the fresh range. If a limit moved, apply the limit-move ruling below; any `limit-moved` band report occurs before the lap leg. A limit move never repositions the value during this loop. Under `clear-it`, a lap clears the saved fraction after the consuming movement and before carried leftover is applied. Under `one-lap-per-change`, a second reach of the same consuming limit is stored without consuming and further excess is dropped.",
    "**Drift clipping.** A rising drift is eligible only below its stop; a falling drift only above it; a drift toward the anchor uses the matching test for its current direction. Clip each contribution to its stop before combining drifts. `overshoots-then-returns` is observable only when that row settles alone: its raw path may expose the overshoot, then a silent correction stores the stop, reports no mark, and recomputes reached state from the stored stop. A drift reaching a consuming limit clips there without consuming it.",
    "**Sets.** A set has no raw result. Marks see only a successful stored outcome. Clamping a target stores the nearer limit; raw reading never sees the rejected target. A successful set clears residue. A refused set does not.",
    "**Resets.** A reset stores its target, recomputes and stores every line's reached state from that target, and applies its arm, band, and fraction choices silently. Band state follows the row's `resets-bands` answer, not an automatic recompute. For a band that answers `read-from-initial`, `return-to-starts` restores the state stored at creation. It reports no crossing.",
    "**Limit moves.** A moving limit never fires a bare line. After the limit and any resulting current-value change settle, recompute and store every line's reached state and every line-geometry band's state against the new positions. Event-edged bands keep their state. A line-geometry band that enters or leaves this way reports the state change with cause `limit-moved`; a bare line reports nothing. The saved fraction is not cleared. A limit move that lands the value exactly on a consuming edge does not consume.",
    "**Continuous drift.** A `per-real-second` drift accrues continuously. Each settlement contributes its rate multiplied by elapsed cited-clock time, and fractional accrual passes through `small-change`.",
    "Sets, resets, and limit moves at one moment settle in the order the citing game rules fire them. A game rule that fires several at once must state their order.",
    "**Share-preserving limit moves.** `keep-the-share` is one absolute repositioning. A whole-number target rounds to nearest, with ties away from zero. Residue is unchanged.",
    "A band id may be cited anywhere this adoption's own game asks for a condition (`contracts.<adoption>.bands.<id>`). Other adoptions still may not cite it."
  ],
  "answers": {
    "number-kind": "whole-number",
    "small-change": "save-the-fraction",
    "exact-landing": "at-the-line-counts",
    "at-the-ceiling": "start-a-lap",
    "at-the-floor": "stop-at-the-floor",
    "jumped-lines": "all-in-order",
    "the-extra-after-a-lap": "drop-it",
    "more-than-one-lap": "one-lap-per-change",
    "a-lap-clears-saved-fraction": "clear-it",
    "lines-read": "the-final-value"
  },
  "values": {
    "min": 0,
    "max": 100,
    "initial": 0,
    "fraction-step": 1,
    "lap-lands-on": 0
  },
  "rows": {
    "lines": [
      {
        "id": "stagger-warning",
        "value-kind": "number",
        "value": 70,
        "direction": "rising",
        "refire": "every-crossing"
      },
      {
        "id": "stagger-break",
        "value-kind": "citation",
        "value-key": "contracts.boss-stagger.max",
        "direction": "rising",
        "refire": "every-crossing"
      },
      {
        "id": "poise-settled",
        "value-kind": "number",
        "value": 0,
        "direction": "falling",
        "refire": "every-crossing"
      }
    ],
    "bands": [
      {
        "id": "stagger-lockout",
        "enter-on": "line",
        "enter-value-kind": "number",
        "enter-value": 100,
        "enter-unit": "number",
        "enter-direction": "rising",
        "leave-on": "after-a-wait",
        "leave-declared-in": "tuning.stagger.lockout-seconds",
        "repeat": "restart-the-wait",
        "starts": "out",
        "blocks-change": "blocks-rises"
      }
    ],
    "drifts": [
      {
        "id": "poise-decay",
        "direction": "falls",
        "cadence": "per-real-second",
        "step-amount-key": "tuning.stagger.poise-decay-rate",
        "amount-kind": "grows-while-it-runs",
        "amount-declared-in": "02-mechanics.md#poise-decay-ramp",
        "stops-at-key": "contracts.boss-stagger.min",
        "at-stop": "lands-exactly"
      }
    ],
    "interrupts": [
      {
        "id": "after-a-hit",
        "drift": "poise-decay",
        "kind": "paused-after-event",
        "event-declared-in": "02-mechanics.md#poise-hit-landed",
        "pause-length-key": "tuning.stagger.poise-decay-delay",
        "pause-length-kind": "fixed",
        "repeat-event": "restart-the-wait"
      },
      {
        "id": "while-locked",
        "drift": "poise-decay",
        "kind": "off-while-condition",
        "condition-declared-in": "02-mechanics.md#stagger-lockout-band"
      }
    ],
    "reading-notes": [],
    "quantity-unit": [],
    "sets": [],
    "costs": [],
    "resets": []
  },
  "pack": "sha256:995be0ad12bc80c0f420ab42cf566f79a8543cc212533df2168fa0c3381b9fe3"
}