docs(docs): drop stale references to the removed SQL mirror and client gate

This commit is contained in:
bchanot committed 2026-10-28 18:14:10 +01:00
1 parent ef1f4b593f
commit a21866e25c
6 files changed
+11 -10

No files matched your search

+1 -1
View File
@@ -58,7 +58,7 @@ Conventions fixed now so every step follows them:
- UUID primary keys (`gen_random_uuid()`), `created_at` / `updated_at` with a shared trigger, soft delete `deleted_at` where the architecture names it.
- Enums as PostgreSQL `enum` types when the value set is closed by the business (report status, appointment status), `text` + CHECK when the set is expected to grow (document types).
- JSONB documents (`reports.current_document`, `anatomical_sheet_versions.content`) carry their own `schema_version` and are validated by the Rust core's contracts (`crates/core/src/domain`, since R2) at the application boundary and by a CHECK on `schema_version` in SQL. SQL re-checks only what publication needs (`private.sheet_document_issues`, BDR-032), with the same rule codes as the core.
- JSONB documents (`reports.current_document`, `anatomical_sheet_versions.content`) carry their own `schema_version` and are validated by the Rust core's contracts (`crates/core/src/domain`, since R2) at the application boundary and by a CHECK on `schema_version` in SQL. Since V1-2.1 the core is the only authority on the sheet document's rules: SQL keeps the structural guards (shape, schema version, size, species) and the declared status check at approval and publication, and publication rests on a server verdict (`V1-2_ANATOMICAL_SHEETS.md` §12.2, O22).
- Every table exposed to the browser: RLS enabled, no `USING (true)` policy for `authenticated`, no anonymous policy on core tables (§17.4).
## 4. RLS strategy