docs(docs): V1-1 owner decisions N1-N9 and M1 as built
Contract: N4 voiding instead of deletion, N5 date constraints, N6 write budget per workspace under a lock, N7 effective-privilege wording and residual admin paths, N9 audit metadata limited to ids; M1 as-built notes and isolated-stack results (§8.1). SUPABASE.md §3.3 with the owner procedure to apply M1 on DEV without reset; backend architecture, test strategy, plan and CLAUDE.md lines.
This commit is contained in:
1 parent
7bf4fb6079
commit
0f8c9833cc
6 files changed
+237
-59
No files matched your search
@@ -354,8 +354,9 @@ ratified by the owner on 2026-10-25 (BDR-073): records attached to a
|
||||
workspace, one personal workspace per practitioner, cabinets later, no global
|
||||
client record shared between practitioners, no consents, grants, sharing,
|
||||
files or candidate matching. Contract and technical design:
|
||||
`V1-1_OWNERS_ANIMALS.md` (business decisions approved; the SQL, RLS and RPC
|
||||
design awaits the owner's validation before the first migration). Where the
|
||||
`V1-1_OWNERS_ANIMALS.md` (business decisions approved; architecture and N1-N9
|
||||
validated 2026-10-25, BDR-074; V1-1.1 workspaces migration written and tested
|
||||
in isolation, not applied to DEV). Where the
|
||||
text above differs (global clients, consents, grants, photo, files, deceased
|
||||
flow), the contract governs V1-1.
|
||||
|
||||
|
||||
Reference in new issue
Block a user