Compatible
Client features and mission constraints are aligned with the reference inspection and approach assumptions.
- Cooperative cues observable
- Approach corridor defined
- Inspection geometry available
Standards posture
Interoperability should be designed, traced, and verified.
Antandros is built around a standards-aware thesis: commercial servicing can scale only when client spacecraft and servicer spacecraft converge around repeatable interfaces, approach assumptions, and verification evidence.
Standards traceability
Not a universal-compatibility claim.
Antandros does not claim that every spacecraft can be inspected, approached, docked with, or serviced through one interface. The standards traceability and universality assessment is intended to identify where compatibility is feasible, where interface-control definitions are needed, and where adapters or future standards work may be required.
The framework maps the proposed servicer architecture and reference readiness-package interface against applicable or emerging best practices for rendezvous and proximity operations, cooperative servicing, inspection, and safe client-servicer interaction.
Compatibility framework
A clear way to classify service readiness.
Adaptable
Client needs an interface definition, mission-specific data package, or adapter concept before inspection or servicing.
- Partial cue compatibility
- Mission-specific limits
- Adapter or documentation needed
Constrained
Client geometry, operations, or safety assumptions do not support the current reference approach without major changes.
- No safe hold-point geometry
- Insufficient target knowledge
- Unacceptable risk posture
Traceability outputs
What gets documented before a mission matures.
01
Interface assumptions
Reference features, cooperative markers, inspection planes, standoff distances, and keep-out constraints.
02
RPO behavior
Approach profile, hold points, abort logic, relative-navigation assumptions, and operational margins.
03
Inspection products
Required views, sensor assumptions, data products, confidence limits, and review responsibilities.
04
Risk controls
Client safety constraints, assumption logs, configuration control, fault responses, and retreat conditions.
05
Adapter needs
Interface-control gaps, mission-specific hardware needs, documentation gaps, and future standardization opportunities.
06
Verification evidence
Requirements mapping, simulated sequence results, test coverage, and readiness classification.
Commercial logic
Standardization reduces bespoke mission burden.
Every custom spacecraft interface can add custom approach procedures, custom robotic tools, custom risk analysis, and custom economics. Antandros aims to make inspection and eventual servicing more repeatable by defining the cooperative client assumptions and servicer-side behaviors together.
The near-term goal is not to force one universal hardware standard. It is to create a disciplined path for assessing readiness, identifying gaps, and maturing customers toward service-ready spacecraft design.
Design for readiness
Start with inspectability, then mature toward serviceability.
Antandros can help frame cooperative cues, interface assumptions, and standards traceability for future servicing concepts.