@domandigital/craft 0.21.0 → 0.22.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @domandigital/craft
 
+## 0.22.1
+
+### Patch Changes
+
+- 68f65c3: <!-- copy-ok: names the phrases the release starts catching --> craft learns from Eunice Ordor's design and copy reviews (catalogue 2026.10.5). Her 73-note review of the new Doman Digital site is the first record in a reviewer corpus (`reviews/` in the repository; the schema test keeps each record to `design-review.schema.json`), and CHARACTER.md writes up the principles it teaches. `design-review.schema.json` gains optional fields for a reviewer's own record: `reviewer`, `date`, `source` and `rulings` on the review, and `source`, `verdict`, `founderRuling`, `principle` and `tells` on a note; `REVIEW_VERDICTS` is exported. Two new review-tier tells: `hero-cta-pair` (source and rendered) reports two buttons side by side in a hero, found in 140 of 140 null-build heroes, and `confession-line` reports copy that scopes a business by what it has not done or will not do ("What this is and is not", "we have not yet built", "our experience so far is one practice"). `plain-english`, already blocking, now covers the whole family the founder banned on 20 October 2026: bare "plainly" and "in plain terms/language/words", with licence text ("plainly marked") let through. `review-phrase` adds "plain" as a self-description ("a plain recommendation").
+
+## 0.22.0
+
+### Minor Changes
+
+- 3902169: The every-viewport measure counts phone screens to the footer (DOM-1052, part of DOM-772): page height at 375 x 667 over 667, with lazy images loaded. `screens` sets a length budget per route, route pattern or prefix (`{ "/": 6.5, "/services/*": 6, "/areas/[town]": 5, "*": 9 }`, the most specific wins), on `measureViewports`, `measureRoute`, `measureSite` and `viewports.json`. A route over its budget fails a new `screens` check ("page too long for a phone"), baselined like the others; with no budget the count is only reported. `ViewportsResult.screens` and the measured file carry the count, `craft viewports` and `craft phone-first --measured` print it for every route, and `screenBudgetFor`, `checkScreenBudgets` and `formatScreens` are exported. The Bellerose home page ran 12.7 phone screens against a target of 6.5.
+
 ## 0.21.0
 
 ### Minor Changes

package/CHARACTER.md

@@ -632,6 +632,135 @@ back as `change`, ask for what is `hold`, find out what is `gather-evidence`,
 and leave what is `no-change`. When a note names something that was not
 inspected, look before you act on it.
 
