Problem
After #727, capture-event becomes a generic event writer with no mistake or correction surface — that coupling is deliberately removed. This leaves no reliable, first-class way to capture the values specific to a mistake: the verbatim correction, and the fact that the event is a mistake. We want a dependable path for this rather than relying on an agent to remember an ad-hoc convention each time.
Proposed solution
Tentative, to be settled when the ticket is taken up. Likely a thin capture-mistake skill layered over capture-event that supplies the mistake marker (e.g. a mistake tag) and captures the correction, so those values are recorded without fail. The exact mechanism — where the correction lives, how the marker is expressed — is intentionally left open.
Notes
- Placeholder, filed so the intent is not lost. The record schema is expected to mature before this is undertaken.
Dependencies
Problem
After #727,
capture-eventbecomes a generic event writer with no mistake or correction surface — that coupling is deliberately removed. This leaves no reliable, first-class way to capture the values specific to a mistake: the verbatim correction, and the fact that the event is a mistake. We want a dependable path for this rather than relying on an agent to remember an ad-hoc convention each time.Proposed solution
Tentative, to be settled when the ticket is taken up. Likely a thin
capture-mistakeskill layered overcapture-eventthat supplies the mistake marker (e.g. amistaketag) and captures the correction, so those values are recorded without fail. The exact mechanism — where the correction lives, how the marker is expressed — is intentionally left open.Notes
Dependencies
capture-event). Do not start until the schema has settled.