Board Move Source Destination Audit

Audit explicit board occupancy at move source/destination, without deciding piece movement, capture rules or legal moves.

Description

Audit explicit board occupancy at move source/destination, without deciding piece movement, capture rules or legal moves.

A move's source and destination have independent occupancy facts. Checking them alone does not determine a legal move.

When to use this tool

Audit explicit board occupancy at move source/destination, without deciding piece movement, capture rules or legal moves.

  • Prepare the supplied occupied, from, to 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

  1. Enter occupied, from, to. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.sourcePresent, result.destinationOccupied, result.sameCell. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require occupied to have unique cell labels. Return whether from is present, whether to is occupied and whether the labels are identical.1

Input fieldMeaning and representationAccepted input
occupiedoccupied.List of strings; at most 128 entries
fromfrom.Text; at most 8,192 UTF-16 code units, subject to the grammar above
toto.Text; at most 8,192 UTF-16 code units, subject to the grammar above
Output fieldInterpretation
resultObject containing the named outputs below.
result.sourcePresentFlag for source present under the exact condition described above.
result.destinationOccupiedFlag for destination occupied under the exact condition described above.
result.sameCellFlag for same cell under the exact condition described above.
json
{
  "input": {
    "occupied": [
      "a1",
      "b1"
    ],
    "from": "a1",
    "to": "b1"
  },
  "output": {
    "result": {
      "sourcePresent": true,
      "destinationOccupied": true,
      "sameCell": false
    }
  }
}

Limitations and assumptions

  • No coordinate grammar, ownership, piece movement or capture rule is checked, and the occupancy list is not modified.
  • 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

  1. Tool behavior and example: Board Move Source Destination Audit — tool.io

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.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies