Data Rate / Storage Planner (Camera Codecs) 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

t7-040

Effect

Computation or source lookup only

Input and validation requirements

A card size of exactly zero makes the cards-needed calculation undefined due to division by zero; the instrument should reject that input. The convention probe also shows materially different results if duration units are misread.

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": {
    "codec_preset": "Apple ProRes 422 HQ",
    "resolution": "3840x2160",
    "fps": 30,
    "duration_s": 3600,
    "card_capacity_GB": 128
  },
  "expected_outputs": {
    "data_rate_Mbps": 707,
    "data_rate_MB_s": 88.375,
    "storage_GB": 318.15,
    "cards_needed": 3
  },
  "reference_data": {
    "codec": "Apple ProRes 422 HQ",
    "resolution": "3840x2160",
    "fps": 30,
    "nominal_data_rate_Mbps": 707,
    "source_convention": "widely tabulated standard value; Apple ProRes manufacturer nominal-rate table"
  },
  "working": "1. Convert rate: 707 Mbps ÷ 8 = 88.375 MB/s. 2. Storage: 88.375 MB/s × 3,600 s = 318,150 MB. 3. Convert to decimal GB: 318,150 MB ÷ 1,000 = 318.15 GB. 4. Cards: ceil(318.15 GB ÷ 128 GB) = ceil(2.485546875) = 3 cards."
}

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