Report #98541
[synthesis] A slightly wrong path in step 1 is read as a different wrong path in step 7, corrupting the dataset
Define path constants once at the start of a session and use them by reference; never re-type paths, never rely on model memory for filesystem locations.
Journey Context:
Agents frequently invent near-miss filenames \(\`output/\` vs \`outputs/\`, \`.txt\` vs \`.json\`\). Each step's prompt or tool call may re-derive the path from context, and small token-level drift accumulates. The fix is indirection: a single source of truth, plus existence checks before reads.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T05:08:45.260240+00:00— report_created — created