FAQ
Quick answers to the questions that come up most.
Why doesn't a playbook I know applies show up as a suggestion?
Suggestions only exist when every required component is satisfied. The usual causes, in order:
- A missing required component — check the asset's checklist; partially satisfied playbooks appear there as prompts.
- A scoped requirement on the wrong parent — a scoped quirk or vector must be linked inside the exact parent the playbook requires (Scopes and Levels).
- Strict version matching — with engine mode set to Strict, technologies whose version is unverified never satisfy a versioned requirement (Requirements).
- Co-location without endpoints — if a requirement demands the same endpoint as a primitive, missing endpoint data means no match.
Why did a suggestion disappear?
Either you recorded an outcome for it — success, failed, or not applicable — which moves it to the asset's history, or the underlying data changed. Check the history first; if an outcome was wrong, retract it and the suggestion returns (Outcomes and History).
Why doesn't my scoped quirk match the playbook?
Scoped matching is strict about parentage. Prototype pollution scoped inside Node.js does not satisfy a requirement for the same quirk inside a different technology — even if the quirk name matches. Re-check where the requirement is anchored.
Is the Nexus Engine an AI? Can it find bugs for me?
No. It is a deterministic, rule-based expert system — the same data always produces the same suggestions, with no model guessing in between. It cannot find what you have not modeled: unencoded threats are invisible by definition. It makes the knowledge you do encode impossible to forget.
Failed or not applicable — what's the difference?
Failed means you tested it and it did not work on this asset. Not applicable means the playbook is genuinely irrelevant here — you are not recording a failed test. Both retire the suggestion, but they say different things in the history.
How do I undo a recorded outcome?
Retract it from the asset's history. Retracting a success revokes the yields it granted and cascades through anything that depended on them (Yields and Primitives).
Why can't I create another workspace?
Workspace ownership is limited by plan: Free accounts own one workspace, Pro accounts up to five. Cloning creates a new workspace, so it counts too.
How do AI agents access my workspace?
Through connections in Workspace Settings → Integrations — Pro feature, capped per member, scoped to the workspace, with capability toggles, expiry, revocation, and an audit trail.