Memory Without Enforcement is Dangerous — Why I Built SpecLock

I spent a year building products with AI coding tools. Bolt.new, Claude Code, Cursor — I used them all, every day. The AI was great at writing code. Terrible at respecting boundaries. ## The Pattern That Kept Repeating Session 1: "Never touch the auth files." Session 3: Auth is completely rewritten. Session 2: "We're using PostgreSQL." Session 5: "I've migrated you to MongoDB — it seemed better." Session 1: "The API uses Bearer tokens." Session 7: "I switched to session cookies for simplicity." Every. Single. Time. ## "But AI Has Memory Now" Yes — Claude Code shipped native memory in February 2026. Cursor has Memory Bank. Mem0 exists. But here's what nobody talks about: memory without enforcement is dangerous. Your AI "remembers" your rules in a text file. But when the context gets long, it ignores them. When a fix seems easier by breaking your constraint, it breaks it. When it "knows better," it overrides your decision. Remembering is not the same as respecting. ## What I Built I buil