🧠 NeuroForge — Live AI Bridge for Luau Runtime Instrumentation

Think of NeuroForge as a radio antenna bolted onto a running Roblox experience. Instead of shouting commands into the void and waiting for a rebuild cycle, you tune into the frequency of a live session — AI assistants on one side, an instrumented Luau runtime on the other — and the conversation flows in both directions, in real time, under strict identity and permission rules.

NeuroForge is a Model Context Protocol (MCP) server that gives AI coding companions (Claude, Cursor, or any MCP-compatible client) a structured, auditable doorway into a running Roblox Luau environment. It pairs with a whitelist-oriented execution platform so that every code submission, every inspection request, and every returned value is bound to a verified participant and a scoped capability grant.

No guesswork. No blind pasting. Just a disciplined, observable bridge between the model that thinks and the runtime that runs.

---

🚀 What NeuroForge Actually Is

Most developer tooling treats a game session as a black box: you write code, you deploy, you hope, you squint at logs. NeuroForge flips that posture. It turns the live Luau session into a queryable, scriptable surface — but only through the narrow pipe the operator has deliberately opened.

Under the hood, NeuroForge is three cooperating layers:

1. The MCP Face — a protocol-compliant server that exposes tools, resources, and prompts to AI assistants. This is the part your assistant "sees."
2. The Relay Spine — a transport-agnostic message channel that ferries requests from the server to enrolled runtime agents and returns structured results. It is designed to be resilient to latency spikes and partial failures.
3. The Runtime Instrumentation Kit — a Luau-side library that loads into a permitted session, registers handlers, enforces the local policy, and reports back with typed payloads.

Each layer is replaceable. Each layer is observable. Each layer can be locked down.

---

📦 Getting the Project Onto Your Machine

Because distribution happens through a curated release channel, the binary and its companion Luau instrumentation bundle are pulled together. Verify the integrity manifest before first launch — NeuroForge refuses to attach to a runtime if the manifest does not match.

After acquisition, the expected layout on disk is:

• /app — the MCP server entry point and its adapter modules
• /runtime — the Luau instrumentation kit to be staged into the target environment
• /policy — default capability matrices and identity descriptors
• /logs — rolling structured event journals

Configuration lives in a single neuroforge.toml file at the repository root. Sensitive values are referenced by environment indirection rather than inlined — never commit raw credentials to this file.

---

🗺️ Table of Contents