An operating journey for every role
Create the project and save its one-time tokens, load sources, review the graph, plan tests, execute with evidence, and make a controlled change decision.
01
1. Set up a project
Enter the system URL, environment, and required roles in onboarding.
- Save Owner, Widget, and Agent tokens immediately; token values cannot be recovered
- Use the owner token only in control
- Put the widget token in issue capture
- Put the agent token in the browser extension
- Keep ENABLE_PUBLIC_DEMO=false in production
02
2. Prepare the business source
Upload SRS/BRD material or inspect the embedded canonical graph.
- 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
Human review gates every build or release.
- Verify context, request/response, and attachment
- Link the issue to its story and route
- Choose rejected, approved/config, or approved/build
- Follow the build queue to fixed/published
- Inspect webhook delivery rather than assuming success