docs(docs): V1-2.6 T17 ratified, vertebral regions fallback entry

This commit is contained in:
bchanot committed 2026-11-06 11:12:17 +01:00
1 parent 452a346f17
commit 439cabd09e
5 files changed
+17 -12

No files matched your search

+7 -4
View File
@@ -24,7 +24,7 @@ was authorised on 2026-11-05; every later sub-step starts only on a new explicit
| T14 | Multi-tab notice | not asked | open, follow-up | none |
| T15 | « Annuler » wording | brief U0: « Annuler la dernière modification » for the history; « Abandonner » or « Abandonner les modifications » for a form | ratified | none left to decide; U1 applies it |
| T16 | Curve handle editing | deferral only if the audit confirms it; exact geometry; no destructive conversion; identified future lot; brief U0: deferral kept, existing geometries checked before any activation of the new model, no DEV access during U0; « Remplacer par un polygone » explicit, validated, old path kept until success, undoable | ratified: deferred to the curves lot | none in V1-2.6; the path count before the new model is activated on an environment and before U6 or U8 reaches any environment beyond the throwaway sandbox |
| T17 | Vertebral regions entry without a vertebra role | not asked; wording presented at the U0 checkpoint, no answer invented | open | U6 (not U0) |
| T17 | Vertebral regions entry without a vertebra role | brief U1 (2026-11-06, BDR-102): fallback « Régions vertébrales » entry in Annotations when no category carries the role `vertebra`; once a Vertèbres category exists, the regions are configured from it, never in two places | ratified | none left to decide; U6 builds it |
## Implementer decisions (recorded at U0 in contract §17.12, no owner question)
@@ -379,8 +379,11 @@ level-1 text stays as written (precedence rule of the level-1 contract header).
| Region code read-only after creation | 09 (not legible) | C5: read-only after creation | U6 planning |
| Category of an access placed by hand after U6 when annotations overlap | 08 | T10 section above | U6 planning |
## T17 · Vertebral regions entry without a vertebra role (open, blocks U6, not U0)
## T17 · Vertebral regions entry without a vertebra role (ratified)
- Facts: board 09 opens the regions from the Vertèbres category; the equine working copy has no role before V1-2.8.
- Recommendation: when no category carries the vertebra role, the Annotations panel keeps a « Régions
vertébrales » entry; when one does, the entry sits under it as on board 09.
- Owner answer, brief « Autorisation de U1 uniquement » (2026-11-06, BDR-102): when no category carries the role
`vertebra`, Annotations offers a fallback entry « Régions vertébrales »; when a Vertèbres category exists, the
regions are configured from that category, with no duplicate entry. The new category model is not built before U6.
- Effect: U1 places the existing regions editor in Annotations as that entry (no role exists before U6, so it is the
fallback case); U6 adds the vertebra-role path of board 09 and removes the entry when the role is present.
+3 -3
View File
@@ -397,7 +397,7 @@ seed untouched, axe, keyboard and touch journeys, sandbox and worker runs.
Each sub-step lists the decisions it consumes; the single table is in `V1-2-6_UX_DECISIONS.md` and the blocking
criteria in `V1-2-6_UX_RISKS.md`. Answered 2026-11-05: T2/T3 (with conditions), T4 (with both SQL checks), T5
(history and new-sheet defaults), T9, T10 (option B), T11, T12 (principle), T15, T16. Still open: before U5 or U6,
T1 only if a measure exceeds the budget; before U6, T17; before U7, the T12 text; at V1-2.8, T6; T14 a follow-up.
T1 only if a measure exceeds the budget; before U7, the T12 text; at V1-2.8, T6; T14 a follow-up.
---
@@ -565,7 +565,7 @@ Common rules for every sub-step that touches code:
automatic access with the navigation category `cat-access` (T10 option B, ratified), built on the U5 overlap
list and created only when it is empty; board 09: regions open from the
vertebra-role category, the region picker of a zone filtered to the vertebra-role category's annotations (page
filter, no rule), staged « Appliquer » with the error count; fallback per T17 when no category has the role (the
filter, no rule), staged « Appliquer » with the error count; fallback « Régions vertébrales » entry per T17 (ratified 2026-11-06) when no category has the role (the
equine copy before V1-2.8). `docs/ANNOTATION-RENDERING.md` amended first.
- Files: core `domain/sheet/schema.rs`, `create.rs`, `edit.rs`, `report.rs`, `verdict.rs` (gate marker in
`verified_with`), `anatomy/layer.rs` (`layer()` 85-102, `Context::point` 242, `zone_visual` 297-304),
@@ -576,7 +576,7 @@ Common rules for every sub-step that touches code:
(spec table), `RUST.md`, `DEPLOY.md` (order, write lock).
- Dependencies: U3, U5 (U5 brings `annotations_in_rect`, the overlap list the automatic access needs, after U4's
rectangle); T2 and T3 (ratified with conditions), T4 (ratified with both SQL checks), T5 (ratified), T10 option B
(ratified), T17 (open: blocks U6).
(ratified), T17 (ratified 2026-11-06, BDR-102).
- Rust ops: schema fields, edit refusal kinds, verdict-tier issues, layer reading, snapshot stripping, verdict
marker.
- Tests: `V1-2-6_UX_TESTS.md` U6; each row of `V1-2-6_UX_COMPATIBILITY.md` is an acceptance line, and §8 lists the
-1
View File
@@ -57,7 +57,6 @@ Each line holds until its condition is met; nothing in this list authorises a su
| U1 and every later sub-step | all code | a new explicit owner authorisation each (U0, documents only, authorised 2026-11-05) |
| T2/T3 proofs (COMPATIBILITY §8) | writing a key outside a test | every proof green and reviewed |
| T4 checks live on the environment | the U6 write lock | U6 migration (withdrawal, core gate, publication check, save check, rules epoch) first, then the U6 worker |
| T17 answered | U6 (regions entry) | owner answer |
| T1 | U5 or U6 only if a measure exceeds 600 000 B | owner decision on the measured figure |
| T12 text | U7 | owner supplies the FR and EN text, its source and its validation record |
| T16 database count | activating the new model on an environment; U6 or U8 on any environment beyond the throwaway sandbox | read-only count of paths recorded and zero (non-zero reopens T16) |
+1 -1
View File
@@ -109,7 +109,7 @@ every path's `d` text byte for byte through the sub-step's journeys, save and re
| Write lock (T4) | on a sandbox with the old worker image and the U6 SQL: a role-less draft's round never opens (gate); a save stripping the roles of a role-bearing draft refused (save check); the U6 app on a stack without the rules epoch writes no key and creates no new-model sheet; publication and approval refused outside the fixed model even with a forged passed verdict (pgTAP) |
| Flipped suites | `sheet_verdict.rs:39-52`, `80-90`, `sheet-verification.sandbox.ts:27`, `209-211`, `373`, worker fixtures and `tests/verify_loop.rs` moved to converted in-memory copies, each change mapped in the commit message; seed unchanged |
| Navigation access (T10 option B, ratified) | `cat-access` with role `navigation` created on demand in the same core-built batch as the view and its access, only when the overlap list is empty; an edit that gives, changes or clears `navigation` refused; a second `cat-access` insertion refused; absent from the category panel and the pickers; an observable annotation in it and a second navigation category refused (edit) and reported (verdict); its role stripped from snapshots, N-1 reads the category |
| Unit and E2E app | board 07 locks (no delete, name read-only, role badge, « Couleur d'origine »); opacity slider and field synchronised, commit on release; board 09: regions from the vertebra-role category, picker filtered, staged « Appliquer (n erreurs) »; fallback entry when no category has the role (T17); board 08 automatic access |
| Unit and E2E app | board 07 locks (no delete, name read-only, role badge, « Couleur d'origine »); opacity slider and field synchronised, commit on release; board 09: regions from the vertebra-role category, picker filtered, staged « Appliquer (n erreurs) »; fallback « Régions vertébrales » entry when no category has the role, no duplicate entry once a Vertèbres category exists (T17); board 08 automatic access |
| Acceptance journey | a new non-equine sheet with the new UX (drawing, rectangle view, automatic access, points, zones, findings, custom opacity), saved, submitted, worker verdict passes, round `open`; its PDF exported, reopened by the app and read by N-1 (archive kept); the same journey with the roles stripped by a direct save: refused at save, the stored draft unchanged; a draft that never carried roles saves, its verdict fails and no round opens; no publication in either case |
| Recovery | a copy taken before an opacity edit restored after reload; conflict journey on a role-bearing category; « Garder ma version » with a role-less document: on a sheet whose stored draft carries roles, the save is refused by the declared check; on a role-less sheet it saves and shows the issue and the repair |
| Security | fresh review: no path writes the keys into an envelope; the SQL checks are exactly those declared under T4 and O22 as amended at U0 (contract §12.2: the save check and the approval and publication check, fixed-category invariants only); the core gate checks a version marker only |
+6 -3
View File
@@ -2864,15 +2864,18 @@ reopens T16.
(§7.4); U7 blocked until the owner supplies the FR and EN text, its source and
its validation record; no normative wording before that.
**Vertebral regions (T17, owner 2026-11-06, BDR-102).** With no category
carrying the role `vertebra`, Annotations offers a fallback « Régions
vertébrales » entry; once a Vertèbres category exists, the regions are
configured from it (board 09), never in two places.
**Wording (T15).** « Annuler la dernière modification » names the history
command (header button, tooltip and accessible name, the toast after a
gesture); « Abandonner » or « Abandonner les modifications » names leaving a
form or discarding unsaved changes (level-1 C11).
**Open.** T1 (only if a measure exceeds the 600 000 B wasm budget), T6
(V1-2.8), T14 (multi-tab notice, follow-up), T17 (the vertebral regions entry
when no category carries the vertebra role; blocks U6), the T12 text (blocks
U7), and the category of an access placed by hand after U6 when annotations
(V1-2.8), T14 (multi-tab notice, follow-up), the T12 text (blocks U7), and the category of an access placed by hand after U6 when annotations
overlap the rectangle (a U6 design point, DECISIONS T10).
**Implementer decisions** (no owner question): T7 both keys stripped from