The run lifecycle
A TARX run is the unit of work created when the prepared alpha receives a prompt.
Normal path
The accepted alpha path is:
prompt -> run created -> lifecycle visible -> evidence visible -> run persistsIn the current prepared-machine proof, the run can reach:
ready_for_reviewready_for_morning_review
Those states mean the run reached a terminal reviewable state and its evidence surfaces can be inspected.
Activity source
The active Always On UI can consume runtime SSE activity for fresh runs. The /events path remains available as replay and fallback.
Support language:
- say “runtime activity is visible”
- say “SSE activity is proven for active prepared-alpha runs”
- do not say “fake live stream”
- do not say “cloud stream”
Terminal states
Current support states include:
| State | Meaning |
|---|---|
| ready for review | The run has terminal reviewable evidence. |
| hold | The run stopped on a blocker that should be inspectable. |
| cancelled | The user cancelled an active run through the product path. |
| failed | The run failed and should show an honest blocker. |
If the run does not complete
Do not reset the narrative. Inspect the run, review, files, terminal, and preview surfaces. The alpha is allowed to show a hold or failed state when the runtime has a real blocker.
Next
Continue to Ready for review.