Procurement
Evaluate the baseline, then define the deployment evidence required for the environment.
ASODI deployment discussions are evidence-led and environment-specific; public engineering status is not customer operational acceptance.
Environment-specific acceptance
Production identity, network, persistence, source onboarding, monitoring, backup/restore, operator acceptance and security assessment requirements must be defined for each deployment.
No universal live-coverage claim
Producer connectivity and geographic or orbital coverage depend on authorised sources, provider agreements, deployment architecture and acceptance evidence.
Written due diligence
Procurement and partnership evaluation should use written scope, technical evidence, security boundaries and acceptance criteria before commercial or operational claims are made.
Boundary
Engineering information, not operational authority.
The current ASODI baseline is limited to read-only situational awareness, evidence inspection, replay and source-integrity presentation. It does not create command or actuation authority.
A software build or public product page does not establish operational certification, universal live coverage, independent security certification or regulatory approval.