Legacy Landmine Map for AI Coding
Capture the decisions that live only in people's heads, before an agent's helpful refactor breaks prod
- Problem
- An engineer with eight years on legacy frontends notes AI handles anything with a standard answer but cannot handle 'why can't this field be deleted' or 'this ugly code worked around a bug once' — that knowledge lives in people's memory, not the code. When an agent optimizes it away, prod breaks, and the knowledge leaves with the old-timers.
- Solution
- A lightweight decision memory: one annotation line in code links to a 'why it is this way' note, and the tool aggregates them into a visual landmine map. Coding agents get a read-only query API to check history before editing and auto-append a change rationale afterwards.
- Users
- Small teams maintaining 10+ year-old systems, full-stack engineers owning three platforms alone, and traditional enterprises starting to hand coding to AI
- MVP
- One-line annotation syntax for historical decisions; landmine dashboard grouped by file and module; read-only query API for agents; auto-appended change rationale; export as readable team docs
- Revenue
- Per-seat subscription with 3 free collaborators; enterprise tier with self-hosting and audit logs
- Why now
- Coding agents now make most edits, turning human context into a scarce asset; AI can draft the summaries, so the cost of recording drops sharply.