Solo Hunter

The sequence below is a starting path — follow it once end to end and you will have used every part of the core loop.

1. Create your workspace

Sign in and create a workspace. It is the container for everything: assets, components, playbooks, notespaces. If you're working alone, one workspace is all you need.

Details: Account and Workspaces.

2. Seed the starter library

Open the dashboard and use the Starter Library card. This gives you a working set of technologies, functionalities, gadgets, vectors, quirks, and playbooks — so the engine has something to match with.

Details: The Starter Library.

3. Add your first scope

Create a platform (where the work comes from), a program (the scope of testing), and one asset (the concrete thing you are testing).

Details: Workspace and Manage Your Scope.

4. Map the asset

Open the asset's Components panel and link what you actually observe — the stack, the features, a behavior you noticed. Record endpoints when you know them, and scope vectors and quirks inside the component they belong to.

Details: Map an Asset.

5. Work the checklist

Open the asset's Suggestions → Checklists panel. The proactive side asks what is missing; resolve prompts with evidence — link what exists, and only answer "no" after checking the full surface. The reactive side lists the objectives your components brought with them.

Details: Work a Prompt, Proactive Checklist, Reactive Checklist.

6. Run a playbook

Back in Suggestions → Playbooks, open the top-ranked suggestion, execute it against the target, and record the outcome — success, failure, or not applicable. A success earns the playbook's yields as primitives, which can unlock the next playbook in a chain.

Details: Run a Playbook, Yields and Primitives.

7. Grow the vault

Every engagement adds to the library. When you observe something new, record it as a component; when you learn an escalation, write it as a playbook. The Authoring Guide is the reference for making playbooks that actually fire.