docs(docs): realign active docs on develop for P0
Roadmap section and step statuses in the plan, D-R9 Rust services in place of Edge Functions and a Node worker, platform roles per BDR-026, equine sheet draft-only, curation-only authoring until Step 17, OPEN_QUESTIONS statuses and conflict resolutions, dated snapshot notices on the Step 0 documents.
This commit is contained in:
1 parent
c71fafa3c5
commit
ac60b24267
12 files changed
+260
-92
No files matched your search
@@ -298,7 +298,7 @@ the decision lands; only the naming one is implemented in this document.
|
||||
| 3 | A new publication becomes the current version; older versions are **not deprecated automatically** and stay readable under the access rules. | Already the behaviour of `publish_sheet_version`; deprecation stays a manual act. |
|
||||
| 4 | Official sheets are **platform-owned**, administered by authorised accounts. | Already the model: `creator_user_id = null`, `is_official = true`, platform admins edit. |
|
||||
| 5 | Name anatomical findings apart from the observations typed during a report. | Finding category kind `observation` renamed **`consultation_reason`** (`dysfunction` / `consultation_reason` / `anamnesis` / `custom`). The report-side object keeps the name Observation. |
|
||||
| 6 | Server-side validation and integrity for every publication; the frontend is never a security boundary. | SQL already re-checks references, sizes and species. The full shape check (Zod) moves server-side before community publication: plpgsql shape rules or an Edge Function gate, decided at the community step. |
|
||||
| 6 | Server-side validation and integrity for every publication; the frontend is never a security boundary. | SQL already re-checks references, sizes and species. The full shape check (the Rust core's `sheet.check` since R2) moves server-side before community publication: plpgsql shape rules or a Rust service gate (Edge Functions retired, D-R9), decided at the community step. |
|
||||
| 7 | Account deletion handles dependencies and transfers explicitly (RGPD); no dependency may block the erasure of personal data forever. | Retention step (§16): published versions get their `created_by` / `published_by` anonymised through a dedicated system path (the immutability guard will allow that single transition), personal sheets are transferred or archived, `creator_user_id` keeps `on delete restrict` only as the backstop that forces the explicit path. |
|
||||
|
||||
## 6. Official equine sheet: import (Step 4b) and curation (Step 4c)
|
||||
|
||||
Reference in new issue
Block a user