Changes & Versions
Problems where model behavior, prompts, contracts, schemas, outputs, references, rubrics, or expectations change without the surrounding workflow updating correctly.
Primary Issues
- 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.
- Output Breaks After Model Change
Output that previously worked begins failing after a model, mode, runtime, or product behavior changes.
- Version Change Breaks Existing Prompt
A prompt that previously produced usable results stops working after a version change in the model, tool, policy, schema, product surface, or workflow.
- Prompt Changed but Workflow Did Not
A prompt changes but the workflow, parser, review step, routing rule, or downstream expectation still assumes the old prompt behavior.
- Rubric Changed but Results Did Not
A review rubric, scoring rule, evaluation standard, or classification criterion changes, but AI results continue to reflect the old rubric.
- Old Output Expectations Survive Migration
Expectations from a prior model, prompt, schema, tool, or workflow survive a migration and continue shaping review or downstream handling after they should be replaced.
- 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.
- Prompt Behavior Changed Without Version Change
A prompt begins producing different behavior even though no prompt version, model version, workflow version, or declared dependency change is recorded.
- 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.
Also Related Issues
- Context Changes After Restore
Restoring, reopening, resuming, or reloading a task changes the context that the AI uses to continue the work.
- Stale Context Affects Output
Old context, prior instructions, outdated references, or earlier task state continue to affect output after they should no longer apply.
- Actual Policy Differs From Declared Policy
The policy the AI or workflow actually follows differs from the policy that is documented, declared, displayed, or expected.
- Revoked Approval Still Treated as Active
An approval, permission, exception, or authorization that was revoked continues to affect AI behavior or workflow decisions as if it were still active.
- Policy Update Not Reflected in Output
A policy, rule, standard, or instruction has been updated, but the AI output still follows the older version.
- Small Change Produces Large Downstream Effects
A small prompt, schema, policy, output, or workflow change creates unexpectedly large effects in downstream steps.
Ontology Metadata
- Code
CAT-0080- Version
[email protected]- Ontology release
- 0.1.0
- Updated
- 2026-05-10T00:00:00Z
History
No public history entries recorded.