Expanded capabilities
- Persist ExecutionJob and WorkflowRun state in PostgreSQL
- Advance Golden Path stages with leases and cursors
- Pause for approvals and resume only after human decisions
- Expose terminal DONE/FAILED outcomes with inspectable outputJson
- Refuse prompt-held or chat-invented workflow state
How they learn & improve
WORKFLOW improves reliability from stuck-job FEEDBACK and approved runtime calibrations — it never auto-skips approvals to ‘get unstuck’.
- Queue and lease jobs under tenant + policy context.
- Record stage transitions for TERMINUS/HERMES observation.
- Apply human-approved runtime learning without bypassing gates.
How they work together
WORKFLOW is the durable spine: ATLAS/POLICY decide, stages execute, APPROVAL QUEUE pauses, RESPONSE/FEEDBACK close the loop.
- ATLASStarts classified work as durable jobs.
- Approval queuePauses until a human decision arrives.
- TERMINUSExposes queue/lease posture for operators.
- HERMESSurfaces flow health across stage transitions.
Practical benefits
- Replayable executionYou can inspect what ran yesterday — state lives in the database, not a chat transcript.
- Safe pause/resumeSensitive stages wait for approvals instead of racing ahead.
- Stuck-job visibilityTERMINUS/HERMES show lease pressure so ops fixes workers — not by inventing fake progress.
Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.
