Moving Box / Truck Size Estimator mechanism

Model scope

The stated algorithms are plausible heuristics, but the spec omits the actual lookup tables, table provenance, room-count definitions, truck-selection inequality, capacity margin, and payload constraints. The test vectors therefore use explicitly declared common moving-planning conventions and should remain conditional until the production table source and edition are fixed.

• The box formula, boxes ≈ rooms × average boxes per room, is a reasonable heuristic but cannot be verified as a unique standard without the actual rate table and a definition of room versus bedroom.
• The truck formula, truck_cuft = sum of item volumes, is dimensionally correct, but truck selection also requires a stated rule such as choosing the smallest capacity greater than or equal to the calculated volume.
• A home-size lookup is underspecified: the input alternates between total rooms, bedrooms, and home size, but no authoritative mapping table is supplied.
• The specification does not state whether item volumes include packing materials, furniture void space, or a recommended unused-capacity margin.
• The source and edition of the moving-industry lookup tables are not provided; U-Haul-style tables are company-specific guidance rather than a universal standard.

Units and conventions

• All item and truck-capacity volumes are in cubic feet (cu ft).
• The itemized-volume calculation is sum(quantity × nominal item volume) plus any explicitly supplied bulk volume.
• The box-rate table returns boxes per room, and the room count is an integer total-room count, not bedroom count.
• Truck selection uses the smallest listed truck whose nominal capacity is greater than or equal to the calculated volume.
• Nominal moving-box volumes use 1.5 cu ft for a small/book box, 3.0 cu ft for a medium box, and 4.5 cu ft for a large box.
• The concrete table fragments below use widely tabulated standard values in common U-Haul-style moving guidance; they are conditional test conventions, not proof that the unspecified catalog table uses these values.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "rooms": 2,
    "itemized_inventory": {
      "small_boxes": 20,
      "medium_boxes": 30,
      "large_boxes": 10,
      "other_items_volume_cuft": 80
    }
  },
  "expected_outputs": {
    "estimated_box_count": 50,
    "suggested_truck_size": "cargo van",
    "required_volume_cuft": 245,
    "truck_capacity_cuft": 245
  },
  "reference_data": {
    "box_rate_row": {
      "rooms": 2,
      "avg_boxes_per_room": 25,
      "source_convention": "widely tabulated standard value; rough moving-planning heuristic"
    },
    "moving_box_volume_rows": [
      {
        "box_type": "small/book",
        "volume_cuft": 1.5,
        "source_convention": "widely tabulated standard value; common nominal moving-box size"
      },
      {
        "box_type": "medium",
        "volume_cuft": 3,
        "source_convention": "widely tabulated standard value; common nominal moving-box size"
      },
      {
        "box_type": "large",
        "volume_cuft": 4.5,
        "source_convention": "widely tabulated standard value; common nominal moving-box size"
      }
    ],
    "truck_capacity_row": {
      "truck": "cargo van",
      "capacity_cuft": 245,
      "source_convention": "widely tabulated standard value; U-Haul-style published nominal cargo capacity"
    }
  },
  "working": "Boxes: 2 rooms × 25 boxes/room = 50 boxes. Volume: (20 × 1.5) + (30 × 3.0) + (10 × 4.5) + 80 = 30 + 90 + 45 + 80 = 245 cu ft. Truck lookup: 245 cu ft ≤ cargo-van capacity 245 cu ft, so select cargo van. This lands exactly on the 245-cu-ft truck table entry."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

The specification does not provide the required lookup-table values, validity rules, truck-size thresholds, or precedence when both home-size and itemized inputs are supplied. It also does not define rejection behavior for negative room counts or volume units, allowing nonsensical or materially different outputs.

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche7/tranche7-results.json
• BOUNDARY_HAZARD_CATALOG.json