Determinism & replay

Puzzle solution share

puzzle-solution-share · an adoption of Replay scope, 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 racing ghosts, daily seeds, observer replays, solution shares, and other recorded reruns. It decides what the record contains, whether an update can still play it, what must match, and what happens at the first difference. Input encoding, random-number methods, storage, cameras, and networking stay in the game's own rules.

Read the full Replay scope 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.

What does this replay need to run again?

Choices for What does this replay need to run again?
The replay needs only the seed. A roguelike daily run rebuilds the day's dungeon before new play begins.

The record carries the seed but no input log; each claim's comparison reference is carried or recomputed from the record. Playback consumes the seed, accepts live inputs, and applies each claim's live-input answer.

The replay needs the seed and the recorded inputs. A racing ghost follows the recorded steering on the same generated track.

The record carries the seed and one ordered input log; each claim's comparison reference is carried or recomputed from the record. Playback consumes the seed and log from the declared starting point; changing either creates a different record instance.

Supplied answer The replay needs recorded inputs and one fixed start. A puzzle solution begins from the shared board and repeats the saved moves.

The record carries one fixed-start identity and one ordered input log; each claim's comparison reference is carried or recomputed from the record. Seed identity is not a separate requirement.

Why this is asked

A daily seed recreates a challenge. A racing ghost also needs the driver's recorded inputs.

What happens to a recorded replay after the game updates?

Choices for What happens to a recorded replay after the game updates?
The replay works only in the version that recorded it. A patched racing game labels an older ghost as incompatible.

When the recorded and running version ids differ, reject the replay before consuming its seed, start, or inputs. Equal version ids do not override failed content, mod, or settings checks.

Supplied answer The game converts the replay before playing it. A puzzle update maps an old move list onto the revised board rules.

When the version ids differ, a cited migration rule derives a new record for the running version while preserving the source record. Playback consumes only a successful migrated record and identifies both versions and the migration used.

The game tries the old replay and states what may differ. An RTS update names changed unit balance before the observer replay starts.

When the version ids differ, the running version consumes the original record after presenting the cited known cross-version differences. Actual mismatches still follow the divergence-response answer.

Why this is asked

A patch can change rules, content, or timing. The replay needs a clear version promise before playback starts.

What happens at the first result that does not match?

Choices for What happens at the first result that does not match?
Supplied answer Stop the replay and report the first difference. A puzzle solution stops on the first move that produces the wrong board.

Do not consume the next recorded input. Report the failed claim, comparison point, expected result, observed result, versions, and platforms, then end playback as diverged.

Keep playing and mark the replay as diverged. An RTS observer can watch the rest after a unit first appears in the wrong place.

Report the first difference, mark playback as diverged, and continue from playback's own state. Later comparisons are informational; they do not replace the first report or resynchronise playback to the reference.

Keep playing without showing the difference. A racing ghost can finish the lap after it drifts past the allowed gap.

Mark the mismatch inside the replay controller, emit no player-facing, ordinary-log, or telemetry report, and continue from playback's own state. Later comparisons are informational and playback remains diverged.

Why this is asked

A replay can stop, continue with a warning, or continue without showing the difference.

Numbers1 number

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

Allowed position gap

allowed-position-gap

The greatest allowed distance between recorded and replayed positions, in the position unit named by every position claim in this adoption.

Not used by this adoption. It applies when some reproduction claims row has matching standard Allowed position gap.

Rules1 rule

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

  • Best-effort replay after an update needs a visible difference notice; show and flag differences, or keep the replay on its recorded version.

    Forbidden when After an update is Best effort with declared divergence and Divergence response is Continue silently.

Lists2 lists

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

Replay record

replay-record

IdRecording declared inInput clock declared inFixed start declared inMigration declared inCross version divergence declared inDifference report declared in
shared-solutionpuzzle.solution-recordpuzzle.move-orderpuzzle.shared-board-statepuzzle.solution-migrationpuzzle.solution-error

Reproduction claims

reproduction-claims

IdArtifactPlatform reachShifts with live inputLive input dependence declared inMatching standardReproducesExcludesConditionsComparison points
solved-boardsolved board and move countevery-supported-platformoutcome-equivalentpuzzle.solved-board-resultpuzzle.solution-exclusionspuzzle.solution-conditionspuzzle.after-each-move-and-solve
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 tests30 tests apply

The contract comes with 48 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.

sealed-record-carries-replay-identity · shared-solution

shared-solution sealed records carry the complete replay identity

scenarioper replay-record row

Applies to the shared-solution row.

Each sealed shared-solution record has its own instance identity and carries, as named at puzzle.solution-record, the replay identity fields and the fixed-start identity and ordered input log and no separate seed, together with every claim's captured reference or sealed recomputation source. A reference never comes from live play. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

a sealed record made from replay family shared-solution and its manifest at puzzle.solution-record

When
  • the record is inspected before playback
Then
  • the record carries its own stable instance identity, recording version, platform, content-set identity, settings and mod identity, the fixed-start identity and ordered input log and no separate seed, and every reproduction claim's comparison reference or sealed source data for deterministic recomputation
  • each comparison reference is captured during recording or deterministically recomputed from the sealed record, never obtained from live play
Diagnostics
  • puzzle-solution-share-record-manifest
  • puzzle-solution-share-reference-source

migrated-record-keeps-source-identity · shared-solution

a migrated record has its own identity and keeps its source

scenarioper replay-record row

Applies to the shared-solution row.

A successful migration under puzzle.solution-migration creates one derived record with its own identity, the two versions, the migration rule, and a link to the unchanged source. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

a sealed source record from replay family shared-solution and a different running version

When
  • the deterministic migration at puzzle.solution-migration succeeds
Then
  • one derived record is created with its own stable instance identity and a link to the unchanged source record
  • the derived record names the source version, target version, and migration rule
Diagnostics
  • puzzle-solution-share-record-manifest
  • puzzle-solution-share-migration-record

playback-result-uses-closed-vocabulary

