Operator checklist and troubleshooting
Use this page as a quick reference when you prepare a demo or run a release analysis end to end. The checklist covers the setup that prevents most problems, and the table below maps common symptoms to their likely cause and the fastest fix.
Operator checklist
- Confirm source repository access before the demo.
- Use a known branch and commit for repeatable evidence.
- Set the GitHub token for private repositories, and never expose a real token while recording.
- Save the session before running long workflows.
- Run upstream cards before the cards that depend on them.
- Confirm the IR Card and Component Card contain outputs before launching visualizations or test generation.
- Use the export buttons as evidence handoff points: JSON, verification result, components, endpoints, and the test-suite ZIP.
- Before test execution, confirm the target URL, admin token, and user token.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Card waits for input | Upstream card has not run or is not connected | Run the upstream card and confirm the connector line. |
| Generate IR does not run | System Source is incomplete | Confirm repository URL, branch, and commit. |
| Visualization is empty | IR Card did not receive data | Re-run Generate IR and IR Card. |
| Policy Drift is waiting | Both verification branches have not finished | Run both Formal Verification cards. |
| Too many scenarios | Scenario Generation is not constrained | Connect Formal Verification or Change Impact. |
| LLM Prompter says no scenarios selected | No scenario rows are selected | Select visible scenarios or select all. |
| Test Executor cannot run | Target URL or tokens are missing | Add the target URL, admin token, and user token. |
Summary
AridNova gives engineering organizations a repeatable way to understand microservice architecture, verify authorization policy, detect drift, and generate focused tests — moving teams from manual inspection to evidence-driven release confidence.