Map an Asset
Turn a target into a structured component inventory — click by click.
Mapping is the highest-leverage habit in Nimbus Vault. Everything the engine can ever tell you is bounded by what you record. This page is the operational loop; Scopes and Levels explains the model behind it.
Where mapping happens
Open the asset (via its program, or Programs → Assets), and switch the right-hand sidebar to the Components panel. That panel is the inventory: one section per component type, each holding the things you have observed.
The linking flow
Start a link
Pick components
Fill in what you know
- **Endpoints (Optional)** — the concrete paths where you observed it. Type a path, press **Add endpoint**; a leading `/` is added for you, duplicates are ignored. Each endpoint becomes its own instance.
- **Version (Optional)** — technologies only, e.g. `18.2.0`.
- **State Polarity** — stateful quirks only: `Present` or `Absent`.
- **CLQs / CLGs / CLVs (Optional)** — attach scoped children right here (`Add a CLQ...`), including nested `CLVVs` and `CLVQs`.
Link
Scope it correctly
The level you link at changes what the engine can do with it:
- Direct on the asset — for observations that belong to the whole target.
- Scoped inside a parent — a vector inside the file upload that produces it, a quirk inside the technology where you saw the behavior. Scoped requirements demand the exact parent (why).
- Nested deeper — vector inside vector, quirk on a vector: each scoped level has its own link modal (
Link CLQs,Link CLVs, ...) with an Assign to choice: Global — or a specific endpoint, tying the child to one instance.
Technology defaults
If a technology carries defaults — common quirks, vectors, or gadgets defined in its notespace — they surface when you link it, governed by the default's Inheritance Level (Asset or Component) and Inheritance Mode (Auto or Manual). Confirm what applies instead of retyping the stack's usual suspects.
Habits that pay
- Technologies and functionalities first. They define the possibility space; vectors, quirks, and gadgets get linked onto the things that produce them.
- Endpoints are half the value. A capability without an endpoint can still match — but co-location requirements, the ones that keep chains honest, need them.
- One sitting beats five. The value is in completeness; a half-mapped asset yields half-trustworthy suggestions.
- Not sure of the exact value? Link what you can confirm now; resolve the specifics when a prompt asks.
If a submit stays disabled, the rail shows why — State polarity required, CLVQ targets a vector that is not linked, and similar messages name the missing field.
What's next
The engine now has something to work with: work the prompts it generates.