FY27 starts with a harder question: can you prove what you intend to build?

Coverage: September 25–October 1, 2026 (America/New_York)

October 1 starts the U.S. federal fiscal year 2027. It does not turn a budget request into an award. The FY27 defense budget materials set out proposed priorities, while a signed continuing resolution funds continuing federal activities through December 11, 2026. For teams planning products, the immediate work is concrete: turn a mission need into a configuration, a credible cost and manufacturing plan, and evidence that survives the next design change. FY27 budget materials · Continuing resolution

Inside DDNA — recently merged capabilities#

From sources to decisions#

DDNA's newest merged work gives teams a Google Drive source connection and a Sources workspace with folders, search, sorting, previews, and in-browser file viewing. Source changes can be held for a deliberate Update Intent now decision after the first Intent package exists. Guided questions use plainer language and surface the details needed to answer them. People can propose changes to the same Intent document while review is underway, withdraw their own pending suggestions, and see when one change depends on another. Project access groups let teams grant access by company or role while retaining individual assignments. People connecting through MCP can choose the permissions they grant on the consent page.

Enlarge

Synthetic DDNA demo: source intake presents file and connected-source options. No customer content or imported file is shown.

Requirements that inherit the whole Intent#

Requirement generation now processes approved Intent documents by section rather than relying on a clipped combined text. Independent generation work can run in parallel, and generated requirements are published into the active working configuration before the run reports success. Review and approval remain human decisions. The Requirements workbench and project insights also make status and open questions easier to see. These are recent code and workflow changes; availability for a given workspace should be confirmed during the release rollout.

A system record you can work from#

The System map adds routed interface lines, saved layouts, direct node placement and movement, and an exportable block diagram with an interface schedule. Engineers can edit typed interfaces and inspect release gates in the same system context. A durable model review service records revision-pinned findings and gate evaluations; its release gate is advisory by default. A node can become a subsystem project with its own requirements, tasks, and team while inheriting the system's Intent. Systems and boards can link code repositories that DDNA reads without writing into them; a release records the observed code commits, and parent projects can see subsystem requirement and task progress.

Enlarge

Synthetic DDNA demo: the System map shows two typed parts under one system, with a cabled data interface between them.

Enlarge

The same synthetic working configuration exported as a preliminary Block diagram. Its interface schedule names the data link and its title block shows that no revision has been approved or released.

For products with variants, shared record edits can reach every configuration that uses the record. Teams can place alternative parts in a slot, add an existing part, and release configurations together. A part answers a system requirement once where the obligation is shared, including from the part's Formalize view. The configuration is the arrangement of parts; its version is the released revision of that arrangement.

Work the task and the thread#

DDNA's Tasks workspace reads and edits native project tasks, gates, evidence, and POA&M work in the underlying repository. Engineers can see assignments across projects, create a task from an engineering issue, set start and due dates, move a plan, and drag timeline bars. Project Chat can traverse connected Market Intelligence evidence, project facts, Intent sections, and requirements, keep citations, and place document edits into the review flow. Reviewers can step through changed documents and accept or reject suggestions. Ask DDNA and Project Chat open at the latest message; the merged sign-in flow is email first and adds Windows Hello passkey support. The site release line also adds dedicated privacy and terms pages.

Enlarge

Current DDNA sign-in screen: the email path asks for the invited work address before continuing.

Faster graph crawl and digital-thread reads#

• Indexed starting points. Project memory resolves the record that owns an ID before following its links, keeping a neighborhood read scoped to the relevant records.
• Smaller walks. Traversal returns the fields a reader needs instead of repeating full document bodies on every edge. Project-memory reads likewise return compact, ordered neighborhoods.
• Faster first read. The neighborhood reader plans small matching branches separately, so a new graph session can begin exploring the digital thread without planning one large traversal.
• Less contention during updates. Engineering records index concise readable text, and unchanged property writes can avoid extra graph storage work. This part needs rollout and an update of existing graph records before its benefit is broadly available.

Internal component benchmarks show substantial gains for whole-document walks and project-memory reads. Combined end-to-end Project Chat response time has not yet been measured for this release.

In development: Intent and Needs Register#

An open change set adds an Intent Register with a ConOps view and a Needs Register before Requirements. The proposed workflow links a need to its sources and revision, takes stakeholder sign-off on a combined set, and presents later requirement generation as reviewed changes with visible impact on verification. It is under review with rollout switches off by default. We will call it available only after the release and activation are verified.

FY27 engineering radar#

Funding is a planning boundary, not a product requirement. The FY27 defense budget request contains proposed investment in autonomous systems, science and technology, and the industrial base. The continuing resolution provides near-term funding for continuing activities. Teams should map each opportunity to the actual solicitation, funding instrument, and technical acceptance criteria rather than treating a budget headline as a funded contract. That mapping is where product Intent starts.

A new ISR challenge asks for demonstrated systems and production paths. On September 29, DIU released its Low Cost ISR challenge. It asks respondents to separate demonstrated from developmental capability and describe payload interfaces, size, weight and power limits, reliability, expeditionary operations, lifecycle cost, and manufacturing readiness. The stated submission deadline is October 14; planned fly-offs later in FY27 are tentative. For an engineering team, one architecture claim now crosses air vehicle, sensor, communications, sustainment, and production evidence. DDNA is not affiliated with this challenge; the solicitation illustrates why a single controlled product record matters.

Oversight needs a baseline that can evolve. A September 25 GAO review of naval shipyard infrastructure estimates that the effort will exceed $200 billion and take more than 50 years. GAO found that the oversight framework lacks defined reviews to revisit objectives and resources as needs change. The general engineering lesson is immediate: long programs need explicit decision points that connect mission purpose, approved requirements, cost, schedule, and the current physical configuration.

Open topics still need outcome evidence. A September 29 GAO review of SBIR and STTR awards found incomplete commercialization reporting and questioned the reliability of the available outcome data. An open topic gives a company room to define the problem; it also raises the burden of showing the path from a stated need to a measurable result. That makes the intent, assumptions, verification plan, and adoption evidence part of the proposal from the start.

What to watch in FY27#

Requirements as a chain of decisions. The DIU ISR challenge explicitly distinguishes current and developmental capability. A useful requirement should preserve that distinction, its mission source, owner, acceptance method, and applicable configuration. Watch for solicitations that ask for evidence at submission, then for evaluation decisions that connect the offered architecture to actual fly-off results. A polished requirement list without source and verification links will not answer that question.

Manufacturing readiness as a design constraint. DIU asks for the ability and risks of producing beyond a prototype, while the FY27 budget materials make industrial capacity a proposed priority. A sensor change can alter power, cooling, airframe mass, supplier lead times, test fixtures, and unit cost. Watch for production-representative demonstrations, interface packages that another supplier can actually use, and cost claims that include sustainment. A fly-off result alone does not establish an affordable production system.

Budget reviews backed by engineering state. GAO's defense research review describes the planning, programming, budgeting, and execution path from strategic priorities and requirements into proposed technology investments. GAO's shipyard review shows why objectives and resources must be revisited over time. Watch for program reviews that can show what changed in the need, which requirement or interface moved, what evidence remains valid, and what new funding or test work follows. That is the DDNA thesis in budget language: one coherent program state from intent through release.

If your FY27 plan depends on a product claim you cannot yet trace to a test, configuration, and manufacturing path, that is the right place to start the conversation.