## TL;DR
Fix this in action item carry over agent by acting on the exact problem first: fill every carried item only from an action line retrieved in the source meeting record, keep the owner and wording from that line unchanged, and reject any carried item whose text appears in no source meeting so invented commitments never reach the next agenda. Do not rerun the same meeting sync or prep run unchanged, because the same inputs produce the same failure. Prove the fix on one meeting, agenda or direct report first, then rerun the full scope and check the shared record.

```text
agent hallucinating answers not in source data for carry action items into the next agenda error hallucination failure
```

## Use this when
- The operation in action item carry over agent fails with this exact problem: agent hallucinating answers not in source data for carry action items into the next agenda error hallucination failure.
- The same failure repeats on retry with unchanged inputs.
- A one on one agenda, talking point, action item or prep step is blocked until this is resolved.

## Not for this skill when
- The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
- The meeting completes and you only disagree with a people judgement such as a rating or a promotion call. That is a manager and people team decision, not this failure.

## Steps
1. Reproduce the failure on one named meeting or direct report in action item carry over agent and record the full problem text plus the meeting, participants and date involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: fill every carried item only from an action line retrieved in the source meeting record, keep the owner and wording from that line unchanged, and reject any carried item whose text appears in no source meeting so invented commitments never reach the next agenda. Verify: the single failing meeting or agenda now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring meetings, reports or recurring occurrences that share the same template, calendar series or sync, because this class of failure rarely affects only one meeting. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in action item carry over agent on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the shared agenda record, the calendar event or the meeting notes, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the meeting prep log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Variant phrasings

### agent hallucinating answers not in source data for carry action items into the next agenda error hallucination failure
The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single meeting proof, then the full rerun.

### How to fix - agent hallucinating answers not in source data for carry action items into the next agenda error hallucination failure
The how to phrasing for the same failure in action item carry over agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### action item carry over agent troubleshooting for this failure
The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

## Why it happens
An agent smoothing over a messy notes page can invent a tidy action nobody agreed to, and carrying it forward gives the invention an owner and a due date it never had.

## Edge cases
- The meeting was rescheduled, reassigned or edited after the failing run started. Refresh the meeting state and reapply the fix against the current agenda and attendees, not the values from the failed run.
- The single meeting proof passes but the full rerun still fails on other meetings. Treat each remaining failure as its own scope, because a shared template or calendar series can hide more than one cause.
- The source systems disagree on the correct value. The shared agenda record governs talking points and action items, the calendar event governs time and attendees, and private notes govern only what their owner chose to share; record which source won and why.

Compatibility: action item carry over agent at current versions, plus the calendar, agenda or people tool the query names; no extra tooling beyond access to the source records needed to verify results.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ApgYFXqu-25kTiefvi9piA