docs(docs): compatibility record states SQL structure-only and the N-1 states

This commit is contained in:
bchanot committed 2026-11-23 00:20:26 +01:00
1 parent 8ff2c2ce15
commit 3591be48f7
1 file changed
+20
@@ -40,6 +40,8 @@ digest would change: that serialisation is forbidden and pinned by tests.
Under T10 option B (ratified, BDR-101), the automatic access adds, on demand, one internal category
`cat-access` with role `navigation`: an ordinary `{id, name, color}` category for every reader before U6 once the
role is stripped (§4).
This is the route A form before 2026-11-22; the reserved id `cat-access` below supersedes it, and the `navigation`
role arrives only with U6, if kept.
2026-11-22 (owner, detail views): the internal category of detail-view accesses is marked by its reserved id
`cat-access`, with no key and no schema bump (documents stay plain v2, no SQL migration). The core creates it when
@@ -49,6 +51,24 @@ core's (editor refusal plus verdict `category.id.duplicate`), not SQL's. N-1 app
it (census, Task 4). U6 still brings the `role` key for the fixed categories with its write lock, and decides
whether `navigation` stays in the role list.
SQL reads categories as structure only (`check_document_structure`, `20261028110000:411-441`, the business mirror
dropped at `:139-144`; correction of 2026-11-22: earlier board revisions said SQL also checked uniqueness), so no
migration is needed.
States of an N-1 application on a sheet carrying `cat-access`, and what the new version does:
| N-1 action | New version |
|---|---|
| Reads `cat-access` as an ordinary category | shows the fixed label |
| Renames it | the fixed label is shown anyway |
| Recolours it | accesses take the new colour |
| Files a point or zone in it | shown under « Accès aux vues détaillées »; can be given an ordinary category back |
| Removes it while an access uses it | refused by validation (`annotation.category.missing`), nothing lost |
| Removes it once empty | allowed; the core recreates it at the next access |
| Draws an access choosing any category | works whatever the category |
None of these blocks reading, saving, verification or the bilan.
Document kinds used below:
- **Old**: any document saved or published before U6 (equine historical, equine working copy, sandbox sheets, seed,