Inputs, prompt conditions and scoring
What the model receives
The model receives stable asset IDs, existing filenames, content hashes, version relationships, requested operations and the full naming policy. Cases include duplicates under different names, conflicting versions, case/Unicode collisions and ambiguous parentage. The 72 operation rows belong to two packs; repeat outputs are not additional packs.
What changes between prompts
Both conditions receive the complete policy, facts and output schema. The scaffold adds an ordered process for identity reconciliation, naming, lineage, collision checks and escalation. The output is a dry-run proposal; the evaluation does not rename files.
How the result is scored
A deterministic exact-key scorer assesses filenames, actions, versions, parentage, duplicates, exceptions and idempotence. The mean correctness score is accompanied by strict whole-change-set and critical-safety checks. An attractive average does not mean every proposed operation is safe to apply; whole-set acceptance is the operational decision.