Audit & Accountability Evidence For Autonomous Systems
DoDD 3000.09 requires an official to account for what an autonomous system did. Sovereign Interlock is the independently verifiable witness on the command post computer.
Government login required.
Search title: Sovereign Interlock — Hardware Governor for Autonomous Agent Accountability
Pathway: Tradewinds Solutions Marketplace — post-competition, readily Awardable
Award: Residual Delta via the component's contracting activity. If no local KO, success@tradewindai.com can connect Acquisition Support. Tradewinds is not a party to the contract.
The first purchase is a fixed-fee period on one mission computer you provide.
Command Post
The Command Post Holds The Record
The chip on the command post computer signs the chain. The rule set is generated there. On the mission computer, what falls outside the set is refused. The card on that path carries the deny count for that generation in the same chain.
The Rule Set
The Command Post Permits A Rule Set
The Mission Computer Accepts ONLY Those Rules
That acceptance is the interlock's handshake. The same load applies to autonomous aircraft, surface vessels or ground vehicles.
- 01Sovereign Interlock sits under the mission application.
- 02The platform keeps its mission software.
- 03The chip is the TPM on that computer.
- 04If the chip cannot sign, the computer fails closed.
The Physical Stack
Where Sovereign Interlock Sits On The Mission Computer
One computer, five layers. The interlock sits between the chip and the kernel, under the mission software it records.
If L2 cannot sign, L3 fails closed. The mission computer stops sending
Why it is of value
DoDD 3000.09 requires an official to account for what an autonomous system did. The handshake is that official's record: the command post loaded the set, the mission computer enforced it, and the chip signed the result. The prime still builds the aircraft and still runs the mission. The program office holds a record the prime did not write.
Why it is immutable
The chip signs the chain on the mission computer. A missing line or an altered line is recorded on the chain. The check is made on the command post's machine. The prime cannot add a line after the event. Whoever later holds the aircraft cannot add one either.
When the aircraft is seized
The record of what the aircraft reached, and what it refused, is already signed.
The aircraft cannot remain a trusted node in the formation. A new path is refused on the aircraft, and that refusal is signed.
If a path back later exists, the signed record returns. The captured aircraft is then a sensor. The command post holds the chain.
The signed record cannot be changed. The aircraft cannot remain a trusted node.
Independent Evidence
Signed Record Verification
This is one record from that mission computer. The program office checks it on the command post's machine. A missing or altered line is visible. The prime cannot add a line after the event.
The chip signs the chain on the mission computer. The check is made on the command post's machine.
The requirement is already written
Five Eyes · NSA / CISA · 22 June 2025
AI compresses attack timelines to months, not years. Controls must perform under real incident pressure. A log written by the host under attack is not a control.
DODIG-2025-090
DoD has no completed zero-trust policy set for weapon systems or operational technology. Thunderdome covers office IT. This is the layer underneath.
DoDD 3000.09
Autonomy accountability is required. This is a hardware-signed record of what the mission computer was permitted to do, and what it was refused.
For the prime
You still build the uncrewed system and its mission software. The program office is not left with your log.
One proof. Their numbers
The command post holds the signed rule set, the refusal, and the next generation of those rules. These are the control numbers that ask for that proof.
CMMC Level 2 · NIST SP 800-171
- 3.1.1The mission application is held to the rule set.
- 3.13.1The card’s deny count for that generation is in the same chain.
- 3.4.3The next generation of the rules is the next signed record.
NIST SP 800-53 · FedRAMP asks for these
- AC-3The rule set is held on the host.
- AC-4What falls outside the set is refused on the wire.
- SC-7The card’s deny count sits in the signed chain.
- AU-2The refusal is recorded.
- AU-3The record names the act and the outcome.
- AU-9The record is signed and chained.
- AU-12The record is produced as the act happens.
- IA-3The mission computer is identified in the record.
- CM-3The next rules are the next signed generation.
ITSG-33
Canadian programs ask for this same proof under AC-3, AC-4, SC-7, AU-2, AU-3, AU-9, AU-12, IA-3, and CM-3.
EU AI Act
- Art. 12The record of what the mission computer did.
- Art. 14The human hand on the rules.
- Art. 15The cybersecurity of that boundary.
Give mission compute a boundary it cannot silently cross
Sovereign Interlock governs the mission computer. It does not fly the aircraft, replace command and control, or control a fleet.