An operating journey for every role
Sign in once, choose a project, load sources, review scope, design tests, execute with evidence, and make a controlled release decision.
01
1. Create or join a project
Use your named account; a target URL is optional until execution.
- Create an empty project or accept an email-bound invitation
- Invite collaborators with the least role they need
- Transfer ownership before an owner leaves
- Issue Widget or Agent service keys only for integrations
- Keep ENABLE_PUBLIC_DEMO=false in production
02
2. Prepare the business source
Upload a BRD or SRS into the selected project; no business catalog is injected automatically.
- Confirm source name, version, and fingerprint
- Review department → module → workflow → story
- Treat unmapped items as business decisions
- Add route/API/source-of-truth only from confirmed evidence
- Review history and impact before publishing edits
03
3. Plan and execute
Turn approved scope into repeatable tests.
- Choose page, module, or full-system scope
- Select environment, role, and data profile
- Create a command for the agent to claim
- Record steps, outcome, duration, and evidence
- Never count an evidence-free result as a real pass
04
4. Review an issue
Named-member transitions gate every fix and evidence-backed closure.
- Open → Approved for Fix or Rejected with rationale
- Record the fixed build and delivery reference before Awaiting Retest
- Retest with a verified run linked to the defect or designed-case lineage
- Closed requires a fully passing retest on that exact build
- Inspect webhook delivery rather than assuming success