# Tombstone — Councils #18 + #19 dead-code archive

**Date:** 2026-05-28
**Council artifacts:** `_council/2026-05-28-dead-code-artifacts-netherite-core/{BRIEF.md, teammate-notes/*.md, review/SYNTHESIS.md}`
**Verdict shape:** 5-seat parallel pass (balance, performance, race, lore, compliance), combined dispatch for two clusters in one teammate-notes file each (Joseph's call — netherite_core pre-decided + improvement audit + trim full vote in one round, to budget tokens).

## What was archived (23 files)

### Cluster B — `cluster-B-netherite-core/` (7 mcfunctions)
The dead 7 are the abandoned **item-frame altar** upgrade pattern. The shipped Ancient Netherite Core uses the **hand-hold sneak** pattern instead (`tick → tick_logic → consume_block → upgrade_hand_to_N`). The altar files would have counted netherite blocks in 5×5/7×7/9×9 layers around an item frame containing the core; `set_level_*` would have written `custom_data.level=N` to the item inside the frame. The shipped path uses `loot replace entity @s weapon.mainhand` against `evercraft:artifacts/special/ancient_netherite_core_N` instead.

Files:
- `count_layer_2.mcfunction` (25 blocks, 5×5)
- `count_layer_3.mcfunction` (49 blocks, 7×7, uses `fill … replace …` for fast count)
- `count_layer_4.mcfunction` (81 blocks, 9×9)
- `set_level_1.mcfunction` through `set_level_4.mcfunction` (write `custom_data.level` + `item modify entity @s container.0 evercraft:netherite_core/level_N` against item-display entity)

### Cluster C — `cluster-C-trim/` (9 council + 2 copper_bolting cascades)

**`copper_bolting/` (4 council + 2 cascade):** the abandoned "Bolt trim wearer right-clicks copper items in their crafting grid to oxidize/de-oxidize them via custom UI items in the cursor" mechanic. The shipped Bolt full-set ability is `lightning` / `do_lightning` / `try_lightning` / `remove_cooldown` (lightning-strike-on-hit). Self-deprecating dev lore (`"Becomes a ghost item when closing inventory :/"`) and the misspelled `degredation_level` confirm the scaffold never reached completion. The whole subtree uses storage `trim_abilities:copper_bolting` (NOT `evercraft:`) and the unused function tag `#evercraft:trim/bolt_operations`.
- `copper_bolting/2.mcfunction` (entry — degradation-level string detection)
- `copper_bolting/block_test.mcfunction` (waxable-id macro tester)
- `copper_bolting/block_test_init.mcfunction` (bootstrap shim)
- `copper_bolting/execute.mcfunction` (cursor UI handler)
- **CASCADE:** `copper_bolting/oxidize.mcfunction` (oxidation-tier command builder)
- **CASCADE:** `copper_bolting/scrape.mcfunction` (de-oxidation-tier command builder)

**`eye/` (2 council):** the abandoned multi-block-step raycast iteration. The shipped Eye trim teleport uses a single-block-step recursive `evercraft:trim/full_set/eye/raycast.mcfunction` (7 lines, `do_teleport` + self-recursion via `trim_math1 1..50`). The dead files iterated 2 and 3 blocks at a time. 4 seats independently re-read `raycast.mcfunction` and confirmed it does NOT call `eye/2` or `eye/3`. (Balance seat dissented citing an outdated chain trace; refuted by direct file evidence.)
- `eye/2.mcfunction` (2-block-step iteration with self-recurse + tail-call to `eye/3`)
- `eye/3.mcfunction` (3-block-step terminal iteration)

**`single/` (3 council):** orphans from pre-pivot single-trim subsystems.
- `bolt/replace_armor_data.mcfunction` — generic macro template (`$item modify entity @s $(slot_type)$(slot_index) {…}`); superseded by 4-hardcoded-call inline pattern in `single/bolt/got.mcfunction:2-5`
- `sentry/find_target.mcfunction` — recursive hostile-target raycast (up to 20 steps); superseded by `single/sentry/patrol.mcfunction` iron-golem-summon design
- `sentry/pillager_buffs.mcfunction` — personal regen+resistance+strength+speed+knockback-immunity buff; pre-pivot Sentry personal-buff design, lost to the golem-summon design. **Balance seat noted: had this shipped it would have been net-overpowered for a single-piece trim.**

### Chained-dead cascades (4 + 1 = 5 JSONs)

**`cascade-item-modifier-netherite-core/` (4 JSONs):** referenced only from the now-archived `set_level_*.mcfunction` files. No live caller — the shipped hand-hold pattern uses loot-table swaps instead of item modifiers.
- `level_1.json` (referenced from `set_level_1.mcfunction:11`)
- `level_2.json` (referenced from `set_level_2.mcfunction:8`)
- `level_3.json` (referenced from `set_level_3.mcfunction:9`)
- `level_4.json` (referenced from `set_level_4.mcfunction:11`)

**`cascade-tags-function-trim/` (1 JSON):** the function tag `#evercraft:trim/bolt_operations` is invoked only from the now-archived `copper_bolting/2.mcfunction`. Its members (`oxidize`, `scrape`) are also archived. Tag becomes empty-purpose.
- `bolt_operations.json`

## Not in this archive — followups queued

The improvement audit on the LIVE netherite_core hand-hold pattern surfaced 9 P0/P1/P2 findings (P0-1 hopper-minecart tag-race, P0-2 nc_blocks-monotonic-accumulator exploit, P0-3 int-vs-byte mismatch verification, P1-1 triple-scheduling, P1-2 28-NBT-scan inefficiency, P1-3 nc_absorbing tag persistence, P2 anc.* naming, P2 L4-lore-drift, P2 consume_block spam guard). Queued in `BIG_BRAIN/10-pending.md` under `## Wiring Audit #18+#19 — Followups`.

Pillager War Horn lore drift (description says "summon pillagers", shipped behavior summons iron golems) also queued — separate from this archive.

## Restoration

To revive any file, copy back to its original path under `data/evercraft/function/` (or item_modifier/tags subtree). For full feature revival of copper_bolting or the netherite_core item-frame-altar pattern, expect to also rewrite the entry-point wiring (no live caller exists for either).