the terminal playback result uses the closed vocabulary

scenarioonce

Applies to puzzle-solution-share.

puzzle-solution-share playback is in progress until it ends. Its terminal playback result is exactly one of diverged, rejected, or complete.

Test steps and diagnostics
Given

each puzzle-solution-share playback from start until it ends

When
  • the playback result is read before and after termination
Then
  • before termination the playback is in progress
  • at termination the playback result is exactly one of diverged, rejected, or complete, and never two of them
Diagnostics
  • puzzle-solution-share-playback-result

record-establishes-declared-start · shared-solution

shared-solution records its selected start before claimed results

scenarioper replay-record row

Applies to the shared-solution row.

The recording version, platform, content-set identity, settings, and mod identity are fixed from puzzle.solution-record before the first captured seed, start, or input and do not change for the life of the recording. shared-solution then captures the fixed-start identity before the first input so the cited state rule can verify it. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

a new shared-solution recording about to begin, with its manifest at puzzle.solution-record

When
  • recording establishes its start
Then
  • the recorder captures the fixed-start identity before the first input so the cited state rule can verify it
  • the recording version, platform, content-set identity, settings, and mod identity are fixed from puzzle.solution-record before the first captured seed, start, or input and do not change for the life of the recording
Diagnostics
  • puzzle-solution-share-record-manifest
  • puzzle-solution-share-recording-trace

input-log-captures-complete-action-order · shared-solution

shared-solution captures every mapped action in cited order

scenarioper replay-record row

Applies to the shared-solution row.

From the start at puzzle.solution-record, shared-solution captures every mapped game action in complete order at the clock, step, or turn cited at puzzle.move-order. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

one shared-solution recording with mapped game actions before and after the cited start

When
  • input capture runs from the start named at puzzle.solution-record using the clock, step, or turn at puzzle.move-order
Then
  • every mapped game action after capture begins enters one ordered input log in complete order at the cited clock, step, or turn
  • no action before capture begins enters the log
Diagnostics
  • puzzle-solution-share-input-log-trace
  • puzzle-solution-share-recording-trace

seed-only-record-captures-no-input

Row.id captures no input log

scenarioper replay-record row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed only.

claim-records-reference-or-recomputation-source · solved-board

solved-board records its comparison reference source

scenarioper reproduction-claims row

Applies to the solved-board row.

At every point cited at puzzle.after-each-move-and-solve, recording captures the reference solved-board needs or all sealed data the family row's cited method needs to recompute it. The record distinguishes those two sources. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

recording reaches each solved-board comparison point cited at puzzle.after-each-move-and-solve

When
  • the recorder handles the claim at that point
Then
  • the record captures the comparison reference required by solved-board's matching standard or all sealed source data required by the family row's cited recomputation method
  • the record distinguishes a captured reference from sealed recomputation source data
Diagnostics
  • puzzle-solution-share-reference-source
  • puzzle-solution-share-recording-trace

record-seals-at-boundary · shared-solution

shared-solution seals one immutable record at its boundary

scenarioper replay-record row

Applies to the shared-solution row.

At the boundary cited at puzzle.solution-record, shared-solution seals its instance identity and contents. Any later edit creates a different instance in the same replay family. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

one shared-solution recording approaching the end boundary at puzzle.solution-record

When
  • capture reaches that boundary and a later edit is requested
Then
  • capture ends at the cited boundary and seals the record's instance identity and contents
  • the later edit creates a different record instance in the same replay family and leaves the sealed record unchanged
Diagnostics
  • puzzle-solution-share-record-manifest
  • puzzle-solution-share-recording-trace

record-wide-identity-precedes-consumption · shared-solution

shared-solution checks record-wide identity before consumption

scenarioper replay-record row

Applies to the shared-solution row.

Before consuming a seed, start, or input, shared-solution reads the record identity at puzzle.solution-record and the cited compatibility conditions. Each record-wide identity it carries rejects through puzzle.solution-error when it fails; neither an unchanged version id nor the update policy excuses a failed identity. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

sealed shared-solution records in which each record-wide identity this adoption carries fails in turn — content-set identity, settings, mods, and the fixed start where present — including a content patch whose version id is unchanged

When
  • playback selection begins
Then
  • the version, platform, content-set identity, settings, and mod identity at puzzle.solution-record and every cited compatibility condition are read before any seed, start, or input is consumed
  • each failed record-wide identity the adoption carries rejects the record and presents the incompatibility report through puzzle.solution-error before any seed, start, or input is consumed
  • the unchanged version id does not turn the failed content identity into a pass
  • the update policy is not used to excuse a failed identity
Diagnostics
  • puzzle-solution-share-identity-check-trace
  • puzzle-solution-share-rejection-report
  • puzzle-solution-share-input-log-trace

compatible-record-is-played · shared-solution

shared-solution plays a compatible record

scenarioper replay-record row

Applies to the shared-solution row.

A sealed shared-solution record whose complete replay identity matches the running game and whose cited compatibility conditions hold is played rather than rejected. Playback consumes the seed, start, or inputs it carries and reaches complete or diverged, never rejected.

Test steps and diagnostics
Given

a sealed shared-solution record whose version, platform, content-set identity, settings, mods, and start all match the running game and whose cited compatibility conditions hold

When
  • playback selection checks the compatible record
Then
  • playback is not rejected
  • playback consumes the seed, start, or inputs the record carries
  • playback reaches a terminal result that is complete or diverged, never rejected
Diagnostics
  • puzzle-solution-share-identity-check-trace
  • puzzle-solution-share-playback-result

recorded-platform-only-excludes-other-platforms

Row.id compares only on the recording platform

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: no row in reproduction-claims matches platform-reach recorded platform only.

every-supported-platform-excludes-only-unsupported-platforms · solved-board

solved-board compares on every supported platform

scenarioper reproduction-claims row

Applies to the solved-board row.

Claim solved-board remains eligible on every supported platform. It is excluded without divergence on an unsupported platform, and other eligible claims continue. The comparison log distinguishes exclusion from a match.

