What a Releasable Configuration Requires for Section 842 Battery Compliance

Section 842 battery compliance is usually discussed as a status — a supplier has it or does not, evidenced by a certificate or a test report. Treating it that way hides where the difficulty actually sits. Compliance requires three separate records, held by three different parts of the acquisition system, that have to point at the same object. The records are individually well understood. The join is not.

Three records, one configuration

Qualification. The cell or pack meets the relevant military specification under the conditions and at the facility intended for production. A qualification result is bound to a specific product configuration, manufacturing process, and location. Change any of those and the qualification requires reexamination. This is a performance record tied to a controlled design revision.

Provenance. The materials and manufacturing steps trace to non-FEOC sources at the cost threshold Section 4865 sets — 95% of functional-component cost from non-covered-country origins, with no production technology licensed from a foreign entity of concern. Section 842 is the umbrella; 4865 supplies the cost test, and Section 154 separately bars named entities such as CATL. A provenance record says nothing about whether the cell works. It says where the cell came from.

Acceptance. The delivered item was inspected by an authorized government representative and matched against the contract's quality and quantity requirements before the government assumed ownership. This is a custody-transfer record. It confirms that what arrived matches what was ordered.

A battery is releasable when all three records exist and converge on the same controlled cell revision in the same accepted lot. At that point a contracting officer or program manager can verify that the item accepted is the configuration that was qualified, built from the supply chain that was provenanced.

Call the function that binds those records configuration-release authority: the responsibility for confirming, at the point of acceptance, that the qualified configuration and the provenanced supply chain are both present in the delivered item. In practice it means someone signs something stating that a specific cell part number and revision appears in the qualification file, in the provenance package, and on the receiving report.

Configuration-release authority is not a defined FAR or DFARS term. The component responsibilities are distributed across the qualifying activity, the contractor's quality system, the contracting officer, DCMA, and the acceptance representative. The job of confirming that all three records land on one identified cell is not assigned to any of them. It is a logical requirement of the mandate but not an institutional assignment.

The existing machinery and where its coverage ends

The acquisition system already has detailed procedures for tying an accepted item to a qualified configuration. FAR first-article procedures require a test report identified to the contract and lot, followed by contracting-officer approval before production proceeds. A change in design, material, manufacturing process, or production facility triggers a new first article — the principle this publication covered in issue #4 as the qualification clock.

MIL-PRF-32565, the performance specification for rechargeable 6T lithium-ion batteries, is the most complete application of that machinery to batteries. It requires qualification inspection and conformance inspection. It mandates that qualification samples come off the same equipment and procedures intended for production. Its identification requirements are extensive: military part number, manufacturer's part number, contract, lot, serial number, CAGE code, chemistry classification, manufacturing location. Its traceability guidance reaches design, fabrication, assembly, test, rework, screening, qualification, and conformance status.

Put on contract, those provisions produce a working join between a qualified product and an accepted production lot. They do not produce a Section 4865 provenance package. The specification predates the battery-origin mandates and contains no fields for functional-component cost allocation, material country of origin, or FEOC technology-license status. The qualification-to-acceptance machinery does what it was written to do and stops short of the provenance category.

That gap is a matter of drafting date. The qualification gap is more elementary: the machinery has no product in it. QPL-32565 Notice 1, dated January 2017, states that no products or sources have been established. As of 27 August 2026, the QPL record still lists no manufacturer, no product, no part number, no manufacturing location. The Army's Ground Vehicle Systems Center identifies a laboratory able to test to MIL-PRF-32565 but names no candidate product and no scheduled qualification decision.

Nine and a half years with an empty list is not a scheduling problem. For the standard military battery specification, the qualification evidence category has nothing in it, the provenance category has no home inside the specification at all, and the acceptance machinery, which functions, has nothing qualified or provenanced to receive.

Packet Digital: production-transition scope, no visible configuration baseline

Packet Digital holds two 2026 Navy SBIR Phase III orders under topic N07-160. The April action, valued at $27M, covers pilot prototypes, raw materials, pilot production, LRIP-1 and LRIP-2 lithium-ion pouch cells, cell manufacture and testing, integration into multiple pack designs, and pack testing and delivery through April 2028. The May action, $9.8M, covers equipment installation, raw materials, pilot and low-rate production, and testing through November 2027. The awarding organization is Naval Air Warfare Center Aircraft Division, Lakehurst.

The SBIR lineage traces cleanly. Topic N07-160 began with a 2008 Phase I and 2009 Phase II on power-management circuits for Marine communications-electronics equipment. Under SBA policy, Phase III designates work derived from prior SBIR effort using non-SBIR funds. The designation establishes derivation and funding status. It does not certify TRL, and it does not certify production readiness.

Packet Digital describes an 80,000-square-foot Fargo facility producing "100% American-Made Battery Cells," with electrode manufacturing, cell assembly, and cell finishing in house. A November 2025 MOU with LibertyStream Infrastructure Partners and Wellspring Hydro describes an intended lithium-carbonate supply pathway from North Dakota oilfield brine. The company identifies Lockheed Martin's Indago 4 UAS as a platform it has been contracted to supply.

