Compliance checklist

Rendezvous, Proximity Operations (RPO) Threat Response (RTR) VICTUS Responsive Launch Space Vehicle (SV) · SYD89-26-RPO-RLSV. 9 requirement sentences found in the notice and 2 attachments: every "shall", "must" and "required", quoted as written and sorted into submission requirements (1) and performance / contract clauses (8). Nothing is generated.

Pro

The full checklist is a Pro feature

9 requirement sentences on this RFP. Pro shows every one, grouped by section, with a CSV export, for $39/mo. Below is a preview.

Submission requirements · 1

RFI for future RPO Threat Response VICTUS Responsive Launch SV_v2-5.pdf · RPO-D Capability · 1

Deadline: Submission is required no later than 19 October 2026 at 1200 PDT. 4.1.3.2.

Performance / contract clauses · 8

RFI for future RPO Threat Response VICTUS Responsive Launch SV_v2-5.pdf · Page 3 · 1

Other MOSA systems are acceptable, but a Handle compliant interface must be considered 2: The GFE Payload Size, Weight, and Power (SWAP) values are in addition to vendor-supplied payloads addressing the Space Domain Awareness (SDA) and RPO requirements 2.2.3.

RFI for future RPO Threat Response VICTUS Responsive Launch SV_v2-5.pdf · RPO-D Capability · 2

Specifically, the thrust level shall be high enough such that maneuver burn times are negligible compared to the orbital period, allowing maneuvers to be modeled as instantaneous velocity changes (Δv) rather than finite-burn, low-thrust trajectories. 2.2.5.
RFI Specific Questions Responses to the RFI must include answers to the following technical and organizational questions (2.3.1 – 2.3.5) within their submission: 2.3.1.

Extracted from the notice text and attachments as published. The solicitation governs; read Sections L and M in full before you submit.