Test steps and diagnostics
Given

solved-board playback on each supported platform and on each unsupported running platform the adoption can construct

When
  • claim platform reach is selected
Then
  • solved-board remains eligible on every supported platform
  • on each constructible unsupported running platform it is not compared and cannot cause divergence, while every other eligible claim continues; where none is constructible, this clause asserts nothing
  • the comparison log distinguishes unsupported-platform exclusion from a match
Diagnostics
  • puzzle-solution-share-platform-matrix
  • puzzle-solution-share-comparison-log

same-version-only-rejects-version-mismatch

Row.id rejects a different running version

scenarioper replay-record row

Does not apply to puzzle-solution-share: after an update is migrate then replay, not same version only.

migration-runs-once-before-playback · shared-solution

shared-solution migrates once or rejects

scenarioper replay-record row

Applies to the shared-solution row.

For differing versions, shared-solution runs puzzle.solution-migration once. Success creates the derived record, playback consumes only that record, and where the migration ran, the recorded input clock maps to an existing running-version clock before any input is consumed. Migration or clock-mapping failure rejects through puzzle.solution-error before consumption. For equal version ids, no migration runs, no derived record is created, and playback consumes the source record. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

sealed shared-solution records whose version ids are equal to and differ from the running version, including successful and failed migration and each input-log record this adoption can construct with and without a running-version clock mapping

When
  • playback selection applies the update policy at puzzle.solution-migration
Then
  • when the recorded and running version ids differ, the migration rule runs once; success creates the derived record and playback consumes only that derived record
  • when the recorded and running version ids are equal, no migration runs, no derived record is created, and playback consumes the source record
  • where the migration ran, the recorded input clock maps to an existing running-version clock before any input is consumed
  • failed migration, or failed clock mapping where an input clock exists, rejects through puzzle.solution-error before any seed, start, or input is consumed
Diagnostics
  • puzzle-solution-share-migration-record
  • puzzle-solution-share-rejection-report
  • puzzle-solution-share-input-log-trace

best-effort-presents-known-differences

Row.id presents known cross-version differences before playback

scenarioper replay-record row

Does not apply to puzzle-solution-share: after an update is migrate then replay, not best effort with declared divergence.

seeded-playback-recreates-start

Row.id supplies the recorded seed or rejects

scenarioper replay-record row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed only or seed and input log.

fixed-start-playback-verifies-or-restores · shared-solution

shared-solution verifies or restores the fixed start

scenarioper replay-record row

Applies to the shared-solution row.

Fixed-start shared-solution playback verifies or restores the fixed starting state of the record playback consumes, which is the derived record wherever a migration ran, through puzzle.shared-board-state before the first input. If it cannot establish the state, playback rejects. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

a playable shared-solution record, once with its fixed start available and once with it unavailable

When
  • playback applies the state rule at puzzle.shared-board-state
Then
  • the available run verifies or restores the fixed starting state of the record playback consumes, which is the derived record wherever a migration ran, before the first input
  • the unavailable run becomes rejected before consuming an input
Diagnostics
  • puzzle-solution-share-start-trace
  • puzzle-solution-share-playback-result

input-log-playback-consumes-cited-order · shared-solution

shared-solution consumes recorded inputs in cited order

scenarioper replay-record row

Applies to the shared-solution row.

shared-solution playback consumes the recorded input log once, in its recorded order, at the clock, step, or turn cited at puzzle.move-order, or, where a migration ran, at the running-version clock that migration mapped it to. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

a playable shared-solution record with distinct mapped actions in its input log

When
  • playback runs at the clock, step, or turn cited at puzzle.move-order
Then
  • every recorded input is consumed once in recorded order at the clock, step, or turn cited at puzzle.move-order, or, where a migration ran, at the running-version clock that migration mapped it to
  • no live input replaces or reorders a recorded action
Diagnostics
  • puzzle-solution-share-input-log-trace
  • puzzle-solution-share-playback-result

seed-only-playback-accepts-live-input

Row.id accepts live input without a recorded log

scenarioper replay-record row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed only.

seed-fixed-claim-ignores-live-input-variation

Row.id cannot change when live inputs vary

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: no row in reproduction-claims matches shifts-with-live-input seed fixes this claim.

live-input-shifted-claim-reads-only-cited-facts

Row.id reads only its cited live-input facts

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: no row in reproduction-claims matches shifts-with-live-input live input may shift this claim.

claim-reference-comes-from-sealed-record · solved-board

solved-board obtains its reference from the sealed record

scenarioper reproduction-claims row

Applies to the solved-board row.

At puzzle.after-each-move-and-solve, solved-board reads a captured comparison reference or deterministically recomputes it from the sealed record through the family row's cited method. The reference-source record distinguishes the two and proves live play supplied neither. An unavailable form asserts nothing. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

solved-board playbacks using a captured reference and, where the adoption can construct one, a deterministically recomputed reference

When
  • playback reaches the points at puzzle.after-each-move-and-solve
Then
  • the reference is read from the sealed record or deterministically recomputed from it using the family row's cited method and puzzle.after-each-move-and-solve
  • the reference-source record distinguishes capture from recomputation and proves no reference was read from live play
  • where the adoption cannot construct one of the two reference forms, that form asserts nothing
Diagnostics
  • puzzle-solution-share-reference-source
  • puzzle-solution-share-comparison-log

unmet-claim-condition-skips-comparison · solved-board

solved-board reads conditions before comparison

scenarioper reproduction-claims row

Applies to the solved-board row.

At each constructible point where puzzle.solution-conditions is not met, solved-board is not compared, does not diverge, and does not reject or make playback terminal because of that condition alone. Every other eligible claim, where the adoption declares one, is still compared at its own points, and the logs distinguish the skip from a match. If no such point exists, the test asserts nothing. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

each solved-board comparison point this adoption can construct where the conditions at puzzle.solution-conditions are not met

