overview Updated 2026-10-06
Overview
How the method, the component taxonomy, and the vault's storage model fit together.
Three layers, one model
Everything Nimbus Vault does is built on a single model, expressed in three layers:
- Methodology — how to think about a target: CAVET's Observe → Probe → Reason → Test workflow, the contextual-hacking mindset, and chain recognition as a way of seeing compound attacks.
- Components — the vocabulary: the five component types, their categories and tags, and the scopes that let observations nest inside their parents.
- Notespaces — storage: where observations live, what a link can carry (endpoints, instances, polarity, impact, versions), and how earned primitives extend an asset beyond what recon can find.
The Nexus Engine reads this model; playbooks are written against it. Learn the model once and every other page — mapping, prompts, suggestions, chains — is a view of the same structure.
Where to start
- New to the ideas? Read The CAVET Method first.
- Ready to work? Start with Map an Asset and come back when a field name stops making sense.