What a SpaceWERX program office asks before moving to mission design.

These answers distinguish current targets and planned milestones from validated results. The linked investor and press materials provide the broader economic, readiness, and company context.

• What operational response time can a customer expect?

  Our current mission-design target is approximately 72 hours after deployment to establish the swarm formation in its assigned orbital band. That figure comes from the post-ejection formation scenario in the technical narrative; it is not a flight-proven customer response time, an end-to-end tasking window, or a contractual service-level agreement.

  Actual response will depend on target orbit, launch and rideshare conditions, mission authorization, and the required proximity-operations sequence. The investor brief provides the broader path from design validation to repeatable operations.

• What is the current mission-assurance testing status?

  The evidence-backed posture is pre-flight validation: high-fidelity orbital simulation for five-drone operations, a design package covering mass, power, and thermal budgets, and hardware-in-the-loop testing of the decentralized autonomy stack. That HIL work exercises GPS-denied relative navigation, communication latency, multi-drone coordination, and fail-safe dispersal behavior.

  This does not imply completed flight qualification or on-orbit validation. The readiness and economics brief describes the current validation stage and the follow-on hardware path; technical reviewers can request a direct briefing.

• What is the cost per debris kilogram?

  We do not publish a fixed price per kilogram yet. The current target is $2–5M per swarm deployment for approximately 3–5 objects, not a guaranteed per-kilogram rate. A mission-specific estimate will depend on target mass, orbit, object condition, rideshare or launch access, and the required capture and relocation profile.

  The investor comparison shows how the deployment target relates to the 1–10 kg debris lane while keeping mission economics explicitly directional.

• What is the IP ownership and access posture?

  The swarm consensus and coordination layer, v3.0 cold-gas chassis, propellant manifold, rendezvous sequence, and detailed engineering schematics remain proprietary to Orbital Reclaim LLC / Polsia Inc. Detailed technical material is shared through NDA-protected technical interchange at the appropriate partnership stage.

  The public boundary is deliberate: the physics models, including the Monte Carlo collision model and Kessler cascade stress test, are MIT-licensed and auditable. The company information page provides approved context; technical access can be discussed by direct inquiry.

• How does the partnership model work across the ecosystem?

  We see three complementary roles: program offices fund and evaluate mission outcomes; prime or integrator partners contribute mission integration, acquisition, and regulatory pathways; and commercial operators contribute target context, rideshare access, and operational demand. The roles are designed to support a government-backed demonstration without implying a signed partnership or current customer commitment.

  The intended ladder is Phase I → Phase II / Orbital Prime: simulation and design validation first, followed by flight-qualified hardware and an operational demonstration. See the investor brief for the partnership and deployment context, and the press page for approved company and partner references.

• What is the current TRL and readiness position?

  We are not assigning an unsupported numeric TRL or claiming flight heritage. The defensible position is pre-flight: the physics and mission behaviors are represented in simulation, the hardware design is in validation, and the autonomy stack is being exercised in hardware-in-the-loop testing. Flight qualification and an on-orbit demonstration remain future milestones.

  The readiness discussion lays out the evidence and the path to deployment; the public company materials should be used for approved external context.

• What is the ramp-to-operations plan?

  The planned sequence is Phase I simulation and design validation, then Phase II flight-qualified hardware, regulatory preparation, and operational demonstrations. If those milestones are met and the required funding and approvals are secured, the program can progress toward repeatable swarm deployments rather than a one-off technology demonstration.

  The deployment pathway captures the intended transition from validation to operations. It is a plan, not a claim that flight qualification, regulatory approvals, or repeatable customer deployments are complete; program-specific questions can be sent to orbitreclaim@polsia.app.