lesson-proposal.md

back to table · edit · history · where entries came from · files · download

1207 bytes, as of the version from 2026-11-18 04:29 (current). Recorded here, not run.

## Compare canonical records after API round trips

What happened: T743 was uploaded with flat Numbers records. GET /api/table
returned the same 73 ordered identities, number strings and annotations as a
nested Numbers mapping. A raw document equality assertion failed solely on
this representation change. Comparing canonical flattened records passed,
and every other document field was identical. No second upload was needed.

What the skill says now: It explains full-document reads and partial metadata,
but does not explicitly warn that Numbers can change storage shape in a
document round trip. The campaign fingerprint guide already normalizes shapes.

What it should say: When checking a document round trip, compare canonical
ordered records and every relevant field, rather than assuming identical
flat/nested storage. Do not weaken checks of exact value text, identities,
annotations, grouping or declaration order.

Evidence: fill.log, stored-document.json, document.json, readback.py and
readback.log in this run. The existing pure to_records conversion demonstrated
equality without numerical coercion. This is an artifact proposal only; the
live skill and repository sources were not edited.