Garden Plant Spacing Planner implementation

Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

Record owner

Guth Instruments

Lifecycle

verified-clean

Evidence ID

t4-269

Effect

Computation or source lookup only

Input and validation requirements

The offset-pattern rule specifies only approximately 15% greater density and does not define the triangular-packing geometry, integer rounding, or edge handling. For a grid count of 24, it produces 27.6 before rounding, so the exact required plant count is not uniquely determined. Zero spacing also yields undefined division and must be rejected.

Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

{
  "inputs": {
    "bed_length": 3,
    "bed_width": 2,
    "spacing": 0.5,
    "row_spacing": 0.5,
    "unit": "m",
    "layout_pattern": "grid"
  },
  "expected_outputs": {
    "plants_per_row": 7,
    "rows": 5,
    "total": 35,
    "layout_diagram": "7 columns x 5 rows"
  },
  "working": "plants_per_row = floor(3 / 0.5) + 1 = floor(6) + 1 = 6 + 1 = 7; rows = floor(2 / 0.5) + 1 = floor(4) + 1 = 4 + 1 = 5; total = 7 x 5 = 35."
}

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-tranche4/tranche4-results.json