Those are real artifacts: a traceable SBIR lineage, funded production-transition scope, a domestic cell-manufacturing facility claim, a named platform, a stated direction toward vertical integration in raw materials. None of them is a qualification, provenance, or acceptance record. What the public record does not contain:

• A controlled cell part number or revision under the Phase III orders
• A named cathode chemistry for that cell
• A military specification or qualifying activity
• A qualification or first-article approval
• Cell-level material-source documentation
• Section 4865 functional-component-cost evidence
• A receiving report linking an accepted production lot to both a qualified baseline and a provenance record

Phase III is by design the stage at which production processes are being stood up; qualification, provenance documentation, and formal acceptance are activities that occur during or after it. The absence of a joined record here is not a finding about Packet Digital's execution — it is narrower than that and worth stating exactly: the joined artifact is not in the public record, and the scopes of the 2026 orders do not reference one. Whether such records exist behind classification or proprietary barriers is not a question the public record can answer, and I am not going to guess.

DIBC: the evidence chain has not started

DIBC's RPP-BES-26-01, "Energy Storage and Batteries," closed on 17 July 2026, requesting a domestic 18650/21700 cylindrical-cell production line. As of 28 August 2026, the consortium's solicitation register labels it "Closed," a status it uses distinctly from "Awarded" and "Closed-Awaiting Award." The awards page carries no RPP-BES-26-01 entry. DoD announcements and defense trade press through the cutoff show no selected performer, no award value, no Phase 2 invitation.

This publication assessed the solicitation in issue #8, finding that its production threshold and sourcing requirements asked less than Section 4865 requires. That assessment stands. The point relevant here needs less analysis: with no announced performer, there is no performer-specific cell configuration, qualification plan, material-source submission, first-article lot, or acceptance artifact to examine. Evaluation or negotiation may well be running behind the posted status. The public record stops at "Closed."

DDP: an assessment mechanism without a published convergence point

The Drone Dominance Program's Supply Chain Framework Version 2, published 23 July 2026, is the closest thing in the field to a working battery-provenance compliance system. This publication first covered it in issue #10 as the first program-specific battery-component sourcing staircase.

The framework runs a phased progression. Phase 2 minimums require pack assembly outside covered countries, no packs from entities barred under Section 154, assembly by an Acquisition Security Database-compliant entity, and electronics sourced from original manufacturers or authorized distributors. Minimum requirements are disqualifying; preferred requirements feed competitive scoring. Non-covered-country cell compliance with Section 842 enters as a Phase 3 preferred criterion and hardens into a Phase 4 minimum. Phase 4 preferred targets U.S. production of pack, cell, BMS, and PCB.

Compliance runs on supplier self-certification evaluated by third-party assessors, through a process DCMA describes as resembling the Blue List: the vendor submits a checklist package through a portal, contracts with a recognized assessor, receives an assessment, and gets the report back through the portal. Previously evaluated systems require only change analysis.

That is more institutional machinery than either of the other two cases exposes. It creates component-origin gates, an assessment mechanism, and a change-analysis obligation. What the published framework does not enumerate is the supplier document package, the battery bill-of-material fields, the controlled cell identifiers, the required cost or source records, the assessor's test procedures, the evidence-retention rules, or the approval record by which an assessor's result becomes an authorized configuration disposition. DCMA's public account does not disclose the checklist fields or a battery-specific evidence schema.

Neither the framework nor the Gauntlet II request states that the cell covered by the provenance assessment must be identified by controlled part number and revision in the flight-test configuration, the qualification record, the production inspection record, and the receiving report. The provenance assessment and the platform-performance evaluation run as parallel tracks in the published documents, with no point at which they are required to meet. Meeting would mean one cell part number appearing in three places:

1. The assessor's provenance report, confirming non-FEOC sourcing for that cell revision
2. The Gauntlet flight-test record, confirming the platform flew with that cell revision
3. The acceptance artifact, confirming the delivered item contains that cell revision

DDP may be building this internally. The observation is about published artifacts: the framework describes how a supply chain gets assessed and does not describe who ties the assessed supply chain to a qualified, accepted cell revision.

What would have to exist

In issue #5, this publication laid out five publicly observable layers of compliance evidence and found none of them complete. The three-record framework here consolidates that finding and makes its implication explicit. MIL-PRF-32565 provides qualification machinery with no qualified product. Section 4865 creates provenance obligations with no home inside the qualification or acceptance process. FAR Part 46 and DFARS Appendix F provide acceptance procedures that do not automatically reach cell-level configuration or supply-chain origin.

Packet Digital is executing production-transition contracts, DDP is building a phased compliance architecture, and DIBC is soliciting domestic cell production. What remains unassigned is the function of confirming, at the moment of acceptance, that the qualified configuration and the provenanced supply chain are both represented in the delivered battery.

For a program office writing requirements now, the practical form of that assignment is not complicated: require a controlled cell part number and revision on the qualification approval, on the provenance package, and on the receiving report, and name in the contract who compares the three before acceptance. That requirement does not exist in any battery specification, framework, or solicitation examined here. Until it does, the individual records can all be in order and the configuration still will not be demonstrably releasable.