Platform Operator Guide
This is the current operating model for PhantomYerra: how assessments move from launch to active execution, into completed history, through findings review, and finally into reports and exports.
Active Projects
Assessments stay here while the dashboard is still live and the backend status is not terminal.
Completed
Terminal assessments move here once execution is finished or intentionally stopped and the final state is written.
Findings
Review confirmed or review-ready evidence. Use filters, exports, and report launch paths from the scan context.
Reports
Generate PDF, DOCX, HTML, CSV, XLSX, or SARIF outputs only from reportable completed assessments.
Lifecycle truth
| State | What it means in PhantomYerra |
|---|---|
| Draft / setup | The wizard is still collecting scope, connectors, target details, and module-specific options. Nothing is scanning yet. |
| Active | The scan dashboard is live, events are still arriving, and the assessment remains listed under Active Projects. |
| Completed | Execution is terminal. The assessment moves to Completed and stays reopenable, findings-aware, and reportable. |
| Stopped | An operator or guardrail ended execution intentionally. Findings gathered so far remain preserved and reportable if the scan is terminal. |
| Failed | The assessment hit a runtime or dependency error. Evidence up to the failure is retained, but you should review the error path before reporting. |
Daily operator flow
-
1
Create and launch
Choose the surface, complete only the relevant wizard steps, validate connector reachability if the module requires it, and launch from the review screen.
-
2
Watch the active dashboard
Use the scan dashboard as the source of truth while the assessment is running. Active Projects should contain the assessment during this period.
-
3
Reopen after completion
Once terminal, the assessment should move to Completed. Reopening from Completed should preserve the same scan context, findings counts, and reportability.
-
4
Review findings and exports
Use the Findings page to inspect the preserved scan profile, export deduplicated CSV/XLSX artifacts, and launch report generation with the selected scan already resolved.
-
5
Generate the report
From Findings or Reports, select the completed assessment, choose the output format, confirm sections, and save the generated artifact with its scan-aware filename.
Imports, exports, and where they appear
What to check before you trust a completed assessment
- The assessment is no longer shown as active and the dashboard status banner is terminal.
- The same scan id can be reopened from Completed without losing counts, context, or surface-specific metadata.
- The Findings page loads all findings for that scan, not a partial or stale subset.
- The Reports wizard can resolve the same completed assessment without asking you to refresh or rehydrate it manually.
- CSV, XLSX, SARIF, PDF, and DOCX artifacts carry scan-aware filenames and preserve the selected scan context.
Common operator questions
Because the dashboard is the historical record for the assessment. A terminal scan should stay reopenable from Completed, with final status, counts, evidence context, and report actions intact.
Imported completed assessments should land in Completed. That is the canonical place to reopen the dashboard, view findings, and launch reports.
A scan is reportable when it is in a terminal state, the completed assessment can be reselected in Reports, and the findings pipeline resolves the same scan id correctly.
The desktop app uses a native save dialog for renderer-delivered files. If no file appears, check the save destination you selected and then review the app logs for a backend export failure.