The documents your program office will ask for.
Capability statement for the contracting officer, product briefs for the technical evaluator, a case study for the skeptic, a teaming brief for the prime, and the doctrine paper for anyone deciding whether AI belongs near their mission. All PDF, all current, no forms to fill in.
Sixteen artifacts. One story.
Everything here matches what the website claims, same numbers, same boundaries, same refusals. Hand any of it to your reviewers without caveats.
The year the money arrived. The FY26 AI budget, MIT and Stanford evidence, the DoD AI strategy, six mission workflows, the 2026 toolbox, and five predictions we will score publicly.
Web page + PDF · 9 pages The Standard The Cleared FDE Standard, v1.0The public definition of a cleared forward-deployed AI engineer: five competency domains, one operating contract, and a measurable acceptance instrument. Free to reference with attribution.
PDF · 2 pages Capability statement Federal AI, Capability StatementCore competencies, differentiators, products, and registry data, HUBZone, CAGE 7UCA4, UEI MV3AMKSSPZR1, NAICS 541511, on one page.
PDF · 1 page Doctrine paper AI That Survives Contact with the MissionWhy AI programs die between interesting and operational, the boundary, authority, and data walls, and the forward-deployed doctrine that gets them across.
PDF · 4 pages Case study From Five Conflicting Systems to One Readiness PictureAn Air Force training organization reclaimed 12–15 analyst hours a week. What was delivered, under what constraints, and why it held up.
PDF · 1 page Product brief Optimize, Mission IntelligenceThe readiness intelligence layer: sense, understand, forecast, simulate, decide. Documented engagement outcomes and the 90-day proof standard.
PDF · 1 page Product brief Direct-To, Mission Readiness OSMission request in, verified outcome out. The operator contract, Mission Skills, and the $70K / 90-day Mission Workflow Sprint.
PDF · 1 page Product brief EnclaveDeck, Operator WorkspaceOne governed surface over live mission systems: the OPAEV trust loop, System Packs, and air-gap-native architecture. Private pilots.
PDF · 1 page Teaming brief For Primes & IntegratorsHUBZone credit, cleared FDEs, and deployable product IP for your next bid, plus the registry data your teaming database needs.
PDF · 1 page Delivery record The Federal AI Delivery RecordAn append-only public log of engagements and published artifacts: what was delivered, what was accepted, whether kill criteria fired. Receipts, not claims.
Web page · living document Engineering reference The Evidence Ledger, v1.0The append-only, hash-chained record behind every governed workflow: who asked, who approved, what changed. With a reference JSON Schema your validators can run today.
Web page + JSON Schema For contracting officers How to Buy Federal AIThe acquisition paths on one page: SBIR Phase III sole source for Optimize, HUBZone sole source under FAR 19.1306 up to $5.5M, simplified acquisition under the $350K threshold, and prime teaming, with draft market-research language.
Web page + 1-page PDF For primes and capture teams Teaming with Federal AIWhat a prime gets: cleared engineers and a cleared facility, current Air Force delivery, HUBZone credit, and SBIR Phase III authority for Optimize. Workshare-ready, data rights prepared, teaming request form.
Web page + teaming brief PDF Tool · for contracting officers and champions Acquisition Path FinderEight questions to the fastest legal path to award: SBIR Phase III, HUBZone sole source, simplified acquisition, or teaming, with the market-research paragraph your file needs and the questions your CO will ask.
Runs in your browser Tool · for AI Integration Leads AI Integration Lead 90-day plannerYour component, domain, boundary, and team in; a 30/60/90 plan out, with the six answers your program office will ask for, first-win candidates, and the acquisition path.
Runs in your browser Field checklist Air-Gap Delivery Checklist, v1.0The pre-flight list for software delivery into disconnected environments: offline packaging, transfer evidence, deterministic builds, and acceptance. Free to use with attribution.
PDF · 1 pageDocument boundary
Every document on this page is approved for public release and contains no CUI, no customer data, and no classified information. Engagement outcomes are reported by the customer organization and imply no government or U.S. Air Force endorsement. Named-unit verification is available only in an appropriate setting, with unit consent. Please do not send classified or CUI material to any address or form on this site.
Read something you want to pressure-test?
Thirty minutes with a technical lead, bring the document and the doubt. You leave with a candidate architecture and a clear go/no-go, not a follow-up deck.