docs(docs): V1-2.2 RUST.md §12, contract decisions, core pointers

RUST.md §12 records the authoring core, its proofs, measures and
residual risks. The contract records the owner's V1-2.2 answers
(§17.4): editor exports supplied by the owner, the strict-parse code,
the draft load rule; CLAUDE.md and the sheet-model rule point to it.
This commit is contained in:
bchanot committed 2026-10-29 13:14:23 +01:00
1 parent 8ae756534c
commit 741c25c464
4 files changed
+144 -5

No files matched your search

+21 -3
View File
@@ -1041,7 +1041,8 @@ Four stages, each a superset of the previous:
| Rule | Submit | Approve | Publish | Code |
|---|---|---|---|---|
| Strict parse and the 19 error codes | yes | | | `verification.validation.*` |
| Strict parse of the document and, for a derived version, of its base (§6.5; owner decision 2026-10-29) | yes | | | `verification.integrity.document`, `verification.integrity.base` |
| The 19 error codes | yes | | | `verification.validation.rules` |
| Caps of §1, all of them | yes | | | `verification.validation.caps` |
| Every annotation has a geometry | yes | | | `verification.validation.no_geometry` |
| Every reachable drawing present, size and sha256 equal to its row, read without removal | yes | | | `verification.integrity.*` |
@@ -1058,7 +1059,7 @@ Four stages, each a superset of the previous:
| Species active and other than `other` | | | yes | `publish.species.inactive`, `publish.species.other` |
| Caller capability (E, V, P) and `aal2` | yes | yes | yes | `rights.capability`, `rights.mfa` |
- The rules of the first five lines come from the stored verdict. SQL checks
- The rules of the first six lines come from the stored verdict. SQL checks
relations, states, rights, separation, the verdict's structure (§6.4), and
the declared defensive check of statuses on the stored document (§12.2).
- Shown, never blocking: uncited elements, the two warning codes, the number
@@ -1304,6 +1305,9 @@ The page reads the file with the core SVG reader before anything is stored.
| Any other removal (editor metadata and namespaces, `data-*` attributes, `<style>` elements, `class` or `style` on the root, ids outside the grammar, unsupported elements such as `symbol`, oversized `title` or `desc`) | cleaning offered: « Nettoyer et utiliser cette version », after the composed preview of the cleaned drawing and one confirmation; a removed `<style>` element is named, since the `class` attributes it styled then render unstyled |
| No removal | used as is |
- An oversized `title` or `desc` is a removal for the cleaning only: the reader
of stored drawings refuses such a file whole (`too_complex`), so it reaches
Storage only cleaned (V1-2.2).
- The classification and the cleaning are core functions (V1-2.2), tested on
committed vector-tool exports (tool and version named in the fixture) and
on the hostile corpus; a property test proves that cleaned output reads back
@@ -1396,7 +1400,11 @@ A drawing never blocks authoring: only the round waits for its verdict.
`not_found_or_denied`, `drawing_missing`, `drawing_hash_mismatch`,
`fingerprint_mismatch`, `invalid_document`, `caps`, `core_unavailable`,
`unavailable`. A draft with integrity errors previews with its issues and no
fingerprint.
fingerprint. For a draft, a caps excess and a referenced drawing that was not
given are reported in the state, never a load failure; `caps` and
`drawing_missing` refuse a published or deprecated version only (owner
decision 2026-10-29). A hash mismatch and an unreadable document refuse every
mode.
- `LoadedSheet` (the report editor's sheet) keeps its mandatory migration map;
`archive::SheetStatus` is not extended; a deprecated version previews like a
published one with a « retirée » mark. The readers of user data
@@ -2272,6 +2280,16 @@ checkpoint `2af61e7`:
| M7 | The Git fixture is accepted for the V1-2.1 upgrade rehearsal (sha256 equal to the DEV metadata's; bytes, metadata and relations before and after); no DEV Storage read, so the live DEV object's integrity is not demonstrated | §12.3, §16.2 |
| Size | The SQL check follows the contract's measure, the UTF-8 bytes of the JSON text; the binary `jsonb` size is not the measure; the cap stays 2 MiB | §12.2, M5 |
### 17.4 V1-2.2 decisions (owner, 2026-10-29)
Asked before the code of V1-2.2, on the brief « Autorisation de démarrer V1-2.2 »:
| Item | Decision | Where |
|---|---|---|
| Vector-tool exports | The owner supplies the editors' exports (Inkscape, Illustrator, Figma, Affinity) under `crates/core/tests/fixtures/svg/exports/owner/`; the cairo and ImageMagick exports of the development machine are committed meanwhile, tool and version in the file name | §9.2, §15 |
| Strict-parse code | `verification.integrity.document` (and `.base` for the base), as §6.5 files it; the 19 rule errors are `verification.validation.rules` | §6.5, §6.7 |
| Draft load | caps excess and missing drawings reported for a draft, refused for a published or deprecated version | §10 |
---
## 18. Documents touched by V1-2.0