Mission planning support
Agents assemble planning inputs from authorized systems, with every source access checked against clearance and recorded for the after-action review.
All industries
Industry guide / Defense & National Security
Classification, not efficiency, is the binding constraint
Classification-aware agent teams that run under policy, up to TS/SCI, with CAC/PIV identity and air-gap deployment.
Trunnion DAF / LiveExplore Trunnion DAF →
Why this work
needs its own approach.
In defense and national security the hard problem is not whether an agent can do the work, it is whether it can be permitted to.
Material carries classification levels and need-to-know restrictions, identity has to trace to a real credential rather than an application account, and an accreditation reviewer will ask how the system enforces both. Aggregation makes it harder: individually unremarkable facts can combine into something that warrants protection, and an agent that reads widely and summarizes is an efficient aggregator. Classification therefore has to be an enforced input to every access decision and has to propagate to anything derived from classified sources, not sit alongside the data as a label.
Where to look
for useful assistance.
Representative areas to evaluate with the product team - not a release-level feature guarantee.
Consider the workflow: an intelligence summary request
An illustrative discussion scenario. These steps describe the intended operating pattern, not a claim that every behavior is implemented in the current product release.
- 01
An analyst requests a summary across several holdings. The mission is composed from declared agent roles rather than assembled ad hoc, so the run is reproducible.
- 02
Each read is evaluated against the analyst's clearance and the classification of the source. Sources above the operating level are not silently omitted; the denial is recorded.
- 03
A retrieval agent and an analysis agent hold separate permission sets. The analysis agent can read the retrieved material and cannot reach the source systems directly.
- 04
The draft summary inherits the handling requirements of its highest-classification input rather than defaulting to the workflow's level.
- 05
Release outside the enclave is a consequential action, so it pauses at an approval gate for a named operator with the authority to make that call.
- 06
The release is designed to retain sources touched, policy decisions, supporting trace, approver, and release decision. Coverage, integrity checking, and replay are verified for the contracted release.
Bring the decisions
into focus.
Scope the workflow and evidence before relying on a product in your environment.
- 01
What mission and environment are in scope?
Start with a non-sensitive example from your operation. Identify the task, the systems and the people involved.
- 02
What release-specific evidence can be reviewed through an appropriate channel?
Ask to see the behavior in the exact release being proposed, including what happens when an input or dependency is unavailable.
- 03
What customer authorization and acquisition requirements apply?
Agree on what must be demonstrated, who accepts it and what remains outside the initial scope.
What to agree before the evaluation
A useful evaluation separates mission usefulness from authorization. The team should be able to identify what the workflow prepared, what a person decided, and which operating conditions still require assessment. Agree on that evidence before extending the use case or moving it into a more sensitive environment.
Questions about
Trunnion DAF.
Who owns DAF?
DAF intellectual property belongs to Trunnion AI. It is listed under Innovations, not as a vertical platform.
How do federal customers engage?
DAF is delivered to federal customers exclusively through Viceroy NM. Use the Viceroy NM link to begin that conversation.
Does this page establish certification or an authorization?
No. Availability is not a certification or authorization for a particular environment. Applicable evidence and approvals must be established for the intended use.
Trunnion DAF
Agentic software for mission work.
DAF - the Defense Agent Framework - is a live Trunnion AI innovation. Trunnion owns the technology; federal delivery is handled exclusively through Viceroy NM.
DAF is owned by Trunnion AI and delivered to federal customers exclusively through Viceroy NM.
Explore Trunnion DAFBring us the work that needs to move forward.
A specific workflow. A real operating constraint. An accountable next step.