{
 "run_date": "2026-06-18",
 "decision_item": "RFS-011",
 "artifact": "requirements-answer-pack",
 "source_state": "Open: stakeholder sign-off pending",
 "question_count": 5,
 "locked_decision_count": 4,
 "open_decision_count": 5,
 "questions": [
  {
   "key": "hourly_target_area",
   "title": "Hourly target area",
   "prompt": "What land block must one fleet revisit every hour in the first trial?",
   "why_needed": "This is the missing input that turns per-drone coverage into fleet count and maximum affordable payload cost.",
   "options": [
    {
     "label": "250 ha first trial",
     "answer_to_record": "Hourly revisit target = 250 ha.",
     "evidence": "2 payloads at 120 m with a USD 33k unit-cost ceiling, or 1 payload with a waiver and a USD 66k ceiling.",
     "design_consequence": "This is the least costly meaningful trial block and can fit one waiver-enabled custom payload or two cheaper 120 m payloads.",
     "follow_up": "Use this if RFS wants a focused proof flight before scaling.",
     "source_link": "coverage-sizing-grid.html"
    },
    {
     "label": "500 ha planning case",
     "answer_to_record": "Hourly revisit target = 500 ha.",
     "evidence": "3 payloads at 120 m with a USD 22k unit-cost ceiling, or 2 payloads with a waiver and a USD 33k ceiling.",
     "design_consequence": "This is the current central planning case; it makes altitude authorisation and unit-cost control decisive.",
     "follow_up": "Use this if RFS wants a few-square-kilometre operational block.",
     "source_link": "coverage-sizing-grid.html"
    },
    {
     "label": "1000 ha stretch case",
     "answer_to_record": "Hourly revisit target = 1000 ha.",
     "evidence": "6 payloads at 120 m with a USD 11k unit-cost ceiling, or 3 payloads with a waiver and a USD 22k ceiling.",
     "design_consequence": "This exceeds the current custom-payload budget envelope unless the payload becomes cheaper or the fleet budget changes.",
     "follow_up": "Use this only if RFS accepts a budget or architecture change.",
     "source_link": "coverage-sizing-grid.html"
    }
   ],
   "closeout_test": "Record one target area or a bounded first-trial range in hectares."
  },
  {
   "key": "altitude_path",
   "title": "Altitude path",
   "prompt": "Can the first survey case assume above-120 m operations?",
   "why_needed": "The waiver case roughly doubles per-drone coverage and can remove one payload from the 500 ha planning case.",
   "options": [
    {
     "label": "Stay at 120 m",
     "answer_to_record": "Altitude basis = 120 m AGL cap.",
     "evidence": "The conservative model covers about 182 ha/h per payload.",
     "design_consequence": "Fleet count rises; the optics and payload branch must work within the most conservative operating envelope.",
     "follow_up": "Keep procurement and optics gates tied to the 120 m rows.",
     "source_link": "fleet-coverage.html"
    },
    {
     "label": "Waiver path is realistic",
     "answer_to_record": "Altitude basis = above-120 m waiver case may be used.",
     "evidence": "The waiver model covers about 378 ha/h per payload.",
     "design_consequence": "Fewer payloads may cover the same block, but the optical design must still hold the 3 cm target gate at the higher altitude.",
     "follow_up": "Ask RFS to name the trial altitude and authorisation path.",
     "source_link": "fleet-coverage.html"
    }
   ],
   "closeout_test": "Record whether the 120 m cap is binding or the waiver case is in scope."
  },
  {
   "key": "payload_branch",
   "title": "Payload branch",
   "prompt": "Should AAO quote COTS first, custom optics first, or both in parallel?",
   "why_needed": "Fast 640-class COTS cameras now pass first-order physics, but only exact product data can prove raw radiometry, calibration access, mass, power, and cost.",
   "options": [
    {
     "label": "Quote COTS first",
     "answer_to_record": "Procurement branch = COTS quote gate before custom fabrication.",
     "evidence": "45 deg 640-class radiometric camera reaches SNR 105.8; 69 deg 640-class mapping camera reaches SNR 38.4.",
     "design_consequence": "This can protect the AUD 100k fleet budget, but only if raw/pre-AGC frames and calibration state are accessible.",
     "follow_up": "Request vendor evidence and quotes before ordering hardware.",
     "source_link": "cots-fleet-screen.html"
    },
    {
     "label": "Run COTS and custom in parallel",
     "answer_to_record": "Procurement branch = parallel COTS quote gate and custom optics maturation.",
     "evidence": "The custom reference reaches SNR 45.0, while fast 640-class COTS paths also clear the benchmark.",
     "design_consequence": "This preserves schedule optionality but spends effort on two paths until quotes and interface evidence arrive.",
     "follow_up": "Use the same raw-data and calibration checklist for both paths.",
     "source_link": "requirements-closeout.html"
    },
    {
     "label": "Custom first",
     "answer_to_record": "Procurement branch = custom optics first.",
     "evidence": "The custom reference is the controlled design path; Lepton 3.1R SWaP floor is rejected at SNR 0.4, so not every cheap COTS path is viable.",
     "design_consequence": "This keeps optical ownership but probably limits the AUD 100k fleet to one or two payloads unless cost is reduced.",
     "follow_up": "Restart prescription work only after EFL/FOV and F-number targets are fixed.",
     "source_link": "cots-fleet-screen.html"
    }
   ],
   "closeout_test": "Record one procurement branch and the product evidence required before spending."
  },
  {
   "key": "airframe_class",
   "title": "Airframe class",
   "prompt": "Is a 2 kg-capable fixed-wing or VTOL survey aircraft acceptable for the first payload?",
   "why_needed": "The current payload boundary points to heavier survey aircraft; a smaller airframe would reopen payload mass, optics, and coverage assumptions.",
   "options": [
    {
     "label": "2 kg class accepted",
     "answer_to_record": "Airframe basis = 2 kg-capable fixed-wing or VTOL class is acceptable.",
     "evidence": "The fleet coverage model uses fixed-wing survey platforms and flags 2 kg payload support as a gating assumption.",
     "design_consequence": "The 150 mm / sub-2 kg custom path can remain in the design space.",
     "follow_up": "Carry the current payload envelope into vendor and airframe conversations.",
     "source_link": "fleet-coverage.html"
    },
    {
     "label": "Must be lighter",
     "answer_to_record": "Airframe basis = first payload must fit a lighter drone class.",
     "evidence": "The COTS screen shows Lepton-class SWaP paths are too weak for the 3 cm target, so smaller is not automatically mission-capable.",
     "design_consequence": "The project must relax target, coverage, altitude, or payload ownership before the optics work can proceed honestly.",
     "follow_up": "Define the actual mass, power, and volume ceiling before more prescription work.",
     "source_link": "cots-fleet-screen.html"
    }
   ],
   "closeout_test": "Record the accepted aircraft class or the replacement mass and power envelope."
  },
  {
   "key": "signoff_authority",
   "title": "Requirements sign-off",
   "prompt": "Who can accept the locked baseline and close RFS-011?",
   "why_needed": "The site now has enough decision artifacts to close the interview, but the TODO must stay open until a stakeholder explicitly accepts the answers.",
   "options": [
    {
     "label": "Accept locked baseline",
     "answer_to_record": "Stakeholder accepts area-survey role, 3 cm char target, 640-class LWIR branch, 150 mm package, sub-2 kg payload, and AUD 100k payload budget.",
     "evidence": "These are the locked rows on the closeout checklist.",
     "design_consequence": "RFS-019 can restart toward a survey prescription instead of revisiting mission role and target class.",
     "follow_up": "Record the name, date, and source note before marking RFS-011 complete.",
     "source_link": "requirements-closeout.html"
    },
    {
     "label": "Reopen one baseline item",
     "answer_to_record": "Stakeholder reopens one or more locked baseline decisions.",
     "evidence": "Any change to role, target class, detector branch, payload envelope, or budget changes the downstream optical target.",
     "design_consequence": "RFS-011 stays open and the derived coverage, COTS, and prescription pages must be rerun before prototype work.",
     "follow_up": "Name the changed decision and rerun the affected decision artifacts.",
     "source_link": "mission-decision.html"
    }
   ],
   "closeout_test": "Record the accepting stakeholder, accepted baseline, and answer source."
  }
 ],
 "answer_record_fields": [
  "Answered by",
  "Answer date",
  "Hourly target area",
  "Altitude basis",
  "Payload branch",
  "Airframe class",
  "Sign-off authority",
  "Evidence source"
 ],
 "evidence_links": [
  {
   "label": "Requirements closeout checklist",
   "href": "requirements-closeout.html"
  },
  {
   "label": "Coverage sizing grid",
   "href": "coverage-sizing-grid.html"
  },
  {
   "label": "COTS payload screen",
   "href": "cots-fleet-screen.html"
  },
  {
   "label": "Fleet coverage model",
   "href": "fleet-coverage.html"
  },
  {
   "label": "Mission decision packet",
   "href": "mission-decision.html"
  },
  {
   "label": "Evidence intake ledger",
   "href": "requirements-evidence-ledger.html"
  }
 ],
 "closeout_rule": "Do not mark RFS-011 complete until the selected answers and the accepting stakeholder are recorded in project notes."
}