Assembler
assembler · an adoption of Job resolution, version 1
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 crafting benches, build queues, research, and cooking: one job rule decides inputs, claims, work, interruption, limits, delivery, and failure, written down once. What a recipe makes and what it is worth stay with the game's own rules.
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.
Does this job need inputs that can be claimed and spent?
What happens to recorded work when this job stops?
- Asked when
- the work phases list has at least one row.
- If not asked
- The job has no work span before finish; start and finish settle in one batch, unless an allowed delivery answer leaves the result visibly finished. No partial work is recorded, and no interruption can stop the job before its finish gate. A recoverable failure while waiting still lands it in stopped, with the start gate as its resume point.
What does a listed failure do unless that failure says otherwise?
- Asked when
- the failures list has at least one row.
- If not asked
- No accepted or finished job fails; refusal, stopping, cancellation, and blocked delivery are different outcomes.
What happens to inputs this job still claims when it is cancelled?
- Asked when
- the cancellations list has at least one row.
- If not asked
- An accepted job cannot be cancelled. A reviewer confirms this before the adoption relies on it.
What happens to later waiting jobs that needed a cancelled job's output?
- Asked when
- the dependent cancellations list has at least one row.
- If not asked
- Cancelling a job leaves later waiting jobs in place, even when they needed its output.
When do required inputs become unavailable to other rules?
- Asked when
- Job inputs is Required inputs.
- If not asked
- This job claims no input, so there is no claim time to choose.
Does a stopped job keep the inputs it has already claimed?
- Asked when
- Partial work is Keep with job or Reverse while stopped or Reset at stop and Input claim timing is Taken at request or Taken at start or With progress.
- If not asked
- When no pre-finish claim exists there is nothing to hold; otherwise the stopped job keeps its claim.
When is the completed result delivered?
- Asked when
- the delivery cases list has at least one row, or the output destinations list has at least one row, or the collection events list has at least one row, or the readmission events list has at least one row, or the redelivery events list has at least one row.
- If not asked
- A finished output is delivered automatically as soon as its normal destination accepts it.
What happens when the whole output does not fit at its normal destination?
Numbersno numbers
This contract has no numbers to set.
Rules3 rules
A rule is a check between the numbers. Validation reports a rule that fails.
-
Forbidden when Input claim timing is With progress and Partial work is Reset at stop.
-
Forbidden when Input claim timing is With progress and Partial work is Reverse while stopped. (a warning, not an error)
-
Forbidden when Delivery trigger is On collection and Output full is Hold undelivered, or Delivery trigger is On collection and Output full is Try destinations.
Lists17 lists
Each list holds the rows this adoption supplies. A list can be empty.
Job
job
| Job declared in | Normal destination declared in | Output kind |
|---|---|---|
factory.assembler-recipes | factory.output-slot | new-thing |
Read first
read-first
This adoption declares no read first.
Work phases
work-phases
| Id | Duration declared in |
|---|---|
assembly | factory.assembler-times |
Interruptions
interruptions
This adoption declares no interruptions.
Reversal rules
reversal-rules
This adoption declares no reversal rules.
Progress rounding rules
progress-rounding-rules
This adoption declares no progress rounding rules.
Cancel return rules
cancel-return-rules
This adoption declares no cancel return rules.
Collection events
collection-events
This adoption declares no collection events.
Readmission events
readmission-events
This adoption declares no readmission events.
Redelivery events
redelivery-events
This adoption declares no redelivery events.
Work limits
work-limits
| Id | Covers declared in | Scope | Places declared in | Place assignment declared in | Working limit key | Waiting limit key | Waiting order | Order declared in | Releases working at |
|---|---|---|---|---|---|---|---|---|---|
assembler-head | factory.assembler-requests | each-place | world.assemblers | factory.requesting-assembler | numbers.one-active | — | request-order | — | — |
Standing orders
standing-orders
| Id | Work limit | Requests job declared in | Eligible declared in |
|---|---|---|---|
repeat-selected | assembler-head | factory.selected-recipe | factory.recipe-needed-and-affordable |
Failures
failures
This adoption declares no failures.
Cancellations
cancellations
This adoption declares no cancellations.
Dependent cancellations
dependent-cancellations
This adoption declares no dependent cancellations.
Delivery cases
delivery-cases
| Id | Condition declared in |
|---|---|
full-output-slot | factory.output-slot-capacity |
Output destinations
output-destinations
This adoption declares no output destinations.
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 tests28 tests apply
The contract comes with 66 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.
reports-identify-the-run
reports identify their job run and state change
Applies to assembler.
A request reads the rule cited at job-declared-in once, makes any pool and place assignment, and reports job-requested. Across the runs needed to reach every constructible report, every report in each run keeps that run's id and the same job id and records the cause, work, claim changes, and chosen destination. Every report except job-requested carries old and new state; job-requested carries a new state only. job-rejected is not a state; destination-refused is a finished-to-finished report.
Test steps and diagnostics
- Given
the set of
assemblerjob runs needed to reach every transition and stateless report the adoption can construct- When
- the report log is read in settlement order
- Then
- the request reads the rule cited at job-declared-in once, assigns exactly one pool and one cited place where those declarations exist, then reports job-requested
- every report in each run carries that run's id and the same job id, plus cause, work before and after, units newly claimed, released, spent, or lost, and the destination when one is chosen
- every report except job-requested carries old and new state; job-requested carries a new state only and sits outside any ordered instant batch
- job-rejected ends the run without becoming a lifecycle state, and destination-refused has old and new state both finished
- Diagnostics
assembler-job-rule-read-logassembler-report-logassembler-state-traceassembler-work-before-afterassembler-claim-ledger
claims-keep-their-source
claims preserve ownership and settle once
Applies to assembler.
A claim makes its units unavailable everywhere else but keeps their source known. Release returns surviving units there. Spending and loss remove units, so neither kind can later be released. A no-input adoption has no claim event to assert.
Test steps and diagnostics
- Given
each claim, release, spend, and loss that a run of
assemblercan construct; a no-input adoption has an empty claim ledger here- When
- another rule tries to use a claimed unit and the run later settles that unit
- Then
- the claimed unit is unavailable to every other rule while its source remains recorded
- release returns each surviving unit to that source
- spending or losing removes the unit, and no removed unit is later released
- Diagnostics
assembler-claim-ledgerassembler-source-recordassembler-usable-inputs
exact-inputs-required
a request with a missing tested share is rejected cleanly
Applies to assembler.
A request cannot pass with less than its tested share. Whole-claim timings test the full requirement. For progress claiming, both gates test at least the initial rounded share and never the full requirement by default; a stricter offer check named by the rule cited at job-declared-in may test more, and the test reads that rule to decide. Rejection claims nothing, records no work, and creates no output.
Test steps and diagnostics
- Given
a request for
assemblerwith less than the tested input share available — the full requirement for a whole-claim timing; for progress claiming both gates test at least the initial rounded share and never the full requirement by default, while a stricter offer check named by the rule cited at job-declared-in may test more, and the test reads that rule to decide- When
- the availability check runs without reserving inputs
- Then
- job-rejected reports cause missing-inputs and ends the run
- no input is claimed, no work is recorded, and no output is created
- Diagnostics
assembler-report-logassembler-claim-ledgerassembler-work-before-afterassembler-output-identity
no-input-check-is-empty
a no-input job skips the input check
Does not apply to assembler: job inputs is required inputs, not no inputs.
request-time-claim-is-atomic
request-time inputs are claimed at admission
Does not apply to assembler: input claim timing is taken at start, not taken at request.
waiting-admission-uses-pool-capacity · assembler-head
assembler-head accounts for waiting admission
Applies to the assembler-head row.
Pool assembler-head is selected under factory.assembler-requests. Waiting admission consumes its waiting capacity; an immediate start does not. Where the row declares a waiting limit, reaching it makes the next would-wait request reject with job-limit-full. With no waiting limit, this pool's waiting count never causes job-limit-full. This test names the address and restates nothing from it.
Test steps and diagnostics
- Given
requests assigned to pool
assembler-head, including one that can start immediately and one that would wait; where this pool declares a waiting limit, also fill that limit- When
- each request reaches admission under the coverage rule cited at
factory.assembler-requests
- each request reaches admission under the coverage rule cited at
- Then
- an admitted waiting request consumes one waiting count, while an immediate start consumes none
- where the pool declares a waiting limit, a request that would exceed it reports job-rejected with cause job-limit-full
- where the row declares no waiting limit, no request is ever rejected with job-limit-full by this pool's waiting count
- Diagnostics
assembler-count-traceassembler-report-logassembler-pool-assignment
readmission-event-pairs-with-reservation
Row.id is legal exactly for pre-start reservation
Does not apply to assembler: readmission-events has no rows.
reservation-needs-a-readmission-event
pre-start reservation declares a readmission event
Does not apply to assembler: output full is wait until space, not wait before start.
waiting-records-every-current-reason
waiting records reasons but no work
Applies to assembler.
Each waiting shape this adoption can construct reports every current reason and records no work. Only the taken-at-request answer can already hold an input claim there; an adoption with no waiting shape has no assertion in this test.
Test steps and diagnostics
- Given
each admitted
assemblerrequest that the adoption can construct with one or more reasons it cannot start; an adoption that constructs none asserts nothing here- When
- the admitted request enters waiting
- Then
- job-waiting reports every current reason
- no work is recorded and no input is claimed in waiting except an already-required request-time claim
- Diagnostics
assembler-report-logassembler-state-traceassembler-claim-ledger
start-time-claim-is-atomic
start-time inputs are claimed before start
Applies to assembler.
The full requirement is claimed atomically at the start gate. If it cannot be claimed, the job waits with inputs-unavailable; if a declared waiting limit is full, it rejects with job-limit-full and releases any output reservation.
Test steps and diagnostics
- Given
an admitted
assemblerjob at its start gate- When
- the full requirement is available, then in a second run is unavailable
- Then
- the available run claims the full requirement atomically before job-started
- the unavailable run enters waiting with cause inputs-unavailable, or rejects with job-limit-full where its full waiting limit prevents admission, releasing any output reservation on rejection
- Diagnostics
assembler-claim-ledgerassembler-report-logassembler-reservation-ledger
finish-time-inputs-stay-at-source
finish-time inputs remain usable before the finish gate
Does not apply to assembler: input claim timing is taken at start, not taken at finish.
progress-claim-starts-with-rounded-share
progress claiming begins with the initial share
Does not apply to assembler: input claim timing is taken at start, not with progress.
start-counts-settle-before-report
start exchanges waiting room for working room
Applies to assembler.
At job-started, the job has left any waiting count and acquired any selected working count. No job rests in started; it is a transition boundary. A pre-start output reservation remains held. Shapes this adoption cannot construct add no assertion.
Test steps and diagnostics
- Given
each admitted
assemblerjob that can start, with and without a pool where those shapes exist- When
- the job crosses the start boundary
- Then
- any waiting count is left and any selected working count is acquired before job-started
- an output reservation, where the selected answer created one, remains held through delivery
- no job is ever observed resting in started; it is a transition boundary
- Diagnostics
assembler-count-traceassembler-reservation-ledgerassembler-report-log
work-phase-enters-working · assembly
assembly enters working and reaches the finish gate
Applies to the assembly row.
Work phase assembly enters working, reports job-working, and completes as factory.assembler-times says. Work is recorded at full precision. Reaching the required amount reaches the finish gate but does not spend inputs or create output. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
a started
assemblerjob using work phaseassembly- When
- the job enters working and completes as
factory.assembler-timessays
- the job enters working and completes as
- Then
- job-working reports entry to working
- exposed work points use full precision and any display meter remains outside this contract
- reaching required work moves to the finish gate without yet spending inputs or creating output
- Diagnostics
assembler-state-traceassembler-work-before-afterassembler-claim-ledgerassembler-output-identity
instant-start-settles-finish-in-one-batch
a job without work settles start and finish together
Applies to assembler.
With no work phase, start and finish settle in one batch unless hold-undelivered, an all-refused try-destinations route, or on-collection parks the job in visible finished, or a finish-gate cause stops it at the gate: an unavailable finish-time claim or a wait-until-space capacity wait. An adoption with a work phase has no assertion here.
Test steps and diagnostics
- Given
the absence case: if
assemblerhas no work-phases row, a request that passes its gates; if it has a work phase, this template asserts nothing- When
- the job starts
- Then
- start and finish settle in one ordered batch
- the ordered batch ends early only when hold-undelivered, an all-refused try-destinations route, or on-collection parks the job in visible finished, or a finish-gate cause stops it at the gate: an unavailable finish-time claim or a wait-until-space capacity wait
- Diagnostics
assembler-report-logassembler-state-trace
no-stop-before-the-finish-gate
a job without work does not stop before finish
Applies to assembler.
An adoption with no work-phases row records no partial work and never enters stopped for an interruption of work before its finish gate. A recoverable failure while waiting is a failure, not an interruption: it lands in stopped under step 16 with the start gate as its resume point. An adoption with a work phase asserts nothing here.
Test steps and diagnostics
- Given
the absence case where
assemblerhas no work-phases row; an adoption with a work phase asserts nothing here- When
- an admitted job advances to its finish gate
- Then
- no partial work is recorded
- the job never enters stopped for an interruption of work before its finish gate; a recoverable failure while waiting lands in stopped under step 16 with the start gate as its resume point
- Diagnostics
assembler-work-before-afterassembler-state-trace
progress-rounding-rule-pairs-with-progress
Row.id is legal exactly for progress claiming
Does not apply to assembler: progress-rounding-rules has no rows.
progress-needs-a-rounding-rule
progress claiming declares a rounding rule
Does not apply to assembler: input claim timing is taken at start, not with progress.
declared-interruption-stops-once
Row.id records an ordinary stop once
Does not apply to assembler: interruptions has no rows.
unnamed-instructions-cannot-stop
only named instructions can stop work
Applies to assembler.
An instruction absent from every interruptions row is not an allowed stop. With an empty list, stops arise only from lifecycle inability. An adoption with no working state, or no unnamed instruction, asserts nothing here.
Test steps and diagnostics
- Given
each instruction this adoption can construct that is absent from all interruptions rows; an adoption with no working state, or no unnamed instruction, asserts nothing here
- When
- the instruction is offered to a
assemblerjob in working, where that state exists
- the instruction is offered to a
- Then
- the instruction does not add a stop cause and does not report job-stopped
- Diagnostics
assembler-stop-causesassembler-report-log
kept-work-stays-with-the-job
an ordinary stop preserves recorded work
Applies to assembler.
The same job keeps all recorded work through an ordinary stop and resumes from that amount; the work is never transferred to another job. An adoption that can construct no ordinary stop asserts nothing here, and a finish-gate stop never applies this answer.
Test steps and diagnostics
- Given
each
assemblerjob with recorded work that the adoption can drive to a first ordinary stop; an adoption that can construct no ordinary stop asserts nothing here, and a finish-gate stop never applies this answer- When
- the stop settles and that same job later resumes
- Then
- the same job retains the same recorded amount through the stop and resumes from it
- no other job receives that work
- Diagnostics
assembler-work-before-afterassembler-run-id-trace
reversal-rule-pairs-with-reversing-work
Row.id is legal exactly for reversing stopped work
Does not apply to assembler: reversal-rules has no rows.
reversing-work-needs-a-reversal-rule
reversing stopped work declares a reversal rule
Does not apply to assembler: partial work is keep with job, not reverse while stopped.
reset-work-clears-on-ordinary-stop
an ordinary stop resets recorded work
Does not apply to assembler: partial work is keep with job, not reset at stop.
stopped-job-holds-claim
a stopped job keeps its current claim
Applies to assembler.
Where stopped work reverses, claim changes caused by the decrease settle through this stopped-claims step. A whole claim taken at request or start then follows hold exactly as a progress claim does, after any progress claim is first reduced to the recorded work. The adjusted claim remains assigned to the job.
Test steps and diagnostics
- Given
each
assemblerstop the adoption can construct with a current claim; an adoption with no such stop asserts nothing here- When
- any work decrease and progress-based claim adjustment settle and the stop remains active
- Then
- where reverse-while-stopped applies, claim changes caused by the decrease settle through the stopped-claims step
- a whole claim taken at request or at start follows this answer exactly as a progress claim does, after any progress claim is first reduced to the recorded work
- the adjusted current claim stays assigned to the job and unavailable elsewhere until another lifecycle step settles it
- Diagnostics
assembler-claim-ledgerassembler-stop-causes
stopped-job-releases-and-reclaims
a stopped job releases and must reclaim inputs
Does not apply to assembler: stopped claims is hold, not release and reclaim.
resume-waits-for-every-cause
the same job resumes only after every cause clears
Applies to assembler.
The same job resumes only after every active cause clears and every gate passes. It competes for room through its pool where the adoption declares one, and otherwise proceeds without a pool. If a gate or claim is unavailable, it remains stopped and keeps the room free; on success it reports job-resumed and returns to its recorded resume point without creating another request.
Test steps and diagnostics
- Given
each stopped
assemblershape the adoption can construct, including overlapping causes where constructible- When
- causes clear one at a time and the last cause clears
- Then
- no resume occurs while a cause remains
- after the last cause clears, the same job rechecks gates and competes for room through its pool where the adoption declares one, and otherwise proceeds without a pool; it reports job-resumed only on success and creates no new request
- if a gate or claim is unavailable, the job remains stopped and keeps the room free
- an interrupted-work resume returns to its recorded work point, while a waiting-origin recoverable failure returns to the start gate
- Diagnostics
assembler-stop-causesassembler-resume-pointassembler-run-id-traceassembler-report-log
unasked-stopped-claim-answer-holds
an unasked stopped-claim choice defaults to hold
Applies to assembler.
Where stopped-claims was not asked, a request-time claim held by a job stopped from waiting or by a finish-gate cause remains assigned after any progress adjustment. An adoption with an explicit answer, or without that live shape, has no assertion here.
Test steps and diagnostics
- Given
each
assemblerrequest-time claim held while its job is stopped from waiting or by a finish-gate cause and stopped-claims was not asked; an adoption with an answer or no such claim asserts nothing here- When
- the stop settles
- Then
- the current claim remains assigned to the stopped job after any progress-based adjustment
- Diagnostics
assembler-claim-ledgerassembler-stop-causes
finish-gate-wait-retains-completed-work
a full destination stops at the finish gate
Applies to assembler.
A full destination adds the slot-retaining output-full cause at the finish gate, work phase or not. Completed work and working room remain; partial-work does not apply; resume returns directly to the finish gate. An instant job stops there too, and its one batch ends at that gate.
Test steps and diagnostics
- Given
a job in
assemblerwith completed work, or an instant job at the finish gate of its one batch, and no room for the whole output- When
- the finish gate first blocks and later gains room
- Then
- the job stops with slot-retaining cause output-full, preserves completed work, retains its working count while every active cause is slot-retaining, and does not apply partial-work
- the first active non-retaining cause releases the working count, and no successful output is established while output-full remains
- where a current claim exists, the explicit stopped-claims answer applies; if that question was not asked, the claim is held
- when every cause clears it reports job-resumed and returns directly to the finish gate without repeating work
- Diagnostics
assembler-state-traceassembler-work-before-afterassembler-count-traceassembler-report-log
finish-claim-wait-is-slot-retaining
an unavailable finish claim stops at the gate
Does not apply to assembler: input claim timing is taken at start, not taken at finish.
work-limit-offers-room-and-releases-counts · assembler-head
assembler-head offers and releases room in lifecycle order
Applies to the assembler-head row.
Pool assembler-head uses working limit numbers.one-active. It offers free room to admitted jobs before scanning standing orders. Terminal entry releases every count immediately. On success, finished or omission releases after job-finished; delivered releases after job-delivered. The cited coverage and limit rules are at factory.assembler-requests and numbers.one-active; this test restates neither.
Test steps and diagnostics
- Given
pool
assembler-headat its working limitnumbers.one-active, with admitted jobs eligible to start or resume and active jobs driven through each success or terminal side path the adoption can construct- When
- room becomes free, a reason clears, a terminal state is entered, and a successful job reaches the transition this row selects
- Then
- free room is offered first to admitted eligible jobs in the pool's waiting order, and a cleared reason re-offers room
- where the adoption declares an interruption, a job stopped by instruction is ordered at its stop moment and never outranks the job that displaced it
- entry to cancelled, terminal failed, or delivered releases every count immediately
- on success, releases-working-at finished releases after finished and job-finished, releases-working-at delivered releases after delivered and job-delivered, and omission follows finished; room offers and standing-order scans then run
- Diagnostics
assembler-count-traceassembler-pool-offer-logassembler-report-logassembler-standing-order-scan-log
pool-releases-at-finished
Row.id releases working room after finish
Does not apply to assembler: no row in work-limits matches releases-working-at finished.
pool-releases-at-delivered
Row.id releases working room after delivery
Does not apply to assembler: no row in work-limits matches releases-working-at delivered.
each-place-pool-assigns-one-place · assembler-head
assembler-head keeps separate counts per place
Applies to the assembler-head row.
Pool assembler-head keeps separate counts for the places at world.assemblers and assigns each request through factory.requesting-assembler. Each request uses exactly one place. The test names the addresses and restates nothing from them.
Test steps and diagnostics
- Given
two places from
world.assemblersand requests covered byfactory.assembler-requests- When
factory.requesting-assemblerassigns each request
- Then
- every request belongs to exactly one cited place and consumes only that place's working and waiting counts
- free room at one place does not change another place's counts
- Diagnostics
assembler-pool-assignmentassembler-count-trace
shared-pool-uses-one-count
Row.id shares one count
Does not apply to assembler: no row in work-limits matches scope shared.
request-order-pool-offers-in-admission-order · assembler-head
assembler-head offers room in request order
Applies to the assembler-head row.
Pool assembler-head offers room to eligible jobs in request order. A request enters waiting even with free room when an earlier admitted job is first.
Test steps and diagnostics
- Given
two eligible admitted jobs in pool
assembler-headwith a known admission order- When
- one working place becomes free
- Then
- the earlier admitted eligible job receives the first offer
- a request whose pool has free room still enters waiting when the pool's order places an earlier admitted job first
- Diagnostics
assembler-pool-offer-logassembler-waiting-order-record
game-rule-pool-offers-in-cited-order
Row.id offers room in its cited order
Does not apply to assembler: no row in work-limits matches waiting-order game rule order.
no-pool-means-every-ready-job-starts
without a pool every ready job starts
Applies to assembler.
An adoption with no work-limits row starts every otherwise-ready job and never reports job-waiting with a pool cause. An adoption with pools asserts nothing here.
Test steps and diagnostics
- Given
the absence case where
assemblerhas no work-limits row; an adoption with pools asserts nothing here- When
- an otherwise-ready job reaches its start gate
- Then
- every otherwise-ready job starts
- no job reports job-waiting with a pool cause
- Diagnostics
assembler-state-traceassembler-report-log
standing-order-scans-are-level-triggered · repeat-selected
repeat-selected is scanned in written order until room is filled
Applies to the repeat-selected row.
Standing order repeat-selected belongs to assembler-head. After room offers, scans consult factory.recipe-needed-and-affordable in written order and can create repeated requests from factory.selected-recipe until eligibility or room ends. Scans also run at pool creation, when eligibility becomes true, and after the specified outside rejection. The test names the addresses and restates nothing from them.
Test steps and diagnostics
- Given
standing order
repeat-selectedattached to poolassembler-head, with its cited eligibility false and then true and enough room for more than one job- When
- the pool is created, finishes room offers, observes eligibility become true, and later receives a rejected request that this scan did not create
- Then
- each scan considers rows in written order after room offers and consults
factory.recipe-needed-and-affordable - while this row remains eligible, one scan can create more than one request named by
factory.selected-recipeuntil no row is eligible or no room remains - creation of the pool, fresh eligibility, and the stated rejection each cause a scan; the row remains for later scans
- each scan considers rows in written order after room offers and consults
- Diagnostics
assembler-standing-order-scan-logassembler-request-logassembler-count-trace
read-first-note-precedes-verification
Row.id is read before the adoption is trusted
Does not apply to assembler: read-first has no rows.
failure-row-fires-from-its-state
Row.id resolves only from Row.from state
Does not apply to assembler: failure result is not asked for assembler.
failure-row-result-recoverable
Row.id applies its recoverable result
Does not apply to assembler: failures has no rows.
failure-row-result-ruined
Row.id applies its ruined result
Does not apply to assembler: failures has no rows.
progress-failure-adjusts-claim-after-loss
Row.id settles progress claims after failure loss
Does not apply to assembler: input claim timing is taken at start, not with progress.
no-failure-without-a-failure-row
accepted jobs do not fail without a declared failure
Applies to assembler.
An adoption with no failures row never reports job-failed from an accepted or finished job. An adoption with a failure row asserts nothing here.
Test steps and diagnostics
- Given
the absence case where
assemblerhas no failures row; an adoption with a failure row asserts nothing here- When
- accepted and finished jobs are observed
- Then
- no accepted or finished job reports job-failed
- Diagnostics
assembler-report-log
declared-cancellation-settles-one-job
Row.id snapshots and cancels one job
Does not apply to assembler: cancel return is not asked for assembler.
cancel-return-rule-pairs-with-rule-sized-return
Row.id is legal exactly for rule-sized cancellation return
Does not apply to assembler: cancel-return-rules has no rows.
rule-sized-return-needs-a-return-rule
rule-sized cancellation return declares a return rule
Does not apply to assembler: cancel return is not asked for assembler.
no-cancellation-without-a-cancellation-row
accepted jobs cannot be cancelled without a declared cancellation
Applies to assembler.
An adoption with no cancellations row never reports job-cancelled, and a reviewer confirms that promise before the adoption relies on it. An adoption with a cancellation row asserts nothing here.
Test steps and diagnostics
- Given
the absence case where
assemblerhas no cancellations row; an adoption with a cancellation row asserts nothing here- When
- accepted jobs are observed and the adoption prepares to rely on this promise
- Then
- no accepted job reports job-cancelled
- Diagnostics
assembler-report-logassembler-review-record
dependent-cancellation-follows-answer
Row.id settles later dependent jobs
Does not apply to assembler: cancel dependents is not asked for assembler.
finish-spends-and-establishes-one-output
the finish gate commits inputs and one output atomically
Applies to assembler.
At the finish gate, required claims are spent and one successful output is established in the same commit before job-finished. A compound result is still one unit. For an in-place job, the state change at the site is the delivery; it has no destination capacity and answers never-full. A new thing follows the selected delivery path.
Test steps and diagnostics
- Given
a job in
assemblerat the finish gate with every required claim and capacity gate satisfied- When
- the job finishes
- Then
- required claims are spent and exactly one successful output is established atomically before job-finished
- a compound output remains one delivery unit
- where the job row declares in-place, the state change at the site is the in-place delivery; an in-place output has no destination capacity, so the adoption answers never-full and no capacity branch is taken; where it declares new-thing, the one output follows the selected delivery rules
- Diagnostics
assembler-claim-ledgerassembler-output-identityassembler-state-traceassembler-report-log
delivery-case-invokes-selected-answer · full-output-slot
full-output-slot invokes the selected capacity response
Applies to the full-output-slot row.
When factory.output-slot-capacity establishes delivery case full-output-slot, the lifecycle applies the selected output-full answer to the whole output: a job with a work phase stops at the finish gate with completed work retained until capacity clears. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
a whole
assembleroutput and delivery casefull-output-slot- When
- the condition at
factory.output-slot-capacityholds
- the condition at
- Then
- the lifecycle applies exactly the selected output-full answer to the whole output, without splitting it or inventing another capacity response: a job with a work phase stops at the finish gate with completed work retained until capacity clears
- Diagnostics
assembler-delivery-attempts
normal-destination-never-blocks
the normal destination accepts every whole output
Does not apply to assembler: output full is wait until space, not never full.
pre-start-reservation-blocks-admission
a job waits before admission for reserved output room
Does not apply to assembler: output full is wait until space, not wait before start.
held-output-retries-only-on-event
a held output remains one inaccessible owned result
Does not apply to assembler: output full is wait until space, not hold undelivered.
held-output-needs-a-redelivery-event
a held output declares a redelivery event
Does not apply to assembler: output full is wait until space, not hold undelivered.
redelivery-event-pairs-with-retry-answer
Row.id is legal exactly for a refused-output retry
Does not apply to assembler: redelivery-events has no rows.
fallback-destination-pairs-with-ordered-route
Row.id is legal exactly for the ordered route
Does not apply to assembler: output-destinations has no rows.
fallback-destination-keeps-written-order
Row.id is tried in its written place
Does not apply to assembler: output full is wait until space, not try destinations.
ordered-route-keeps-one-output
the ordered route tries whole-output destinations in order
Does not apply to assembler: output full is wait until space, not try destinations.
automatic-delivery-reports-once
an accepted output is delivered immediately
Applies to assembler.
Under the automatic answer, or where delivery-trigger was never asked and delivery is therefore automatic, an accepted output moves from finished to delivered and reports job-delivered exactly once. An adoption answering on-collection asserts nothing here, and where the job row declares in-place this test asserts nothing beyond the single report.
Test steps and diagnostics
- Given
a finished
assembleroutput accepted by its chosen destination under the automatic answer, or where delivery-trigger was never asked and delivery is therefore automatic; an adoption answering on-collection asserts nothing here, and where the job row declares in-place this test asserts nothing beyond the single report- When
- capacity resolution accepts it
- Then
- the job moves finished to delivered immediately and reports job-delivered exactly once
- Diagnostics
assembler-state-traceassembler-report-log
collection-event-pairs-with-collection-delivery
Row.id is legal exactly for collection delivery
Does not apply to assembler: collection-events has no rows.
collection-needs-a-collection-event
collection delivery declares a collection event
Does not apply to assembler: delivery trigger is automatic, not on collection.
collection-delivery-waits-for-event
an accepted output remains accessible until collection
Does not apply to assembler: delivery trigger is automatic, not on collection.
rejection-ends-the-requested-run
a rejected run is not retried by the lifecycle
Applies to assembler.
Rejection ends its run. Clearing the reason does not revive it: a later retry belongs to the requester, unless a standing order creates a new run. Where this adoption declares no standing-orders row, no request repeats automatically.
Test steps and diagnostics
- Given
each
assemblerrequest that the adoption can construct as rejected- When
- the rejection settles and its cause later clears
- Then
- the rejected run remains ended and the lifecycle creates no retry
- a later retry has a new run created by the requester unless a standing-order scan creates it
- where this adoption declares no standing-orders row, no request repeats automatically
- Diagnostics
assembler-run-id-traceassembler-request-log
lifecycle-holds
the lifecycle and settlement order hold for the whole run
Applies to assembler.
Across sequences of requests, starts, advances, interruptions, resumes, failures, cancellations, finishes, and deliveries over one run, each transition settles with its claim changes and reports before the next begins. Claim changes precede the report unless a numbered step says otherwise. The stated forward and side paths are the only observed transitions. Instant automatic delivery keeps job-started, job-finished, and job-delivered in one batch. Same-moment order comes from Event resolution, not this contract. The adoption supplies the audit seeds through verification inputs.
Test steps and diagnostics
- Holds
one transition, all of its claim changes, and all of its reports settle before another transition begins; claim changes precede the transition report unless a numbered step states otherwise; an instant start with an accepting destination keeps job-started, job-finished, and job-delivered in one ordered batch with no outside event between them; only the forward path requested to waiting to started to working to finished to delivered, with unvisited states skipped without changing order, the stopped and resume side path, the cancellation side path, terminal failure, and recoverable failure into stopped are observed; same-moment events enter one at a time in the order Event resolution supplies, and this contract adds no ordering rule
- Seeds
["audit-a","audit-b"]- Scope
sequences of requests, starts, advances, interruptions, resumes, failures, cancellations, finishes, and deliveries over one run- Diagnostics
assembler-state-traceassembler-claim-ledgerassembler-report-logassembler-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.
{
"questions": {
"job-inputs": {
"asks": "Does this job need inputs that can be claimed and spent?",
"options": {
"required-inputs": {
"meaning": "The job needs one or more inputs. Brewing one potion may need two herbs and one bottle.",
"semantics": "The request checks the required share at the request gate. The lifecycle claims and spends that share at the selected times."
},
"no-inputs": {
"meaning": "The job claims and spends no input. Researching Pottery may need an unlocked lab but no material.",
"semantics": "Input checks, claims, returns, and spending are empty. Eligibility conditions may still prevent the game from offering the request."
}
}
},
"partial-work": {
"asks": "What happens to recorded work when this job stops?",
"when": {
"row-count": {
"work-phases": "non-empty"
}
},
"otherwise": "The job has no work span before finish; start and finish settle in one batch, unless an allowed delivery answer leaves the result visibly finished. No partial work is recorded, and no interruption can stop the job before its finish gate. A recoverable failure while waiting still lands it in stopped, with the start gate as its resume point.",
"options": {
"keep-with-job": {
"meaning": "Recorded work stays with the same job. A half-built wall remains halfway built after rain stops the work.",
"semantics": "A normal stop preserves all recorded work. Only this job can resume from it."
},
"reverse-while-stopped": {
"meaning": "Recorded work falls while the job is stopped. A cooling forge loses heat while no smith works.",
"semantics": "Recorded work decreases under reversal-declared-in and never passes below no work. Claim changes caused by the decrease settle through lifecycle step 12."
},
"reset-at-stop": {
"meaning": "Recorded work returns to none when the job stops. An interrupted lockpick attempt starts again from the beginning.",
"semantics": "The first ordinary stop records no work. Cancellation records no terminal work after its input snapshot is taken."
}
}
},
"failure-result": {
"asks": "What does a listed failure do unless that failure says otherwise?",
"when": {
"row-count": {
"failures": "non-empty"
}
},
"otherwise": "No accepted or finished job fails; refusal, stopping, cancellation, and blocked delivery are different outcomes.",
"options": {
"partial-inputs-or-work": {
"meaning": "Failure may lose part of the current inputs, recorded work, or both, whichever exist. A spill may lose one cup of broth while the same soup remains unfinished.",
"semantics": "The cited failure rule may lose a strict subset of claimed inputs, reduce recorded work without passing below no work, or do both. It creates no successful output and leaves the same job stopped."
},
"job-ruined": {
"meaning": "Failure ends this job for good. An overcooked meal is ruined and cannot finish as the same meal.",
"semantics": "The job enters terminal failed and creates no successful output. A finished but undelivered new output is destroyed."
}
}
},
"cancel-return": {
"asks": "What happens to inputs this job still claims when it is cancelled?",
"when": {
"row-count": {
"cancellations": "non-empty"
}
},
"otherwise": "An accepted job cannot be cancelled. A reviewer confirms this before the adoption relies on it.",
"options": {
"return-claimed": {
"meaning": "Every surviving claimed input returns to its source. Cancelling a queued soldier returns the 50 gold already set aside.",
"semantics": "Release every unit still claimed by the job. Do not add units that were never claimed or were already lost."
},
"return-nothing": {
"meaning": "No claimed input returns. Cancelling a fired clay pot spends the clay already placed in the kiln.",
"semantics": "Spend every unit still claimed by the job and release none. Inputs not yet claimed remain at their sources."
},
"return-by-rule": {
"meaning": "A game rule chooses the returned share. Cancelling a half-built wall may return unused bricks but not dried mortar.",
"semantics": "Release the subset named by cancel-return-declared-in, never more than the current claim, and spend the rest."
}
}
},
"cancel-dependents": {
"asks": "What happens to later waiting jobs that needed a cancelled job's output?",
"when": {
"row-count": {
"dependent-cancellations": "non-empty"
}
},
"otherwise": "Cancelling a job leaves later waiting jobs in place, even when they needed its output.",
"options": {
"end-dependents": {
"meaning": "Later jobs that can no longer get the needed output are cancelled too. Cancelling an iron ingot also cancels the waiting sword that needed it.",
"semantics": "Cancel every transitively dependent later waiting job whose requirement can no longer be met. Settle them in waiting order."
},
"leave-dependents": {
"meaning": "Later jobs remain waiting. A sword order may wait for another iron ingot after its first ingot job is cancelled.",
"semantics": "Leave every later dependent job waiting. The wait ends only when the requirement is met again or the job is cancelled."
}
}
},
"input-claim-timing": {
"asks": "When do required inputs become unavailable to other rules?",
"when": {
"flag": {
"job-inputs": [
"required-inputs"
]
}
},
"otherwise": "This job claims no input, so there is no claim time to choose.",
"options": {
"taken-at-request": {
"meaning": "All inputs are claimed when the request is accepted. A queued soldier reserves its full gold cost before training starts.",
"semantics": "Atomically claim the full requirement at admission, whether the job waits or starts."
},
"taken-at-start": {
"meaning": "All inputs are claimed when work starts. A workbench leaves wood available until the bench begins the chair.",
"semantics": "Atomically claim the full requirement at start. No other rule can use claimed units."
},
"taken-at-finish": {
"meaning": "Inputs stay available until successful finish. A ritual checks for three crystals only when the casting completes.",
"semantics": "Claim and spend the full requirement at the finish gate. No pre-finish input claim exists."
},
"with-progress": {
"meaning": "Inputs are claimed as work advances. A wall claims half its bricks when it reaches half of its recorded work.",
"semantics": "Before each observable advance, claim the rounded share required at the proposed work point. Release the matching share when work reverses."
}
}
},
"stopped-claims": {
"asks": "Does a stopped job keep the inputs it has already claimed?",
"when": {
"flag": {
"partial-work": [
"keep-with-job",
"reverse-while-stopped",
"reset-at-stop"
],
"input-claim-timing": [
"taken-at-request",
"taken-at-start",
"with-progress"
]
}
},
"otherwise": "When no pre-finish claim exists there is nothing to hold; otherwise the stopped job keeps its claim.",
"options": {
"hold": {
"meaning": "The job keeps the claim while stopped. A paused wall keeps its reserved bricks at the site.",
"semantics": "Retain the current claim while stopped. Work changes may first reduce a progress-based claim."
},
"release-and-reclaim": {
"meaning": "The claim returns while stopped and must be claimed again before resuming. A paused research topic releases its points for another topic.",
"semantics": "Release the current claim while stopped. Reclaim the required share before resuming; remain stopped if that share is unavailable."
}
}
},
"delivery-trigger": {
"asks": "When is the completed result delivered?",
"when": {
"any": [
{
"row-count": {
"delivery-cases": "non-empty"
}
},
{
"row-count": {
"output-destinations": "non-empty"
}
},
{
"row-count": {
"collection-events": "non-empty"
}
},
{
"row-count": {
"readmission-events": "non-empty"
}
},
{
"row-count": {
"redelivery-events": "non-empty"
}
}
]
},
"otherwise": "A finished output is delivered automatically as soon as its normal destination accepts it.",
"options": {
"automatic": {
"meaning": "Delivery happens as soon as a destination accepts the output. A trained unit leaves the barracks for its rally point at once.",
"semantics": "Move from finished to delivered immediately after the capacity policy accepts one destination."
},
"on-collection": {
"meaning": "The output waits for collection at its accepted place. A cooked meal stays on the stove until a player picks it up.",
"semantics": "Keep the accessible output in finished until collection-declared-in occurs, then report delivery once."
}
}
},
"output-full": {
"asks": "What happens when the whole output does not fit at its normal destination?",
"options": {
"never-full": {
"meaning": "The normal destination always accepts the output. Completed research always fits in the research ledger.",
"semantics": "No job reaches a capacity-blocked state. A reviewer confirms the capacity promise before the adoption relies on it. An in-place output always answers this way. If the capacity promise is false, the adoption is broken; there is no fallback lifecycle branch."
},
"wait-before-start": {
"meaning": "The job waits before starting until room is reserved. A bakery starts a loaf only after one shelf space is held for it.",
"semantics": "Keep admission pending until the whole output has reserved room. Hold that reservation through delivery."
},
"wait-until-space": {
"meaning": "Completed work stops at the finish gate until the output fits. An assembler holds a finished engine while its output slot is full.",
"semantics": "The job moves to stopped at its finish gate, work phase or not, and retains completed work until capacity clears."
},
"hold-undelivered": {
"meaning": "The job finishes and owns one inaccessible output until delivery can retry. A forge holds one finished sword while the rack is full.",
"semantics": "Spend inputs and keep one owned output in finished. Only redelivery-declared-in retries the normal destination; work is not repeated."
},
"try-destinations": {
"meaning": "The job tries named places in order. A mined gem tries the backpack, then the cart, then waits if both refuse it.",
"semantics": "Try the normal destination, then output-destinations in written order. Keep the same output in finished if all refuse; only redelivery-declared-in retries the route."
}
}
}
},
"declares": {
"values": {},
"rows": {
"job": {
"description": "Give the job rule and the normal output destination. One adoption has exactly one row.",
"when-empty": "An empty job list is never a behavior choice: this adoption requires exactly one job row, and a reviewer rejects a file without it.",
"record": {
"job-declared-in": {
"type": "citation",
"required": true,
"description": "The rule naming required inputs, one successful output unit, any in-place target, and game-owned choices or quality rules."
},
"normal-destination-declared-in": {
"type": "citation",
"required": true,
"description": "The rule naming the output's ordinary destination."
},
"output-kind": {
"type": "string",
"required": true,
"options": [
"new-thing",
"in-place"
],
"description": "Whether success creates a new thing or transforms the cited target in place."
}
}
},
"read-first": {
"description": "Optionally point a reviewer to prose that must be read before trusting the adoption.",
"when-empty": "No advance reading is required.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this reviewer note."
},
"read-first": {
"type": "citation",
"required": true,
"description": "The prose a reviewer should read first."
}
}
},
"work-phases": {
"description": "List the work span before finish. One adoption has at most one row.",
"when-empty": "Start and finish settle in one batch.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name the work span in the game's words."
},
"duration-declared-in": {
"type": "citation",
"required": true,
"description": "The duration and clock rule, or the event rule that completes the work."
}
}
},
"interruptions": {
"description": "List the game rules allowed to instruct a working job to stop.",
"when-empty": "Stops arise only from lifecycle inability.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this interruption."
},
"interruptions-declared-in": {
"type": "citation",
"required": true,
"description": "The rules allowed to instruct the stop."
}
}
},
"reversal-rules": {
"description": "Give the work-decrease rule exactly when stopped work reverses.",
"when-empty": "Stopped work does not reverse.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this reversal rule."
},
"reversal-declared-in": {
"type": "citation",
"required": true,
"description": "The rule that determines how recorded work decreases while stopped."
}
}
},
"progress-rounding-rules": {
"description": "Give the proportional rounding rule exactly when inputs are claimed with progress.",
"when-empty": "Inputs are not claimed with progress.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this rounding rule."
},
"progress-rounding-declared-in": {
"type": "citation",
"required": true,
"description": "The rule that rounds each divisible input's proportional claim."
}
}
},
"cancel-return-rules": {
"description": "Give the return rule exactly when cancellation returns a rule-sized share.",
"when-empty": "Cancellation does not return a rule-sized share.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this cancellation return rule."
},
"cancel-return-declared-in": {
"type": "citation",
"required": true,
"description": "The rule naming the part of the current claim returned on cancellation."
}
}
},
"collection-events": {
"description": "Give the collection event exactly when a finished output waits for collection.",
"when-empty": "A finished output does not wait for collection.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this collection event."
},
"collection-declared-in": {
"type": "citation",
"required": true,
"description": "The event that accepts the finished output and delivers it."
}
}
},
"readmission-events": {
"description": "Give the readmission event exactly when output room is reserved before start.",
"when-empty": "Output room is not reserved before start.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this readmission event."
},
"readmission-declared-in": {
"type": "citation",
"required": true,
"description": "The rule or event that tries admission again without polling."
}
}
},
"redelivery-events": {
"description": "Give the retry event when a held output or a route that can be refused may actually try delivery again.",
"when-empty": "A held output or a route that can be refused does not retry delivery.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this redelivery event."
},
"redelivery-declared-in": {
"type": "citation",
"required": true,
"description": "The rule or event that tries delivery again without polling."
}
}
},
"work-limits": {
"description": "List each working and waiting pool.",
"when-empty": "Jobs share no work limit and every otherwise-ready job starts.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this pool in the game's words."
},
"covers-declared-in": {
"type": "citation",
"required": true,
"description": "The rule identifying exactly which requests use this pool."
},
"scope": {
"type": "string",
"required": true,
"options": [
"each-place",
"shared"
],
"description": "Whether each cited place has separate counts or all covered jobs share one set."
},
"places-declared-in": {
"type": "citation",
"when": {
"row": {
"scope": [
"each-place"
]
}
},
"description": "For separate place counts, the rule identifying those places."
},
"place-assignment-declared-in": {
"type": "citation",
"when": {
"row": {
"scope": [
"each-place"
]
}
},
"description": "For separate place counts, the rule assigning each request to one place."
},
"working-limit-key": {
"type": "citation",
"required": true,
"description": "The positive whole number of jobs that may occupy the working count."
},
"waiting-limit-key": {
"type": "citation",
"required": false,
"description": "The non-negative whole number that may remain waiting. Omission means no finite waiting limit."
},
"waiting-order": {
"type": "string",
"required": true,
"options": [
"request-order",
"game-rule-order"
],
"description": "Whether room goes by request order or a cited total ordering rule."
},
"order-declared-in": {
"type": "citation",
"when": {
"row": {
"waiting-order": [
"game-rule-order"
]
}
},
"description": "The total ordering rule when game-rule order applies."
},
"releases-working-at": {
"type": "string",
"required": false,
"options": [
"finished",
"delivered"
],
"description": "The successful transition after whose report the working count is released. Omission means finished."
}
}
},
"standing-orders": {
"description": "List retained repeat orders.",
"when-empty": "No request repeats automatically.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this repeating order."
},
"work-limit": {
"type": "string",
"required": true,
"description": "The work-limit row whose free room may create the job."
},
"requests-job-declared-in": {
"type": "citation",
"required": true,
"description": "The job kind this row requests."
},
"eligible-declared-in": {
"type": "citation",
"required": true,
"description": "The rule deciding whether another request may be created."
}
}
},
"failures": {
"description": "List failures that may happen after acceptance.",
"when-empty": "Accepted and finished jobs do not fail.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this failure, such as overcooked or storm-damage."
},
"from-state": {
"type": "string",
"required": true,
"options": [
"waiting",
"working",
"stopped",
"finished"
],
"description": "The state from which this failure may happen."
},
"trigger-declared-in": {
"type": "citation",
"required": true,
"description": "The rule giving the chance, condition, or event and any permitted loss."
},
"result": {
"type": "string",
"required": false,
"options": [
"partial-inputs-or-work",
"job-ruined"
],
"description": "A result for this failure. Omission uses the shared answer."
}
}
},
"cancellations": {
"description": "List controls or events that may cancel an unfinished job.",
"when-empty": "An accepted job cannot be cancelled; a reviewer confirms this before the adoption relies on it.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name the cancellation in the game's words."
},
"trigger-declared-in": {
"type": "citation",
"required": true,
"description": "The control or event that cancels the unfinished job."
}
}
},
"dependent-cancellations": {
"description": "List static links through which a later waiting job needs an earlier job's output.",
"when-empty": "No later waiting job has a static dependency on an earlier job's output.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this dependency case."
},
"cancellation": {
"type": "string",
"required": true,
"description": "The matching cancellation row."
},
"link-declared-in": {
"type": "citation",
"required": true,
"description": "The static link from the later requirement to the earlier output."
}
}
},
"delivery-cases": {
"description": "List a real capacity or delivery condition not already carried by a collection, readmission, redelivery, or fallback row.",
"when-empty": "When every other delivery row set is also empty, delivery is automatic and the normal destination always accepts the output. A reviewer confirms both promises before the adoption relies on them.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this delivery situation."
},
"condition-declared-in": {
"type": "citation",
"required": true,
"description": "The capacity or collection rule that makes the situation relevant."
}
}
},
"output-destinations": {
"description": "List fallback destinations after the normal destination, in the order tried.",
"when-empty": "No fallback destination follows the normal destination.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "Name this fallback destination."
},
"destination-declared-in": {
"type": "citation",
"required": true,
"description": "The rule naming the destination and how it accepts the whole output."
}
}
}
}
},
"rules": {
"progress-does-not-reset-on-stop": {
"forbid": {
"flag": {
"input-claim-timing": [
"with-progress"
],
"partial-work": [
"reset-at-stop"
]
}
},
"message": "Progress-based input claims cannot reset all work when inputs run out; keep or reverse the work, or claim inputs at another time."
},
"progress-reversal-warning": {
"forbid": {
"flag": {
"input-claim-timing": [
"with-progress"
],
"partial-work": [
"reverse-while-stopped"
]
}
},
"severity": "warning",
"message": "Reversing work while inputs are claimed with progress can make the same materials leave and return repeatedly."
},
"collection-needs-a-placed-output": {
"forbid": {
"any": [
{
"flag": {
"delivery-trigger": [
"on-collection"
],
"output-full": [
"hold-undelivered"
]
}
},
{
"flag": {
"delivery-trigger": [
"on-collection"
],
"output-full": [
"try-destinations"
]
}
}
]
},
"message": "A collected result must already be at an accepted destination; choose a destination rule that puts it there first."
}
},
"contract": "job-resolution",
"version": 1,
"summary": "Covers crafting benches, build queues, research, and cooking: one job rule decides inputs, claims, work, interruption, limits, delivery, and failure, written down once. What a recipe makes and what it is worth stay with the game's own rules.",
"origin": "https://opengdd.org/contracts/job-resolution-1",
"mechanism": [
"This is the single normative authority for states, event order, input claims, and reports. Questions describe choices used here; they do not redefine these steps.",
"A **job run** begins with one request and ends at rejection, cancellation, terminal failure, or delivery. Every report carries the same job id and run id. It also carries old and new lifecycle state, cause, recorded work before and after, input units newly claimed, released, spent, or lost, and the output destination when chosen. Amounts use units and numbers from the cited game rules. `job-requested` has no old state and sits outside the ordered instant batch. `job-rejected` ends the run but is not a lifecycle state. `destination-refused` is stateless: old and new state are both `finished`.",
"A claim makes inputs unavailable to every other rule while keeping their source known. Releasing a claim returns surviving units to that source. Spending or losing units removes them; neither can later be released.",
"The forward path is `requested -> waiting -> started -> working -> finished -> delivered`. Side paths are `working -> stopped -> working`, `requested/waiting/working/stopped -> cancelled`, and `waiting/working/stopped/finished -> failed`. A recoverable failure reports `job-failed` and lands in `stopped` instead.",
"Not every job visits every state. `waiting` and `stopped` can return to the forward path. `cancelled`, terminal `failed`, and `delivered` are terminal. `started` is a transition boundary, not a waiting state. Entry to any terminal state immediately releases every working or waiting count. `releases-working-at` affects only the success path and never delays terminal release.",
"Every stopped job records all active stop causes and its resume point. It resumes only after every cause clears. Finish-gate causes are `output-full` and `inputs-unavailable-at-finish`; they are slot-retaining. Every other cause is non-retaining. Entry to `stopped` always releases a waiting count. A stopped job retains its working count only while every active cause is slot-retaining; the first non-retaining cause releases it. `partial-work` applies once when the first ordinary stop cause joins the set, never for a finish-gate cause. `failure-recovery` is neither: it is non-retaining, and `partial-work` never applies to it, because step 16 has already settled the loss.",
"Whenever a pool has free working room, it first offers that room to admitted jobs eligible to start or resume, in the pool's waiting order. A job stopped by an instruction joins that order at the stop moment and never outranks the job that displaced it. A cleared reason also causes a waiting or stopped job to be offered free room again. After those offers, the pool scans standing orders in written order. It also scans when created, after a rejection of a request the pool did not create in this scan, and when cited eligibility becomes true. A scan keeps creating eligible requests until no row is eligible or no room remains. A scan may create more than one job from the same row, filling all free room. These are level-triggered scans, not one-time edges.",
"### Request and accept",
"1. Read `job-declared-in` once. It names required inputs, one successful output unit, any in-place target, and game-owned choice or quality rules. If work limits exist, assign the request to exactly one pool. For separate place counts, assign it to exactly one cited place. Report `job-requested`. 2. Check availability without reserving anything. For required inputs, test the full requirement under the three whole-claim timings. Under progress-based claiming, test only the initial rounded share. A game rule may require a stricter offer check. If the tested share is missing, report `job-rejected` with cause `missing-inputs`; claim nothing, record no work, and create no output. Jobs with no inputs skip the check. 3. Decide whether the request would enter `waiting`, including a free pool whose order places an earlier admitted job first. Waiting admission always consumes waiting capacity. If that limit is full, reject with cause `job-limit-full`. A request that starts immediately uses no waiting count. 4. Attempt admission. When room must be reserved before start, reserve the whole output atomically. If room is unavailable, the request stays `requested`; `readmission-declared-in` causes another attempt without polling. Recheck input and waiting limits on delayed admission. On admission, accept the request. Claim the full requirement in the same batch when inputs are taken at request. An admitted request that cannot start enters `waiting`; report `job-waiting` and every current reason. No work is recorded in `waiting`, and no input is claimed there except the claim made by `taken-at-request`.",
"### Start",
"5. Recheck every admission and start gate. Claim the full requirement under start timing. Under progress-based timing, claim the initial share. A failed claim enters `waiting`, consuming waiting capacity; if the waiting limit is full, reject with cause `job-limit-full` and release any output reservation. Otherwise report `job-waiting` with cause `inputs-unavailable`. Inputs taken at request are already held; inputs taken at finish remain at their source. 6. Keep any output reservation through delivery; other output answers reserve nothing. Leave the waiting count, acquire the working count, and report `job-started`. 7. Without a work-phase row, resolve start and finish in one batch. The reports stay ordered unless `hold-undelivered`, all-refused `try-destinations`, or `on-collection` legally parks the job in visible `finished`, or a finish-gate cause stops it there. With a work phase, enter `working` and report `job-working`.",
"### Work and input claims",
"8. Work completes as `duration-declared-in` says: its clock advances or its completion event occurs. Record exposed work points at full precision. A display meter is outside this contract. 9. With progress-based timing, every observable advance first claims the rounded share for the proposed work point. If unavailable, do not record the advance; stop with cause `inputs-unavailable`. Whole-claim timings keep their full claim. Finish timing keeps inputs available elsewhere. 10. Reaching the required work moves to the finish gate. It does not yet spend inputs or create the successful output.",
"### Stop, resume, and interrupt",
"11. An interruption is a temporary inability or instruction to advance that is not refusal, failure, cancellation, or delivery. It moves `working -> stopped`, adds its cause, applies `partial-work` and the claim policy, then reports `job-stopped`. An instructed stop must be named by `interruptions-declared-in`. A later cause joins the set and reports `stopped -> stopped`; it does not apply the work answer again. 12. First adjust a progress-based claim to any reduced work. Then apply `stopped-claims`: hold the claim, or release it to its source. Whole claims taken at request or start follow the same answer. Finish timing has no claim. When the question is not asked, the claim is held. 13. When every cause clears, the job competes for free working room through its pool, or proceeds without a pool. Recheck every gate and reclaim any released share. If a gate or claim is unavailable, remain stopped and keep the room free. Otherwise report `job-resumed` and return to the recorded resume point: a waiting-origin failure continues at step 5 and acquires the selected count at step 6, while interrupted work reacquires the count and enters `working`. The same job resumes; no new request is created. 14. The finish gate tests capacity and any finish-time claim together. The finish-gate wait answer adds `output-full`; an unavailable claim adds `inputs-unavailable-at-finish`. These causes preserve completed work and retain working room unless another active cause releases it. They never apply `partial-work`. `stopped-claims` applies to finish-gate stops exactly as in step 12. When every cause clears and any released claim is reclaimed, report `job-resumed` and return directly to the finish gate.",
"### Fail",
"15. A failure row may fire only from its named state. A failure from `finished` is always terminal; no recoverable result exists there. Resolve its row result, or the shared failure answer when the row has none, atomically. For a recoverable result, apply the stopped-claim policy before the one `job-failed` report. 16. A partial result may lose a strict subset of claimed inputs, reduce work without passing below none, or do both. It creates no successful output. Under progress-based timing, apply losses first. If the claim is held, reduce work to the highest point the surviving claim supports and release excess claim. If the claim was released, reduce work only by the named loss. The same job lands in `stopped` with cause `failure-recovery`; its recorded resume point is the start gate for a waiting-origin failure, the prior work point for a working failure, or the already-recorded point for a stopped failure. Later recovery follows the normal resume rule. 17. A ruined job enters terminal `failed`, can never finish as the same job, and creates no successful output. Failure from `finished` destroys its one undelivered new output. For in-place work, it ruins the transformation, not the target's existence. The cited failure rule owns the damaged state. Failure itself returns no claimed input; remaining claims stay assigned to the failed job unless the cited failure rule disposes of them. After cited claim changes, terminal entry releases every count and reports `job-failed`.",
"### Cancel",
"18. A declared cancellation may target `requested`, `waiting`, `working`, or `stopped`. Snapshot current claims, release every count, apply the return answer when asked, enter `cancelled`, and report `job-cancelled`. Under the reset answer, terminal work becomes none after the snapshot. Cancellation creates no output and never undoes a finished or delivered output. 19. Returning claimed inputs releases every surviving claimed unit. Returning nothing spends them. A rule-sized return releases exactly its named subset and spends the rest. No answer recreates a unit already lost, and unclaimed inputs remain where they are. 20. A dependency is the declared static link from a later waiting job's requirement to the cancelled job's output. Ending dependents finds every transitive later waiting job whose requirement can no longer be met. After the first cancellation settles, cancel those jobs in waiting order, each with its own claim settlement and report. Leaving dependents keeps them waiting. Completed intermediate jobs and delivered outputs remain.",
"### Finish and deliver",
"21. At the finish gate, finish-time timing tries to claim the full input. If unavailable, follow the finish-gate stop rule. Other timings must hold the required claim. Atomically spend inputs and establish the one successful output: a new thing or a cited target transformed in place. An in-place output is delivered by that state change at its site. A compound output is still one atomic delivery unit. Report `job-finished`. 22. Resolve capacity by the selected answer. An always-accepting destination takes the whole output. A pre-start reservation is already held. A finish-gate wait follows the stop rule. A held output remains one owned, inaccessible output until its cited retry. An ordered route tries the normal destination and then fallback rows. Every refusal by any destination, including a held output's first refusal and each refusal on a cited retry, reports `destination-refused`. If all refuse, keep the same output until the cited retry. Delivery never polls. An in-place output has no destination capacity: it is delivered by the state change of step 21, and the adoption answers `never-full`. 23. Automatic delivery moves an accepted result `finished -> delivered` immediately. Collection keeps it accessible at its chosen destination until the cited event, then moves it to `delivered`. Report `job-delivered` exactly once. 24. On success, release working room after the transition named by the pool row and after that transition's report. Then run the room-offer and standing-order process. Rejection ends its run; a later retry belongs to the requester unless a standing order creates it.",
"### Ordering guarantee",
"One transition, all claim changes, and all reports settle before another transition begins. Claim changes happen before the transition report unless a step says otherwise. Automatic delivery to an accepting destination after an instant start keeps `job-started`, `job-finished`, and `job-delivered` in one ordered batch with no outside event between them. Events offered at the same moment enter this lifecycle one at a time in the order supplied by **Event resolution**. This contract creates no same-moment ordering rule."
],
"answers": {
"job-inputs": "required-inputs",
"partial-work": "keep-with-job",
"input-claim-timing": "taken-at-start",
"stopped-claims": "hold",
"delivery-trigger": "automatic",
"output-full": "wait-until-space"
},
"values": {},
"rows": {
"job": [
{
"job-declared-in": "factory.assembler-recipes",
"normal-destination-declared-in": "factory.output-slot",
"output-kind": "new-thing"
}
],
"work-phases": [
{
"id": "assembly",
"duration-declared-in": "factory.assembler-times"
}
],
"work-limits": [
{
"id": "assembler-head",
"covers-declared-in": "factory.assembler-requests",
"scope": "each-place",
"places-declared-in": "world.assemblers",
"place-assignment-declared-in": "factory.requesting-assembler",
"working-limit-key": "numbers.one-active",
"waiting-order": "request-order"
}
],
"standing-orders": [
{
"id": "repeat-selected",
"work-limit": "assembler-head",
"requests-job-declared-in": "factory.selected-recipe",
"eligible-declared-in": "factory.recipe-needed-and-affordable"
}
],
"delivery-cases": [
{
"id": "full-output-slot",
"condition-declared-in": "factory.output-slot-capacity"
}
],
"read-first": [],
"interruptions": [],
"reversal-rules": [],
"progress-rounding-rules": [],
"cancel-return-rules": [],
"collection-events": [],
"readmission-events": [],
"redelivery-events": [],
"failures": [],
"cancellations": [],
"dependent-cancellations": [],
"output-destinations": []
},
"pack": "sha256:bfbe0f8482c06bd771e70af5afb44d53afad291161ea87d85f32021397ab2c3b"
}