# TOMBSTONE — tamed_bond/ dead-code (2026-05-27)

Council convening #6 (`_council/2026-05-27-dead-code-tamed_bond/`) triaged 4 dead-code candidates inside the live tamed_bond/ system via 5-seat audit (balance/performance/race/lore/compliance). All 4 candidates were WIRED in this convening (the author's unfinished multiplayer-correctness layer for per-player UUID-keyed memento storage). The one item archived here is a stale parallel loot_table.

## Files archived

### `loot_table/tamed_bond/memento.json`

Stale parallel codepath. Surfaced by lore seat as Risk 2.

The live memento item NBT is built procedurally in `tamed_bond/on_pet_death.mcfunction:31-41` and includes:
- 9 pet types (wolf/cat/horse/parrot/fox + donkey/mule/llama/camel, Council #6 split the "other" fallback into per-species)
- `minecraft:custom_data.owner_uuid` binding to the dead pet's `Owner` UUID for revival
- `minecraft:consumable` component (the use-trigger that drives the Moonbloom Ceremony)
- 8-line lore array

This loot_table.json was an earlier draft. It only has 4 explicit pet types (wolf/cat/mount_animals/parrot) + a lead fallback, no fox entry, no owner_uuid binding, no `minecraft:consumable` component, only 5 lore lines (missing the bottom "Use under a full moon, open sky" pair). Zero callers (`grep -rn "tamed_bond/memento" data/evercraft/` finds only the schedule + advancement-revoke references that share the substring).

If anyone ever converted `summon item` + `data modify Item` over to a `loot spawn` call, they would silently ship the older NBT — broken revival owner-binding (no owner_uuid) and no fox support. Better to delete the trap.

## Followups in 10-pending

- Inter-pet `last_stand/activate` `limit=1` ambiguity (same-player buddy/) — out of tamed_bond scope.
- Other `@e[tag=ec.tb_*,limit=1]` selectors may need distance gates (memento_pickup re-arm path).
