Engineering
Engineering
How the system is built — repos, the Payload data layer, the bridge, and the deployment doctrine.
The three repos
| Repo | Stack | Cloud Run service |
|---|---|---|
screver-ma-app | Next.js 15 + Payload 3.77 + Postgres 17 | screver-ma-app[-staging] |
screver-ma-ai | Express + Anthropic SDK | screver-ma-ai[-staging] (internal) |
screver-ma-docs | Fumadocs (Next.js) | screver-ma-docs[-staging] |
Each repo has its own git, its own .github/workflows/ci-deploy.yml, and deploys independently.
How v1 is wired
The full clickable prototype is ported into screver-ma-app as a single client bundle (see
the three repos). The core is wired to Payload:
- A reviewer's Accept / Modify / Reject writes a real evidence-grade Parameter (with supersede) and an append-only AuditEvent, signed by the logged-in Payload user.
- This runs through a best-effort bridge (
window.SCREVER): if Payload is unreachable, the UI falls back to a fixtures-only demo so the showcase never breaks.
The Wizard chat calls the screver-ma-ai service (real claude-sonnet-4-6, grounded on a
bundled corpus) via the app's /wizard-api proxy, keeping the Anthropic key server-side.
Read next
- Local development — run all three locally.
- Deployment — Cloud Run, secrets, and the hard-won learnings.
- The three repos — what's inside each.