AI program operations for complex defense programs
Make the whole program
Salient turns fragmented program records into coordinated work. Approved AI agents prepare source-linked Program Management Review (PMR) packages, trace cross-functional impacts, reconcile recovery plans, and drive commitments to closure—from one governed picture of the program.
Authoritative records stay in your systems · Consequential decisions stay with your people
What Wednesday feels like
The program moved overnight. You don't start from scratch.
Before the first meeting, Salient has organized the approved changes, started approved agents on the follow-up work, and surfaced the one decision that needs you.
Same program · same Wednesday · 07:42Illustrative program · synthetic data
AfterWith Salient
Program Read 18 · since yesterday
LiveMorning. Three things changed.
Two are already being worked. The team starts with a decision, not a scavenger hunt.
3 accepted changes2 agents working1 decision for you
Needs authorized disposition before work releaseAuthorize or redirect parallel recovery for Lots 04–06?
Customer-acceptance milestone M-7 · +2 days · $420K residual exposure
Three options · assumptions · sensitivities · source receipts attached- 01Test evidenceVibration qualification reopenedEffectivity agent · checking Revision C, Lots 04–06Working
- 02Supplier commitJ14 delivery moved 11 daysRecovery agent · comparing three schedule-and-cost recovery pathsWorking
- 03Contract obligationRecovery plan due FridayNeeds Program Manager + contracts discussion · customer release heldDiscuss
BeforeWithout Salient
The team starts with a scavenger hunt.
- Reach shared truthBefore · without Salient
Open five systems and ask four functions for separate answers.
- Prepare the decisionBefore · without Salient
Rebuild the PMR and wait for the afternoon war room.
- Drive follow-throughBefore · without Salient
Chase owners across meetings, email, decks, and trackers.
How Salient works
One operating layer. Many program workflows.
From the same source-linked context, agents prepare PMRs, trace impacts, compare recovery paths, and monitor closure—while leaders retain authority over consequential action.
Recovery run · TR-184 qualification reopened · Protect M-7Synthetic program · approved evidence
Step 1 of 4
A test finding reopens TR-184—the vibration qualification record—putting customer-acceptance milestone M-7 at risk. Salient checks approved records across configuration, schedule, cost, and customer obligations.
New accepted evidence · 14 May 09:42TR-184 · Vibration qualification reopenedFinding 07 · intermittent power loss
Automatic check complete38 commitments checked across 6 record domains
Inside the recovery run
See the source-linked trace behind that recovery run.
Follow the same TR-184 event as Salient checks affected records automatically, prepares the next action, and pauses at the human decision.
The Salient TraceSource-linked from changed evidence to open closure
Illustrative program · synthetic dataAutomatic checks across recordsStops for human approvalThen coordinates and monitors
01Changed evidence
Intermittent power loss on Mission Computer Revision C
Test repository · Finding 0702Records checked
J14 connector appears in 12 work-in-process units
Product lifecycle + enterprise systems$1.4M forecast exposure on the fixed-price lot
Enterprise system + cost ledgerForecast +18 days · customer recovery plan required
Schedule + contract registerNo form-fit-function or interface control document change
Baseline comparison complete03Human decision
Resequence unaffected integration to protect M-7.
Chief Engineer + Program Manager04Owned commitments
Approved revision in product lifecycle system
7 of 12 units complete
Schedule + cost forecast updated · acknowledgement pending
Awaiting final reworked unit
Program Read · recovery in progressM-7 recovery plan approved
4 records checked · 3 impacts · 1 clearedForecast exposure · $1.4M → $420K1 verified · 1 active · 1 awaiting · 1 blocked
Operating architecture
People and agents operate together. The program stays coherent.
Salient turns authoritative records into shared program context that people and agents use to do the work—then preserves approved outcomes as the starting point for what comes next.
How Salient fits / illustrative architecture
Records → Salient state → agent work → governed update
Systems remain authoritative
- P6Integrated schedule + progress logs
- CobraEarned value + cost forecast
- DOORSRequirements
- Enterprise / lifecycle systemsEnterprise resource planning (ERP) + product lifecycle management (PLM)
- PowerPoint / deliverablesContract Data Requirements Lists (CDRLs)
Connect in place or provide approved snapshots.
Match records. Preserve state.
TR-184Lot 04M-7CDRL A005
- Entities matched
- State preserved over time
- Every claim source-linked
- Complete audit trace
03 · Put agents to work
AI-agnosticSalient agents—or yours
- Impact agentTrace TR-184 across Lots 04–06Check PLM + ERP effectivity · cite unresolved gapsWorking
- Recovery agentCompare three M-7 recovery pathsForecast IMS + EAC deltas · surface assumptions3 options
- PMR agentAssemble PMR 07 from accepted deltasDraft risks + decisions + open commitments · PM releasesDraft ready
- Closure agentCheck DR-031 against current receiptsFlag late, blocked, or contradictory items for ownersMonitoring
Approval receipt attachedDR-031 · Program Manager + Chief Engineer
Approved outputs + execution evidenceResults update Salient state
Authority checkpoint Program Manager / Chief Engineer approval
Read + prepare by defaultHuman approval before consequential actionNo silent writeback
Built for defense programs
Programs too complex to fit in one person's head.
Every Program Read begins where the last one ended. Prior baselines, approved transitions, and unresolved work remain explicit—without replacing the systems that own the records.
Program memory / illustrative program
What changed since the last accepted Program Read?
Every current fact retains the prior state, authorizing decision, and source receipt.
| Program domain | B17 · Last accepted | DR-031 · Authorized change | B18 · Current |
|---|---|---|---|
| Engineering evidence | AcceptedTR-184 · Qualified | Human approvedRepeat vibration qualification authorized | OpenRepeat qualification requiredTest repository · Finding 07 · 14 May |
| Configuration + effectivity | AcceptedRevision C · Lots 04–06 | Human approvedECN-221 applied to affected units | 7 of 12Lot 04 rework · Lots 05–06 redesignPLM + ERP · ECN-221 · 12 Jun |
| Cost + schedule | AcceptedM-7 on plan · no exposure | Human approvedProtect M-7 through rework + second article | At riskRecovery active · $420K residual exposureIMS + EAC · DR-031 · 12 Jun |
| Customer obligation | AcceptedCustomer acceptance at M-7 | Human approvedIssue contractual recovery plan | Awaiting ackRecovery plan submittedContract register · CDRL receipt · 12 Jun |
- B17 · Last acceptedTR-184 · Qualified
- DR-031 · Human approvedRepeat vibration qualification authorized
- B18 · CurrentRepeat qualification requiredTest repository · Finding 07 · 14 May
- B17 · Last acceptedRevision C · Lots 04–06
- DR-031 · Human approvedECN-221 applied to affected units
- B18 · CurrentLot 04 rework · Lots 05–06 redesignPLM + ERP · ECN-221 · 12 Jun
- B17 · Last acceptedM-7 on plan · no exposure
- DR-031 · Human approvedProtect M-7 through rework + second article
- B18 · CurrentRecovery active · $420K residual exposureIMS + EAC · DR-031 · 12 Jun
- B17 · Last acceptedCustomer acceptance at M-7
- DR-031 · Human approvedIssue contractual recovery plan
- B18 · CurrentRecovery plan submittedContract register · CDRL receipt · 12 Jun
Defense design partners
Prove it on one program.
Evaluate one consequential decision cycle inside one approved data boundary—not a broad integration program.
Discuss a bounded evaluation ↗This website and email are not approved channels for classified, controlled unclassified information (CUI), International Traffic in Arms Regulations (ITAR)-controlled, proprietary, or other sensitive program information.