What problem does it solve? Manual security testing often fixates on a single endpoint and misses bugs that live in the surrounding workflow, such as authorization gaps across user roles, object states, alternate transports, and adjacent objects. ## Core Features & Use Cases - Actor Tree Testing: Evaluates every object and action from unauthenticated, low-privilege, sibling, elevated, admin, and service contexts to find broken access control. - State and Transport Trees: Tests objects across lifecycle states (draft, pending, archived, deleted, restored) and across UI, REST, GraphQL, mobile, webhook, and import/export paths to find where policy enforcement is weaker. - Secondary-Object Pivoting: Extends testing to attachments, exports, previews, clones, audit logs, and AI/RAG features that often lack the primary object's protections. - Use Case: After mapping a bug bounty target's invite flow, use the decision trees to test the invite token across every role, state transition, and transport, then pivot to the exported member list and audit log for inconsistent authorization checks. ## Quick Start Apply the manual decision trees to the workflow I just mapped and enumerate the actor, state, transport, and secondary-object test cases I should run.
