Start with the mission
Scope the task and the people accountable for its outcome before selecting a workflow.

DAF - the Defense Agent Framework - is a live Trunnion AI innovation. Trunnion owns the technology; federal delivery is handled exclusively through Viceroy NM.
See the work in context
An illustrative workspace for defense & federal mission teams. Explore the work and the decision behind it.
A non-sensitive mission scenario needs a defined environment, authority and evaluation boundary.
Confirm customer authorization and the proposed operating conditions.
Review the material behind the proposed action.
Confirm scope, permissions and consequences.
Approve, revise or decline through the defined workflow.
Mission work needs software that can be evaluated against its actual environment, authority and information boundary. A public description is a starting point for that conversation, not evidence of authorization to operate.
Built by Trunnion AI, a wholly owned Duskbridge company. DAF is delivered to federal customers exclusively through Viceroy NM.

Scope the task and the people accountable for its outcome before selecting a workflow.
Establish the information, identity and deployment requirements that apply to the intended use.
Review the execution, human approval and evidence behavior for the exact proposed release.
An illustrative sequence, not a product screenshot or a guarantee of released behavior.
Begin the federal mission and acquisition conversation through the route-to-market partner.
Agree on the use case and environment through appropriate channels.
Review the applicable product and control evidence.
Proceed only within the customer's approval and operating conditions.
Start with the workflow you need to improve. Then confirm what the proposed release can actually do.
DAF intellectual property belongs to Trunnion AI. It is listed under Innovations, not as a vertical platform.
DAF is delivered to federal customers exclusively through Viceroy NM. Use the Viceroy NM link to begin that conversation.
No. Availability is not a certification or authorization for a particular environment. Applicable evidence and approvals must be established for the intended use.
Portfolio relationships do not establish an included integration or entitlement.
Start with a non-sensitive overview. Product fit, release scope and next steps belong in a direct conversation.