A build and deploy platform for prototyping sites. Augur composes one or more spaces, each a separate git repo holding a self-contained design system and its prototypes, into a single static site with a shared overlay layer, and ships it to Cloudflare Pages.

• Spaces are repos. The deploy shell mounts each space as a git submodule at spaces/<id>; locally, any folder of space clones works via GV_SPACES_ROOT. A directory counts as a space when it has a space.json at its root. The default space builds at the site root; every other space serves under /<id>/. A space with adminOnly: true in its space.json is sealed behind the admin login.
• The build is a single script. node build.js walks every space, publishes only the contents of prototypes/ folders plus the space's galleries, generates the landing page and per-space indexes, and stamps a public /_build.json so collaborators can verify their commit is live. Internal files (research notes, anything outside prototypes/) are never published.
• An overlay worker runs on top. src/_worker.js adds a per-user login gate, review comments and pins, dev status chips, and live multiplayer canvas boards over the static pages. State lives in Cloudflare KV.
• Deploys are push-to-main, via a deploy shell. This engine repo deploys nothing itself. A separate private shell repo mounts the engine and the spaces as pinned submodules and holds the CI workflows, the user list and all secrets. Pushing the engine or a space repo fires a repository_dispatch that bumps the matching pin in the shell and redeploys, about a minute end to end. Collaborators only ever need their own space repo.
• Offline mode. npm run offline builds from editable sibling clones, runs the real worker locally, and hot-reloads in about a second. See CLAUDE.md for the full conventions.

git clone <this-repo>
cd augur
GV_SPACES_ROOT=/path/to/spaces node build.js  # any dir holding space repos (each with a space.json)
npm run dev                                   # build + serve locally

CI lives in the deploy shell repo — copy-paste workflows and a full instance recipe live in templates/. The shell needs a Cloudflare Pages project (with a KV namespace bound as COMMENTS for the overlay state) and three secrets: CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, and SUBMODULE_PAT (Contents:read on the shell itself + every private space repo; .gitmodules URLs must stay HTTPS for it to work). Each space repo needs AUGUR_DISPATCH_TOKEN (Contents:write on the shell) to announce its pushes. A shell may add AUGUR_PIN_TOKEN (Contents:write on itself) if it wants pin pushes to retrigger CI by themselves — the template workflows don't need it (they push with their own GITHUB_TOKEN and start the deploy explicitly).

Create a repo with a space.json and one or more <project>/prototypes/ folders — a design system is optional; plain self-contained HTML builds fine. (The UI calls these top-level folders "Projects" by default; a space renames the section via space.json projectsLabel.) Add templates/space-deploy-trigger.yml as .github/workflows/deploy-trigger.yml (point SHELL_REPO at your shell) and give it the AUGUR_DISPATCH_TOKEN secret. Grant SUBMODULE_PAT read access on the new repo. Then, in the shell: git submodule add <https-url> spaces/<id> and push. The space id comes from space.json, so the repo name is a free label.

Instances pin this engine and take updates by moving the pin (the shell's engine-bump.yml). Don't fork-and-patch it inside an instance, and don't carry engine edits in a shell or space repo — a patched instance stops taking upstream fixes cleanly, and every instance loses the fix you kept local.

If the engine is missing something, send it here — PRs are welcome (see CONTRIBUTING.md): fork to PR, not to deploy. Your instance then takes the fix by pin bump, like every other. Instance-specific behavior belongs in the shell's deploy.config.json; space-specific behavior in space.json.

MIT. See LICENSE.