Skip to content

fix(agent): frame intent summaries as data (issue #124) - #311

Merged
BaaRai merged 1 commit into
mainfrom
fix/agent-frame-intent-summaries
Nov 17, 2026
Merged

BaaRai merged 1 commit into
mainfrom
fix/agent-frame-intent-summaries

Conversation

@BaaRai

@BaaRai BaaRai commented Nov 17, 2026

Copy link
Copy Markdown
Owner

Intent summaries are planner-written text, but they reached the planner in two trusted places (#124, F3):

  • the wake lines rendered The worker of intent #N (<summary>) ... outside the data envelope;
  • graph_overview kept open_intents / running_intents / recent_done_intents in the plain JSON, and compactIntents marks inherited nodes with source_task_id/inherited, so a summary written by another task's planner arrived as if this planner had written it.

This change keeps the structured intent fields plain (id, state, asset_ids, parents, yields, inherited flags) and moves every summary into one framed block (field=intent_summaries), with the id and the inherited origin inside. The wake lines render the summary in its own frame (field=intent_summary) instead of interpolating it into the sentence.

Tests: TestDataEnvelopeFramesIntentSummaries and TestDataEnvelopeFramesWakeIntentSummary assert the summaries appear only inside a frame and the structured fields stay plain; TestWorkerOverviewEnvelopeSplit is updated for the new split. go test ./agent passes locally (the Postgres-backed tests skip and run in CI).

Not in this change: the declared-vs-derived provenance of record_fact, the other residual in #124, which needs a rule for facts that can be tied to proxy-captured traffic.

The wake lines interpolated a planner-written intent summary into the trusted sentence, and the overview kept every summary in the plain JSON, so an inherited summary crossed tasks as if this planner had written it (#124, F3). Frame the summary on the wake lines and move the open/running/recent-done summaries into one framed block; the structured intent fields stay plain.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant