The Compatibility Engine, explained

A lot of platforms claim to be "zero-config." What that usually means is "we'll guess, and when we guess wrong, you'll figure it out from the error logs."

MoonBase's Compatibility Engine is different in three ways.

1. It writes down what it guessed

Every fingerprint, every repair, every default — logged in the Deployment Recipe. If your site goes live with Node 20 instead of Node 18, you can read *why* in plain English. If a missing script got generated, you can see the exact patch.

2. It learns from itself

The engine watches its own track record. When a repair works, it gets promoted. When a pattern recurs across 50 different users, it becomes a first-class matcher. The Learning System inside the admin panel is how we tune it — and it's open to operator inspection.

3. It refuses to ship broken stuff

A lot of platforms will "succeed" your build and hand you a URL that returns 500 forever. MoonBase runs a real health check before flipping the switch. If the health check fails, the deploy auto-rolls back to the last working version. Your URL is never broken.

---

That's the engine. We'll write more about each piece as the system grows. If you have a weird AI-generated project that *should* deploy but doesn't, send it — we want to see it.