FY26 Release 3 — Topic Fit Scan & Submission Plan

Prepared: 2026-06-17 · Bill plan: docs/canonical/22_don_r3_pursuit_build_bill.md · Prove: GET /api/prove/pursuit-r3 · Synthesizer: npm run synthesizer:r3 DoN window: TPOC questions through 2026-06-23 · submit 2026-06-24 – 2026-07-22 noon EDT
AFWERX window: Pre-release now · submit opens 2026-06-24 · close 2026-07-22
Portals: navysbir.com · afwerx.com/sbir · DSIP topics-app

Operator decision (fill by 2026-06-20)

Doctrine: Submit every GREEN topic after DSIP scan — no arbitrary cap. Skip RED (hardware-only, TS/SCI, materials). See docs/canonical/10_operator_pursuit_stack.md for the full agreed queue.

Scan protocol (2026-06-24 morning)

1. Open DSIP → filter FY26 Release 3 (DoN BAA + AFWERX 26.BZ R3).
2. For each topic, score GREEN / AMBER / RED:
   • GREEN: live ATLAS module + prior draft exists → pursue
   • AMBER: strong fit, no draft → one-week sprint OK
   • RED: hardware-only, materials, medical, TS/SCI — discard
3. Run node scripts/sbir-pipeline.mjs <topic-id> for each GREEN topic.
4. Log choices in docs/pipeline/pipeline.json (DON-R3, AFWERX-BZ-R3 notes).

Expected theme buckets (from DoN pre-release intel)

AFWERX R3 — likely fit areas (verify at open)

TPOC question templates (send before 2026-06-23)

For Applied AI / ISRT-class topics:

ISS operates a production multimodal visual-tactical fusion platform with man-in-the-loop approval gates and tamper-evident audit (TRL 6–7). For Phase I, does the Government prefer (a) integration with an existing program-of-record COP, or (b) standalone feasibility on representative exercise data? Is classified data required for Phase I evaluation?

For contested logistics:

Our platform already tracks Class I–X, convoy circulation, and DDIL store-forward. Should Phase I emphasize (a) predictive shortage analytics, (b) in-transit visibility interop, or (c) sustainment WFF dashboarding for expeditionary HQ?

For runtime autonomy / COA:

ATLAS enforces NO_UNAUTHORIZED_ENGAGEMENTS and human release at execution boundaries. Does the topic require formal assurance-case artifacts (e.g., DO-178C-style) in Phase I, or operational demonstration with audit logs?

What we are NOT pursuing in Release 3

• Topics requiring TS/SCI or classified lab access ISS lacks
• Hardware-first sensors, materials, propulsion, directed-energy
• Blockchain-only plays (ARM ITV) unless topic explicitly matches hash-chain + logistics narrative
• Fourth+ submission while DISCORD and DIANA drafts are incomplete

After topic lock — agent workflow

1. Pull topic details from DSIP API / portal PDF.
2. Fork nearest DOCX from Release 1 (docs/SBIR_Draft_*).
3. Run readiness gate (target ≥78/100, 0 RED flags on Phase I deliverables).
4. Operator certify in DSIP → submit before 2026-07-22 12:00 EDT.

Release 4 (preview — Jul 22 – Aug 19)

Do not start Release 4 drafts until Release 3 is certified. Same scan protocol on 2026-07-22.