+### Eunice's review of the DD site, 2026-10-19
+
+Eunice Ordor reviewed the preview of Doman Digital's own new site on Pastel
+(canvas 986559) on 18 and 19 October 2026: 73 comments across the home,
+services, work, Sensphere case, clinics, who-we-help, process, pricing, plans
+and contact pages. The whole review is kept, note by note, in
+[`reviews/eunice-ordor/2026-10-19-dd-site.json`](https://github.com/Doman-Digital/dd-packages/blob/main/packages/craft/reviews/eunice-ordor/2026-10-19-dd-site.json)
+in the repository:
+her words as she wrote them, what she proposed, what was done with it, the
+founder's ruling where one was needed, and the principle each note teaches. The
+founder went through it on 20 October 2026. As in "Where it came from" above,
+four things are kept apart.
+
+#### What she saw
+
+Twelve notes are praise, and they are a record of what to keep: the structure
+and type, the four routes in, the who-we-help page ("a site that reads as a van
+roof"), the Chair and Blade case, the six-step process and the responsibility
+matrix. The rest name problems. These matter beyond this one site:
+
+- Two equal buttons in the hero (#5), and again on the process page (#36).
+- Confession lines: "What this is and is not", "We have not yet built and
+  run...", "Our clinic experience so far is one practice" (#8, #13), and a
+  defensive caveat under the clinic questions (#10).
+- Summary pages that send the reader elsewhere for the substance: services
+  cards that are a line of nouns and a link (#66 to #69), a homepage case card
+  with none of the case's proof (#19), a pricing page that charges £95 and £165
+  a month and never says what either buys (#40, #48), and a /work page where
+  nothing says we still run any of it (#57).
+- Every /work line states the problem and leaves the result on another page
+  (#56).
+- Tiers that make the same promise at two volumes, so the extra £1,000 reads as
+  better writing (#39).
+- A price that looks steep until the maths is shown: £165 a month is £95 of
+  care and £70 of website (#43).
+- Closed lists where the work is open: the hero sub-line and route 3 narrowed
+  to bookings and enquiries (#2, #6, #25).
+- A page that contradicts itself: the Sensphere form said both that enquiries
+  reach the inbox and that details stay out of one (#15), and a process step
+  said "paid" for a product that had been retired (#22).
+- On a phone, the hero image crops badly (#55).
+
+#### What she proposed
+
+Specific wording for most notes, and three larger changes: a hero slideshow of
+client systems (#3), a call to action after several sections (#50, #51, #70),
+and a social media card (#72). Her diagnoses were nearly all right. Her wording
+often used the patterns COPY.md blocks. Four of her comments blocked at
+<!-- copy-ok: quoting the reviewer's draft line -->
+catalogue 2026.10.4 ("No licence, no lock-in" in #42 is one), and eight do once
+the plain-English family is widened.
+
+#### The founder's rulings, 20 October 2026
+
+- One button in the hero and on each closing section.
+- On a phone the first screen is ours: the headline, the sub-line and one
+  button. Another client's brand never opens it. The slideshow is declined
+  (#3).
+- No confession lines, no "what we are not", and nobody declined in advance.
+  It is an open shop: be honest by being precise, keep it open-ended, and stop
+  being absolute.
+<!-- copy-ok: naming the banned adverb -->
+- The adverb "plainly" and its kin are banned, with "plain English".
+- Cut "Our clinic experience so far is one practice" (#8). On the clinics page
+  keep "Built and run by us", and describe what Sensphere is: a growing
+  practice whose clinicians work remotely (#13).
+- A testimonial (#9) is reworded only once its author approves the new words.
+- Held for their own decisions: e-commerce as a sector (#27), a clinic
+  subscription with its own price (#49), response times (#54) and social media
+  (#72). Verqan stays off /work (#59). Quarterly packs are declined for the
+  site (#53).
+
+#### The principles
+
+Each id is what a note's `principle` field names in the record.
+
+- `open-shop`: precise, never confessional or absolute. Scope is shown by
+  exact claims ("the portal we run for Sensphere"), and a contractual fact is
+  said as what the buyer gets. `confession-line` reports the shapes for
+  review.
+- `summary-pages-carry-substance`: a page that summarises carries a sentence
+  of what happens, so nobody has to click away to learn what we do.
+- `problem-then-result`: every case line ends on the result, from the proof
+  ledger, or on a description of what now happens.
+- `one-hero-cta`: one button in the hero and on each closing section, with the
+  second route as a text link. `hero-cta-pair` reports the pair.
+- `text-links-not-cta-bands`: where a section needs a next step, a text link
+  at its end answers "what next", and the page keeps one closing button.
+  `cta-band-stock` already reports the band.
+- `tiers-by-what-the-site-carries`: each tier names a different business need
+  (one service and a form; several services, comparison and booking), never a
+  bigger version of the same promise.
+- `show-the-price-maths`: where a price looks steep, show the split that makes
+  it fair (£95 of care plus £70 of website), and put the commercial model where
+  the buyer reads.
+- `lists-as-pattern-examples-invitation`: name the pattern, give examples, then
+  invite the case we have not met. A closed list of four reads as a menu.
+- `first-phone-screen-is-ours`: the first screen on a phone is the business's
+  own headline, line and button. A client's brand, however good the work, comes
+  after it and is framed as our work.
+- `no-self-contradiction`: read a page against itself before it ships. Two
+  lines that disagree cost more trust than either line earns.
+- `the-work-continues`: the site sells a relationship that carries on, so a
+  case, a step or a summary says what we still run.
+
+#### The counter-lesson
+
+Her diagnoses beat Claude's defaults. Claude's first pass on this review would
+have kept the "What this is and is not" sentence, the two hero buttons, the
+noun-list service cards and three proof numbers in a row. Each is a default
+craft names (`confession-line`, `hero-cta-pair`, the summary-card pattern,
+`stats-row`). Where the question is "does this read as decided and generous to
+the buyer", she was right. Where it is "is it true, and is it allowed", the
+proof ledger and the house rules held: she asked for promises that are not
+live yet (#53, #54, #72), and her replacement wording goes through copy-check
+like anyone's. A reviewer's diagnosis is taken on its merits; her
+words are copy, and copy is checked.
+
+#### Feeding later reviews in
+
+Every later review, hers or another reviewer's, goes through the
+`reviewer-intake` skill in claude-kit: pull the canvas, keep each note whole,
+classify it, check its facts against the proof ledger, brand facts and Linear,
+write the record under `reviews/<reviewer>/`, and propose tells or fixtures for
+what recurs. `src/__tests__/reviews.test.ts` holds each record to the schema
+and to this file, and fires every tell a note taught on the words it flagged.
+See [reviews/README.md](https://github.com/Doman-Digital/dd-packages/blob/main/packages/craft/reviews/README.md);
+the corpus stays in the repository and is left out of the npm package.
+
 ## Declaring an exception
 
 Doman Digital's own brand is violet. A hue rule with no way to say so flags the
@@ -1341,7 +1470,7 @@ Generated from the package. Run `pnpm --filter @domandigital/craft run docs`
 after changing an entry; a test fails until you do.
 
 <!-- craft:catalogue:start -->
-Catalogue version `2026.10.4`, 72 tells.
+Catalogue version `2026.10.5`, 74 tells.
 
 | Id | Gen | Surface | Severity | Tell | Why it is a default |
 | --- | --- | --- | --- | --- | --- |
@@ -1360,6 +1489,7 @@ Catalogue version `2026.10.4`, 72 tells.
 | `cream-palette` | 2 | source + rendered | warn | Cream ground | Once white-and-violet was named, models moved to a warm off-white: parchment, linen, oat. It reads as 'tasteful' in the same way everywhere. |
 | `italic-serif-display` | 2 | source + rendered | warn | Italic serif display | A serif heading with one italic word ('Beauty, reimagined') is the second wave's signature move. |
 | `hero-eyebrow-chip` | 2 | source + rendered | warn | Eyebrow chip above the hero | A small bordered pill ('New · Now booking') above the headline is in almost every generated hero. |
+| `hero-cta-pair` | 1 | source + rendered | warn | Two buttons in the hero | A filled button beside an outline or ghost one ('Get a free quote' / 'See our plans') is in 140 of 140 heroes Claude builds for a brief. Two equal asks make the visitor choose before they know anything, and say nobody decided what the page is for. |
 | `icon-tile-stack` | 2 | source | warn | Icon in a tinted tile | A library icon in a soft rounded square, stacked above a heading, is the stock card header. |
 | `bento-grid` | 2 | source | warn | Bento grid | Mixed-size tiles in a grid became the default 'features' layout of the second wave. |
 | `radial-spotlight-glow` | 2 | source + rendered | warn | Radial glow | A soft blurred blob or radial spotlight behind the hero is atmosphere without a subject. |
@@ -1371,14 +1501,15 @@ Catalogue version `2026.10.4`, 72 tells.
 | `stock-phrase` | 1 | copy | warn | Stock phrase | Phrases every generated services page uses. They fill space where a fact should be. |
 | `ai-phrase` | 1 | copy | warn | AI phrase | Let's dive in, here's the thing, at its core, seamless, rest assured: the phrase list of the house copy rules. A reader has seen each one in a thousand generated pages. |
 | `plainer-word` | 1 | copy | warn | A plainer word exists | Empower, leverage, harness, delve: each stands in for a plainer verb, and the swap is a reliable sign nobody chose the word. |
-| `plain-english` | 2 | copy | warn | 'Plain English' | Told to avoid jargon, a model announces that it is avoiding jargon. 'Explained plainly' swaps a synonym and keeps the tell. |
+| `plain-english` | 2 | copy | warn | 'Plain English' | Told to avoid jargon, a model announces that it is avoiding jargon: 'in plain English', 'stated plainly', 'we'll tell you plainly', 'in plain terms'. The founder bans the whole family (20 October 2026); a reader takes it as filler. |
 | `buzzword` | 1 | copy | warn | Buzzword | Cutting-edge, world-class, reach out, turnkey: corporate filler older than any model, and still the first thing a model writes about a business it knows nothing about. |
 | `negative-reassurance` | 1 | copy | warn | Negative reassurance | 'No hidden fees', 'no surprises', 'never locked in' reassure by naming the fear, and plant it in a reader who did not have it. |
 | `vague-word` | 1 | copy | warn | Vague word | Innovative, scalable, end-to-end, solutions: each can be true, and each is used where the writer had nothing specific to say. |
-| `review-phrase` | 1 | copy | warn | Review-tier phrase | Truly, genuinely, clear, ultimately, 'the single most', 'bar none': normal English once, and a tell when they stack. The house rules keep them for review, never blocking. |
+| `review-phrase` | 1 | copy | warn | Review-tier phrase | Truly, genuinely, clear, ultimately, 'a plain recommendation', 'the single most', 'bar none': normal English once, and a tell when they stack. The house rules keep them for review, never blocking. |
 | `sales-tagline` | 1 | copy | warn | Sales tagline | 'So your budget goes where it counts', 'Real results', 'pages that convert': advert lines that sound like a pitch and say nothing a reader can check. |
 | `outcome-promise` | 1 | copy | warn | Outcome promise | 'We'll turn that into enquiries', 'once the first areas are working', 'competitors you can outdo': a hoped-for result written as if it were delivered. Rankings and enquiries depend on things nobody controls. |
 | `matey-register` | 2 | copy | warn | Matey register | 'Alright Dave,', 'no worries, we'll get you sorted', 'Quick one:', 'have look at': a put-on, over-familiar British voice, with the small words clipped out. A model asked to sound British writes it; the UK is broad, and a client reads it as cringe and a little rude. |
+| `confession-line` | 2 | copy | warn | Confession line | 'What this is and is not', 'we have not yet built', 'our experience so far is one practice', 'what we would and wouldn't take on': a model scopes a business by confessing its limits. It reads as small print, and it turns a buyer away before they make contact. |
 | `hollow-imperative` | 1 | copy | warn | Hollow imperative | 'Discover', 'Experience', 'Transform your' as the opening verb of a heading or button is a call to action with nothing in it. |
 | `rhetorical-opener` | 1 | copy | warn | Rhetorical question opener | 'Looking for...?', 'Tired of...?', 'Ready to...?' opens with the model guessing at the reader instead of telling them something. |
 | `em-dash` | 2 | copy | warn | Em dash | Generated copy leans on the em dash to join clauses. House copy does not use it. |

package/COPY.md

@@ -57,7 +57,8 @@ A single hit fails the check. These are not judgment calls.
   `in today's rapidly evolving…`, `increasingly digital`,
   `whether you're a X or a Y`, `seamless(ly)`, `unlock your…`,
   `meaningful impact`, `foster collaboration`, `empower`, `leverage`,
-  `harness`, `delve`, `a comprehensive guide to`, `plain English`.
+  `harness`, `delve`, `a comprehensive guide to`, `plain English`,
+  `plainly`, `in plain terms`, `in plain language`.
 
 Also blocking: `in the event that`, `at no additional cost to you`, `rest
 assured`, `it is worth noting that`, `when it comes to`, `we've got you
@@ -78,7 +79,12 @@ exists. Name the mechanism: "Your team can publish without us", not "we
 empower your team".
 
 `plain English` has one house replacement: **"properly explained"**.
-"Explained plainly" swaps a synonym and keeps the tell.
+"Explained plainly" swaps a synonym and keeps the tell, and so do "stated
+plainly", "we'll tell you plainly" and "in plain terms": the whole family
+blocks (founder, 20 October 2026). Drop the adverb and say the thing. Licence
+text ("must be plainly marked") is let through. `plain` and `clear` describing
+the copy itself ("a plain recommendation", "clear pricing") are review tier,
+in `review-phrase`: say what the reader actually gets.
 
 ## Review tier
 
@@ -87,9 +93,10 @@ person reading decides which instance earns its place.
 
 | Tell | What it catches |
 | --- | --- |
-| `review-phrase` | truly, genuinely, deeply, ultimately, clear and clearly ("a clear next step", "clear pricing": say what the reader actually gets), great question, absolutely, one-size-fits-all, and superlative over-claiming: "the single most", "by far the most", "hands down the", "arguably the best", "bar none" |
+| `review-phrase` | truly, genuinely, deeply, ultimately, clear and clearly ("a clear next step", "clear pricing": say what the reader actually gets), plain as a self-description ("plain answers", "a plain recommendation"), great question, absolutely, one-size-fits-all, and superlative over-claiming: "the single most", "by far the most", "hands down the", "arguably the best", "bar none" |
 | `sales-tagline` | advert lines that say nothing a reader can check: "so your budget goes where it counts", "real results", "results that matter", "work harder for you", "pages that convert" |
 | `matey-register` | the put-on British voice: "Alright Dave,", "cheers mate", "no worries", "we'll get you sorted", "proper good", "give me a shout", "chuffed", "Right then,"; and clipped speech that drops the small words: "have look at", "give it go", "Quick one:", "built you a site". Write plain, complete British English |
+| `confession-line` | scoping the business by what it has not done, will not do or is not: "What this is and is not", "we have not yet built", "our clinic experience so far is one practice", "what we would and wouldn't take on", "who we don't work with". It's an open shop: be honest by being precise ("the portal we run for Sensphere") and keep the door open. Contractual facts (eligibility, who runs what) stay, said as what the buyer gets |
 | `outcome-promise` | a hoped-for result written as delivered: "we'll turn that into enquiries", "once the first areas are working", "competitors you can outdo", "exactly what convinces", "guaranteed rankings", "you'll get more". Promise the work; measure and report the results |
 | `ai-vocabulary` | tapestry, testament, realm, elevate, nestled, meticulous, unparalleled, moreover; and underscore, showcasing, pivotal, measured 10 to 14 times over-used in post-2022 text |
 | `stock-email-line` | the form-email opener and closer: "I hope this email finds you well", "hope you're having a great week", "let me know if you have any questions", "don't hesitate to contact us". Start with the reason for writing; end with the next step and who to ask |

package/PRINCIPLES.md

@@ -129,3 +129,12 @@ a stakeholder's observation, the visitor problem under it, the proposed fix and
 the evidence are judged apart, and the smallest change that answers the problem
 wins. "The existing design is already appropriate" is a result. See
 [Reviewing a proposed change](./CHARACTER.md#reviewing-a-proposed-change).
+
+Her review of Doman Digital's own new site (18 and 19 October 2026, 73 notes)
+is kept whole in the reviewer corpus, with the founder's rulings of 20 October,
+and it adds eleven principles and two tells. The main ones: an open shop is honest
+by being precise, never by confessing what it has not done; a summary page
+carries the substance; a case line ends on its result; a hero has one button;
+and the first screen on a phone belongs to the business. Every later review of
+hers feeds craft the same way. See
+[Eunice's review of the DD site](./CHARACTER.md#eunices-review-of-the-dd-site-2026-10-19).

package/README.md

@@ -121,6 +121,12 @@ no change is needed. Evidence only reported by an audit or a stakeholder cannot
 make a problem observed, and a width nobody looked at stays unknown. See
 [Reviewing a proposed change](./CHARACTER.md#reviewing-a-proposed-change).
 
+A reviewer's own review is kept whole in the same shape, in the repository's
+reviewer corpus (`packages/craft/reviews/`, left out of the npm package), with
+what was done with each note and the principle it teaches. Eunice Ordor's
+review of the DD site is the first. See
+[Eunice's review of the DD site](./CHARACTER.md#eunices-review-of-the-dd-site-2026-10-19).
+
 `--snapshot` accepts saved files and preview or production URLs. Drift fails
 with `--strict`; declared estate comparisons stay advisory. Version 1 files
 still validate with a warning. See [CHARACTER.md](./CHARACTER.md) for the full
@@ -371,6 +377,13 @@ the one loaded page in place:
   `tel:` link.
 - **On a landscape phone (844 x 390):** header and fixed layers leave at least
   half the height.
+- **Page length (phone screens):** page height at 375 x 667 over 667, to the
+  footer (lazy images loaded). A phone page has a length budget (the Bellerose
+  home page ran 12.7 screens against a target of 6.5). Set one per route or
+  route pattern with `screens`; a route over its budget fails the `screens`
+  check, and with no budget the count is only reported. Keys are a route
+  (`/`), a pattern (`/areas/[town]`), a prefix (`/services/*`, the route and
+  everything under it) or `*`; the most specific wins.
 - **At 1440 and 1920:** body lines are at most 80 characters (width over the
   `ch` of the element's own font) and no image is stretched past its file.
 
@@ -384,10 +397,16 @@ test.use(PHONE);
 test(`every viewport: ${route}`, async ({ page }) => {
   await page.goto(route);
   // Resizes this page in place; writes phone-first/measured/<route>.json.
-  await measureViewports(page, { route, mainAction: ".hero a" });
+  await measureViewports(page, { route, mainAction: ".hero a", screens: { "/": 6.5, "/services/*": 6 } });
 });
 ```
 
+`result.screens` holds the count, and it is written to the measured file;
+`craft viewports` and `craft phone-first --measured` print it for every route
+(`phone screens to the footer: / 5.8 of 6.5`). In `viewports.json` the budget is
+`"screens": { "/": 6.5, "/services/*": 6 }`; in create-site's
+`site.programme.json` it is `measure.screens`.
+
 `measureViewports` works on the page the suite opened and signed in, so a
 portal keeps its fixtures. `measureRoute(open, { route, mainAction })` does
 both halves for such a page: `open("phone")` and `open("wide")` return the

package/design-review.schema.json

@@ -20,6 +20,67 @@
       "type": "string",
       "minLength": 1
     },
+    "reviewer": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The person whose review this is, when the file is their record. Each note's raisedBy still says who raised it."
+    },
+    "date": {
+      "type": "string",
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "description": "The day the review was given."
+    },
+    "source": {
+      "type": "object",
+      "description": "Where the review came from, when it is a reviewer's own record (a reviewer corpus under reviews/).",
+      "required": [
+        "tool"
+      ],
+      "properties": {
+        "tool": {
+          "type": "string",
+          "minLength": 1,
+          "description": "pastel, a document, a call, an email."
+        },
+        "canvas": {
+          "type": [
+            "integer",
+            "string"
+          ]
+        },
+        "link": {
+          "type": "string"
+        },
+        "comments": {
+          "type": "integer",
+          "minimum": 0
+        },
+        "from": {
+          "type": "string"
+        },
+        "to": {
+          "type": "string"
+        }
+      }
+    },
+    "rulings": {
+      "type": "object",
+      "description": "Who made the final calls recorded in each note's founderRuling, and when.",
+      "required": [
+        "by",
+        "date"
+      ],
+      "properties": {
+        "by": {
+          "type": "string",
+          "minLength": 1
+        },
+        "date": {
+          "type": "string",
+          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
+        }
+      }
+    },
     "notes": {
       "type": "array",
       "items": {
@@ -414,6 +475,101 @@
               }
             }
           }
+        },
+        "source": {
+          "type": "object",
+          "description": "Where the note was left: the tool, and the reference that finds it again.",
+          "required": [
+            "tool"
+          ],
+          "properties": {
+            "tool": {
+              "type": "string",
+              "minLength": 1
+            },
+            "canvas": {
+              "type": [
+                "integer",
+                "string"
+              ]
+            },
+            "comment": {
+              "type": [
+                "integer",
+                "string"
+              ],
+              "description": "The comment's number as the reviewer sees it."
+            },
+            "commentId": {
+              "type": [
+                "integer",
+                "string"
+              ]
+            },
+            "url": {
+              "type": "string",
+              "description": "The page the note was left on."
+            },
+            "at": {
+              "type": "string",
+              "description": "When it was left, ISO 8601."
+            }
+          }
+        },
+        "verdict": {
+          "enum": [
+            "praise",
+            "take",
+            "take-reworded",
+            "partly",
+            "decline",
+            "founder-decision",
+            "known"
+          ],
+          "description": "What was done with the note. take-reworded: the diagnosis is taken and the suggested wording rewritten (it is copy-checked like any other). partly: the aim is taken, by a smaller or different change. known: already tracked, no change here."
+        },
+        "founderRuling": {
+          "type": "object",
+          "required": [
+            "date",
+            "ruling"
+          ],
+          "properties": {
+            "date": {
+              "type": "string",
+              "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
+            },
+            "ruling": {
+              "type": "string",
+              "minLength": 1
+            }
+          },
+          "description": "The founder's call where the note needed one, stated as the decision and nothing more."
+        },
+        "principle": {
+          "type": "string",
+          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
+          "description": "The id of the principle the note teaches, as written up in CHARACTER.md."
+        },
+        "tells": {
+          "type": "array",
+          "description": "Craft tells the note informed. With text, the words that tell must fire on.",
+          "items": {
+            "type": "object",
+            "required": [
+              "id"
+            ],
+            "properties": {
+              "id": {
+                "type": "string",
+                "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$"
+              },
+              "text": {
+                "type": "string",
+                "minLength": 1
+              }
+            }
+          }
         }
       }
     }

package/dist/{audit-LQ2TDISV.js → audit-CDMZ6JHT.js}

@@ -9,10 +9,10 @@ import {
   snapshotPage,
   snapshotUrl,
   snapshotUrls
-} from "./chunk-6DRBFDWT.js";
+} from "./chunk-D6TAYXOS.js";
 import "./chunk-JYNXGCYZ.js";
-import "./chunk-DE2ZAV4G.js";
-import "./chunk-ONA73THJ.js";
+import "./chunk-MLYHSPF7.js";
+import "./chunk-NV6FKMID.js";
 import "./chunk-QYBAVU3P.js";
 export {
   PROVENANCE_BUDGET_MS,