AI tools write great code. They just don't know your architecture.

We love Cursor. We love Claude. We love Copilot. But six months ago we noticed something quietly breaking our codebase. Not bugs. Not bad code. Drift. Our AI tools kept generating perfectly functional code that slowly violated decisions we'd already made as a team. The repository pattern we'd agreed on. The state management library we'd picked after two weeks of debate. The validation approach our senior engineer insisted on. None of it was anywhere AI could actually read. It lived in: A Slack thread from 8 months ago An ARCHITECTURE.md nobody had touched in a year Three .cursorrules files that contradicted each other One senior engineer's memory So AI guessed. And every wrong guess added one more brick of drift. The fix we built: Hopsule is a memory layer that sits between your team's decisions and your AI tools. You record a decision once. Hopsule structures it, versions it, and injects it into every AI session automatically via MCP. Example: Your team accepts: "Database access must