RobloxForge Atlas 🧭

The Cartographer’s Desk for Roblox Studio’s Model Context Protocol

A companion intelligence layer that turns the official Roblox Studio MCP from a raw pipe into a well-lit workshop. Atlas maps every context window, every tool call, every verification receipt into a navigable terrain, so builders stop guessing which slice of reality the model is actually seeing.

---

🧩 What Is This, Really?

Imagine the official MCP as a sprawling, powerful railway network. Tracks exist, signals exist, and engines are running. But there is no timetable, no station map, no conductor’s log. RobloxForge Atlas is the timetable, the station map, and the conductor’s log — bound together, cross-referenced, and printed on paper that doesn’t smudge when the model hallucinates a junction that was never built.

Atlas is not a fork of the official MCP. It is not a wrapper that hides the original. It is a vertical-slice discipline engine: a layer that insists every generation be scoped to a single, verifiable, demonstrable slice of work — then proves it happened with a receipt no one can argue with.

Where the original context described “current official docs, vertical-slice discipline, verification receipts,” Atlas takes those three pillars and grows an entire observatory on top of them.

---

🗺️ The Atlas Difference: From Pipeline to Panorama

Most MCP tooling treats the protocol as a plumbing problem. Connect, stream, done. Atlas treats it as a cartography problem. Every tool has a territory. Every response has a border. Every generation has a latitude and longitude inside the project’s history.

Key philosophical shifts:

• Slices over swamps. Instead of letting a model wander across an entire place file, Atlas enforces vertical slices — one feature, one system, one behavior at a time, each slice independently reviewable.
• Receipts over vibes. A generation is not “done” because it looks right. It is done when a verification receipt is issued, timestamped, and attached to the slice.
• Maps over memories. The model’s context window is ephemeral. Atlas’s terrain map is persistent, queryable, and version-controlled alongside your project.

---

🎯 Feature Constellation

🧠 Context Intelligence Layer

Atlas continuously samples the live context handed to the official MCP and renders it as a heat map. You see which folders, scripts, and instances the model actually read — not what you hoped it read. This single feature eliminates the most common source of “but I told it to look at the module” frustration.

🧱 Vertical Slice Enforcement

Define a slice with a name, a boundary, and an exit condition. Atlas refuses to close the slice until the exit condition is proven. No more sprawling changes that touch 47 scripts because the model got enthusiastic.

🧾 Verification Receipts

Every slice produces a receipt: a compact, portable record of what changed, what was tested in Studio, and what the observed outcome was. Receipts are chainable, so a sequence of slices forms an audit trail that reads like a build log written by someone who actually cares.

🌐 Responsive Multi-Pane Workspace

The Atlas desktop surface rearranges itself based on which phase you are in: scoping, generating, verifying, or reviewing. Panes collapse when idle and expand when a slice is active. It feels less like an IDE and more like a cockpit that knows which instruments matter right now.