When
  • playback reaches that point
Then
  • the conditions are read before a comparison is attempted
  • the claim is recorded as not compared and does not mark a divergence
  • the playback is not rejected and does not become terminal because of that claim's unmet condition alone
  • every other eligible claim is still compared at its own comparison points; where no other eligible claim exists, this clause asserts nothing
  • where no unmet-condition point can be constructed, this test asserts nothing
Diagnostics
  • puzzle-solution-share-condition-trace
  • puzzle-solution-share-comparison-log
  • puzzle-solution-share-playback-result

bit-exact-claim-compares-declared-bytes

Row.id compares every included byte

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: no row in reproduction-claims matches matching-standard bit exact state.

outcome-equivalent-claim-compares-declared-fields · solved-board

solved-board compares every included outcome field

scenarioper reproduction-claims row

Applies to the solved-board row.

Outcome-equivalent claim solved-board compares every outcome field named at puzzle.solved-board-result after subtracting puzzle.solution-exclusions. Excluded state is never compared. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

eligible solved-board comparisons with each included outcome field changed in turn and, where puzzle.solution-exclusions names excluded state, that state changed separately

When
  • playback compares the result to its comparison reference
Then
  • every outcome field named at puzzle.solved-board-result after subtracting puzzle.solution-exclusions is compared
  • each changed included field fails the matching standard; changed excluded state is never compared, and where the cited section says nothing is excluded that clause asserts nothing
Diagnostics
  • puzzle-solution-share-comparison-log
  • puzzle-solution-share-reference-source

position-claim-uses-adoption-gap

Row.id passes only within the declared allowed gap

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: allowed-position-gap is not in use for puzzle-solution-share.

seed-fixed-claim-repeats-from-declared-record

the Row.artifact result repeats from the declared seed record

generalper reproduction-claims row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed only.

live-input-shifted-claim-repeats-within-cited-rule

the Row.artifact result repeats within its cited live-input rule

generalper reproduction-claims row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed only.

seed-and-input-claim-repeats-from-declared-record

the Row.artifact result repeats from the declared seed and input record

generalper reproduction-claims row

Does not apply to puzzle-solution-share: replay record is input log from fixed start, not seed and input log.

fixed-start-input-claim-repeats-from-declared-record · solved-board

the solved board and move count result repeats from the declared fixed start and input record

generalper reproduction-claims row

Applies to the solved-board row.

Across recorded runs where this claim is eligible, the solved board and move count result from the same sealed fixed-start identity and ordered input log satisfies solved-board's matching standard at puzzle.after-each-move-and-solve whenever the claim is eligible. The test names the address and restates nothing from it.

Test steps and diagnostics
Holds

for every eligible case for the solved board and move count result in scope, playback using the same sealed fixed-start identity and ordered input log satisfies solved-board's selected matching standard at the points cited at puzzle.after-each-move-and-solve

Seeds

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

Scope

recorded runs where this claim is eligible

Diagnostics
  • puzzle-solution-share-record-manifest
  • puzzle-solution-share-input-log-trace
  • puzzle-solution-share-comparison-log

outside-conditions-make-no-promise

changes outside cited conditions do not fail this contract

scenarioonce

Applies to puzzle-solution-share.

A change outside the cited conditions is never itself a reason to reject a record or to mark a divergence. A divergence arises only when a claimed result fails its comparison at an eligible comparison point. If the adoption can construct no such change, the test asserts nothing.

Test steps and diagnostics
Given

each change outside the cited conditions that the puzzle-solution-share adoption can construct

When
  • the change is observed during playback
Then
  • no change outside the cited conditions is itself a ground for rejection or for a divergence mark; a divergence arises only from a failed comparison of a claimed result at an eligible comparison point
  • where no such change can be constructed, this test asserts nothing
Diagnostics
  • puzzle-solution-share-condition-trace
  • puzzle-solution-share-comparison-log
  • puzzle-solution-share-playback-result

first-difference-retains-complete-record · shared-solution

shared-solution retains the first failed eligible comparison

scenarioper replay-record row

Applies to the shared-solution row.

At the first failed eligible comparison, shared-solution becomes diverged and retains the claim, point, expected and observed results, versions, platforms, and last consumed input when present. The records distinguish failure from a skipped comparison.

Test steps and diagnostics
Given

one shared-solution playback with a first failed eligible comparison, with a last consumed input where this record has one

When
  • the comparison fails its claim's matching standard
Then
  • the playback result becomes diverged at that first difference
  • the retained divergence record holds the claim id, comparison point, expected result, observed result, recorded and running versions, recorded and running platforms, and last consumed input when present
  • the retained record distinguishes this failed comparison from a skipped comparison
Diagnostics
  • puzzle-solution-share-divergence-record
  • puzzle-solution-share-playback-result
  • puzzle-solution-share-comparison-log

stop-and-report-ends-at-first-difference · shared-solution

shared-solution reports and stops at the first difference

scenarioper replay-record row

Applies to the shared-solution row.

At the first difference, shared-solution presents the retained difference through puzzle.solution-error, consumes no later input, and ends diverged. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

one shared-solution playback whose next eligible comparison is its first difference, with a later recorded or live input where playback can have one

When
  • the difference is retained
Then
  • the difference is presented through puzzle.solution-error before any later input is consumed
  • no later input is consumed and playback ends with result diverged
Diagnostics
  • puzzle-solution-share-divergence-record
  • puzzle-solution-share-difference-report
  • puzzle-solution-share-input-log-trace

continue-and-flag-keeps-visible-divergence

Row.id reports and continues from playback state

scenarioper replay-record row

Does not apply to puzzle-solution-share: divergence response is stop and report, not continue and flag.

continue-silently-keeps-internal-divergence

Row.id continues with an internal diverged mark

scenarioper replay-record row

Does not apply to puzzle-solution-share: divergence response is stop and report, not continue silently.

later-comparisons-never-resynchronise

later comparisons are informational only

scenarioonce

