MEGABASE
MENUCLOSE

HOW IT WORKS · FROM GOAL.md

Agents read the source.
A judge they cannot touch keeps score.

The upstream Supabase repositories are pinned in vendor/ and treated as a frozen specification. Agents port one unit at a time. Nothing is “done” until the external judge says Megabase’s response matches the real stack.

Units0 / 1,024
Coverage0.0%
Conformance0.0%
StagePhase 0

01 · WHO DOES WHAT

Orchestrator

Reads coverage, assigns targets, merges branches, enforces levels.

Builders

One per component, each on its own branch, following the loop.

Reviewer

Has not seen the code being reviewed. Checks the hard rules. Any change to the judge needs reviewer approval.

Humans

Wrote the mission and the operating manual. Every other action is an intervention, logged in public.

02 · THE LOOP, EVERY ITERATION

  1. 01 Read the state GOAL.md, PROGRESS.md, coverage/, the board.
  2. 02 Pick one target Top Ready issue for this role and component.
  3. 03 Write the spec first Inputs, outputs, errors, upstream files.
  4. 04 Implement in Rust Fail loudly with MEGABASE_NOT_IMPLEMENTED.
  5. 05 Judge Side-by-side against the pinned official stack.
  6. 06 Keep or revert No regressions. Conformance must not fall.
  7. 07 Record PR, coverage, treemap, comments.

03 · THE JUDGE

Official Supabase runs next to Megabase.

Same pinned versions. Same requests. Status, headers that matter, and bodies are compared, with documented normalization for timestamps and IDs. Agents may build the harness. They may never change what it compares against.

04 · FAIL LOUDLY

Nothing silently wrong.

JSON
{
  "code": "MEGABASE_NOT_IMPLEMENTED",
  "component": "rest",
  "unit": "…",
  "message": "…"
}

06 · HARD RULES FOR AGENTS

  1. Rust only for in-scope code.
  2. Never modify vendor/ or judge/ on a feature branch.
  3. Never disable, skip or weaken a test to raise a score.
  4. No regressions.
  5. Fail loudly: HTTP 501 with a structured body.
  6. Credit the source in NOTICE and LICENSES/.
  7. No secrets, no production data.
  8. One iteration, one commit.

Total conformance = share of all differential tests where Megabase’s response is identical to Supabase’s.

07 · RUN IN PUBLIC ON GITHUB

Milestones are levels. Epics group units. Every change is a pull request. The board is the work queue.

Issue counts per column are filled at build time from the GitHub Project when that data is present. Today: —

Open the repository ↗