Mind · Reasoning
FrameError
Typed failure signaling that lateral reframing, not retry, is required
Definition
Mechanism
A typed failure signaling that an acceptance gate rejection requires lateral reframing of the problem rather than retry. Produced by an AcceptSpec when a non-compensatory gate fails, the FrameError carries the specific gate that rejected and a reframing hint pointing the upstream planner toward a different frame. Distinct from transient failures (which warrant Retry) and from compensable failures (which warrant Compensate): a FrameError asserts that the current frame is wrong, not that execution went wrong.
Invariants
- A FrameError from a child forces the parent to restructure its approach, not re-execute.
- Must carry identification of the rejecting gate and a reframing hint — a bare FrameError without context is actionable only as 'halt'.
Risks
Failure modes
Receiving Solver treats FrameError as a generic failure and retries, wasting budget on the wrong frame.
Missing reframing hint leaves the parent Solver unable to select a new approach — degenerates to halt.
Cascaded FrameErrors without dampening cause thrash between frames.
Relationships
Builds on
References
Infrastructure
Non-compensatory acceptance contract; consumer Verify yields Solution or FrameError
Infrastructure
Structured rollback via logged inverses in LIFO order
Classified re-attempt with backoff conditioned on failure type
Used by
References
Four tests of a decomposition against a stated claim frame: each candidate dimension must pass Necessity, Independence and Universality, and the accepted set must pass Completeness
Infrastructure
Typed artifact emitted by a Solver's Feedback surface — downstream evaluation that feeds Pathway Memory
Apex triage node of a SolverTree, with Pathway Memory as its compounding learning site
Reference