Test Document Library
Below are the fictional MRT-X scenario inputs that the methodology was validated against. Reviewers can copy any document and paste it into the Analyze surface to exercise the pipeline against the live catalog.
Provenance — these documents are fictional methodology test material anchored to the publicly distributed NAVAIR PMA-263 Request for Information for Medium Range Tactical Unmanned Aircraft Systems (Notice 243-26-024, 11 February 2026) as operational context only. The capstone does not respond to the RFI; the platform described is not a proposed solution (per ADR-0006). The fictional vendor “Aerix Defense Systems” does not exist.
Requirements
Paste these into the Analyze form with Document type → Requirements. The 10-statement cap on each submission means you may want to paste individual subsections of the SRD rather than the full file at once.
58 shall-statements across program management, mission performance, sensors / payload, propulsion + power, flight control, structures, environmental, and software / safety domains. The full Part A baseline.
Verification reports
Paste these into the Analyze form with Document type → Verification report. Each report exercises a different subset of the catalog. Two reports (BATT and ENV) are deliberately clean — the engine should produce zero findings on them, though in practice it over-flags at the rate documented in the test report.
Vendor SSA with weapon-payload hazard analysis gaps, C2-link-loss ambiguity, and a Catastrophic / Remote probability assertion without reliability basis.
- RPT-MRTX-PROP-001 — Propulsion & Fuel System SafetyRPT-MRTX-PROP-001-propulsion-fuel-safety.md
Vendor substantiation covering the turbogenerator and wet-frame fuel architecture. Includes crash-load fuel containment gap, non-petroleum CONTRA against the RFI, and a qualitative-only fire protection claim.
- RPT-MRTX-ELEC-001 — Electrical Power System ComplianceRPT-MRTX-ELEC-001-electrical-compliance.md
Vendor electrical substantiation. Includes a 270 VDC arc-fault detection claim without test data and a HVDC-category extrapolation of MIL-STD-704F.
- RPT-MRTX-SW-001 — Flight Control & Software AssuranceRPT-MRTX-SW-001-software-assurance.md
Vendor SW assurance report. Contains the cross-artifact crown jewel: a TRL 8 maturity claim based on community flight hours contradicting the absent flight-critical SW design-assurance evidence.
- RPT-MRTX-FT-001 — Flight Test Report: Endurance & PerformanceRPT-MRTX-FT-001-flight-test-endurance.md
Flight test report. Endurance demonstrated at no-payload and reduced-payload but never at the operational ISR payload mass — a verification gap. Includes wind / airspeed bracketing ambiguity.
- RPT-MRTX-ENV-001 — Environmental Qualification (CONTROL)RPT-MRTX-ENV-001-environmental-qual.md
Test report covering temperature, altitude, humidity, salt-fog, and shipboard environments per MIL-STD-810H methods. Intentionally clean — engine should not flag anything here.
- RPT-MRTX-BATT-001 — Lithium Battery Safety Qualification (CONTROL)RPT-MRTX-BATT-001-battery-safety-qual.md
Vendor / test report on the Li-ion + supercap energy buffer. Intentionally clean — engine should not flag anything here.
Reference + supporting documents
These provide context for the requirements baseline and the platform design choices. They are not formatted for the Analyze surface — download for review only.
Parent operational requirements from which the SRD baseline is derived. Documents the Group 1 → Group 2 reclassification and the series-hybrid architecture rationale.
- TS-MRTX-PWR-001 — Battery Topology vs Weight Trade StudyTS-MRTX-PWR-001-battery-trade-study-v1.md
Trade study that drives the Part A C1 INFEAS crown jewel — establishes that no current battery chemistry closes the published endurance requirement within the Group 1 mass ceiling.
Excerpt of the publicly distributed NAVAIR PMA-263 RFI Notice 243-26-024 (11 February 2026) listing the requirements categories the scenario anchors to. Provides operational context only.