Missing Source Code Investigation — Classical AI Commits Disappearing #1145

Closed
opened 2026-04-09 22:17:36 +00:00 by perplexity · 1 comment
Member

Source

KT Supplementary Notes 2026-04-08 — Missing Source Code Investigation section

Problem

Alexander reports that classical AI implementations (state machines, GOFAI techniques meant to reduce LLM dependency) keep going missing from the codebase. Multiple cycles of agents implementing these features, then the source disappearing.

Possible Explanations (investigate in order of likelihood)

  1. Duplicate agents (Bezalel-A, Ezra duplicate) on different machines overwriting each other's commits
  2. Agent reverting commits it doesn't understand during a "cleanup" operation
  3. Claude-routed work sessions fighting the implementation due to alignment friction
  4. Code was hallucinated and never actually committed

Investigation Steps

  1. Run across all repos
  2. Search for: state machine, VMAT, classical AI, GOFAI, value function, routing logic
  3. Check if commits exist anywhere in the history
  4. If committed and then reverted, will show who reverted them
  5. Cross-reference with agent identity audit (fleet audit issue)
  6. Check if branch protection or force-push policies could have caused loss

Acceptance Criteria

  • Git history audited for classical AI commits
  • Either found the commits (and who removed them) or confirmed they were never committed
  • Root cause identified
  • Prevention strategy implemented (branch protection, commit signing, etc.)
  • Report filed with findings
  • Fleet Audit issue (duplicate agents are the most likely cause)
  • Hermes Trismegistus proposal (classical AI / GOFAI layer is part of her scope)
## Source KT Supplementary Notes 2026-04-08 — Missing Source Code Investigation section ## Problem Alexander reports that classical AI implementations (state machines, GOFAI techniques meant to reduce LLM dependency) keep going missing from the codebase. Multiple cycles of agents implementing these features, then the source disappearing. ## Possible Explanations (investigate in order of likelihood) 1. **Duplicate agents** (Bezalel-A, Ezra duplicate) on different machines overwriting each other's commits 2. **Agent reverting commits** it doesn't understand during a "cleanup" operation 3. **Claude-routed work sessions** fighting the implementation due to alignment friction 4. **Code was hallucinated** and never actually committed ## Investigation Steps 1. Run across all repos 2. Search for: state machine, VMAT, classical AI, GOFAI, value function, routing logic 3. Check if commits exist anywhere in the history 4. If committed and then reverted, will show who reverted them 5. Cross-reference with agent identity audit (fleet audit issue) 6. Check if branch protection or force-push policies could have caused loss ## Acceptance Criteria - [ ] Git history audited for classical AI commits - [ ] Either found the commits (and who removed them) or confirmed they were never committed - [ ] Root cause identified - [ ] Prevention strategy implemented (branch protection, commit signing, etc.) - [ ] Report filed with findings ## Related - Fleet Audit issue (duplicate agents are the most likely cause) - Hermes Trismegistus proposal (classical AI / GOFAI layer is part of her scope)
perplexity added this to the KT-2026-04-08: Infrastructure Stabilization milestone 2026-04-09 22:17:36 +00:00
bezalel was assigned by Timmy 2026-04-10 00:30:35 +00:00
Owner

/claim — mimo-v2-pro [CODE] lane. Branch: mimo/code/issue-1145

/claim — mimo-v2-pro [CODE] lane. Branch: `mimo/code/issue-1145`
Timmy closed this issue 2026-04-10 21:00:41 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#1145