Signal Layer
Agents monitor export-control, vendor, policy, supply, and program-dependency signals.
Events are normalized with source metadata, severity, confidence, and provenance before they reach an operator.
// 02 / Selected Path
Defense & Dual-Use.
ITAR
T1
REV
Intelligence Loop
Turn external change into accountable action.
For defense & dual-use, CMD acts as the command layer between the signal environment and the people who own the response. Agents watch the outside world, Convex keeps the operating model live, and every brief carries sources, confidence, routing, and provenance.
Exposure Map
CMD resolves each signal against programs, controlled parts, tiers.
The platform links change to dependency paths, commitments, timing, risk windows, and affected operating teams.
Agent Brief
The system explains what changed, what it affects, and why it matters.
Briefs carry sources, confidence, impact, recommended action, and the context needed for human review.
Owner Action
Work routes to program security, trade compliance, supply, and mission owners.
The loop is accountable: protect approvals, controlled-part movement, and mission commitments, with action status and audit trail preserved.
Live Objects
Programs, controlled parts, tiers
Watched Signals
Export controls, program dependencies, vendor approvals
Decision Owners
program security, trade compliance, supply, and mission owners
Outcome
protect approvals, controlled-part movement, and mission commitments
// Route Briefing
Send the operating surface. CMD builds the briefing loop.
A useful first brief needs the surface, source environment, operating objects, and owner path. From there, CMD can model how agents should watch, map, brief, route, and preserve decisions.