AFWERX CSO

The active government acquisition pathway for VERDICT WEIGHT pilots.

Why AFWERX CSO is the active pathway

The federal Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs are the historical default channel for early-stage dual-use technology engagement with the U.S. government. As of October 2025, SBIR/STTR authorization expired without a renewal. While the programs may eventually be reauthorized, they are not currently a viable pathway for new submissions.

The active pathway for AI capability pilots in the Air Force and Space Force domains is the AFWERX Commercial Solutions Opening (CSO). CSO is a streamlined contracting vehicle designed specifically for commercial technology that addresses identified DoD problems. It is the channel VERDICT WEIGHT is positioned for.

This page reflects the contracting landscape as of the project’s most recent review. The framework’s operational positioning does not depend on any specific funding vehicle; if the landscape shifts, the framework’s value proposition does not.

What AFWERX CSO offers

Feature	Description
Contract vehicle	Other Transaction Authority (OTA) and FAR-based procurement
Phase structure	Phase 1 (feasibility) → Phase 2 (prototype) → Phase 3 (transition)
Timeline	Faster than traditional FAR procurement; weeks-to-months rather than months-to-years
Eligibility	Commercial entities; small business status helps but is not always required
Use cases	Dual-use technology with identified DoD applicability

VERDICT WEIGHT fits the CSO use-case profile cleanly:

• Dual-use: applicable to defense, regulated industry, and critical infrastructure.
• Identified DoD applicability: confidence-gated autonomy is the deployment posture for nearly every AI program of record.
• Commercial readiness: the framework is published, tested, IP-protected, and validated; this is not a research proposal.
• Specific differentiation: Curveball detection (Stream 6) addresses a threat that is specifically relevant to autonomous military systems and that no other open framework currently composes with confidence scoring.

Mapping VERDICT WEIGHT to CSO problem statements

CSO solicitations are typically published against specific DoD-articulated problem areas. The framework maps cleanly to several recurring themes:

Trustworthy autonomy

Confidence layer with calibrated reliability and adversarial robustness.

AI assurance

Cryptographic provenance and tamper-evident audit for AI decisions.

Adversarial AI

Curveball-class attack detection composed with confidence scoring.

Mission AI integration

Auditable confidence for human-AI teaming in operational systems.

When a relevant CSO opens, the framework’s positioning materials map to the problem statement directly. The technical case is documented; the empirical case is published; the IP is protected. The work to respond to a specific CSO is composition rather than creation.

What VERDICT WEIGHT brings to a pilot

A defense pilot of VERDICT WEIGHT delivers, on a measurable cadence:

Pilot phase	Deliverables
Phase 1 (feasibility)	Integration with the program-of-record’s existing model stack; baseline calibration measurement; threat-model alignment document.
Phase 2 (prototype)	Calibration refit on mission-representative data; Curveball detection validated against mission-relevant adversarial corpus; audit-chain integration with existing logging infrastructure.
Phase 3 (transition)	Production deployment with operator runbooks; sustainment plan; training materials.

Each phase produces artifacts that survive the engagement: a refitted calibration map specific to the deployment, a tested adversarial corpus, an audit infrastructure integrated with the operator’s environment.

IP and ownership posture

The framework is published under a clear IP regime that simplifies acquisition-side review:

Asset	Status
Framework name and brand	USPTO Trademark #99747827
Framework method	USPTO Provisional Patent #64/032,606 (filed April 2026)
Source code	Published with appropriate license on GitHub (Odingard/verdict-weight)
Distribution	PyPI for ease of integration; Zenodo for immutable archival reference

This combination is straightforward for a contracting officer to evaluate. Ownership is unambiguous; the framework can be deployed under standard commercial terms; the open source distribution is for evaluation and integration, not for IP ambiguity.

How to engage

For pilot inquiries within an AFWERX CSO context or directly through a program office:

• Email: [e-mail]
• Subject line: indicate the CSO solicitation number or program of record.

A pilot conversation typically begins with a 30–60 minute technical alignment call to map the framework’s capabilities to the program’s specific threat model and integration constraints.

What VERDICT WEIGHT does not claim about CSO

The framework’s case to a contracting officer rests on technical merit, IP posture, and validation rigor. It does not rest on any of the following:

• A pre-existing relationship with any specific program office.
• Any claim of prior award status.
• Any claim of certification, accreditation, or assurance status that has not been independently granted.

These distinctions matter. Operators, contracting officers, and reviewers can evaluate the framework on the published evidence; the framework does not need to puff its credentials.