docs(docs): V1-1 contract approved, technical design for review
Owner ratified the V1-1 business decisions. The contract now records them as approved, adds the nomenclature, the proposed SQL schema, RLS, RPCs, technical limits, journeys and test plan, and lists the choices left for the owner. OPEN_QUESTIONS, plan, DOMAIN_MAP, README and CLAUDE.md follow.
This commit is contained in:
1 parent
5502617193
commit
a6346105f1
7 files changed
+1061
-381
No files matched your search
@@ -9,8 +9,8 @@ Docker sandbox; 11 pgTAP files under the flat `supabase/tests/`. The locations
|
||||
`apps/app/tests/components`, `apps/app/tests/integration`, `apps/app/e2e`,
|
||||
`supabase/tests/{db,rls}` and `supabase/seed/test/` in §1 and §3 are planned,
|
||||
not created; the real-stack e2e lives in `packages/supabase/tests/e2e`. No
|
||||
real-browser suite exists yet (TODO RR-8; V1-1 contract §8.4 proposes the
|
||||
first one). No CI has ever run (BDR-047): "CI" in the tables means the
|
||||
real-browser suite exists yet (TODO RR-8; V1-1 contract §12.5 proposes the
|
||||
first one, decision D14). No CI has ever run (BDR-047): "CI" in the tables means the
|
||||
prepared workflow.
|
||||
|
||||
## 1. Layers
|
||||
|
||||
Reference in new issue
Block a user