Capabilities · What ExistX knows
Four connected engineering disciplines: the things ExistX knows. How that knowledge is applied lives under How We Work; what it produces lives under What We Deliver. A discipline is neither a process nor a product.
Why four
Capability pages usually blur three different questions: what a firm knows, how it works, and what it delivers. ExistX keeps them separate, so a label is never mistaken for a process, and neither is mistaken for evidence.
What ExistX knows
The four bodies of engineering knowledge below. Each has one page that defines its scope and its boundaries.
How ExistX works
Engineering approaches that connect the disciplines: described under How We Work, never as a fifth discipline.
What ExistX delivers
High-Assurance Software-Enabled Mission Systems: described under What We Deliver, as a system outcome.
The disciplines
Scope lists define territory (what each discipline covers), not per-item performance claims.
Discipline 01
Connects algorithm and key-management decisions to implementation, assurance, agility, embedded constraints, and lifecycle transition.
Scope may include
Discipline 02
Integrates threat, architecture, software, components, evidence, and lifecycle decisions within a defined system boundary.
Scope may include
Discipline 03
Mission-software and lifecycle engineering: architecture, modernization, DevSecOps, automated testing, assurance, migration, and incremental delivery.
Scope may include
Discipline 04
Connects mission needs to architecture, embedded systems, interfaces, digital models, hardware-software integration, test, and lifecycle decisions.
Scope may include
Relationship model
Where disciplines combine, named relationships appear. The map is an orientation device: a named intersection is not automatically a current offering, and no overlap gets its own page without distinct intent and evidence.
Integrated capability model
Cryptographic, cybersecurity, software, and systems engineering are connected throughout the mission lifecycle. Their intersections form the specialized relationships shown in the map.
The combined outcome: High-Assurance Software-Enabled Mission Systems
Evidence
Each discipline page states its claims boundaries and links to Work, where evidence carries an explicit state: deployed, demonstrated, in active development, planned, or conceptual.
Next step
Start with the discipline closest to your technical need. Each page defines scope, methods, relationships, claims boundaries, and the evidence path.
Do not include classified, controlled, proprietary, export-controlled, or customer-sensitive information in any message sent through this site.