VULCAN · the estate diagnostic
Before the platform, the count. On a defense installation.
Readiness is an argument assembled from assets, people, training, parts, maintenance and facilities, each authoritative in a different system. The count establishes which system holds which fact before anyone asks the model to reconcile them.
The unit of account.
The eight gates contain no sector content. What changes between estates is the unit of account and the obligation attached to it, and the diagnostic establishes that first.
This estate
Defense installation
Unit of account
The facility and its control system
Carries
The readiness obligation
A design commitment about where obligation lands, not a deployment claim. No measured evidence from another estate transfers here.
The eight gates, run here.
The gates are the same on every estate. What they touch here is named below; what they return is listed at the end.
Dataset census
Asset records, personnel and training, maintenance, supply, schedules, budgets and compliance artifacts, enumerated across the staff sections that own them.
Authority registry
Each readiness fact scored to the system that is authoritative for it, with the reviewer and the basis recorded.
Boundary matrix
Classification and disconnected-operation tiers named explicitly. What may move between enclaves is listed, never assumed.
- 01
Dataset census
Every dataset enumerated with columns, row volume, owner and last refresh
- 02
Authority registry
Each dataset scored for authority; score, basis and reviewer recorded and reproducible
- 03
Duplicate resolution
Recut datasets identified, the survivor named, lossy recuts flagged
- 04
Identifier profile
Candidate keys profiled; collisions and drift documented, never corrected in silence
- 05
Crosswalk
An explicit bridge between the analytics key and the system-of-record identifier; exceptions quarantined, not merged
- 06
Boundary matrix
Every dataset assigned a tier; those barred from broad pipelines listed explicitly
- 07
Ingestion manifest
A deterministic include, defer or reject call per dataset, diffable between runs
- 08
Expectations suite
Automated expectations that fail the build, not a report read afterwards
The seam.
Business systems do not talk to equipment systems, and the question that matters on this estate needs both. The diagnostic maps both sides before anything is connected.
IT
Business systems
- Readiness
- Personnel
- Supply
- Maintenance
OT
Equipment systems
- FRCS: power
- HVAC
- Water
- Access control
The question that needs both
If facility control systems degrade, which missions stop generating?
What the count returns here.
- 01A definitive inventory of readiness datasets across the staff sections, with owners and refresh cadence
- 02The facility and its control system established as the unit of account, with the readiness obligation attached
- 03A boundary matrix that respects classification and disconnected conditions by design
- 04An ingestion manifest that can run where the mission runs
The gates do not change because the estate carries a mission. The unit of account does.
The full method
The method, and the one measured engagement.
The VULCAN page carries the full argument: the eight gates, the platform path, the scorecard, and the single engagement where the diagnostic has been run and measured at full scale.
Read the full methodThe operating world
Defense & Readiness
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Defense & Readiness