BT411

71 Commits 2 Branches 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
arcattackandClaude Opus 4.8	16af8dbffb	context: correct 0xBD3 — it's the damage/explosion hub (0x434), NOT the valve/Myomers gate Risk-4 investigation (before wiring WAVE 8) found my earlier 'keystone unblocks 4 things' claim was wrong. Verified from the binary: - 0xBD3 SubsystemMessageManager = a damage/explosion consolidation hub (ConsolidateAndSendDamage, weaponExplosions), cached to Mech[0x10d]=0x434, mislabeled 'controlsMapper' in our recon (the live drive squats there; the real mapper is roster slot 0 via SetMappingSubsystem). - The valve MoveValve guard (FUN_004ac9c8 ->owner+0x190+0x274) AND the Myomers gate (FUN_004ad7d4 ->owner+0x190+0x260) read a DIFFERENT object at mech+0x190 (!= 0x434). So 0xBD3 does NOT gate the valve/Myomers/MessageBoard; mech+0x190 (unidentified, no decompiled writer yet) is the real keystone for those gauge-adjacent routes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-07 22:49:29 -05:00
arcattackandClaude Opus 4.8	1cd57ade85	context-system: bootstrap the progressive-context expert knowledge base (foundation) Adapt the spark-lesson / expert-seed.md progressive-context pattern to the bt411 port: a thin router + context/.md knowledge graph so the 2236-line CLAUDE.md's deep knowledge loads on-demand instead of every session. NON-DESTRUCTIVE foundation pass (live CLAUDE.md unchanged; proposed router is a draft): - reference/glossary.yaml -- ~45 terms (engine/formats/scene/reconstruction) - context/decomp-reference.md -- the quantitative hub: resource types, ClassID map, mech offsets, damage delivery, weapon constants, env gates, tools - context/reconstruction-gotchas.md -- the 12 systemic bug classes (conventions/DO-NOT hub) - context/bgf-format.md -- geometry format + CONN/PCONN + LOD-sqrt3 + ramp shading - context/gauges-hud.md -- the gauge/MFD system (the just-completed wave) - context/open-questions.md -- deferred systems + get-from-Nick - context/_ROUTER-DRAFT.md -- the proposed slim CLAUDE.md (identity, protocols, quick-lookup, evidence tiers T0-T4, conventions, structure) - phases/phase-01-context-restructure.md -- design + migration plan + status docs/.md ledgers stay as the DETAILED logs; context/*.md are the curated digests that route into them. Remaining: ~10 topic files (project-overview, subsystems, combat-damage, rendering, locomotion, wintesla-port, build-and-run, ...) then the CLAUDE.md swap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-07 22:06:53 -05:00

Author

SHA1

Message

Date

arcattackandClaude Opus 4.8

16af8dbffb

context: correct 0xBD3 — it's the damage/explosion hub (0x434), NOT the valve/Myomers gate

Risk-4 investigation (before wiring WAVE 8) found my earlier 'keystone unblocks 4 things'
claim was wrong. Verified from the binary:
- 0xBD3 SubsystemMessageManager = a damage/explosion consolidation hub (ConsolidateAndSendDamage,
  weaponExplosions), cached to Mech[0x10d]=0x434, mislabeled 'controlsMapper' in our recon (the
  live drive squats there; the real mapper is roster slot 0 via SetMappingSubsystem).
- The valve MoveValve guard (FUN_004ac9c8 ->owner+0x190+0x274) AND the Myomers gate
  (FUN_004ad7d4 ->owner+0x190+0x260) read a DIFFERENT object at mech+0x190 (!= 0x434). So 0xBD3
  does NOT gate the valve/Myomers/MessageBoard; mech+0x190 (unidentified, no decompiled writer yet)
  is the real keystone for those gauge-adjacent routes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-07 22:49:29 -05:00

arcattackandClaude Opus 4.8

1cd57ade85

context-system: bootstrap the progressive-context expert knowledge base (foundation)

Adapt the spark-lesson / expert-seed.md progressive-context pattern to the bt411 port:
a thin router + context/*.md knowledge graph so the 2236-line CLAUDE.md's deep knowledge
loads on-demand instead of every session.

NON-DESTRUCTIVE foundation pass (live CLAUDE.md unchanged; proposed router is a draft):
- reference/glossary.yaml        -- ~45 terms (engine/formats/scene/reconstruction)
- context/decomp-reference.md    -- the quantitative hub: resource types, ClassID map,
                                    mech offsets, damage delivery, weapon constants, env gates, tools
- context/reconstruction-gotchas.md -- the 12 systemic bug classes (conventions/DO-NOT hub)
- context/bgf-format.md          -- geometry format + CONN/PCONN + LOD-sqrt3 + ramp shading
- context/gauges-hud.md          -- the gauge/MFD system (the just-completed wave)
- context/open-questions.md      -- deferred systems + get-from-Nick
- context/_ROUTER-DRAFT.md       -- the proposed slim CLAUDE.md (identity, protocols,
                                    quick-lookup, evidence tiers T0-T4, conventions, structure)
- phases/phase-01-context-restructure.md -- design + migration plan + status

docs/*.md ledgers stay as the DETAILED logs; context/*.md are the curated digests that
route into them. Remaining: ~10 topic files (project-overview, subsystems, combat-damage,
rendering, locomotion, wintesla-port, build-and-run, ...) then the CLAUDE.md swap.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-07 22:06:53 -05:00