AI-Adjacent Issue
Generated Output Changed Hidden Metadata
Generated output changes hidden metadata, identifiers, references, state, or system fields that affect later behavior but are not obvious in the visible output.
What This Looks Like
The visible generated output looks acceptable, but hidden metadata changes along with it. Identifiers, timestamps, references, slugs, labels, IDs, version fields, provenance, formatting metadata, or system-managed fields may change and affect later workflows, links, imports, or references.
Why Users Blame AI
The user sees the change after generating or regenerating output, so the AI appears to have broken something unexpectedly. The cause may be export behavior, file generation, CMS metadata, serialization, hidden fields, downstream import rules, or a tool that updates metadata while writing visible content.
What to Check First
- Whether generated output rewrites IDs, slugs, timestamps, or reference fields
- Whether hidden metadata is preserved across regeneration
- Whether downstream systems depend on metadata not visible to the user
- Whether the output tool creates new objects instead of updating existing ones
- Whether saved references point to stable identifiers or generated labels
- Whether metadata changes are included in review or diff output
When This Is AI-Adjacent
Use this AI-Adjacent Issue when generated output changes hidden metadata or system-managed state. If a saved reference no longer works, use the related Workbench Issue for reference instability. If the output change itself is undeclared, use the related output-change Issue.
Related Workbench Issues
Output Changed Without Declared Change
Output shape, content, format, fields, or behavior changes without a declared change to the prompt, schema, model, workflow, or governing rule.
Action Changed Something Else Too
An AI or agent action makes the requested change but also changes another object, field, file, state, rule, or workflow element that was not supposed to change.
Output Breaks the Next Step
The AI output looks acceptable by itself but cannot be used by the next tool, workflow step, parser, reviewer, or downstream consumer.
Saved Reference No Longer Works
A saved source, citation, file reference, prompt reference, or workflow pointer previously worked but no longer resolves to the expected object or meaning.
Same Contract Name Has Different Meanings
The same prompt, schema, field, policy, tool, or workflow contract name is used in different places with different meanings.
Common Ways People Describe This
- generated output changed hidden metadata
- AI output changed metadata
- generated file changed hidden fields
- AI changed invisible state
- output changed hidden identifiers
- generated content affected metadata