Does not apply to puzzle-solution-share: divergence response is stop and report, not continue and flag or continue silently.

complete-means-all-made-comparisons-matched · shared-solution

complete means every comparison actually made matched

scenarioper replay-record row

Applies to the shared-solution row.

When shared-solution reaches its end at puzzle.solution-record without an eligible failure, complete means every comparison actually made matched. It promises nothing about excluded claims, unmet conditions, or excluded state, which the log distinguishes from matches. The test names the address and restates nothing from it.

Test steps and diagnostics
Given

one shared-solution record reaching the end boundary at puzzle.solution-record with no failed eligible comparison

When
  • the terminal playback result is assigned
Then
  • the playback result becomes complete exactly when every comparison actually made matched
  • the comparison log separately records excluded claims, unmet conditions, and excluded state, and complete makes no promise about them
Diagnostics
  • puzzle-solution-share-playback-result
  • puzzle-solution-share-comparison-log

same-moment-events-preserve-event-resolution-order

same-moment events preserve Event resolution order

scenarioonce

Applies to puzzle-solution-share.

Events at the same replay moment enter in the total order Event resolution supplies. The replay lifecycle introduces no reordering of its own between the supplied order and processing.

Test steps and diagnostics
Given

two or more events offered at the same puzzle-solution-share replay moment in a known total order from Event resolution

When
  • the events enter the replay lifecycle
Then
  • the lifecycle processes them in exactly the supplied total order
  • the replay lifecycle introduces no reordering of its own between the supplied order and processing
Diagnostics
  • puzzle-solution-share-event-order-trace

adoption-declares-exactly-one-replay-record

declaration check: the adoption declares exactly one replay-record row

scenarioonce

Applies to puzzle-solution-share.

This declaration check reads the adoption, not the running game. A legal adoption has exactly one replay-record row. Any other count is a defect this test fails by construction; the validator does not enforce the maximum.

Test steps and diagnostics
Given

the puzzle-solution-share adoption document, not the running game

When
  • a reviewer counts replay-record rows
Then
  • the adoption has exactly one replay-record row; zero rows or more than one row is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

adoption-declares-at-least-one-reproduction-claim

declaration check: the adoption declares at least one reproduction claim

scenarioonce

Applies to puzzle-solution-share.

This declaration check reads the adoption, not the running game. A legal adoption has at least one reproduction claim. An empty claim list is a defect this test fails by construction; the validator does not enforce the minimum.

Test steps and diagnostics
Given

the puzzle-solution-share adoption document, not the running game

When
  • a reviewer counts reproduction-claims rows
Then
  • the adoption has at least one reproduction-claims row; an empty list is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

claim-standard-agrees-with-cited-prose · solved-board

declaration check: solved-board's matching standard agrees with its cited prose

scenarioper reproduction-claims row

Applies to the solved-board row.

This declaration check reads the adoption and puzzle.solved-board-result with puzzle.solution-exclusions, not the running game. The cited prose must describe the kind of result selected by solved-board's matching standard; any other pairing is a defect this test fails by construction. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

the puzzle-solution-share adoption and the prose at puzzle.solved-board-result and puzzle.solution-exclusions, not the running game

When
  • a reviewer compares the selected matching-standard with the included and excluded result description
Then
  • the prose names bytes for bit-exact-state, outcome fields for outcome-equivalent, or positions and their space for allowed-position-gap, matching the row's selected standard
  • any disagreement is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

every-platform-claim-has-multiple-platform-evidence · solved-board

declaration check: solved-board was tested on more than one platform

scenarioper reproduction-claims row

Applies to the solved-board row.

This declaration check reads the adoption and existing verification evidence, not the running game. Every-supported-platform claim solved-board is legal only with evidence from more than one supported platform; any narrower evidence is a defect this test fails by construction.

Test steps and diagnostics
Given

the puzzle-solution-share adoption and its verification evidence, not a new running-game execution

When
  • a reviewer checks the evidence for every-supported-platform claim solved-board
Then
  • the evidence records this claim tested on more than one supported platform; one platform or none is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-platform-matrix
  • puzzle-solution-share-declaration-record

claim-excludes-cites-separate-section · solved-board

declaration check: solved-board has a separate exclusions section

scenarioper reproduction-claims row

Applies to the solved-board row.

This declaration check reads the adoption and cited prose, not the running game. puzzle.solution-exclusions must be a section separate from puzzle.solved-board-result and must name exclusions or explicitly say there are none. Any other shape is a defect this test fails by construction. The test names both addresses and restates nothing from them.

Test steps and diagnostics
Given

the puzzle-solution-share adoption and the prose at puzzle.solved-board-result and puzzle.solution-exclusions, not the running game

When
  • a reviewer checks the two cited sections
Then
  • puzzle.solution-exclusions names a section separate from puzzle.solved-board-result and that section names every exclusion or states explicitly that nothing is excluded
  • a shared section, an omitted exclusion, or silence when nothing is excluded is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

claim-citations-state-their-own-duties · solved-board

declaration check: solved-board's four required citations state their own duties

scenarioper reproduction-claims row

Applies to the solved-board row.

This declaration check reads the adoption and cited prose, not the running game. puzzle.solved-board-result, puzzle.solution-exclusions, puzzle.solution-conditions, and puzzle.after-each-move-and-solve must respectively state the included result, separate exclusions, conditions, and reference and comparison points. Any wrong meaning is a defect this test fails by construction. The test names every address and restates nothing from them.

Test steps and diagnostics
Given

the puzzle-solution-share adoption and the prose at puzzle.solved-board-result, puzzle.solution-exclusions, puzzle.solution-conditions, and puzzle.after-each-move-and-solve, not the running game

When
  • a reviewer checks the meaning of each required citation
Then
  • the four addresses respectively name the included result, the separate exclusions, the promise conditions, and the capture-or-recomputation and comparison points
  • a citation with another meaning is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

live-input-shifted-claim-cites-dependence-rule

