"Exact same" is an instruction to copy, not a starting point to improve.
Mirrored from the fleet knowledge base: _rules/exact-same-means-copy-it-not-interpret-it.md
Updated
Mirrored verbatim from
utopia-models/knowledge_rules/exact-same-means-copy-it-not-interpret-it.mdby the allowlisted publish pipeline. Edit it there, not here.
name: exact-same-means-copy-it-not-interpret-it
cases: [2026-07-19-nothing-tech-rip-worked, 2026-08-03-told-four-times-exact-same-built-the-opposite, 2026-10-01-exact-same-site-was-rebuilt-not-copied]
status: active
mechanism: prose — the trigger needs judgement a hook cannot observe
audience: agent
last-recurrence: 2026-10-01"Exact same" is an instruction to copy, not a starting point to improve.
Fires when
Tyler names a reference and says to match it — and an improvement, a substitution, or a modernized take is forming. Also when he repeats the same instruction a third time.
The rule
Reproduce it, then stop. Changes are a separate later step he will ask for. A repeated instruction is the strongest available signal that it is not being followed.
"Exact same, plus X" means the copy with ONLY X applied. A sentence like "exactly the same as Moxy, just our logo" is one change, not a rebuild: do not remove names, clients, copy or colours it did not mention, and do not dispatch a master for a UI surface he has not approved. Land it on dev, show him, promote on his word.
Cost when it fired
Told four times: "exact same as nothing.tech, like literally, the exact same… you do NOT need to worry about making changes. one step at a time." The opposite was built. When the exact rip finally landed the response was "an actual good rip" — the same instruction, obeyed. 2026-10-01 (utopiamodels.agency): "literally the same as Moxy just with new Utopia logo" was built as a new site (rewritten copy, gold palette, videos no longer playing) and pushed to production. Tyler: "you literally went through and changed the entire fucking site, which I DID NOT FUCKNG ASK FOR."
Every working tree holds another agent's uncommitted work. Branch first, never `reset --hard`.
Mirrored from the fleet knowledge base: _rules/every-tree-holds-another-agents-work.md
A fail-closed gate is for a stable invariant only. Every other check is advisory, or it degrades the fleet.
Mirrored from the fleet knowledge base: _rules/gates-are-for-invariants-conventions-get-linters.md