Mission intelligence / resource operations
IF is the mission intelligence system being built for teams coordinating spacecraft, robots, payloads, software agents, and human approvals. Turn fragmented evidence into a defensible decision—and a replayable path to execution.
The product
IF connects the question a program must answer to the sources, policies, entities, commands, and review gates behind it. The first domain is asteroid-resource prospecting; the architecture is built for any high-consequence multi-entity operation.
Rank candidates across independent evidence axes, expose uncertainty, and show how the recommendation moves when assumptions change.
Express spacecraft, robots, payloads, agents, and people as one typed mission graph without collapsing authority, health, connectivity, or lifecycle state.
Preserve accepted and rejected alternatives in a replayable record that can survive engineering, program, safety, and investment review.
The workflow
Each layer is useful on its own. Together they create a product that can move from an uncertain target decision toward supervised operations without losing the logic that justified the move.
Compare candidates without hiding distinct evidence behind one unexplained score. Trace the source of every axis and make uncertainty part of the recommendation.
IF keeps mission lifecycle, entity condition, communications, resources, and approval authority as independent state axes. Invalid transitions do not become runtime surprises.
Review the exact sources, model or baseline, policy, candidate commands, constraint decisions, and state changes that produced an outcome.
First domain / extensible core
We start where evidence is sparse, decisions are consequential, and coordination crosses software and physical systems. The same product architecture can expand only after the first decision workflow earns trust.
The path to product
The roadmap moves through independent scientific, product, safety, integration, and qualification gates. A polished interface never advances a capability by itself.
Typed orchestration, planning, safety validation, distributed execution, mission control, and replay.
Public core / nowTarget-score definitions, versioned source ingestion, scientific review, uncertainty, and data quality.
Prospecting intelligence / nextReviewed ranking product, higher-fidelity adapter, controlled data enclave, and HIL evidence.
Fidelity + integration / futureIndependent review, repeatable mission runs, a hosted-payload path, and a bounded release candidate.
Qualification / futureEvidence boundary
The website shows what IF is meant to become. This is what exists today—and what still has to be earned before the system can move closer to a real mission.
Implemented and exercised in the IF research system.
Planned gates; none are implied by the interface concept.
Legal state transitions, authority, and capability are explicit before a planner may propose action.
Learned ranking never grants itself authority. A separate boundary approves or rejects transitions.
Sources, policies, commands, and outcomes must be reconstructable instead of accepted on confidence alone.
Shape the system
IF is being shaped for teams that need to connect uncertain evidence, autonomous entities, and human authority in one mission system.
Talk about IF