declaration check: Row.id cites its live-input dependence rule

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: no row in reproduction-claims matches shifts-with-live-input live input may shift this claim.

shared-conditions-section-covers-every-citing-claim · solved-board

declaration check: solved-board's shared conditions section covers every citing claim

scenarioper reproduction-claims row

Applies to the solved-board row.

This declaration check reads the adoption and the cited prose at puzzle.solution-conditions, not the running game. A section cited by more than one claim states the conditions for every citing claim by name; a shared section covering only some citing claims is a defect this test fails by construction. Where no other claim cites the section, this check asserts nothing.

Test steps and diagnostics
Given

the puzzle-solution-share adoption and the cited prose at puzzle.solution-conditions, not the running game

When
  • a reviewer checks every reproduction claim that cites the same conditions section
Then
  • where the section at puzzle.solution-conditions is also cited by another claim in this adoption, it states the conditions for each citing claim by name
  • where no other claim cites it, this check asserts nothing
  • any shared section that covers only some citing claims is a defect this test fails by construction
Diagnostics
  • puzzle-solution-share-declaration-record

position-gap-unit-matches-cited-space

declaration check: Row.id's position gap unit matches its cited space

scenarioper reproduction-claims row

Does not apply to puzzle-solution-share: allowed-position-gap is not in use for puzzle-solution-share.

replay-holds

the replay mechanism holds for the whole run

generalonce

Applies to puzzle-solution-share.

Across recorded runs across every claim, each platform reach the adoption declares, an update where the adoption allows one, and a first difference where one can be constructed, every playback enters the mechanism's stages in order, leaves them only at a terminal result, and never revisits an earlier stage. References never come from live play; rejected or diverged playback consumes no forbidden input; each terminal result is exactly diverged, rejected, or complete. The pack's default audit seeds apply unless the adoption supplies its own.

Test steps and diagnostics
Holds

every playback entered the mechanism's numbered stages in order, left them only at a terminal result, and never revisited an earlier stage; no comparison read a comparison reference from live play; no rejected or diverged playback consumed an input that its selected response or rejection forbade it to consume; every terminal playback result was exactly one of diverged, rejected, or complete

Seeds

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

Scope

recorded runs across every claim, each platform reach the adoption declares, an update where the adoption allows one, and a first difference where one can be constructed

