[P0] Add structured execution outcomes, trace inspection, and repair primitives #10

Closed
opened 2026-08-12 01:18:38 +00:00 by lost-rob0t · 0 comments
lost-rob0t commented 2026-08-12 01:18:38 +00:00 (Migrated from github.com)

Goal

Make model/program failures inspectable and repairable instead of returning opaque stderr blobs.

Scope

  • define canonical outcomes for success, logical failure, timeout, depth/resource exhaustion, capability denial, validation failure, and exception;
  • preserve variable bindings/residual constraints where applicable;
  • expose structured trace trees for executed plans/goals;
  • add predicate/plan inspection helpers;
  • add bounded retry/repair hooks that can feed structured failure state back to a model;
  • keep repair scoped to the failing unit rather than regenerating the entire run;
  • make all diagnostics serializable as ordinary Prolog terms/dicts.

Acceptance criteria

  • failing goals and plans produce machine-readable outcomes;
  • traces distinguish logical failure from exceptions/timeouts;
  • a deterministic fixture demonstrates generate -> execute -> inspect -> repair -> succeed;
  • repair retries obey the original run budget;
  • diagnostics never require scraping terminal output.

Dependencies

Research

See RLM-RESEARCH-004-prologmcp-repair-loop.org.

## Goal Make model/program failures inspectable and repairable instead of returning opaque stderr blobs. ## Scope - define canonical outcomes for success, logical failure, timeout, depth/resource exhaustion, capability denial, validation failure, and exception; - preserve variable bindings/residual constraints where applicable; - expose structured trace trees for executed plans/goals; - add predicate/plan inspection helpers; - add bounded retry/repair hooks that can feed structured failure state back to a model; - keep repair scoped to the failing unit rather than regenerating the entire run; - make all diagnostics serializable as ordinary Prolog terms/dicts. ## Acceptance criteria - failing goals and plans produce machine-readable outcomes; - traces distinguish logical failure from exceptions/timeouts; - a deterministic fixture demonstrates generate -> execute -> inspect -> repair -> succeed; - repair retries obey the original run budget; - diagnostics never require scraping terminal output. ## Dependencies - #7 - #9 - parent #3 ## Research See `RLM-RESEARCH-004-prologmcp-repair-loop.org`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/prolog-rlm#10
No description provided.