chore(memory): V1-2.3 four residual risks with their status

This commit is contained in:
bchanot committed 2026-11-01 21:46:37 +01:00
1 parent ff1b4959d7
commit bd65b81c41
1 file changed
+5 -1
+5 -1
View File
@@ -641,7 +641,11 @@ Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheet
- [x] Q4 `brk` bounded: RLIMIT_AS and argument filters on the verify child
- [x] Q5 throwaway sandbox account passwords generated per run
- [x] Q6 LRN-109 · Q7 docs · Q8 gates: check:all, sandbox fresh + 2 upgrades (pgTAP 1880, types, verify-e2e 10/10), avatar-e2e 5/5, test 87, e2e:shell 86; security PASS, MEDIUM null lease token fixed (3bfd6c8); verifier pending
- [ ] residual risks, open, tracked: header > 64 KiB → `resource_limit` instead of `caps`; object over the policy → `drawing_missing` instead of `size_mismatch`; §16.11 queue inventory owed before any DEV activation
- [ ] residual risk 1, open, tracked: frame header > 64 KiB (several hundred drawings named) → `verification.worker.resource_limit` instead of `caps` (verify_loop + sandbox case k assert current behaviour, not fixed)
- [ ] residual risk 2, open, tracked: object over the policy → failures `[caps, drawing_missing]`, never `size_mismatch` (verify_loop asserts current behaviour, not fixed)
- [x] residual risk 3, closed by proof: largest allowed input measured (child max frame passed; sandbox j: document + base 2 MiB, drawings 6 MiB, worker 156/191 ms)
- [x] residual risk 4, closed: sandbox throwaway password literal replaced by per-run random passwords (2a84e37); DEV seed passwords untouched
- [ ] §16.11 queue inventory (avatars, purges) owed by the owner before any DEV activation; not done, not assumed
- [ ] V1-2.4 wireframes (editor, review, admin entry) · V1-2.5 catalogue, admin space, rights, species, MFA · V1-2.6 editor level 1 · V1-2.7 preview, review, publication UI · V1-2.8 equine working copy and review preparation · V1-2.9 FR/EN acceptance and closure (owner checkpoints V1-2.3, V1-2.4, V1-2.6, V1-2.7, V1-2.8, V1-2.9 + each DEV operation of contract §16.11)
## Release readiness track (owner 2026-10-25, distinct from the functional roadmap; nothing here authorises a release or exposure)