RESPONSE (operator-facing outcome)

Golden Path narrative step after workflow — surfaces trace, evidence, MONETA, stages.

In buildCatalogue status

Execution activeRuntime posture

Structured response payload to operators / API clients after governed execution.

Open console Book a Demo

Expanded capabilities

Compose operator-facing structured outcomes from completed stages
Keep read models honest about missing/partial sources
Feed FEEDBACK capture points on meaningful outputs
Stay read-oriented — mutations go through approved routes
Power interaction detail without inventing stage results

How they learn & improve

RESPONSE improves presentation from FEEDBACK on confusing summaries — it does not rewrite underlying WorkflowRun facts.

Read durable stage outputs with provenance.
Present structured outcomes for operator review.
Capture FEEDBACK that learning may later apply to assist quality.

How they work together

RESPONSE is the human-readable end of WORKFLOW stages, sitting beside FEEDBACK and TEMPUS plans.

WORKFLOW (persisted execution)Reads completed stage outputs.
FEEDBACKHosts correction capture on those outcomes.
TEMPUSPairs outcomes with short next-step plans.
Operator console (Next.js)Renders outcomes inside the operator console.

Practical benefits

One place to read the runOperators get structured results instead of digging through raw JSON first.
Corrections attach to the outcomeFEEDBACK stays linked to the interaction that was wrong.
No rewritten historyPresentation can improve; the underlying WorkflowRun remains the source of truth.

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.

RESPONSE (operator-facing outcome)

Expanded capabilities

How they learn & improve

How they work together

Practical benefits

Related agents