# CONTRACT: V1-2.6 UX, owner ratification of the technical decisions recorded in the docs (2026-11-05) - REQUEST (owner brief « FAUNOSTEO — V1-2.6 UX — Ratification des décisions techniques », 2026-11-05): record the owner's answers to T11, T16, T2/T3, T4, T5, T9/T10 and T12 in `docs/development/V1-2-6_UX_DECISIONS.md` and the associated documents; update risks, dependencies, blocking criteria and tests; add the wasm measuring learning to the learnings registry, its wording checked against the size test really in the repository; independent review; exact verdict and remaining blocking points. Documentation only; stop at the final technical checkpoint. The validated UX choices are not reopened. - OWNER ANSWERS (summary of the brief): - T11 approved: stop the complementary trials of the old UX; keep the anomalies and the untested items in tracking; never declare the old V1-2.6 fully validated. - T16 conditional deferral: defer curve handle editing only if the audit confirms that no existing curved annotation and no journey available today needs it; guarantee exact geometry; prevent any destructive conversion; record full curve editing in an identified future lot. - T2/T3 agreement in principle, conditional on proofs: optional fields in schema v2, omitted when absent, never serialised as null by default; fill opacity 10 to 100 %; controlled widening of the snapshot reader; demonstrate effects on fingerprints, Rust, SQL, PDF, worker, N-1 reader, R3/R4 and BDR-068; document that the old application cannot be returned to after the new fields are written; never call it full backward compatibility. - T4 no residual gap allowed: define the fixed-category checks in the core and at the appropriate server boundaries for save and publication; do not enable writing the new model before the necessary checks exist; progressive rollout or functional lock if needed. - T5 historical preservation: keep ids, names, colours, particular annotations and fingerprints of the historical equine versions; role adaptation only on a working copy; test the conversion without mutating the originals. - T9 explicit choice when an SVG is replaced: keep positions only if the framing is compatible and the checks pass; reposition when the operation is safely supported; cancel without any change; no approximate automatic transformation. - T10 automatic access: prefer a system navigation type distinct from the visible anatomical taxonomy; check the existing schema constraints before choosing an internal id or category; never categorise it arbitrarily as Os, Articulations or Vertèbres. - T12: principle of one versioned copy kept; final legal text, source and validation still to be supplied; U7 delivers no invented or unapproved normative text. - Wasm learning: margin measured with the exact method of the budget test (Node gzipSync with the same parameters), never a system gzip; reference 592 143 B for a limit of 600 000 B, margin 7 857 B; measure after each core change; never raise the ceiling silently. - ACCEPTANCE CRITERIA: - K1 T11: DECISIONS records the approval; level 1 explicitly not declared validated; the anomalies and untested items are listed with their sources and tracked in `.claude/tasks/TODO.md`. - K2 T16: the audit evidence is present and exact (counts and file:line hold in the code); the guarantee of exact geometry and of no conversion is written, with tests; any limit of the audit is stated rather than hidden; the future lot is identified in TODO.md with its dependency rule; stale « U9 in V1-2.6 » wording is gone outside historical records. - K3 T2/T3: the serialisation rule, the 10-100 range and a bounded definition of the snapshot widening are written; a proof is listed for each of fingerprints, Rust, SQL, PDF, worker, N-1, R3/R4, BDR-068; the impossibility of returning to the old application is documented; no text calls the change full backward compatibility (or equivalent) without that qualifier. - K4 T4: checks are defined in the core and at server boundaries for both save and publication; no residual gap is accepted silently (any remaining choice is stated as an open owner question); writing the new model is gated on the checks being live (order or lock written). - K5 T5: the preservation list, the working-copy-only rule and a conversion test that proves the originals unchanged are written. - K6 T9: the three actions with their conditions are written; no automatic or approximate transformation remains anywhere in the docs. - K7 T10: the schema constraints are checked with evidence before a choice; the choice is a navigation type or internal category outside the visible taxonomy; nothing assigns the access to Os, Articulations or Vertèbres; an unratified part is stated as open. - K8 T12: U7 is blocked until the text, its source and its validation exist; no normative wording is written. - K9 The learnings registry holds the wasm entry, written through `memory.sh`; its wording matches `packages/core-wasm/tests/size.test.ts` (call, parameters, file, limit, comparison) and the figures. - K10 Risks, dependencies, blocking criteria and tests are updated and consistent with K1-K9. - K11 No contradiction across the five docs, TODO.md and BDR-100 (superseded recommendations are marked as withdrawn, not left active). - K12 Scope: the change set touches only the FILE SCOPE; no validated UX choice is reopened. - FILE SCOPE: `docs/development/V1-2-6_UX_{DECISIONS,COMPATIBILITY,TESTS,RISKS,PLAN}.md`, `.claude/tasks/TODO.md`, `.claude/memory/{learnings,decisions,journal}.md` (through `memory.sh`), this contract. - OUT OF SCOPE: any change under `crates/`, `apps/`, `packages/`, `supabase/`, `scripts/`; SQL; worker; Supabase DEV; contract amendments of U0 (`V1-2_ANATOMICAL_SHEETS.md`, the level-1 contract, `.claude/rules/`); merge; deploy; V1-2.7; any implementation sub-step. - ABANDON: if a criterion needs a change outside the file scope, stop and report.