Board Token Inventory Delta
Report signed board token inventory changes between explicit typed count observations; does not infer captures, promotions or legality.
Description
Report signed board token inventory changes between explicit typed count observations; does not infer captures, promotions or legality.
Comparing inventory snapshots reveals gains and losses by typed token value.
When to use this tool
Report signed board token inventory changes between explicit typed count observations; does not infer captures, promotions or legality.
- Prepare the supplied beforeJson, afterJson fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter beforeJson, afterJson. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.changes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Normalize beforeJson and afterJson count tables. For each key return after count minus before count, omitting zero changes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| beforeJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| afterJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "beforeJson",
"decoded": [
{
"value": "pawn",
"count": 3
}
]
},
{
"field": "afterJson",
"decoded": [
{
"value": "pawn",
"count": 1
},
{
"value": "queen",
"count": 1
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.changes | The changes list in the ordering and representation described above. |
{
"input": {
"beforeJson": "[{\"value\":\"pawn\",\"count\":3}]",
"afterJson": "[{\"value\":\"pawn\",\"count\":1},{\"value\":\"queen\",\"count\":1}]"
},
"output": {
"result": {
"changes": [
{
"value": "pawn",
"delta": -2
},
{
"value": "queen",
"delta": 1
}
]
}
}
}Limitations and assumptions
- The tool does not infer the cause or legality of a change. It compares count snapshots rather than reconstructing move order.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a game-state-aware rules engine when occupancy, legal moves or scoring rules matter. These operations calculate coordinates, local geometry or supplied ledger totals without inferring a complete position.
References
Similar or alternative tools
- Board Captured Piece Ledger
Aggregate explicit captured-piece events by side and piece name; no inferred moves, scoring or game legality.
- Board Cell Checker Parity
Compute abstract checkerboard cell parity on nonnegative integer coordinates; does not assign chess color names.