SAR Multi-Crop Acreage Estimator

Limitations

← Back to outcome

LIMITATIONS

PROOF_STANDARD = IRS_AUDITOR. Every simulated, synthetic, mocked, manually-assisted, skipped, partially-verified, or statically-checked element is listed here. Mirrored in verification-report.json (disclosedSeams) and proof/EXECUTIVE_EVIDENCE.md.

DISCLOSED_SEAM — incomplete / non-live components

  1. Official competition dataset is absent. The X-band SAR tiles, village

boundary polygons, and label tables are not present in this workspace and cannot be fetched here (auth-gated, no credentials available to the agent). Consequence: no official leaderboard MSE was produced — the customer outcome remains open.

  1. Raster → zonal-statistics (Stage A) was not executed. Calibration

(DN→σ⁰→dB), optional terrain flattening, speckle reduction, and zonal statistics over village polygons are documented in run-deploy-instructions.md but not run (requires GDAL / rasterio / SNAP / Google Earth Engine).

  1. All reported metrics are SIMULATED (synthetic). Inputs come from

src/synth.mjs (per-crop seasonal backscatter, area-weighted linear-power mixing, soil-moisture/speckle/measurement noise). Not field observations. Absolute MSE will differ on real data.

  1. The "official" verification run uses a SYNTHETIC-DERIVED fixture.

tools/synth-to-official.mjs emits official-FORMAT files from src/synth.mjs. The 16/16 result (proof/evidence/verify-official-fixture.json) proves the official path executes and emits a valid submission — not real-data accuracy.

  1. Real-data accuracy is estimated by cross-validation, not a leaderboard.

When real labels are present, MSE is computed out-of-fold on labelled villages — an unbiased estimate, not the official score.

Scope limitations (not defects)

  1. Round 1 only. Crop condition, yield, and production forecasting are out

of scope and not implemented.

  1. Optional residual forest disabled by default. Reported synthetic numbers

are ridge-only; AcreageModel({useForest:true}) exists but is not in the verified path.

Not claimed

  • Not "production-ready": no deployment, security, monitoring, load, or

operational tests were run.

  • Not "certified": status is PROOF_INCOMPLETE (proof/PROOF_SCORECARD.json,

certification-report.md).

  • No guarantee of competition placement or real-world field accuracy.