MerabyCore Orchestrator
A design note for how specialist roles could coordinate. This page does not run a hosted multi-agent orchestrator, and the creator tools do not call it.
Planned specialist roles
These cards describe architecture we might build. They are not agents you can run, hire, or call from the other pages.
Scene Builder (planned)
Planned role: would lay out 3D space, terrain, lighting, and collision from a written brief. Not implemented.
Script Generator (planned)
Planned role: would draft strict-mode, type-annotated scripts and check them against linters. The site ships hand-written templates instead.
Systems Architect (planned)
Planned role: would sketch replication, RemoteEvent checks, and datastore schemas. No architect process is running.
Asset Manager (planned)
Planned role: would bind glTF models, textures, and audio into a project. Workshop downloads are separate static files.
Analysis (planned)
Planned role: would run static checks before a change landed. Preset notes on the Luau page are a fixed checklist, not this role.
Documentation (planned)
Planned role: would keep traceability notes and Moonwave or TypeDoc output. Nothing on this page generates docs.
Principles we would keep
Intent for a future orchestrator. These are not behaviors of the current site.
Local-First Execution
If this shipped, project files would stay on the user machine and roles would talk over local IPC. That runtime does not exist here.
Milestone Review
Planned flow: roles would work in phases and pause before high-impact changes. There is no checkpoint UI today.
Single-Source Schemas
Planned constraint: messages between roles would come from JSON Schemas. The creator pages do not exchange those messages.
Explore Meraby Labs Architecture
Read the design note beside the local schema sketches. They do not power the templates or the lab on this site.
View Developer Documentation