Run a Playbook
Open a suggestion, read it, execute, record — and what each outcome does.
Where suggestions live
Open an asset → Suggestions → Playbooks. You'll see ranked suggestion cards (sortable by Score or Name), with the checklist sections above them. Click a card to open the playbook in a read-only view — the body, requirements, and yields — with a back button to return. The card's menu opens the playbook's own notespace if you need to edit it.
Read it before you run it
Every suggestion shows its reasoning: which requirements matched, how specific the match is, and what the playbook yields if it succeeds. If a match looks wrong, fix the underlying data before testing — editing a link, correcting a polarity, adding the endpoint that was missing.
Execute
Do the work outside Nimbus Vault, within program rules. The vault is where knowledge lives, not where exploitation happens.
Record the outcome
Each suggestion card carries three actions:
| Action | Tooltip | What it does |
|---|---|---|
| ✓ | Mark playbook as successful | Grants the playbook's yields as primitives |
| ✗ | Mark playbook as failed | Retires the suggestion — the engine stops surfacing it |
| − | Mark playbook as not applicable | Retires it as irrelevant, without recording a failed test |
On success, yields are attached to the asset. If the playbook is set to grant all, that happens silently; if it's set to hunter-picks, you're prompted to select which earned primitives actually applied. Yields configured with "Prompt for endpoint when earned" also ask where the capability was discovered — record it when you can; it feeds co-location.
Whichever outcome you choose, the card moves into the asset's History under Playbooks.
After a success
- The earned capabilities appear in the asset's Primitives panel — read-only, the permanent record of what was achieved.
- Playbooks that require those primitives can now appear as new suggestions. That cascade is the vault working as intended (how chains form).
Retracting
Mistakes are correctable: open the asset's History → Playbooks and retract the outcome. A retracted success revokes the yields it granted, and anything that was standing on them is re-evaluated — downstream playbooks that lose a required primitive revert with a visible notice. The history trail stays intact.