3
0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-18 22:25:44 +01:00

Answer architecture round 3: 0 🔴, 1 🟡 (0 misread); what a carry element shows recorded as part of the HTML contract, in the decision, at carryContent and in item 143

This commit is contained in:
2026-10-28 01:44:00 +01:00
parent c049f630ca
commit f5f8fa273b
3 changed files with 15 additions and 4 deletions
+9 -2
View File
@@ -526,8 +526,9 @@ and its issues and Actions are off. Push to GitHub only.
## The formats are API
2026-08-23, strict input 2026-09-01, content models 2026-09-16, the maintainer. Goal 1.
Valid while consumers store what the library emits.
2026-08-23, strict input 2026-09-01, content models 2026-09-16, the maintainer; what a carry
element shows 2026-10-28, the systems-architect. Goal 1. Valid while consumers store what the
library emits.
The emitted markdown and HTML are contracts. After 1.0: previously-emitted output parsing
differently, or not at all, is MAJOR; new syntax while old output still round-trips is MINOR.
@@ -536,6 +537,12 @@ container is the model, not the syntax — so giving a spelled node's model cont
taking it away, is MAJOR whatever ADF's own schema does. Input reads the canonical directive
spelling alone — spacing, key order, each value's spelling — since loosening it later is MINOR.
What an HTML carry element shows is part of that contract too. `htmlToAdf` refuses a carry element
showing anything but what `adfToHtml` shows for its node, so an edit there is refused rather than
lost (Goal 7). A change to what a carry element shows, in `src/html/carry-content.ts` or in the
`src/adf/shown-text.ts` it shares with portable markdown, makes HTML an earlier release wrote
unreadable: MAJOR after 1.0, and a `MIGRATION.md` entry before.
The error surface is a contract too; `README.md` §The errors states it to the consumer, and the
types in `src/result.ts` hold its shape.