JJ Forge

JJ Forge is the reference build every platform we ship starts from: a multi-tenant Postgres schema with row-level security on every table, an agent scaffold, and a pipeline that was green before the first feature was written. You are not paying us to decide where the tenant boundary goes — that is settled, tested, and the same on your build as on the last one. What varies is your domain model, your workflows and your integrations.

1. 01Next.js App RouterReads in React Server Components, mutations in Server Actions with a Zod schema at the boundary. No provider key reaches a browser bundle.
2. 02Postgres with RLSEvery tenant row carries org_id. The triggers that derive it from the parent row and freeze it are written and tested, and attach as the first child tenant tables land. Policies are one indexed equality, deny by default, with a positive, negative and privileged test per table.
3. 03Event spineA mutation writes its row and emits a domain event; handlers subscribe. Each is idempotent on a natural key and dead-letters after five attempts, so a retry cannot bill twice.
4. 04Job workerWebhooks, embeddings and scheduled jobs run in Edge Functions as job_worker, never as service_role. pg_cron schedules them, and every webhook is recorded before it is processed.
5. 05Agent scaffoldAn agent is a registry row, a versioned prompt, a typed tool set and at least three golden eval cases. Autonomy is enforced by which tools exist, not by prompt wording.
6. 06Delivery pipelineA preview deploy per pull request, with lint, types, unit tests and the RLS suite as the merge gate. A new table without a policy test fails the build.