Defense (U.S.)
US
8 source references
4 mapped control areas
Sovereign region
About this template
Controlled technical data does not announce itself. It arrives inside a normal question about a part, a program or a schedule. Program teams reach for this starter when an assistant has to work near arms and export rules without becoming the leak. Everything here is a screening input for cleared people, never a determination.
Two named lists run before the model is called. The first refuses arms and export terms such as defense article, technical data, missile guidance and fire control radar. The second refuses restricted foreign counterparties, with fuzzy matching so a near spelling still trips. Identity must carry a user, an organization, a clearance level and a program, which is how need to know reaches the request path.
Classification and control markings are refused outright, along with phrases about target packages, strike windows and battle damage assessment. Redaction masks personnel security numbers, service identifiers, passports, badge numbers and mission contact rosters. Routing then restricts traffic to approved targets that operators mark as no retention and no training. A single read only search tool is allowed, every other tool is denied, and a session may take two actions.
The response side is unusually strict. Citation checks require sources and a source match, and an unverified or fabricated claim is blocked instead of flagged. The combined floor is 0.94, and faithfulness and accuracy each have to reach 0.96. A response under 400 characters or four sentences fails the same gate. A failure at any floor produces a refusal instead of a thinner answer.
Term rules also refuse prompts about disabling rules of engagement, bypassing positive identification or acting without commander approval. Generated code is screened for device control, bus interfacing and metadata endpoint access. Capture is redacted, includes blocked events, and stops the request when capture fails. The audit marker only shows an evaluated request, and records schedules remain a separate program.
Classification authority stays with the government customer. Export determinations, program access lists and hosting eligibility are decisions this starter cannot make for you. Compare the European defense starter when the obligation is dual use screening and alliance classification rather than domestic arms rules.
Source frameworks, standards and obligations
Control areas mapped by this template
Deployment options
Adapt the template in three steps
Review the scope
Confirm that the regions, source references, control areas and deployment options fit your use case.
Adapt the configuration
Open the template in the Verdictan console. Set its policies, thresholds, routing and review requirements for your environment.
Test before deployment
Test each policy outcome. Confirm that allowed, redacted, blocked and reviewed requests behave as expected.
Explore more Industry-Specific templates
Finance
Protect financial data, flag material nonpublic information, add supervisory notices and retain audit evidence with this starter.
Healthcare (U.S. — HIPAA)
Start with selected HIPAA controls for protected health information, minimum-necessary access, retention and clinical review.
Healthcare (EU — GDPR)
Map European health-data controls for GDPR Article 9 and EU AI Act risk management with this starter.