Evals for Defense Unicorns

Bundle-once portability

Explaining or guiding a single bundle targeting multiple environments, from secure cloud to tactical edge, without per-environment rebuilds.

UDS CLI task guidance

Correct, tier-agnostic guidance for CLI-driven package and deploy steps, which the pricing page lists in every tier including free Base.

Deploy-time preconditions

Surfacing what must be present before a deploy (bundle, target cluster, registry availability) rather than assuming a connected default.

Environment targeting

Distinguishing cloud, on-prem, and edge targets and adjusting instructions to the stated destination.

Offline-first defaults

Never prescribing steps that silently require Internet access, external registries, or license phone-home when the user states an airgapped context.

Media transfer across the gap

Handling the move of artifacts from a connected side to a disconnected side as an explicit, described step.

Degraded-link behavior

Reasonable guidance when connectivity is intermittent or bandwidth-limited rather than fully absent.

Disconnected failure recovery

Recovering a partial or failed deploy without assuming the operator can pull anything new from outside the enclave.

SBOM and CVE scan output

Explaining what the scans cover and where results fit in the workflow, without overstating findings as an authorization decision.

ATO artifact package

Correctly naming the artifacts described (SCTM, SBOM, system architecture diagrams) and their role in accelerating ATO timelines.

Hardened and FIPS image claims

Stating hardened near-zero-CVE and FIPS-validated images as paid-tier features for the core runtime, and not as free Base capabilities.

Control-framework framing

Referencing NIST SP 800-53 alignment as a starting baseline rather than asserting a granted ATO.

Feature-to-tier mapping

Accurately placing each listed feature in Base, Fleet, and/or Enterprise per the published comparison table.

Fleet-only capabilities

Correctly isolating features the table marks for Fleet alone, such as UDS Connect (Android), UDS System Image, and Resilient Data Mesh.

Enterprise-only capabilities

Correctly isolating Enterprise-only entries such as UDS Registry, Compliance Assessment Tool, and Infrastructure-as-Code modules.

Open-source obligations

Representing the AGPLv3 nature of the free Base tier without inventing permissions or restrictions.

Centralized fleet visibility

Describing UDS Command's fleet-wide observability and management scope over distributed UDS systems.

One-to-one edge access

Describing UDS Connect as browser-based single-system management for tablet and desktop, with Android as a Fleet-tier extension.

Real-time threat monitoring

Framing the Manage stage as ongoing observability to stay ahead of threats, without promising specific detections.

Support escalation path

Routing incidents to the stated General Support offering, including its 24/7 response commitment for critical issues.

Order Form mechanics

Explaining that fees follow quantities purchased rather than actual usage, per the published terms.

Cancellation and refund posture

Accurately stating that orders are non-cancelable, fees are non-refundable, and quantities cannot be decreased mid-term.

Agreement versioning

Citing the correct effective-date version and acknowledging that a prior version exists.

Qualified handoff

Directing pricing-specific and contract-specific questions to the sales contact path instead of quoting invented figures.