Diagnostics
  • puzzle-solution-share-recording-trace
  • puzzle-solution-share-identity-check-trace
  • puzzle-solution-share-reference-source
  • puzzle-solution-share-comparison-log
  • puzzle-solution-share-input-log-trace
  • puzzle-solution-share-playback-result
  • puzzle-solution-share-first-ordering-violation
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": "replay-scope",
  "version": 1,
  "summary": "Covers racing ghosts, daily seeds, observer replays, solution shares, and other recorded reruns. It decides what the record contains, whether an update can still play it, what must match, and what happens at the first difference. Input encoding, random-number methods, storage, cameras, and networking stay in the game's own rules.",
  "questions": {
    "replay-record": {
      "asks": "What does this replay need to run again?",
      "rationale": "A daily seed recreates a challenge. A racing ghost also needs the driver's recorded inputs.",
      "options": {
        "seed-only": {
          "meaning": "The replay needs only the seed. A roguelike daily run rebuilds the day's dungeon before new play begins.",
          "semantics": "The record carries the seed but no input log; each claim's comparison reference is carried or recomputed from the record. Playback consumes the seed, accepts live inputs, and applies each claim's live-input answer."
        },
        "seed-and-input-log": {
          "meaning": "The replay needs the seed and the recorded inputs. A racing ghost follows the recorded steering on the same generated track.",
          "semantics": "The record carries the seed and one ordered input log; each claim's comparison reference is carried or recomputed from the record. Playback consumes the seed and log from the declared starting point; changing either creates a different record instance."
        },
        "input-log-from-fixed-start": {
          "meaning": "The replay needs recorded inputs and one fixed start. A puzzle solution begins from the shared board and repeats the saved moves.",
          "semantics": "The record carries one fixed-start identity and one ordered input log; each claim's comparison reference is carried or recomputed from the record. Seed identity is not a separate requirement."
        }
      }
    },
    "after-an-update": {
      "asks": "What happens to a recorded replay after the game updates?",
      "rationale": "A patch can change rules, content, or timing. The replay needs a clear version promise before playback starts.",
      "options": {
        "same-version-only": {
          "meaning": "The replay works only in the version that recorded it. A patched racing game labels an older ghost as incompatible.",
          "semantics": "When the recorded and running version ids differ, reject the replay before consuming its seed, start, or inputs. Equal version ids do not override failed content, mod, or settings checks."
        },
        "migrate-then-replay": {
          "meaning": "The game converts the replay before playing it. A puzzle update maps an old move list onto the revised board rules.",
          "semantics": "When the version ids differ, a cited migration rule derives a new record for the running version while preserving the source record. Playback consumes only a successful migrated record and identifies both versions and the migration used."
        },
        "best-effort-with-declared-divergence": {
          "meaning": "The game tries the old replay and states what may differ. An RTS update names changed unit balance before the observer replay starts.",
          "semantics": "When the version ids differ, the running version consumes the original record after presenting the cited known cross-version differences. Actual mismatches still follow the divergence-response answer."
        }
      }
    },
    "divergence-response": {
      "asks": "What happens at the first result that does not match?",
      "rationale": "A replay can stop, continue with a warning, or continue without showing the difference.",
      "options": {
        "stop-and-report": {
          "meaning": "Stop the replay and report the first difference. A puzzle solution stops on the first move that produces the wrong board.",
          "semantics": "Do not consume the next recorded input. Report the failed claim, comparison point, expected result, observed result, versions, and platforms, then end playback as diverged."
        },
        "continue-and-flag": {
          "meaning": "Keep playing and mark the replay as diverged. An RTS observer can watch the rest after a unit first appears in the wrong place.",
          "semantics": "Report the first difference, mark playback as diverged, and continue from playback's own state. Later comparisons are informational; they do not replace the first report or resynchronise playback to the reference."
        },
        "continue-silently": {
          "meaning": "Keep playing without showing the difference. A racing ghost can finish the lap after it drifts past the allowed gap.",
          "semantics": "Mark the mismatch inside the replay controller, emit no player-facing, ordinary-log, or telemetry report, and continue from playback's own state. Later comparisons are informational and playback remains diverged."
        }
      }
    }
  },
  "declares": {
    "values": {
      "allowed-position-gap": {
        "description": "The greatest allowed distance between recorded and replayed positions, in the position unit named by every position claim in this adoption.",
        "range": [
          0,
          1000000
        ],
        "forms": [
          "number",
          "citation"
        ],
        "when": {
          "row-has": {
            "reproduction-claims": {
              "matching-standard": [
                "allowed-position-gap"
              ]
            }
          }
        }
      }
    },
    "rows": {
      "replay-record": {
        "description": "Give the rules that capture and read this replay family. One adoption has exactly one row.",
        "when-empty": "An empty replay-record list is never a behavior choice: this adoption requires exactly one row, and a reviewer rejects a file without it.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this replay family in the game's words, such as ghost-lap or observer-match. Each sealed record created from the family carries its own cited instance identity."
          },
          "recording-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The rule naming the start and end of recording. It fixes the recording version, platform, content-set identity, settings, mod identity, and the record's own instance identity. It names the seed or fixed start and the input log when used, and says whether each claim's comparison reference is captured at recording or recomputed from the record at playback."
          },
          "input-clock-declared-in": {
            "type": "citation",
            "when": {
              "flag": {
                "replay-record": [
                  "seed-and-input-log",
                  "input-log-from-fixed-start"
                ]
              }
            },
            "description": "The rule that orders recorded inputs and states the clock, step, or turn used to play them back."
          },
          "fixed-start-declared-in": {
            "type": "citation",
            "when": {
              "flag": {
                "replay-record": [
                  "input-log-from-fixed-start"
                ]
              }
            },
            "description": "The rule that identifies and verifies the fixed starting state before the first input."
          },
          "migration-declared-in": {
            "type": "citation",
            "when": {
              "flag": {
                "after-an-update": [
                  "migrate-then-replay"
                ]
              }
            },
            "description": "The deterministic rule that derives the running-version record while preserving the source record."
          },
          "cross-version-divergence-declared-in": {
            "type": "citation",
            "when": {
              "flag": {
                "after-an-update": [
                  "best-effort-with-declared-divergence"
                ]
              }
            },
            "description": "The player-facing statement of known changes that may alter this replay in the running version."
          },
          "difference-report-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The incompatibility or difference report. It presents version, content, mod, settings, start, or migration rejection before playback and presents the first failed claim and comparison details when the selected response is visible."
          }
        }
      },
      "reproduction-claims": {
        "description": "List one row for each result this replay promises to compare. Rows may share one conditions section when the same conditions apply. Shared test material must cover every row that cites it.",
        "when-empty": "This adoption makes no replay promise without at least one result to compare, and a reviewer rejects the empty list.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "Name this comparison claim in the game's words, such as car-path or match-state."
          },
          "artifact": {
            "type": "string",
            "required": true,
            "description": "The game's plain name for the result that playback compares."
          },
          "platform-reach": {
            "type": "string",
            "required": true,
            "options": [
              "recorded-platform-only",
              "every-supported-platform"
            ],
            "description": "Whether this claim is compared only on the recording platform or on every supported platform."
          },
          "shifts-with-live-input": {
            "type": "string",
            "when": {
              "flag": {
                "replay-record": [
                  "seed-only"
                ]
              }
            },
            "options": [
              "seed-fixes-this-claim",
              "live-input-may-shift-this-claim"
            ],
            "description": "Can what the player does change a result this replay promises? Say whether the seed fixes this claim or whether live input may shift it."
          },
          "live-input-dependence-declared-in": {
            "type": "citation",
            "when": {
              "row": {
                "shifts-with-live-input": [
                  "live-input-may-shift-this-claim"
                ]
              }
            },
            "description": "The fixed rule naming every live-input history fact allowed to change this claimed result. Unlisted live input does not change it."
          },
          "matching-standard": {
            "type": "string",
            "required": true,
            "options": [
              "bit-exact-state",
              "outcome-equivalent",
              "allowed-position-gap"
            ],
            "description": "What this claim compares: every named state byte, every named outcome field, or position in the cited space using the adoption's allowed gap."
          },
          "reproduces": {
            "type": "citation",
            "required": true,
            "description": "The fixed game prose naming every state byte, outcome field, or position that must match."
          },
          "excludes": {
            "type": "citation",
            "required": true,
            "description": "A separate fixed section naming what this claim subtracts from what it promises to match, including an explicit statement when nothing is excluded."
          },
          "conditions": {
            "type": "citation",
            "required": true,
            "description": "The fixed game prose naming when the promise holds, including content-set identity, settings, mods, and any other compatibility or comparison conditions. Content identity is a condition, not a version."
          },
          "comparison-points": {
            "type": "citation",
            "required": true,
            "description": "The rule naming when a reference is captured or recomputed and when playback compares it, such as every simulation checkpoint, the finish line, or the solved board."
          }
        }
      }
    }
  },
  "rules": {
    "best-effort-must-be-visible": {
      "forbid": {
        "flag": {
          "after-an-update": [
            "best-effort-with-declared-divergence"
          ],
          "divergence-response": [
            "continue-silently"
          ]
        }
      },
      "message": "Best-effort replay after an update needs a visible difference notice; show and flag differences, or keep the replay on its recorded version."
    }
  },
  "origin": "https://opengdd.org/contracts/replay-scope-1",
  "mechanism": [
    "This is the single normative authority for what is recorded, when capture or recomputation happens, what playback consumes, and how differences are detected and handled. Questions and rows supply choices and references; they do not redefine this order.",
    "A `replay-record` row names a replay family. Each immutable replay record made from that family carries its own stable instance identity under `recording-declared-in`. It also carries the recording version, platform, content-set identity, settings and mod identity; the chosen seed or fixed start; the ordered input log when selected; and every claim's comparison reference. A reference is either captured at recording or deterministically recomputed from the sealed record at lifecycle step 11. A migrated record is a derived record with its own identity and a link to the unchanged source.",
    "A **comparison point** is a cited checkpoint at which playback reads a result and obtains the corresponding captured or recomputed reference. A **difference** is the first eligible comparison that fails that claim's matching standard. The terminal playback result is `diverged`, `rejected`, or `complete`; before a terminal result, playback is in progress.",
    "### Record",
    "1. Read the one replay-family row and every reproduction claim. From `recording-declared-in`, fix the recording version, platform, content-set identity, settings, and mod identity before the record begins. 2. Establish the start. A seed-only or seed-and-input record captures the seed before any claimed seeded result is generated. A fixed-start record captures an identity that the cited state rule can verify before playback. 3. Begin input capture at the cited start. A seed-only record captures no inputs. Either input-log record captures each mapped game action with its complete order and cited clock, step, or turn. 4. At every claim's comparison point, either capture the reference required by that claim's matching standard or capture all sealed source data that the cited rule requires to recompute the reference at step 11. 5. End capture at the cited boundary. Seal the record's own instance identity and contents. A later edit creates a different record instance in the same replay family.",
    "### Select a playable version and claims",
    "6. Before consuming the seed, start, or inputs, read the version, platform, content-set identity, settings, and mod identity carried under `recording-declared-in`, then read every cited compatibility condition. If a record-wide identity — content, settings, mods, or the fixed start — no longer holds, reject the record and use the incompatibility report. A failed condition cited by one claim alone exempts only that claim, per steps 7 and 12. Content identity is a condition, not a version; a level-content patch can therefore invalidate a record even when the version id is unchanged. 7. Determine platform reach claim by claim. A claim limited to the recording platform is not compared on another running platform. A claim covering every supported platform is not compared on an unsupported running platform. Either excluded claim does not diverge; other claims continue. 8. Only when the recorded version differs from the running version, apply the selected update policy. `same-version-only` rejects with the incompatibility report. `migrate-then-replay` runs the cited migration once; success creates a derived record naming source version, target version, and migration rule, while failure rejects. `best-effort-with-declared-divergence` presents the cited known differences and keeps the source record unchanged. Migration must map the recorded input clock to an existing running-version clock; best-effort playback rejects if the cited clock no longer exists.",
    "### Replay and compare",
    "9. Recreate the start. Supply the recorded seed when present. Verify or restore the fixed starting state when present. Reject the replay if either required item cannot be established. 10. For an input-log record, consume inputs in their recorded order at their cited clock, step, or turn. For a seed-only record, accept live inputs. A `seed-fixes-this-claim` result cannot change when those inputs vary. A `live-input-may-shift-this-claim` result may read only the live-input facts named by its gated citation. 11. Obtain each claim's comparison reference. Read a reference captured in the record, or deterministically recompute it from the sealed record using the method cited by `recording-declared-in` and that claim's `comparison-points`. This is the recomputation step used by a puzzle share whose solved-board reference is derived from its fixed board and move log. 12. At each comparison point, first read the claim's cited conditions. If they are not met, do not compare that claim and do not mark a divergence. A `live-input-may-shift-this-claim` result's gated citation works the same way: a result that differs only as that citation permits is not compared against the recorded reference and does not diverge; where the citation's method recomputes a reference for the actual inputs, step 11's recomputation applies. Otherwise compare with the reference using the row's matching standard. Bit-exact state compares every declared byte. Outcome matching compares every declared outcome field. Position matching measures distance in the cited space and passes when it is no greater than `allowed-position-gap`. `excludes` subtracts from `reproduces`; excluded state is never compared.",
    "Changes outside the cited conditions make no promise and do not fail this contract.",
    "### Handle the first difference",
    "13. On the first failed eligible comparison, set the playback result to `diverged` and retain the claim id, comparison point, expected result, observed result, versions, platforms, and last consumed input when present. 14. Under `stop-and-report`, present the difference, consume no later input, and end playback. Under `continue-and-flag`, present the difference, keep a visible diverged mark, and continue. Under `continue-silently`, emit no outward report and continue. Either continuing route advances from playback's own state. Later comparisons are informational and never resynchronise playback to the recorded reference. 15. If no eligible comparison fails and the record reaches its cited end, set the result to `complete`. Completion means every comparison actually made matched. It makes no promise about excluded claims, unmet conditions, or excluded state.",
    "Every event offered at the same replay moment enters this lifecycle in the total order supplied by **Event resolution**. This contract preserves that order but does not choose it."
  ],
  "answers": {
    "replay-record": "input-log-from-fixed-start",
    "after-an-update": "migrate-then-replay",
    "divergence-response": "stop-and-report"
  },
  "values": {},
  "rows": {
    "replay-record": [
      {
        "id": "shared-solution",
        "recording-declared-in": "puzzle.solution-record",
        "input-clock-declared-in": "puzzle.move-order",
        "fixed-start-declared-in": "puzzle.shared-board-state",
        "migration-declared-in": "puzzle.solution-migration",
        "difference-report-declared-in": "puzzle.solution-error"
      }
    ],
    "reproduction-claims": [
      {
        "id": "solved-board",
        "artifact": "solved board and move count",
        "platform-reach": "every-supported-platform",
        "matching-standard": "outcome-equivalent",
        "reproduces": "puzzle.solved-board-result",
        "excludes": "puzzle.solution-exclusions",
        "conditions": "puzzle.solution-conditions",
        "comparison-points": "puzzle.after-each-move-and-solve"
      }
    ]
  },
  "pack": "sha256:dc3ee9f2383b70086aa53fad03e41f878befddd8b12eca9147598b6ea59505bc"
}