@lotics/cli 0.231.0 → 0.233.0

package/dist/src/cli.js

@@ -52,7 +52,7 @@ var __toESM = (mod2, isNodeMode, target) => (target = mod2 != null ? __create(__
 var define_LOTICS_KIT_VERSIONS_default;
 var init_define_LOTICS_KIT_VERSIONS = __esm({
   "<define:__LOTICS_KIT_VERSIONS__>"() {
-    define_LOTICS_KIT_VERSIONS_default = { ui: "60.0.0", sdk: "0.100.0", runtime: "0.22.0" };
+    define_LOTICS_KIT_VERSIONS_default = { ui: "62.0.0", sdk: "0.100.0", runtime: "0.24.0" };
   }
 });
 
@@ -50171,9 +50171,21 @@ var contractPublishDestinationSchema = zod_default.strictObject({
     in: zod_default.array(contractAliasSchema).min(1).describe("Its option aliases the strip offers a row at")
   }).optional().describe("Which destination rows the strip offers; absent, every row")
 });
-var ITINERARY_RUNS = ["when", "kind", "provider", "stage", "duration", "caption", "reference"];
-var STOP_LINE_RUNS = 4;
+var ENTRY_LINES = 2;
+var LINE_RUNS = 4;
+var contractEntryPlacement = {
+  name: contractAliasSchema.optional().describe("The child's field that NAMES the entry and leads it; absent, its `identity`"),
+  words: contractAliasSchema.optional().describe("The child's text field the entry SAYS; absent, its `body`, else (on a log) its first markdown text"),
+  lines: zod_default.array(zod_default.array(contractAliasSchema).min(1).max(LINE_RUNS)).min(1).max(ENTRY_LINES).optional().describe(
+    `The entry's supporting lines, at most ${ENTRY_LINES}, each the child's fields it reads in order, at most ${LINE_RUNS}; absent, a log reads its selects, the parties it was with and the address it reached them at, and a stop reads its slot and its party, with its amount on a second line`
+  ),
+  badge: contractAliasSchema.optional().describe("The child's select drawn as the entry's status at the right \u2014 a lifecycle or a category; absent, a stop's lifecycle, and nothing on a log"),
+  figure: contractAliasSchema.optional().describe("The child's number worn at the trailing end of the entry's head; absent, a log's amount, and nothing on a stop"),
+  evidence: zod_default.array(contractAliasSchema).min(1).optional().describe("The child's fields drawn under the words as what the entry shows, a playable file played; absent, its `recording`"),
+  detail: zod_default.array(contractAliasSchema).min(1).optional().describe("The child's fields kept behind one fold under the words; absent, its `verbatim`")
+};
 var sectionHeadingSchema = zod_default.string().min(1).describe("What this section is headed on the record; absent, the child entity's own label");
+var sectionFactsSchema = zod_default.array(contractAliasSchema).min(1).optional().describe("Fields of THIS record drawn at the head of the section, above its rows \u2014 filed here, and so in no band of the record's facts");
 var ACT_CHANNELS = ["link", "phone", "sms", "email", "zalo", "whatsapp"];
 var actPathSchema = zod_default.string().regex(/^[a-z][a-z0-9_]*\.[a-z][a-z0-9_]*$/, 'a path across the act reads "<link of the act>.<field of the row it names>"');
 function actPath(path24, child, entities) {
@@ -50249,41 +50261,32 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   zod_default.strictObject({
     draw: zod_default.literal("worksheet").describe("Priced lines the reader works down in place, each part footed and the sheet closing under them"),
     heading: sectionHeadingSchema.optional(),
+    facts: sectionFactsSchema,
     cost: contractAliasSchema.optional().describe("The child's field holding what a line COSTS \u2014 the base the margin is taken against"),
     sell: contractAliasSchema.optional().describe("The child's field holding what it SELLS for \u2014 the figure the sheet is read for")
   }),
-  // A BOOK HEADS WITH WHAT IT IS READ AGAINST. The rows are the movements;
-  // what the record is OWED, has collected, still waits for and is due by are
-  // the record's own columns, and stated above the rows they are the whole
-  // point of the section — including at nought rows, where a book with no head
-  // is a heading, a verb and a void.
-  // THE HEAD IS A BAND, so its arity is the band's: TWO TO FOUR. One figure is
-  // a headline and belongs over the record, not over its book; a fifth falls
-  // under the measure a money figure is read at, and a head that quietly seats
-  // four of five states a position that is not the record's.
+  // A BOOK CLOSES ON ITS OWN TOTAL, read against the record's figure that sums
+  // it — the rollup the header band or the facts already draw. A strip of the
+  // record's figures over the rows stated that band a second time, so the
+  // clause carries no head: it says only that the rows are a book.
   zod_default.strictObject({
-    draw: zod_default.literal("ledger").describe("A book of movements, headed by what the record they are against is read against"),
+    draw: zod_default.literal("ledger").describe("A book of movements \u2014 closes on its total, read against the record's rollup that sums it"),
     heading: sectionHeadingSchema.optional(),
-    summary: zod_default.array(
-      zod_default.union([
-        contractAliasSchema,
-        zod_default.strictObject({
-          field: contractAliasSchema,
-          sense: zod_default.literal("expires").describe("A date a right RUNS OUT at \u2014 a free cancellation, a quote's validity \u2014 rather than one the record works to: behind it the head reads closed, never late")
-        }).describe("A date field with the one reading the field itself cannot state")
-      ])
-    ).min(2).max(4).describe("Two to four number or date fields of THIS record, in this order \u2014 what is owed and by when, drawn above the rows")
+    facts: sectionFactsSchema,
+    summary: zod_default.never({
+      error: "is no clause \u2014 a book has no strip: it closes on its total against the record's rollup that sums it, emitted as `against`"
+    }).optional()
   }),
   // A RUN IS DERIVED FROM THE CHILD'S OWN ROLES — the day, the ladder, the
-  // kind, who performs it — and the one thing the roles cannot answer is which
-  // four of them a reader of THIS business reads the stop by. A courier's run
-  // is read by the hour and the address; a stay is read by how long it lasts.
+  // slot, who performs it, the amount — and the one thing the roles cannot
+  // answer is which of them a reader of THIS business reads the stop by. A
+  // courier's run is read by the hour and the address; a stay is read by how
+  // long it lasts. So the clause places, as a log's does.
   zod_default.strictObject({
-    draw: zod_default.literal("itinerary").describe("A run of stops read a day at a time \u2014 stated to say which runs each stop's supporting line carries"),
+    draw: zod_default.literal("itinerary").describe("A run of stops read a day at a time \u2014 stated to place the child's fields on the stop where the roles' placement is not the reading"),
+    ...contractEntryPlacement,
     heading: sectionHeadingSchema.optional(),
-    line: zod_default.array(zod_default.enum(ITINERARY_RUNS)).min(1).max(STOP_LINE_RUNS).describe(
-      `The runs of a stop's muted line, in this order \u2014 at most ${STOP_LINE_RUNS}, each one this run already carries; absent, a stop is read by ${ITINERARY_RUNS.slice(0, STOP_LINE_RUNS).join(", ")}`
-    )
+    facts: sectionFactsSchema
   }),
   // A CLAIM AGAINST A PRICED SCHEDULE: each line is what the contract holds,
   // what earlier periods claimed and what this one claims. Four figures, and
@@ -50293,6 +50296,7 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   zod_default.strictObject({
     draw: zod_default.literal("claim").describe("Lines claimed against a priced schedule, one period at a time \u2014 the contract, before, now, to date and what is left"),
     heading: sectionHeadingSchema.optional(),
+    facts: sectionFactsSchema,
     quantity: contractAliasSchema.describe("The child's number field THIS period's quantity is stated in \u2014 the one cell the reader edits"),
     contract: contractAliasSchema.describe("The child's field holding the quantity the contract prices the line for"),
     price: contractAliasSchema.describe("The child's field holding the line's unit price"),
@@ -50308,6 +50312,7 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   zod_default.strictObject({
     draw: zod_default.literal("tree").describe("The rows nested under each other, each money figure summed up the tree"),
     heading: sectionHeadingSchema.optional(),
+    facts: sectionFactsSchema,
     nest: contractAliasSchema.describe("The child's one-row link to its own entity \u2014 the row each row sits under")
   }),
   // A SCHEDULE OF A RECORD'S OWN ROWS — the bars a register's gantt draws, read
@@ -50317,6 +50322,7 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   zod_default.strictObject({
     draw: zod_default.literal("gantt").describe("The rows as bars across the calendar \u2014 from each row's `when`, for the days its measure counts"),
     heading: sectionHeadingSchema.optional(),
+    facts: sectionFactsSchema,
     until: contractAliasSchema.optional().describe("The child's date field each bar is drawn TO; absent, a bar runs for the days its measure counts"),
     nest: contractAliasSchema.optional().describe("The child's one-row link to its own entity \u2014 folds a row's bars under the row it sits under"),
     depends_on: contractAliasSchema.optional().describe("The child's link to its own entity naming the rows that must finish before a row starts"),
@@ -50327,6 +50333,7 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   zod_default.strictObject({
     draw: zod_default.literal("curve").describe("Two figures of the rows, each added up to date along the rows' `when` and drawn as two lines"),
     heading: sectionHeadingSchema.optional(),
+    facts: sectionFactsSchema,
     planned: contractAliasSchema.describe("The child's number each row was PLANNED to come to"),
     actual: contractAliasSchema.describe("The child's number each row DID come to \u2014 empty on a row that has not happened")
   }),
@@ -50338,13 +50345,8 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
   // five. So the clause names the rung, and the rung it names is placed whole.
   zod_default.strictObject({
     draw: zod_default.literal("log").describe("Dated entries read in the words each states \u2014 stated to place the child's fields on the entry where the roles' placement is not the reading"),
-    heading: sectionHeadingSchema.optional(),
-    name: contractAliasSchema.optional().describe("The child's field that NAMES the entry and leads it; absent, its `identity`"),
-    words: contractAliasSchema.optional().describe("The child's text field the entry SAYS; absent, its `body`, else its first markdown text"),
-    evidence: zod_default.array(contractAliasSchema).min(1).optional().describe("The child's fields drawn under the words as what the entry shows, a playable file played; absent, its `recording`"),
-    detail: zod_default.array(contractAliasSchema).min(1).optional().describe("The child's fields kept behind one fold under the words; absent, its `verbatim`"),
-    line: zod_default.array(contractAliasSchema).min(1).optional().describe("The runs of the entry's supporting line, in this order; absent, its selects, the parties it was with, the one-row links no role claims, and the address it reached them at"),
-    trailing: contractAliasSchema.optional().describe("The child's one field worn at the trailing end of the entry's head \u2014 a figure, a word")
+    ...contractEntryPlacement,
+    heading: sectionHeadingSchema.optional()
   }),
   // ONE PIECE, N DESTINATIONS. The rows are not a register anybody reads: each
   // is this record standing on one destination, so what a reader wants is the
@@ -50409,12 +50411,20 @@ var contractSectionDrawSchema = zod_default.discriminatedUnion("draw", [
 ]).describe("How a section of this screen's record is drawn, where its rows are more than a register");
 var contractSectionHeadingSchema = zod_default.strictObject({
   draw: zod_default.undefined().optional(),
-  heading: sectionHeadingSchema
-}).describe("Rename a section of the rows this record owns, however the roles draw it");
+  heading: sectionHeadingSchema.optional(),
+  facts: sectionFactsSchema
+}).check((ctx) => {
+  if (ctx.value.heading === void 0 && ctx.value.facts === void 0) {
+    ctx.issues.push({ code: "custom", input: ctx.value, message: "states nothing \u2014 a clause that draws no rows another way names the section's `heading`, its `facts`, or both" });
+  }
+}).describe("Rename a section of the rows this record owns, or head it with the record's facts that frame them, however the roles draw it");
 var contractSectionClauseSchema = zod_default.discriminatedUnion("draw", [...contractSectionDrawSchema.options, contractSectionHeadingSchema]);
 function sectionDraw(clause) {
   return clause === void 0 || clause.draw === void 0 ? void 0 : clause;
 }
+function sectionFacts(clause) {
+  return clause !== void 0 && "facts" in clause && clause.facts !== void 0 ? clause.facts : [];
+}
 function publishBodies(clause) {
   const bodies = clause.destination.bodies;
   return typeof bodies === "string" ? [bodies] : [...new Set(Object.values(bodies.options))];
@@ -50542,7 +50552,7 @@ var contractScreenSchema = zod_default.object({
     "Acts on the RECORD's own sections, keyed by the alias each section is derived from \u2014 a field alias (its progress, its prose, its set, its charge, its files) or a child entity's alias (its register, its desk, its run, its log)"
   ),
   sections: zod_default.record(contractAliasSchema, contractSectionClauseSchema).optional().describe(
-    'How a section of the RECORD is DRAWN, keyed by the child entity alias its register is derived from \u2014 or `{"heading": \u2026}` alone to rename any section of the rows it owns'
+    'How a section of the RECORD is DRAWN, keyed by the child entity alias its register is derived from \u2014 or `{"heading": \u2026}`, `{"facts": [\u2026]}` or both alone to rename any section of the rows it owns or head it with the record\'s facts'
   ),
   children: zod_default.array(contractAliasSchema).min(1).optional().describe(
     "The child entities whose rows the RECORD draws in this app, in this order \u2014 only these; absent, every one its links derive"
@@ -52071,6 +52081,43 @@ function entryDay(child, roles) {
   if (when !== void 0 && !countsDown(roleOf(roles, child.alias, when.alias))) return when;
   return child.fields.find((field) => field.type === "date" && roleOf(roles, child.alias, field.alias) === void 0);
 }
+function placeEntry(child, roles, placed, byRole2) {
+  const named3 = (alias) => alias === void 0 ? void 0 : child.fields.find((field) => field.alias === alias);
+  const each = (aliases) => aliases.flatMap((alias) => {
+    const field = named3(alias);
+    return field === void 0 ? [] : [field];
+  });
+  const claimed = /* @__PURE__ */ new Set(
+    [
+      ...placed?.name === void 0 ? [] : [placed.name],
+      ...placed?.words === void 0 ? [] : [placed.words],
+      ...(placed?.lines ?? []).flat(),
+      ...placed?.badge === void 0 ? [] : [placed.badge],
+      ...placed?.figure === void 0 ? [] : [placed.figure],
+      ...placed?.evidence ?? [],
+      ...placed?.detail ?? []
+    ]
+  );
+  const free = (field) => field === void 0 || claimed.has(field.alias) ? void 0 : field;
+  const recorded = fieldsWithRole(child, roles, "recording")[0];
+  const said = fieldsWithRole(child, roles, "verbatim")[0];
+  const name = placed?.name === void 0 ? free(fieldsWithRole(child, roles, "identity")[0]) : named3(placed.name);
+  const body = placed?.words === void 0 ? free(entryBody(child, roles)) : named3(placed.words);
+  const lines = placed?.lines === void 0 ? byRole2.lines.map((line) => line.flatMap((field) => free(field) === void 0 ? [] : [field])).filter((line) => line.length > 0) : placed.lines.map(each).filter((line) => line.length > 0);
+  const badge = placed?.badge === void 0 ? free(byRole2.badge) : named3(placed.badge);
+  const figure = placed?.figure === void 0 ? free(byRole2.figure) : named3(placed.figure);
+  const evidence = placed?.evidence === void 0 ? free(recorded) === void 0 ? [] : [recorded] : each(placed.evidence);
+  const detail = placed?.detail === void 0 ? free(said) === void 0 ? [] : [said] : each(placed.detail);
+  return {
+    ...name === void 0 ? {} : { name },
+    ...body === void 0 ? {} : { body },
+    lines,
+    ...badge === void 0 ? {} : { badge },
+    ...figure === void 0 ? {} : { figure },
+    evidence,
+    detail
+  };
+}
 function childLog(child, roles, via, entity, placed) {
   if (fieldsWithRole(child, roles, "lifecycle").length > 0) return void 0;
   const named3 = (alias) => alias === void 0 ? void 0 : child.fields.find((field) => field.alias === alias);
@@ -52084,29 +52131,24 @@ function childLog(child, roles, via, entity, placed) {
   const withParties = parties.filter((field) => field.alias !== author?.alias);
   const awaiting = owned ? withParties[0] : void 0;
   const clock = owned ? recordDeadline(entity, roles) : void 0;
-  const name = placed?.name === void 0 ? fieldsWithRole(child, roles, "identity")[0] : named3(placed.name);
-  const place = (aliases, byRole2) => aliases === void 0 ? byRole2 : aliases.flatMap((alias) => {
-    const field = named3(alias);
-    return field === void 0 ? [] : [field];
-  });
   const worded = CHILD_COLUMN_ROLES.flatMap((role) => fieldsWithRole(child, roles, role)).filter((field) => field.type === "select");
   const contact = fieldsWithRole(child, roles, "contact")[0];
-  const recorded = fieldsWithRole(child, roles, "recording")[0];
-  const said = fieldsWithRole(child, roles, "verbatim")[0];
   const beside = child.fields.filter(
     (field) => field.type === "select_record_link" && field.cardinality === "one" && roleOf(roles, child.alias, field.alias) === void 0
   );
-  const line = place(placed?.line, [...worded, ...withParties, ...beside, ...contact === void 0 ? [] : [contact]]);
-  const evidence = place(placed?.evidence, recorded === void 0 ? [] : [recorded]);
-  const detail = place(placed?.detail, said === void 0 ? [] : [said]);
+  const { name, lines, badge, figure, evidence, detail } = placeEntry(child, roles, placed, {
+    lines: [[...worded, ...withParties, ...beside, ...contact === void 0 ? [] : [contact]]],
+    figure: fieldsWithRole(child, roles, "amount")[0]
+  });
   const on = (rung, field) => field !== void 0 && rung.includes(field) ? field : void 0;
-  const address = on(line, contact);
-  const recording = on(evidence, recorded);
-  const verbatim = on(detail, said);
+  const address = on(lines.flat(), contact);
+  const recording = on(evidence, fieldsWithRole(child, roles, "recording")[0]);
+  const verbatim = on(detail, fieldsWithRole(child, roles, "verbatim")[0]);
   const files = child.fields.find((field) => field.type === "files" && field.alias !== recording?.alias);
-  const trailing = named3(placed?.trailing);
   const drawn = new Set(
-    [body, when, author, name, official, trailing, ...line, ...evidence, ...detail].flatMap((field) => field === void 0 ? [] : [field.alias])
+    [body, when, author, name, official, badge, figure, ...lines.flat(), ...evidence, ...detail].flatMap(
+      (field) => field === void 0 ? [] : [field.alias]
+    )
   );
   const facts = child.fields.filter(
     (field) => isEditable(field) && field.type !== "select_record_link" && field.type !== "files" && !drawn.has(field.alias)
@@ -52125,8 +52167,9 @@ function childLog(child, roles, via, entity, placed) {
     facts,
     evidence,
     detail,
-    line,
-    ...trailing === void 0 ? {} : { trailing },
+    lines,
+    ...badge === void 0 ? {} : { badge },
+    ...figure === void 0 ? {} : { figure },
     ...official === void 0 ? {} : { answer: { official, ...awaiting === void 0 ? {} : { awaiting }, ...clock === void 0 ? {} : { clock } } }
   };
 }
@@ -52214,9 +52257,6 @@ function recordHistory(entity, entities, roles) {
   const by = column(HISTORY_BY);
   return { plan: { child, link, stage, at: at2, ...by === void 0 ? {} : { by } }, child, back };
 }
-function summaryFieldOf(entry) {
-  return typeof entry === "string" ? entry : entry.field;
-}
 var SECTION_WHY = {
   facts: "every field no other section took",
   prose: "this record's recipe opens with the body, so its markdown is a section",
@@ -52336,14 +52376,12 @@ function recordSections(entity, entities, roles, header, shape = CUSTOM_SHAPE, d
       // ladder's own rows reached from the other side — a fact listing them by
       // name would be the history drawn twice, once as a list of ids.
       ...history === void 0 ? [] : [history.back],
-      // …AND THE FIGURES A SECTION BELOW HEADS ITSELF WITH, and the words a
-      // desk below SENDS: the bodies are drawn as prose above the strip, so a
-      // fact for one is the same column edited twice, and a band holding
-      // nothing else is an empty grid with an entry in the rail.
-      ...Object.values(drawn ?? {}).flatMap((clause) => {
-        const named4 = clause.draw === "ledger" ? clause.summary.map(summaryFieldOf) : clause.draw === "publish" ? publishBodies(clause) : [];
-        return named4.flatMap((alias) => entity.fields.filter((field) => field.alias === alias));
-      }),
+      // …AND THE WORDS A DESK BELOW SENDS: the bodies are drawn as prose above
+      // the strip, so a fact for one is the same column edited twice, and a band
+      // holding nothing else is an empty grid with an entry in the rail.
+      ...Object.values(drawn ?? {}).flatMap(
+        (clause) => clause.draw === "publish" ? publishBodies(clause).flatMap((alias) => entity.fields.filter((field) => field.alias === alias)) : []
+      ),
       ...ownSets,
       ...files,
       ...judged === void 0 ? [] : [judged],
@@ -52360,9 +52398,25 @@ function recordSections(entity, entities, roles, header, shape = CUSTOM_SHAPE, d
       ...header.figure === void 0 ? [] : [header.figure]
     ].map((field) => field.alias)
   );
-  const facts = entity.fields.filter(
+  const candidates2 = entity.fields.filter(
     (field) => !owned.has(field.alias) && !drawsBothWays(field, drawnRelations) && (field.type !== "select_record_link" || field.cardinality === "one" || !listed.has(field.target_entity))
   );
+  const shows = (section) => {
+    const child = sectionRelation(section)?.child.alias;
+    return child === void 0 || stated3.children === void 0 || stated3.children.includes(child);
+  };
+  const heads = /* @__PURE__ */ new Map();
+  const headed2 = /* @__PURE__ */ new Set();
+  for (const section of children) {
+    if (section.kind !== "children" || section.via !== "parent" || !shows(section)) continue;
+    const clause = drawn?.[section.child.alias];
+    if ([...heads.keys()].some((one) => sectionRelation(one)?.child.alias === section.child.alias)) continue;
+    const head = sectionFacts(clause).flatMap((alias) => headed2.has(alias) ? [] : candidates2.filter((field) => field.alias === alias));
+    if (head.length === 0) continue;
+    heads.set(section, head);
+    for (const field of head) headed2.add(field.alias);
+  }
+  const facts = candidates2.filter((field) => !headed2.has(field.alias));
   const levels = {};
   for (const field of facts) {
     const decl = roleOf(roles, entity.alias, field.alias);
@@ -52380,15 +52434,15 @@ function recordSections(entity, entities, roles, header, shape = CUSTOM_SHAPE, d
     Object.values(levels).flatMap((level) => typeof level.limit === "number" ? [] : [level.limit.alias])
   );
   const shown = facts.filter((field) => !folded.has(field.alias));
-  const shows = (section) => {
-    const child = sectionRelation(section)?.child.alias;
-    return child === void 0 || stated3.children === void 0 || stated3.children.includes(child);
-  };
   const place = (section) => {
     const child = sectionRelation(section)?.child.alias;
     return child === void 0 || stated3.children === void 0 ? 0 : stated3.children.indexOf(child);
   };
-  const named3 = [...sets, ...children].filter(shows);
+  const withHeads = children.map((section) => {
+    const head = heads.get(section);
+    return head === void 0 || section.kind !== "children" ? section : { ...section, head };
+  });
+  const named3 = [...sets, ...withHeads].filter(shows);
   const ordered = stated3.children === void 0 ? named3 : [...named3].sort((a, b) => place(a) - place(b));
   return [
     ...shown.length > 0 ? [{ kind: "facts", why: SECTION_WHY.facts, fields: shown, levels }] : [],
@@ -52404,7 +52458,7 @@ function recordSections(entity, entities, roles, header, shape = CUSTOM_SHAPE, d
         ...history === void 0 ? {} : { history: history.plan }
       }
     ],
-    ...stated3.children === void 0 ? [...sets, ...children] : ordered,
+    ...stated3.children === void 0 ? [...sets, ...withHeads] : ordered,
     // ONE SECTION PER PILE: each files field is filed for its own purpose — the
     // tender invited, the bid submitted — and one heading over both joined their
     // names with a `·` and mixed their papers in one strip.
@@ -52619,6 +52673,29 @@ function lookedUpMark(child, roles, link) {
     (field) => field.type === "lookup" && field.source_field_alias === link.alias && roleOf(roles, link.target_entity, field.lookup_field_alias)?.role === "mark"
   );
 }
+function recordSum(entity, child, link, roles) {
+  const amount = fieldsWithRole(child, roles, "amount")[0];
+  if (amount === void 0) return void 0;
+  const links = child.fields.filter((field) => field.type === "select_record_link" && field.target_entity === entity.alias);
+  const hangsOn = links.find((field) => field.alias === link);
+  if (hangsOn === void 0 || hangsOn.type !== "select_record_link") return void 0;
+  return entity.fields.find((field) => {
+    if (field.type !== "rollup" || field.aggregate_option.operation !== "sum" || field.aggregate_option.field_key !== amount.alias) return false;
+    const through = entity.fields.find((candidate) => candidate.alias === field.source_field_alias);
+    if (through === void 0 || through.type !== "select_record_link" || through.target_entity !== child.alias) return false;
+    if (through.paired_field_alias !== void 0) return through.paired_field_alias === hangsOn.alias;
+    if (hangsOn.paired_field_alias !== void 0) return hangsOn.paired_field_alias === through.alias;
+    return links.length === 1;
+  });
+}
+function bookAgainst(entity, child, link, roles) {
+  const sum2 = recordSum(entity, child, link, roles);
+  if (sum2 === void 0) return void 0;
+  const decl = roleOf(roles, entity.alias, sum2.alias);
+  if (decl?.role !== "measure" || typeof decl.against !== "string") return void 0;
+  const against = decl.against;
+  return entity.fields.find((field) => field.alias === against);
+}
 function recordItinerary(archetype, recipeSlot, child, roles, drawn = void 0) {
   if (archetype !== "work_record" || recipeSlot !== "children") return void 0;
   const stated3 = drawn?.[child.alias];
@@ -52627,39 +52704,25 @@ function recordItinerary(archetype, recipeSlot, child, roles, drawn = void 0) {
   const lifecycle = fieldsWithRole(child, roles, "lifecycle")[0];
   if (when === void 0 || lifecycle === void 0) return void 0;
   const slot2 = fieldsWithRole(child, roles, "slot")[0];
-  const kind = fieldsWithRole(child, roles, "category")[0];
   const mark = fieldsWithRole(child, roles, "mark")[0];
   const provider = fieldsWithRole(child, roles, "party")[0];
   const providerMark = provider === void 0 ? void 0 : lookedUpMark(child, roles, provider);
-  const caption = fieldsWithRole(child, roles, "party").find((field) => field.alias !== provider?.alias);
-  const reference = fieldsWithRole(child, roles, "reference")[0];
-  const measures = fieldsWithRole(child, roles, "measure");
-  const span = measures.find((field) => roleOf(roles, child.alias, field.alias)?.counts === "days");
-  const duration3 = measures.find((field) => roleOf(roles, child.alias, field.alias)?.counts === "hours");
+  const span = fieldsWithRole(child, roles, "measure").find((field) => roleOf(roles, child.alias, field.alias)?.counts === "days");
+  const amount = fieldsWithRole(child, roles, "amount")[0];
+  const placement = placeEntry(child, roles, stated3?.draw === "itinerary" ? stated3 : void 0, {
+    lines: [[slot2, provider].flatMap((field) => field === void 0 ? [] : [field]), amount === void 0 ? [] : [amount]],
+    badge: lifecycle
+  });
   return {
+    ...placement,
     when,
     lifecycle,
+    stageOn: placement.lines.flat().some((field) => field.alias === lifecycle.alias) ? "line" : "badge",
     ...slot2 === void 0 ? {} : { slot: slot2 },
-    ...kind === void 0 ? {} : { kind },
-    ...stated3?.draw === "itinerary" ? { line: stated3.line } : {},
     ...mark === void 0 ? {} : { mark },
     ...provider === void 0 ? {} : { provider },
     ...providerMark === void 0 ? {} : { providerMark },
-    ...caption === void 0 ? {} : { caption },
-    ...reference === void 0 ? {} : { reference },
-    ...span === void 0 ? {} : { span },
-    ...duration3 === void 0 ? {} : { duration: duration3 }
-  };
-}
-function itineraryRunFields(plan) {
-  return {
-    when: plan.when,
-    kind: plan.kind,
-    provider: plan.provider,
-    stage: plan.lifecycle,
-    duration: plan.duration,
-    caption: plan.caption,
-    reference: plan.reference
+    ...span === void 0 ? {} : { span }
   };
 }
 function registerRuns(screen, roles) {
@@ -52966,6 +53029,7 @@ function validateWorkspacePlan(model, roles, apps, rules = {}) {
     findings.push(...checkFactGroups(resolved.screen, model.entities, roles));
     findings.push(...checkSectionActs(resolved.screen, model.entities, roles));
     findings.push(...checkSectionDraws(resolved.screen, model.entities, roles));
+    findings.push(...checkSectionFacts(resolved.screen, model.entities, roles));
     findings.push(...checkChildrenShown(resolved.screen, model.entities, roles));
     findings.push(...checkChildRegisters(resolved.screen, model.entities, roles, registered));
     findings.push(...checkDeskStages(resolved.screen));
@@ -53148,16 +53212,21 @@ function checkFactGroups(screen, entities, roles) {
   const sections = recordSections(screen.entity, entities, roles, recordHeader(screen, entities, roles), screen.screen.shape, screen.record, screen.screen);
   const facts = sections.flatMap((section) => section.kind === "facts" ? section.fields : []);
   const drawn = new Set(facts.map((field) => field.alias));
+  const headedBy = new Map(
+    sections.flatMap((section) => section.kind === "children" ? (section.head ?? []).map((field) => [field.alias, section.child.alias]) : [])
+  );
   const misnamed = screen.factGroups.flatMap(
-    (group) => group.fields.flatMap(
-      (field) => drawn.has(field.alias) ? [] : [
+    (group) => group.fields.flatMap((field) => {
+      if (drawn.has(field.alias)) return [];
+      const heads = headedBy.get(field.alias);
+      return [
         {
           severity: "error",
           path: path24,
-          message: `names "${field.alias}", which this record does not draw as a fact \u2014 the header, the band, the ladder, a required set, the files or a register below already states it`
+          message: heads !== void 0 ? `files "${field.alias}" both in "${group.caption}" and in the facts over "${heads}" \u2014 a fact is stated once` : `names "${field.alias}", which this record does not draw as a fact \u2014 the header, the band, the ladder, a required set, the files or a register below already states it`
         }
-      ]
-    )
+      ];
+    })
   );
   const grouped = new Set(screen.factGroups.flatMap((group) => group.fields.map((field) => field.alias)));
   const captions = screen.factGroups.map((group) => `"${group.caption}"`).join(", ");
@@ -53172,6 +53241,58 @@ function checkFactGroups(screen, entities, roles) {
   );
   return [...misnamed, ...unfiled2];
 }
+function checkSectionFacts(screen, entities, roles) {
+  const stated3 = Object.entries(screen.screen.sections ?? {}).flatMap(([alias, clause]) => {
+    const facts = sectionFacts(clause);
+    return facts.length === 0 ? [] : [{ alias, facts }];
+  });
+  if (stated3.length === 0) return [];
+  const entries2 = recordRecipe(screen.screen.shape, screen.entity, entities, roles, recordHeader(screen, entities, roles), screen.record, screen.screen);
+  const registers = /* @__PURE__ */ new Map();
+  for (const { draw, section } of entries2) {
+    if (section.kind === "children" && section.via === "parent" && !registers.has(section.child.alias)) registers.set(section.child.alias, { draw, section });
+  }
+  const twice = new Set(findDuplicates(stated3.flatMap(({ facts }) => facts)));
+  const limitOf = new Map(
+    entries2.flatMap(
+      ({ section }) => section.kind === "facts" ? Object.entries(section.levels).flatMap(([measure, level]) => typeof level.limit === "number" ? [] : [[level.limit.alias, measure]]) : []
+    )
+  );
+  return stated3.flatMap(({ alias, facts }) => {
+    const at2 = `apps.${screen.app.alias}.screen.sections.${alias}.facts`;
+    const register = registers.get(alias);
+    if (register === void 0) {
+      return [
+        {
+          severity: "error",
+          path: at2,
+          message: `heads "${alias}" with this record's facts, and this record draws no register of its own "${alias}" rows \u2014 only rows it owns, drawn as a register, a run or a book, are headed by its facts`
+        }
+      ];
+    }
+    if (register.draw === "related") {
+      return [{ severity: "error", path: at2, message: `heads "${alias}", which this record draws as one counted line \u2014 there are no rows under it for facts to frame` }];
+    }
+    const head = new Set((register.section.head ?? []).map((field) => field.alias));
+    return facts.flatMap((name, index) => {
+      if (twice.has(name)) {
+        return facts.indexOf(name) === index ? [{ severity: "error", path: at2, message: `names "${name}", which heads more than one place \u2014 a fact is stated once` }] : [];
+      }
+      const measure = limitOf.get(name);
+      if (measure !== void 0) {
+        return [{ severity: "error", path: at2, message: `names "${name}", the limit the facts read "${measure}" against \u2014 a measure and its limit are one reading, drawn once` }];
+      }
+      if (head.has(name)) return [];
+      return [
+        {
+          severity: "error",
+          path: at2,
+          message: screen.entity.fields.some((field) => field.alias === name) ? `names "${name}", which this record does not draw as a fact \u2014 the header, the band, the ladder, a required set, the files or a register below already states it` : `names "${name}", which is not a field of entity "${screen.entity.alias}"`
+        }
+      ];
+    });
+  });
+}
 var SECTION_READING = {
   expected_set: "a set of the entries it owes",
   schedule: "a schedule",
@@ -53189,32 +53310,45 @@ function childRegisters(screen, entities, roles) {
     )
   };
 }
-function logPlacementRefusals(at2, child, clause) {
+function entryPlacementRefusals(at2, child, entities, clause, axis, stage) {
   const rungs = [
-    ["name", clause.name === void 0 ? [] : [clause.name]],
-    ["words", clause.words === void 0 ? [] : [clause.words]],
-    ["evidence", clause.evidence ?? []],
-    ["detail", clause.detail ?? []],
-    ["line", clause.line ?? []],
-    ["trailing", clause.trailing === void 0 ? [] : [clause.trailing]]
+    ["name", "name", clause.name === void 0 ? [] : [clause.name]],
+    ["words", "words", clause.words === void 0 ? [] : [clause.words]],
+    ["evidence", "evidence", clause.evidence ?? []],
+    ["detail", "detail", clause.detail ?? []],
+    ...(clause.lines ?? []).map((line, index) => [`line ${index + 1}`, "lines", line]),
+    ["badge", "badge", clause.badge === void 0 ? [] : [clause.badge]],
+    ["figure", "figure", clause.figure === void 0 ? [] : [clause.figure]]
   ];
   const refusals = [];
   const placedOn = /* @__PURE__ */ new Map();
-  for (const [rung, aliases] of rungs) {
+  for (const [rung, key, aliases] of rungs) {
     for (const alias of aliases) {
       const field = child.fields.find((one) => one.alias === alias);
       if (field === void 0) {
-        refusals.push({ severity: "error", path: `${at2}.${rung}`, message: `names "${alias}", which is not a field of "${child.alias}"` });
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `names "${alias}", which is not a field of "${child.alias}"` });
         continue;
       }
       if (rung === "words" && field.type !== "text") {
-        refusals.push({ severity: "error", path: `${at2}.${rung}`, message: `names "${alias}" as the entry's words, which is a ${field.type} \u2014 an entry says a text` });
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `names "${alias}" as the entry's words, which is a ${field.type} \u2014 an entry says a text` });
+      }
+      if (rung === "badge" && (field.type !== "select" || field.multi === true)) {
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `names "${alias}" as the entry's badge, which is ${field.type === "select" ? "a multi-select" : `a ${field.type}`} \u2014 a badge is one option of a select` });
+      }
+      if (rung === "figure" && resolvedFieldType(field, child, entities) !== "number") {
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `names "${alias}" as the entry's figure, which is a ${field.type} \u2014 a figure is a number` });
+      }
+      if (alias === axis?.alias) {
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `places "${alias}" on its ${rung} \u2014 the day is the entry's axis, drawn on every entry already` });
+      }
+      if (alias === stage?.alias && rung !== "badge" && key !== "lines") {
+        refusals.push({ severity: "error", path: `${at2}.${key}`, message: `places "${alias}" on its ${rung} \u2014 the stage is the badge or a run of a line, and drawn as the status wherever else it stands` });
       }
       const earlier = placedOn.get(alias);
       if (earlier !== void 0) {
         refusals.push({
           severity: "error",
-          path: `${at2}.${rung}`,
+          path: `${at2}.${key}`,
           message: `places "${alias}" on its ${earlier} and its ${rung} \u2014 a field is drawn once on an entry`
         });
         continue;
@@ -53222,6 +53356,13 @@ function logPlacementRefusals(at2, child, clause) {
       placedOn.set(alias, rung);
     }
   }
+  if (stage !== void 0 && clause.badge !== void 0 && clause.badge !== stage.alias && !placedOn.has(stage.alias)) {
+    refusals.push({
+      severity: "error",
+      path: `${at2}.badge`,
+      message: `names "${clause.badge}" as the badge while "${stage.alias}" is the stage \u2014 the stage wears the badge unless a line carries it`
+    });
+  }
   return refusals;
 }
 function checkPublishDraw(at2, alias, clause, section, screen, entities, roles) {
@@ -53714,7 +53855,7 @@ function checkSectionDraws(screen, entities, roles) {
       if (child === void 0 || log === void 0 && registers.get(alias) === void 0 && !readings.has(alias)) {
         return [{ severity: "error", path: at2, message: `names "${alias}", which this record draws no section of a child's rows for` }];
       }
-      const placed = logPlacementRefusals(at2, child, clause);
+      const placed = entryPlacementRefusals(at2, child, entities, clause, log?.when ?? entryDay(child, roles));
       if (placed.length > 0) return placed;
       if (log !== void 0) return [];
       const read2 = readings.get(alias);
@@ -53782,25 +53923,11 @@ function checkSectionDraws(screen, entities, roles) {
           {
             severity: "error",
             path: at2,
-            message: `states the line of "${alias}", which this record draws as a register rather than a run \u2014 a run is a child's rows carrying a day and a lifecycle, read wholly open`
+            message: `places the stops of "${alias}", which this record draws as a register rather than a run \u2014 a run is a child's rows carrying a day and a lifecycle, read wholly open`
           }
         ];
       }
-      const carried = itineraryRunFields(run);
-      const seen = /* @__PURE__ */ new Set();
-      return clause.line.flatMap((name) => {
-        if (seen.has(name)) {
-          return [{ severity: "error", path: `${at2}.line`, message: `states "${name}" twice \u2014 a line of ${STOP_LINE_RUNS} has no room to say one thing again` }];
-        }
-        seen.add(name);
-        return carried[name] === void 0 ? [
-          {
-            severity: "error",
-            path: `${at2}.line`,
-            message: `states "${name}", which these rows do not carry \u2014 declare the role that holds it in field_roles, or read the stop by another of ${ITINERARY_RUNS.join(", ")}`
-          }
-        ] : [];
-      });
+      return entryPlacementRefusals(at2, section.child, entities, clause, run.when, run.lifecycle);
     }
     if (clause.draw === "publish") {
       if (!peopleWrite(section.child)) {
@@ -53817,32 +53944,7 @@ function checkSectionDraws(screen, entities, roles) {
     if (clause.draw === "acts") {
       return checkActsDraw(at2, alias, clause, section, screen, entities, roles);
     }
-    if (clause.draw === "ledger") {
-      return clause.summary.flatMap((entry) => {
-        const field = summaryFieldOf(entry);
-        const carried = screen.entity.fields.find((one) => one.alias === field);
-        if (carried === void 0) {
-          return [{ severity: "error", path: `${at2}.summary`, message: `heads "${alias}" with "${field}", which is not a field of entity "${screen.entity.alias}"` }];
-        }
-        const result = resolvedFieldType(carried, screen.entity, entities);
-        if (typeof entry !== "string" && result !== "date") {
-          return [
-            {
-              severity: "error",
-              path: `${at2}.summary`,
-              message: `heads "${alias}" with "${field}" as a date that expires, and it is ${result === void 0 ? `a ${carried.type} whose result this model does not state` : `a ${result}`} \u2014 only a date runs out`
-            }
-          ];
-        }
-        return result === "number" || result === "date" ? [] : [
-          {
-            severity: "error",
-            path: `${at2}.summary`,
-            message: `heads "${alias}" with "${field}", ${result === void 0 ? `a ${carried.type} whose result this model does not state` : `a ${result}`} \u2014 a book's head is what the record is read against: a figure, or the date it is owed by`
-          }
-        ];
-      });
-    }
+    if (clause.draw === "ledger") return [];
     const named3 = [["cost", clause.cost], ["sell", clause.sell]].flatMap(([slot2, field]) => field === void 0 ? [] : [{ slot: slot2, field }]);
     if (named3.length === 0) {
       return [
@@ -55244,7 +55346,7 @@ function resultSideEffects(result) {
 
 // src/version.ts
 init_define_LOTICS_KIT_VERSIONS();
-var VERSION = "0.231.0";
+var VERSION = "0.233.0";
 
 // src/timezone.ts
 init_define_LOTICS_KIT_VERSIONS();
@@ -56725,13 +56827,6 @@ var specBandCellSchema = zod_default.discriminatedUnion("kind", [
     from: specColumnAliasSchema.optional()
   }).strict()
 ]);
-var specSummaryEntrySchema = zod_default.union([
-  specColumnAliasSchema,
-  zod_default.object({ field: specColumnAliasSchema, sense: zod_default.literal("expires") }).strict()
-]);
-function summaryEntryOf(entry) {
-  return typeof entry === "string" ? { field: entry } : entry;
-}
 var specBandSchema = zod_default.discriminatedUnion("kind", [
   zod_default.object({ kind: zod_default.literal("money"), cells: zod_default.array(specBandCellSchema).min(2) }).strict(),
   zod_default.object({ kind: zod_default.literal("comparison"), value: specColumnAliasSchema, reference: specColumnAliasSchema }).strict()
@@ -56787,13 +56882,54 @@ var specChildColumnSchema = zod_default.object({
   /** The column this register is NAMED for — at most one. */
   signature: zod_default.literal(true).optional()
 }).strict();
+var specEntryPlacement = {
+  /** What the entry is CALLED — leads it where present. */
+  name: specColumnAliasSchema.optional(),
+  /** The entry's own words. */
+  body: specColumnAliasSchema.optional(),
+  /** The supporting lines, each the columns it reads in order. */
+  lines: zod_default.array(zod_default.array(specColumnAliasSchema).min(1).max(LINE_RUNS)).min(1).max(ENTRY_LINES).optional(),
+  /** The select drawn as the entry's status at the right. */
+  badge: specColumnAliasSchema.optional(),
+  /** The one figure worn at the trailing end of the entry's head. */
+  figure: specColumnAliasSchema.optional(),
+  /** Which the row's stage is drawn as — the badge, or a run of the line that names it. */
+  stage_on: zod_default.enum(["badge", "line"]).optional(),
+  /** The columns drawn under the words as what the entry shows, in this order. */
+  evidence: zod_default.array(specColumnAliasSchema).min(1).optional(),
+  /** The columns kept behind one fold under the words, in this order. */
+  detail: zod_default.array(specColumnAliasSchema).min(1).optional()
+};
+function placedTwice(ctx) {
+  const placed = ctx.value;
+  const rungs = [
+    ["when", placed.when === void 0 ? [] : [placed.when]],
+    ["name", placed.name === void 0 ? [] : [placed.name]],
+    ["body", placed.body === void 0 ? [] : [placed.body]],
+    ["evidence", placed.evidence ?? []],
+    ["detail", placed.detail ?? []],
+    ...(placed.lines ?? []).map((line, index) => [`line ${index + 1}`, line]),
+    ["badge", placed.badge === void 0 ? [] : [placed.badge]],
+    ["figure", placed.figure === void 0 ? [] : [placed.figure]]
+  ];
+  const on = /* @__PURE__ */ new Map();
+  for (const [rung, aliases] of rungs) {
+    for (const alias of aliases) {
+      const earlier = on.get(alias);
+      if (earlier !== void 0) {
+        ctx.issues.push({ code: "custom", input: placed, message: `places "${alias}" on its ${earlier} and its ${rung} \u2014 a column is drawn once on an entry` });
+      } else on.set(alias, rung);
+    }
+  }
+}
+var specEntryPlacementSchema = zod_default.object(specEntryPlacement).strict().check(placedTwice);
 var specItinerarySchema = zod_default.object({
+  /** The day each stop falls under — the run's axis, never a run of a line. */
   when: specColumnAliasSchema,
+  /** Where the stop stands — drawn where `entry.stage_on` says. */
   lifecycle: specColumnAliasSchema,
   /** Where in the day it sits, ordering the run. */
   slot: specColumnAliasSchema.optional(),
-  /** What KIND of stop it is — the word leading its muted line. */
-  kind: specColumnAliasSchema.optional(),
   /**
    * THE PICTURE THE STOP LEADS WITH — the row's own, or the one looked up off
    * the thing it is a stop FOR. A `mark` is no column of a register, so the
@@ -56801,29 +56937,18 @@ var specItinerarySchema = zod_default.object({
    * or it is not drawn.
    */
   mark: specColumnAliasSchema.optional(),
-  /** WHO PERFORMS THE STOP — the link naming them, whose row may carry a mark of its own. */
+  /** WHO PERFORMS THE STOP — the link naming them, whose face `providerMark` is wherever a line reads them. */
   provider: specColumnAliasSchema.optional(),
   /** THAT PROVIDER'S FACE, looked up onto this row — a name alone is a line of identical initials. */
   providerMark: specColumnAliasSchema.optional(),
-  /** HOW LONG IT TAKES inside its day — the measure whose number counts hours. */
-  duration: specColumnAliasSchema.optional(),
-  /** THE OTHER PARTY THE ROW IS WITH — never the provider, whose name the line already carries behind their own face. */
-  caption: specColumnAliasSchema.optional(),
-  /** The confirmation the reader quotes when they ring about the stop. */
-  reference: specColumnAliasSchema.optional(),
   /** How many days the stop RUNS — a stay of three nights is one row and three days of the run. */
   span: specColumnAliasSchema.optional(),
-  /**
-   * WHICH RUNS THE STOP'S MUTED LINE STATES, in order — the plan's own answer.
-   *
-   * Absent, the kit reads a stop by the four a travel row is read by. Each
-   * name resolves to a column named above, so a line is never a fact the run
-   * did not fetch.
-   */
-  line: zod_default.array(zod_default.enum(ITINERARY_RUNS)).min(1).max(STOP_LINE_RUNS).optional(),
+  /** WHERE EACH COLUMN OF THE STOP IS DRAWN — the plan's answer, so the runtime reads no
+   *  role. Absent, the runtime falls back to the roles' own reading rather than throwing. */
+  entry: specEntryPlacementSchema.optional(),
   /** The closing line's label, where the record's band does not already state that sum. */
   total: zod_default.string().min(1).optional()
-}).strict();
+}).strict().check((ctx) => placedTwice({ value: { ...ctx.value.entry, when: ctx.value.when }, issues: ctx.issues }));
 var specWorksheetSchema = zod_default.object({
   /** HOW MANY the line is for — never summed, because two units have no sum. */
   quantity: specColumnAliasSchema.optional(),
@@ -56946,6 +57071,7 @@ var specProgressHistorySchema = zod_default.strictObject({
 }).describe("The dated stage changes behind this ladder");
 var specProgressPhaseSchema = zod_default.strictObject({ label: zod_default.string().min(1), stages: zod_default.array(specOptionIdSchema).min(1) }).describe("One part of the flow and the stages under it");
 var sectionActs = { acts: zod_default.array(specActSchema).min(1).optional() };
+var sectionHead = { facts: zod_default.array(specColumnAliasSchema).min(1).optional() };
 var specPublishDestinationSchema = zod_default.object({
   entity: contractAliasSchema,
   table: specTableIdSchema,
@@ -57085,18 +57211,26 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
-      draw: zod_default.enum(["register", "itinerary", "ledger"]),
+      ...sectionHead,
+      draw: zod_default.enum(["register", "itinerary"]),
       child: specChildSchema,
-      /**
-       * WHAT THE ROWS COME TO, stated ABOVE them — the record's own figures,
-       * drawn as the section's statement head.
-       *
-       * A book of payments with nothing in it is a heading, a verb and a
-       * void; the same section headed by what is owed says what the rows
-       * would be for before the first one exists. So these are columns of the
-       * RECORD, not of the child, and they are drawn at zero rows too.
-       */
-      summary: zod_default.array(specSummaryEntrySchema).min(1).optional(),
+      ...sectionActs
+    }).strict(),
+    /**
+     * A BOOK OF MOVEMENTS closes on its own total, read against the record's
+     * figure that sums it: the balance line under the rows. No strip of the
+     * record's figures stands over them — the header band already draws those,
+     * and a figure is drawn once per record.
+     */
+    zod_default.object({
+      kind: zod_default.literal("children"),
+      key: zod_default.string().min(1),
+      heading: zod_default.string().min(1),
+      ...sectionHead,
+      draw: zod_default.literal("ledger"),
+      child: specChildSchema,
+      /** THE RECORD's column the collected total is read against — its rollup summing these rows' amount, where the record projects one. */
+      against: specColumnAliasSchema.optional(),
       ...sectionActs
     }).strict(),
     /**
@@ -57111,6 +57245,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("capped"),
       child: specChildSchema,
       /** The param this app's own register reads this record off its route by — the foot's door, where those rows are its. */
@@ -57122,6 +57257,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("worksheet"),
       child: specPricedChildSchema,
       ...sectionActs
@@ -57135,6 +57271,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("claim"),
       child: specClaimChildSchema,
       retention: specColumnAliasSchema.optional(),
@@ -57145,6 +57282,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("tree"),
       child: specChildSchema,
       nest: specColumnAliasSchema,
@@ -57159,6 +57297,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("gantt"),
       child: specChildSchema,
       bars: zod_default.object({
@@ -57176,6 +57315,7 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       kind: zod_default.literal("children"),
       key: zod_default.string().min(1),
       heading: zod_default.string().min(1),
+      ...sectionHead,
       draw: zod_default.literal("curve"),
       child: specChildSchema,
       curve: zod_default.object({ planned: specColumnAliasSchema, actual: specColumnAliasSchema, along: specColumnAliasSchema }).strict(),
@@ -57296,11 +57436,11 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
    * section read from its question with the reply marked `answer.official`;
    * a log is read from its latest entry under day heads.
    *
-   * THE ENTRY IS ONE ANATOMY, and every column it reads is a placement on it:
-   * the runtime draws `evidence`, `detail`, `line` and `trailing` without
-   * knowing which role put a column there. `recording` and `verbatim` say which
-   * of those columns plays and which is the fold's transcript, and `facts` are
-   * the detail rung's grid.
+   * THE ENTRY IS ONE ANATOMY, and every column it reads is a placement on it
+   * (`specEntryPlacementSchema`): the runtime draws the lines, the badge, the
+   * figure, the evidence and the detail without knowing which role put a column
+   * there. `recording` and `verbatim` say which of those columns plays and which
+   * is the fold's transcript, and `facts` are the detail rung's grid.
    *
    * An entry nothing names is corrected where it stands and `child.opens` is
    * absent; a NAMED entry (`entry.name`) is a thing in its own right and opens
@@ -57316,11 +57456,8 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
     /** The heads the entries stand under. */
     group: zod_default.literal("day").optional(),
     entry: zod_default.object({
-      /** What the entry is CALLED — leads it where present. */
-      name: specColumnAliasSchema.optional(),
-      /** The entry's own words. */
-      body: specColumnAliasSchema.optional(),
-      /** The day it is filed under, and read in the order of. */
+      ...specEntryPlacement,
+      /** The day it is filed under, and read in the order of — the axis, never a run of a line. */
       when: specColumnAliasSchema,
       /** Who wrote it. */
       author: specColumnAliasSchema.optional(),
@@ -57335,16 +57472,8 @@ var specSectionSchema = zod_default.discriminatedUnion("kind", [
       /** What was literally said or written — the text column among `detail` that is the transcript. */
       verbatim: specColumnAliasSchema.optional(),
       /** What else the entry STATES — the detail rung's grid, label and value, asked by its composer. */
-      facts: zod_default.array(specColumnAliasSchema).min(1).optional(),
-      /** The columns drawn under the words as what the entry shows, in this order. */
-      evidence: zod_default.array(specColumnAliasSchema).min(1).optional(),
-      /** The columns kept behind one fold under the words, in this order. */
-      detail: zod_default.array(specColumnAliasSchema).min(1).optional(),
-      /** The runs of the entry's supporting line, in this order. */
-      line: zod_default.array(specColumnAliasSchema).min(1).optional(),
-      /** The one column worn at the trailing end of the entry's head. */
-      trailing: specColumnAliasSchema.optional()
-    }).strict(),
+      facts: zod_default.array(specColumnAliasSchema).min(1).optional()
+    }).strict().check(placedTwice),
     /** THE ANSWER, where the entries are a correspondence. */
     answer: zod_default.object({
       /** The yes/no one reply is marked the answer with. */
@@ -66971,12 +67100,19 @@ function bindScreen(screen, live, roles, entities, rules, groups = /* @__PURE__
         // THE ROW'S OWN PICTURE leads its name on every line, and a `mark` is in
         // no register's columns — so it is read beside them or no line has a face.
         ...child.fields.flatMap((field) => roleOf(roles, child.alias, field.alias)?.role === "mark" ? [field.alias] : []),
-        // AND SO IS WHAT THE STOP IS, AND THE CODE IT IS CONFIRMED BY: both close
-        // an itinerary's muted line rather than standing as columns, and the
-        // register's four-column budget would otherwise decide whether the run
-        // can draw its own anatomy.
-        ...itinerary?.kind === void 0 ? [] : [itinerary.kind.alias],
-        ...itinerary?.reference === void 0 ? [] : [itinerary.reference.alias],
+        // AND SO IS EVERYTHING THE STOP'S PLACEMENT DRAWS — its lines, its
+        // badge, its figure, what it shows and what it folds: each stands on the
+        // stop rather than in a column, and the register's four-column budget
+        // would otherwise decide whether the run can draw its own anatomy.
+        ...itinerary === void 0 ? [] : [
+          itinerary.name,
+          itinerary.body,
+          ...itinerary.lines.flat(),
+          itinerary.badge,
+          itinerary.figure,
+          ...itinerary.evidence,
+          ...itinerary.detail
+        ].flatMap((field) => field === void 0 ? [] : [field.alias]),
         // AND SO IS THE STOP'S PICTURE. A `mark` is not in `DRAWN_ROLES`, so no
         // register column would ever have projected it — a run that leads with
         // a face has to ask for the column itself, and a child whose rows open
@@ -66985,10 +67121,6 @@ function bindScreen(screen, live, roles, entities, rules, groups = /* @__PURE__
         // …AND THE PROVIDER'S, which is a lookup no column of a register draws
         // either: the run is the only surface that puts a face beside the name.
         ...itinerary?.providerMark === void 0 ? [] : [itinerary.providerMark.alias],
-        // AND THE OTHER PARTY THE ROW IS WITH, which the register's four-column
-        // budget may never have seated: a caption the plan puts on the line is a
-        // name, and a name the read did not answer with is a blank.
-        ...itinerary?.caption === void 0 ? [] : [itinerary.caption.alias],
         // …AND THE OTHER END OF THE JOURNEY. A route is ONE column, `A → B`, so
         // the register draws the `origin` and READS the `destination` beside it:
         // a column of its own would cost a second seat and leave the reader
@@ -67108,8 +67240,9 @@ function bindScreen(screen, live, roles, entities, rules, groups = /* @__PURE__
           ...section.facts,
           ...section.evidence,
           ...section.detail,
-          ...section.line,
-          ...section.trailing === void 0 ? [] : [section.trailing],
+          ...section.lines.flat(),
+          ...section.badge === void 0 ? [] : [section.badge],
+          ...section.figure === void 0 ? [] : [section.figure],
           ...section.answer === void 0 ? [] : [section.answer.official, ...section.answer.awaiting === void 0 ? [] : [section.answer.awaiting]]
         ]);
         continue;
@@ -67230,7 +67363,7 @@ function stated(entry, field) {
 }
 function factLinkTargets(screen, sections, entities, roles, owns) {
   if (!writesRecord(screen.screen.writes) || !owns) return [];
-  return sections.flatMap((section) => section.kind === "facts" ? section.fields : []).flatMap((field) => linkTarget2(field, entities, roles));
+  return sections.flatMap((section) => section.kind === "facts" ? section.fields : section.kind === "children" ? section.head ?? [] : []).flatMap((field) => linkTarget2(field, entities, roles));
 }
 function linkTarget2(field, entities, roles, stands = false) {
   if (field.type !== "select_record_link" || !(isEditable(field) || stands)) return [];
@@ -67341,6 +67474,7 @@ function savedFields(entry) {
   const bodies = entry.screen.entity.fields.filter((field) => sent.has(field.alias) && stated(entry, field));
   return banded.concat(bodies).concat(entry.sections.flatMap(({ section }) => {
     if (section.kind === "facts") return section.fields.filter((field) => stated(entry, field));
+    if (section.kind === "children") return (section.head ?? []).filter((field) => stated(entry, field));
     if (section.kind === "progress") return [section.field];
     if (section.kind === "prose") return stated(entry, section.field) ? [section.field] : [];
     if (section.kind === "charge") return [section.quantity, section.unitPrice].filter((field) => stated(entry, field));
@@ -67838,7 +67972,7 @@ function composedEntry(section) {
     ...once(section.fields.filter((field) => field.type === "select" && field.multi !== true)),
     // …AND WHAT ELSE THE ENTRY STATES, which is drawn with it: a figure the
     // entry shows and nothing can fill is a column read blank for ever.
-    ...once([...section.line, section.trailing, ...section.facts])
+    ...once([...section.lines.flat(), section.badge, section.figure, ...section.facts])
   ];
 }
 function planCreate(entry, roles, on = entry, drawn) {
@@ -68716,20 +68850,16 @@ function specChild(child, roles, archetype, slot2, entry, expected) {
   });
   const runs = child.itinerary !== void 0 || columns.some((column) => column.role === "when") ? run : void 0;
   const plan = child.itinerary;
-  const total = itineraryTotal(entry, child);
+  const total = itineraryTotal(entry, child, roles);
   const itinerary = plan === void 0 || ref(plan.when) === void 0 || ref(plan.lifecycle) === void 0 ? void 0 : {
     when: ref(plan.when) ?? "",
     lifecycle: ref(plan.lifecycle) ?? "",
     ...ref(plan.slot) === void 0 ? {} : { slot: ref(plan.slot) ?? "" },
-    ...ref(plan.kind) === void 0 ? {} : { kind: ref(plan.kind) ?? "" },
     ...ref(plan.mark) === void 0 ? {} : { mark: ref(plan.mark) ?? "" },
     ...ref(plan.provider) === void 0 ? {} : { provider: ref(plan.provider) ?? "" },
     ...ref(plan.providerMark) === void 0 ? {} : { providerMark: ref(plan.providerMark) ?? "" },
-    ...ref(plan.duration) === void 0 ? {} : { duration: ref(plan.duration) ?? "" },
-    ...ref(plan.caption) === void 0 ? {} : { caption: ref(plan.caption) ?? "" },
-    ...ref(plan.reference) === void 0 ? {} : { reference: ref(plan.reference) ?? "" },
     ...ref(plan.span) === void 0 ? {} : { span: ref(plan.span) ?? "" },
-    ...plan.line === void 0 ? {} : { line: [...plan.line] },
+    entry: { ...specEntryPlacement2(plan, ref), stage_on: plan.stageOn },
     ...total === void 0 ? {} : { total }
   };
   const opens = childOpens(entry, child);
@@ -68861,27 +68991,34 @@ function specClaim(child, roles, clause) {
   const unit = ref(clause.unit);
   return { quantity, contract, price, previous, ...code === void 0 ? {} : { code }, ...unit === void 0 ? {} : { unit } };
 }
-function itineraryTotal(entry, child) {
+function specEntryPlacement2(plan, ref) {
+  const each = (fields) => fields.flatMap((field) => {
+    const bound = ref(field);
+    return bound === void 0 ? [] : [bound];
+  });
+  const name = ref(plan.name);
+  const body = ref(plan.body);
+  const badge = ref(plan.badge);
+  const figure = ref(plan.figure);
+  const lines = plan.lines.map(each).filter((line) => line.length > 0);
+  const evidence = each(plan.evidence);
+  const detail = each(plan.detail);
+  return {
+    ...name === void 0 ? {} : { name },
+    ...body === void 0 ? {} : { body },
+    ...lines.length === 0 ? {} : { lines },
+    ...badge === void 0 ? {} : { badge },
+    ...figure === void 0 ? {} : { figure },
+    ...evidence.length === 0 ? {} : { evidence },
+    ...detail.length === 0 ? {} : { detail }
+  };
+}
+function itineraryTotal(entry, child, roles) {
   const amountAlias = [...child.fields.keys()].find((alias) => child.roles.get(alias) === "amount");
   const amount = amountAlias === void 0 ? void 0 : child.fields.get(amountAlias);
-  if (amountAlias === void 0 || amount === void 0) return void 0;
-  const links = child.entity.fields.filter(
-    (field) => field.type === "select_record_link" && field.target_entity === entry.screen.entity.alias
-  );
-  const hangsOn = links.find((field) => field.alias === child.linkAlias);
-  if (hangsOn === void 0 || hangsOn.type !== "select_record_link") return amount.label;
-  const banded = bandFields(entry.band).some((field) => {
-    if (field.type !== "rollup" || field.aggregate_option.operation !== "sum") return false;
-    if (field.aggregate_option.field_key !== amountAlias) return false;
-    const through = entry.screen.entity.fields.find((candidate) => candidate.alias === field.source_field_alias);
-    if (through === void 0 || through.type !== "select_record_link" || through.target_entity !== child.entity.alias) {
-      return false;
-    }
-    if (through.paired_field_alias !== void 0) return through.paired_field_alias === hangsOn.alias;
-    if (hangsOn.paired_field_alias !== void 0) return hangsOn.paired_field_alias === through.alias;
-    return links.length === 1;
-  });
-  return banded ? void 0 : amount.label;
+  if (amount === void 0) return void 0;
+  const sum2 = recordSum(entry.screen.entity, child.entity, child.linkAlias, roles);
+  return sum2 !== void 0 && bandFields(entry.band).some((field) => field.alias === sum2.alias) ? void 0 : amount.label;
 }
 function specFactSections(entry, roles, fields, stands, before) {
   return factSections(specFactGroups(entry, roles, fields)).map((bands, index) => {
@@ -69031,6 +69168,11 @@ function specRecord(entry, roles, templates, register) {
       case "children": {
         const child = entry.children.get(childKey(section.child.alias, section.link.alias));
         if (child === void 0) break;
+        const framed = (section.head ?? []).flatMap((field) => {
+          const bound2 = entry.fields.get(field.alias);
+          return bound2 === void 0 ? [] : [bound2.alias];
+        });
+        const head = framed.length === 0 ? {} : { facts: framed };
         const desk = child.publish;
         if (desk !== void 0) {
           sections.push({
@@ -69120,7 +69262,7 @@ function specRecord(entry, roles, templates, register) {
         const key = sectionKey(child.entity.alias, child.linkAlias);
         const bound = specChild(child, roles, archetype, slot2, entry, section.expected);
         if (sheet !== void 0) {
-          sections.push({ kind: "children", key, heading: child.heading, draw: "worksheet", child: { ...bound, worksheet: specWorksheet(sheet) }, ...stands });
+          sections.push({ kind: "children", key, heading: child.heading, ...head, draw: "worksheet", child: { ...bound, worksheet: specWorksheet(sheet) }, ...stands });
           break;
         }
         const drawnAs = entry.screen.screen.sections?.[child.entity.alias];
@@ -69132,6 +69274,7 @@ function specRecord(entry, roles, templates, register) {
             key,
             heading: child.heading,
             draw: "claim",
+            ...head,
             child: { ...bound, claim },
             ...retention === void 0 ? {} : { retention },
             ...stands
@@ -69140,7 +69283,7 @@ function specRecord(entry, roles, templates, register) {
         }
         const nest = drawnAs?.draw === "tree" ? childReads(child).get(drawnAs.nest)?.alias : void 0;
         if (nest !== void 0) {
-          sections.push({ kind: "children", key, heading: child.heading, draw: "tree", child: bound, nest, ...stands });
+          sections.push({ kind: "children", key, heading: child.heading, ...head, draw: "tree", child: bound, nest, ...stands });
           break;
         }
         const projected = (alias) => alias === void 0 ? void 0 : childReads(child).get(alias)?.alias;
@@ -69159,6 +69302,7 @@ function specRecord(entry, roles, templates, register) {
               key,
               heading: child.heading,
               draw: "gantt",
+              ...head,
               child: bound,
               bars: {
                 start: from,
@@ -69178,25 +69322,17 @@ function specRecord(entry, roles, templates, register) {
           const actual = projected(drawnAs.actual);
           const along = projected(datedBy(child.entity, roles)?.alias);
           if (planned !== void 0 && actual !== void 0 && along !== void 0) {
-            sections.push({ kind: "children", key, heading: child.heading, draw: "curve", child: bound, curve: { planned, actual, along }, ...stands });
+            sections.push({ kind: "children", key, heading: child.heading, ...head, draw: "curve", child: bound, curve: { planned, actual, along }, ...stands });
             break;
           }
         }
-        const summary = drawnAs?.draw === "ledger" ? drawnAs.summary.flatMap((stated3) => {
-          const alias = typeof stated3 === "string" ? stated3 : stated3.field;
-          const figure = entry.fields.get(alias);
-          if (figure === void 0) return [];
-          return typeof stated3 === "string" ? [figure.alias] : [{ field: figure.alias, sense: stated3.sense }];
-        }) : [];
-        sections.push({
-          kind: "children",
-          key,
-          heading: child.heading,
-          draw: ledger || drawnAs?.draw === "ledger" ? "ledger" : child.itinerary === void 0 ? "register" : "itinerary",
-          child: bound,
-          ...summary.length === 0 ? {} : { summary },
-          ...stands
-        });
+        if (ledger || drawnAs?.draw === "ledger") {
+          const owed = bookAgainst(entry.screen.entity, child.entity, child.linkAlias, roles);
+          const against = owed === void 0 ? void 0 : entry.fields.get(owed.alias)?.alias;
+          sections.push({ kind: "children", key, heading: child.heading, ...head, draw: "ledger", child: bound, ...against === void 0 ? {} : { against }, ...stands });
+          break;
+        }
+        sections.push({ kind: "children", key, heading: child.heading, ...head, draw: child.itinerary === void 0 ? "register" : "itinerary", child: bound, ...stands });
         break;
       }
       case "prose": {
@@ -69258,7 +69394,6 @@ function specRecord(entry, roles, templates, register) {
         const body = one(section.body);
         const when = one(section.when);
         if (body === void 0 || when === void 0) break;
-        const name = one(section.name);
         const author = one(section.author);
         const withParties = many(section.with);
         const address = one(section.address);
@@ -69266,10 +69401,6 @@ function specRecord(entry, roles, templates, register) {
         const recording = one(section.recording);
         const verbatim = one(section.verbatim);
         const facts = many(section.facts);
-        const evidence = many(section.evidence);
-        const detail = many(section.detail);
-        const line = many(section.line);
-        const trailing = one(section.trailing);
         const official = one(section.answer?.official);
         const awaiting = one(section.answer?.awaiting);
         const clock = section.answer?.clock === void 0 ? void 0 : entry.fields.get(section.answer.clock.alias)?.alias;
@@ -69281,7 +69412,7 @@ function specRecord(entry, roles, templates, register) {
           order: section.order,
           ...section.group === void 0 ? {} : { group: section.group },
           entry: {
-            ...name === void 0 ? {} : { name },
+            ...specEntryPlacement2(section, one),
             body,
             when,
             ...author === void 0 ? {} : { author },
@@ -69290,11 +69421,7 @@ function specRecord(entry, roles, templates, register) {
             ...files === void 0 ? {} : { files },
             ...recording === void 0 ? {} : { recording },
             ...verbatim === void 0 ? {} : { verbatim },
-            ...facts.length === 0 ? {} : { facts },
-            ...evidence.length === 0 ? {} : { evidence },
-            ...detail.length === 0 ? {} : { detail },
-            ...line.length === 0 ? {} : { line },
-            ...trailing === void 0 ? {} : { trailing }
+            ...facts.length === 0 ? {} : { facts }
           },
           ...official === void 0 ? {} : { answer: { official, ...awaiting === void 0 ? {} : { awaiting }, ...clock === void 0 ? {} : { clock } } },
           ...stands
@@ -69525,32 +69652,12 @@ function checkSurface(at2, alias, table, fields, manifest) {
 var paramsOf = (manifest, alias) => new Set(Object.keys(manifest.queries?.[alias]?.params ?? {}));
 function itineraryReads(plan) {
   if (plan === void 0) return [];
-  return [
-    plan.when,
-    plan.lifecycle,
-    plan.slot,
-    plan.kind,
-    plan.mark,
-    plan.provider,
-    plan.providerMark,
-    plan.duration,
-    plan.caption,
-    plan.reference,
-    plan.span
-  ].filter(
+  return [plan.when, plan.lifecycle, plan.slot, plan.mark, plan.provider, plan.providerMark, plan.span, ...placementReads(plan.entry ?? {})].filter(
     (alias) => alias !== void 0
   );
 }
-function itineraryRunAliases(plan) {
-  return {
-    when: plan.when,
-    kind: plan.kind,
-    provider: plan.provider,
-    stage: plan.lifecycle,
-    duration: plan.duration,
-    caption: plan.caption,
-    reference: plan.reference
-  };
+function placementReads(entry) {
+  return [entry.name, entry.body, ...(entry.lines ?? []).flat(), entry.badge, entry.figure, ...entry.evidence ?? [], ...entry.detail ?? []];
 }
 function checkDeskIsSoleEditor(at2, desk, record2) {
   const filed = new Map(
@@ -69699,9 +69806,11 @@ function checkRecord(spec, key, record2, manifest) {
         }
       }
     }
-    if (section.kind === "children" && section.draw === "ledger") {
-      for (const entry of section.summary ?? []) {
-        const alias = summaryEntryOf(entry).field;
+    if (section.kind === "children" && section.draw === "ledger" && section.against !== void 0 && !Object.hasOwn(record2.fields, section.against)) {
+      findings.push({ at: childAt, message: `reads its total against "${section.against}", which this record does not project` });
+    }
+    if (section.kind === "children") {
+      for (const alias of section.facts ?? []) {
         if (!Object.hasOwn(record2.fields, alias)) {
           findings.push({ at: childAt, message: `heads its rows with "${alias}", which this record does not project` });
         }
@@ -69778,8 +69887,7 @@ function checkRecord(spec, key, record2, manifest) {
       ...section.kind === "acts" ? actsReads2(section) : [],
       ...section.kind === "schedule" ? [section.planned, section.actual] : [],
       ...section.kind === "log" ? [
-        ...section.entry.name === void 0 ? [] : [section.entry.name],
-        ...section.entry.body === void 0 ? [] : [section.entry.body],
+        ...placementReads(section.entry).filter((alias) => alias !== void 0),
         section.entry.when,
         ...section.entry.author === void 0 ? [] : [section.entry.author],
         ...section.entry.with ?? [],
@@ -69788,10 +69896,6 @@ function checkRecord(spec, key, record2, manifest) {
         ...section.entry.recording === void 0 ? [] : [section.entry.recording],
         ...section.entry.verbatim === void 0 ? [] : [section.entry.verbatim],
         ...section.entry.facts ?? [],
-        ...section.entry.evidence ?? [],
-        ...section.entry.detail ?? [],
-        ...section.entry.line ?? [],
-        ...section.entry.trailing === void 0 ? [] : [section.entry.trailing],
         ...section.answer === void 0 ? [] : [section.answer.official, ...section.answer.awaiting === void 0 ? [] : [section.answer.awaiting]]
       ] : [],
       ...itineraryReads(child.itinerary)
@@ -69801,18 +69905,6 @@ function checkRecord(spec, key, record2, manifest) {
         findings.push({ at: childAt, message: `reads "${alias}", which "${child.query}" does not project` });
       }
     }
-    const run = child.itinerary;
-    if (run?.line !== void 0) {
-      const aliases = itineraryRunAliases(run);
-      for (const name of run.line) {
-        if (aliases[name] === void 0) {
-          findings.push({
-            at: childAt,
-            message: `reads its stops by "${name}", which this run names no column for \u2014 a stop's line states ${ITINERARY_RUNS.join(", ")}`
-          });
-        }
-      }
-    }
     if (section.kind === "log" && section.answer?.clock !== void 0 && !Object.hasOwn(record2.fields, section.answer.clock)) {
       findings.push({ at: childAt, message: `counts down to "${section.answer.clock}", which this record does not project` });
     }
@@ -79316,7 +79408,7 @@ Captured ${totalRows} row${totalRows === 1 ? "" : "s"} across ${result.captured.
 }
 
 // src/model_reference.md
-var model_reference_default = '# The Lotics workspace model (`model.json`)\n\nOne JSON file describing the tables, fields, options, views, roles and first rows\na workspace starts with. `lotics scaffold check model.json` proves it offline \u2014\nno account, no network. `lotics setup model.json --email you@company.com` creates\nthe account and applies it. `lotics scaffold apply model.json` applies it again,\ninto the workspace the credential names.\n\n**There are two forms of this file.** The full one, below, spells the model out.\nThe `from` one names a published preset and carries only what this business\ndiffers by \u2014 see \xA7 Starting from a preset, and prefer it whenever a preset fits\nthe trade.\n\nApps are PLANNED here and built afterwards: `apps` names each app\'s screens as a\nshape over an entity, checked against the roles `field_roles` gives its fields,\nso the plan is refused before anyone builds a screen (\xA7 Apps and screens). The\nbuilt app lives in the workspace; publishing that workspace as a package is how\nit ships.\n\n## The rules\n\n- **At least one entity, at most 50.** More tables than that is a data model\n  being designed, not scaffolded \u2014 scaffold the rest in a second call.\n- **Adoption is explicit.** `lotics setup` REFUSES an entity whose `label`\n  already names a table in the workspace, naming every colliding label at once.\n  `lotics scaffold apply` adopts those tables and adds the fields, options and\n  views they are missing. Nothing is ever modified or deleted, so applying the\n  same model twice creates nothing the second time.\n- **Adoption is by LABEL, not alias.** Change an entity\'s `label` and the next\n  run asks for a NEW table beside the old one. Renaming a FIELD is\n  `lotics field rename <table> <field> "<new label>" --model <this file>`, which\n  moves the platform, this file and every app bound to it together; deleting is\n  `lotics run delete_table`. Neither goes through the file.\n- **The file\'s own majority is the language.** A model names no locale \u2014 which\n  language it is in is what it mostly says, and `scaffold check` notes the label\n  written the other way. The generated screens read the kit\'s pack, and a\n  generated WRITE cannot: its refusals run on the server, so they are worded in\n  that same majority. Mix the two and the workspace answers in two languages.\n- **`lotics scaffold diff model.json` says where the file and the workspace have\n  come apart**, joined on label, entity then field \u2014 the join adoption itself\n  makes. It exits 1 on any difference, so a model that is about to be published\n  as a preset carries the labels in use rather than the ones it was written with.\n- **Rows land only where every bound table is empty.** One table already holding\n  records and no rows are written anywhere, and the result says\n  `rows_skipped: true`: sample rows landing among a customer\'s real ones cannot\n  be told apart from them.\n- **After the first run the WORKSPACE is the source of truth.** The file is an\n  authoring input, not a mirror \u2014 scaffold never deletes what the file stopped\n  naming.\n- **`lotics scaffold check` decides all of it offline**, and reports every\n  problem in one run rather than the first: an alias that resolves to nothing, a\n  link whose pair is not symmetric, and the rows themselves \u2014 a field the entity\n  does not declare, an option alias the field does not declare, a link naming no\n  row in the file, a `ref` used twice, a date that is not one, a value on a\n  platform-computed field, and a files cell that is neither a relative path\n  beside this file nor a `fil_` id.\n\n## Top level\n\n```jsonc\n{\n  "entities": [ /* the tables */ ],\n  "roles":    [ /* workspace groups to create */ ],    // optional\n  "templates":[ /* inline html / email templates */ ], // optional\n  "rows":     { /* first records, keyed by entity alias */ },  // optional\n  "field_roles": { /* the reporting role each field plays, keyed by entity then field */ }, // optional\n  "write_rules": { /* what a CREATE finds, defaults and refuses, keyed by entity */ }, // optional\n  "apps":     [ /* the screens each app will have, as shapes over entities */ ], // optional\n  "apply":    [ /* published packages to copy in afterwards */ ], // optional\n  "preset":   { /* a trade\'s branches, for a PUBLISHED model */ } // optional\n}\n```\n\nThe other form names a preset instead of restating one:\n\n```jsonc\n{\n  "from":     "field_service",             // the preset this model starts from, by slug\n  "variants": ["crews"],                   // optional \u2014 its branches to merge in, in order\n  "rename":   {                            // optional \u2014 what THIS business calls each table\n    "job": { "label": "\u0110\u01A1n h\xE0ng", "fields": { "code": "M\xE3 \u0111\u01A1n" } }\n  },\n  "entities": [ /* tables the preset does not declare */ ],    // optional\n  "rows":     { /* first records, keyed by entity alias */ },  // optional\n  "field_roles": { /* roles on the preset\'s fields and this business\'s own */ }, // optional\n  "write_rules": { /* create-time clauses on the preset\'s entities and its own */ }, // optional\n  "apps":     [ /* the screens each app will have */ ],        // optional\n  "apply":    [ /* published packages to copy in afterwards */ ] // optional\n}\n```\n\n**A model may not carry** `fixtures`, `knowledge` or `knowledge_expects`, and no\n`excel` / `word` / `pdf-form` template: each of those is content that lives in a\npublished bundle, which a model has none of. `apps` here is a plan of screens,\nnever built code. An unknown top-level key is an error, never ignored.\n\n### Aliases\n\nEvery `alias` is a lowercase slug \u2014 a letter, then letters, digits and\nunderscores (`unit_price`, `so_1001`). Aliases are how the file cross-references\nitself; they are never shown to anyone. `label` is what a person sees.\n\nLabels must be unique within their namespace \u2014 two entities, two fields on one\nentity, two options on one field, two views on one entity, two roles or two\ntemplates cannot share a label, because scaffold matches by label.\n\n## Entity\n\n```jsonc\n{\n  "alias": "order",\n  "label": "Orders",            // the table\'s name, which names the SET it holds\n  "singular": "Order",          // optional \u2014 ONE of them, for the act that opens one\n  "description": "\u2026",           // optional\n  "writes": false,              // optional \u2014 only the workspace\'s automations write these rows\n  "fields": [ /* at least one */ ],\n  "views":  [ /* optional; an entity with none still gets the default grid */ ],\n  "read_scope": { /* optional; absent, everyone with access to the table reads every row */\n    "any": [\n      { "member_of": "sales" },                       // a role alias this model declares\n      { "field": "scope", "is": ["shared"] },         // a single select on this entity, by option alias\n      { "field": "assignee", "is": "self" }           // a select_member on this entity \u2014 the members it names\n    ]\n  },\n  "unique": [["bed", "sown_on"]] // optional \u2014 sets of fields no two live rows share\n}\n```\n\n**`unique` is a set of values no two live rows share.** Each entry names fields\nof this entity holding ONE value \u2014 text, number, date, a single select, a link\nof cardinality `"one"` \u2014 and a create or update landing a second row with the\nsame values is refused. A set of one text field is that field\'s own `unique:\ntrue`, so it is refused here. A create carries each set in the names its panel\nsends, so the panel can name the duplicate before the write does, and `scaffold\ncheck` prints it under *Who writes what* as `unique: Bed + Sown on`.\n\n**`singular` is what a create says.** A register\'s own act and the panel it\nopens name the row being made \u2014 `New Order`, `H\u1ED3 s\u01A1 m\u1EDBi` \u2014 while `label` names\nthe table, so without it the button reads `New Orders`. Nothing derives it\n(English plurals are irregular), and most models need none: a Vietnamese noun is\nthe same word either way. `scaffold check` prints it beside the table under *Who\nwrites what* and NOTES a table that will name the set. An act on a child section\nkeeps the label: it adds a line to the register under the record the reader is\nalready standing in.\n\n**`writes: false` says only the workspace\'s automations write these rows** \u2014 a\nlog of what the system sent, a copy of what another system holds. No app opens,\nedits or files one: a record listing them keeps the section and opens each row\nat rest, with no Add; a screen over the entity operates at most the rows its\nrecord owns; a party of it is picked, never found or minted; and the generator\nwrites no create, no update and no `lotics.writes` entry for it. `scaffold\ncheck` prints it under *Who writes what* as `written by automations` and never\nnotes it as created nowhere. A `lifecycle` on it is refused \u2014 a row walked\nthrough stages is worked by a person \u2014 and so is a publish desk over it. Absent,\npeople write the rows; `true` is not a value.\n\n**`read_scope` is a ROW rule, enforced by the platform.** A row is readable when\nANY clause holds: the reader is in that role\'s group, the named select carries\none of those options, or the named `select_member` column names the reader\n(`"is": "self"`, on a column of one member or several). It is resolved at\nscaffold into the table\'s own row filters, so an app, a workflow reading for a\nviewer, and the API all answer the same rows \u2014 a per-record visibility field the\napp merely honours is a convention, not a gate. `any` may not be empty (a rule\nnobody satisfies hides the table), and every role alias and option alias in it\nmust be one this model declares. Scaffold writes the rule onto a table it\nCREATES; a table it adopted that ALREADY CARRIES a rule keeps that one, because\nthe rule is the workspace\'s own statement about its rows \u2014 and a run whose model\nstates a different rule reports the entity rather than leaving the claim silent.\n\n**An app may state that its sharing is its read gate: `"reads": "shared"`.** An\napp reads as its owner, so the rule reaches a viewer only as the predicate every\nquery and editor guard of every app over the entity carries \u2014 right for a desk of\none\'s own rows, wrong for a desk whose audience its sharing already decides, where\nwidening the rule meant a role group nobody remembers to fill. Stated on an APP,\nits queries, pickers and guards carry no entity\'s rule and whoever the app is\nshared with reads and writes every row it draws; every other app and the table\'s\nown filters keep the rule. Share it deliberately. Refused on an app none of whose\ntables states a `read_scope`; `scaffold check` prints it on the app\'s line and\nnames the app beside the rule it is exempt from.\n\n**The rows under a private record INHERIT its rule.** An entity that states no\n`read_scope` and hangs under one that does \u2014 through its `parent` link, over one\nhop or several \u2014 is read by the ancestor\'s rule, answered through that link, on\nits table\'s own filters and in every query and guard alike; nothing is restated,\nso a child needs none of the ancestor\'s columns. Stating a rule on the child\nkeeps that one instead, an ancestor with no rule passes nothing down, and a row\nhanging further under the scoped one than a row filter reaches is refused by\nname \u2014 state a rule on it. So is a hop over a link that names more than one row:\nthe rule would admit a reader any one of them admits while the editor\'s guard\nreads the first, so give the link `"cardinality": "one"` or state a rule on the\nchild.\n\n**ONLY the `parent` role is walked.** A register a scoped record reaches by any\nother link \u2014 the rows that NAME it \u2014 is read by that record\'s id with no rule\ntravelling to it, so it is refused until it states one of its own.\n\n## Field\n\nEvery field carries `alias`, `label`, an optional `description`, and an optional\n`required` \u2014 the table refuses a new row that leaves it empty, and an edit that\nclears it. So every row in `rows` states each required field it carries (a\ndefault is not applied to them), and a required LINK is written with its row:\nthe entity it names is created first, and entities whose required links name\neach other are refused, since none of their rows could ever be created. `label`\nmay not contain `{` or `}` (formulas reference fields by label at the platform\nlevel).\n\n`default` is the value pre-filled into a NEW record. It applies on create only;\nexisting records are never backfilled. Only the types listed below accept one.\n\n### `text`\n\n```jsonc\n{ "alias": "name", "label": "Name", "type": "text",\n  "unique": false,              // optional \u2014 require distinct values\n  "format": "text",             // optional \u2014 "text" | "link" | "markdown"\n  "default": "" }               // optional\n```\n\n### `number`\n\n```jsonc\n{ "alias": "amount", "label": "Amount", "type": "number",\n  "format": "currency",         // optional \u2014 "number" | "currency" | "percentage"\n  "currency": "VND",            // optional \u2014 ISO 4217\n  "default": 0 }                // optional\n```\n\n`format` is what the number IS, and every surface reads it: `currency` prints as\nmoney in the code the row or the field states, `percentage` as a whole percent\nwith its sign. An ABSENT number is drawn absent \u2014 the one exception is a\n`sum` or count rollup the plan reads as a **`measure`**: that is the thing\naccumulated toward a bound, so nothing accumulated yet is zero and the meter\ndraws it. The same rollup read as an `amount` keeps its blank, and so does every\nother role: nothing added to what a row is WORTH means unpriced, not free. A\n`min`, an `avg`, a percentage of nothing and every FORMULA stay blank in any\nrole, because none of them has an answer to give. This is why the pair on one\nscreen reads two ways \u2014 what has come in against what is owed \u2014 and why a\nmeasure\'s own LIMIT, an amount, leaves an unquoted row out of the count rather\nthan reporting it as nothing collected. **AND WHERE THAT LIMIT IS ABSENT \u2014 OR\nZERO \u2014 THERE IS NO LEVEL AT ALL**: a level is a reading AGAINST a bound, so a row\nthat states no bound, or a bound of nothing, draws nothing \u2014 cell, fact and all \u2014\nrather than a numerator whose whole meaning was the comparison. "Collected 0"\nbeside a blank total reads as money against a job worth nothing, and "0 of 0"\nagainst a count of nothing owed claims a comparison nobody can make. A measure the model gives no limit is a plain figure\nand is unaffected. A share is stored in percent units \u2014 68.1 is 68.1 % \u2014 and the\ncolumn, the fact behind it, the meter it is judged by and the figure over the\nregister all say so.\n\n### `date`\n\n```jsonc\n{ "alias": "placed_on", "label": "Placed on", "type": "date",\n  "format": "date",             // optional \u2014 "date" | "datetime" | "date_range" | "datetime_range"\n  "timezone": "Asia/Ho_Chi_Minh",  // optional \u2014 IANA name\n  "derive_from": "created_at",  // optional \u2014 "created_at" | "updated_at"; makes the field read-only\n  "default": "2026-01-01" }     // optional; refused together with derive_from\n```\n\n### `boolean`\n\n```jsonc\n{ "alias": "paid", "label": "Paid", "type": "boolean", "default": false }\n```\n\n### `select`\n\n```jsonc\n{ "alias": "tier", "label": "Tier", "type": "select",\n  "options": [                                     // at least one\n    { "alias": "standard", "label": "Standard", "color": "slate" },\n    { "alias": "gold",     "label": "Gold",     "color": "amber" }\n  ],\n  "multi": false,               // optional\n  "default": ["standard"] }     // optional \u2014 option ALIASES; one unless multi\n```\n\n`color` is one of: `red`, `orange`, `amber`, `yellow`, `lime`, `green`,\n`emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`,\n`fuchsia`, `pink`, `rose`, `slate`, `gray`, `zinc`, `neutral`, `stone`.\n\n### `select_member`\n\nA person picker over the workspace\'s members. No default: a model cannot name\nmembers of a workspace that does not exist yet.\n\n```jsonc\n{ "alias": "owner", "label": "Owner", "type": "select_member", "multi": false }\n```\n\n### `select_record_link`\n\n```jsonc\n{ "alias": "customer", "label": "Customer", "type": "select_record_link",\n  "target_entity": "customer",        // an entity alias this model declares\n  "cardinality": "one",               // optional \u2014 "one" | "many" (default "many")\n  "sync_both_ways": true,             // optional \u2014 keep a paired field on the target\n  "paired_field_alias": "orders",     // the partner field ON THE TARGET entity\n  "display_field_aliases": ["name"] } // optional \u2014 what the link shows / the picker\'s columns\n```\n\nA two-way link is declared on BOTH sides, each naming the other as its\n`paired_field_alias`; the pair must be symmetric or the model is refused.\n\n**A single-valued link needs no partner.** `"cardinality": "one"` on its own is a\nlink that holds one row \u2014 one customer on an invoice, one project on a device \u2014\nand nothing is created on the target. The mirror invariant belongs to a PAIRED\nlink: pair a link when the target\'s own record should list what points at it, and\nleave it unpaired when it should not. Either way the record plan draws the\nrelation as a section on the side it points at, so an unpaired link costs the\ntarget nothing.\n\n### `files`\n\n```jsonc\n{ "alias": "attachments", "label": "Attachments", "type": "files" }\n```\n\n### `formula`\n\n```jsonc\n{ "alias": "total", "label": "Total", "type": "formula",\n  "formula": {\n    "expression": "{amount} * 1.1",  // fields on THIS entity, by alias, in braces\n    "output_type": "number",         // optional \u2014 what it YIELDS: "number" | "text" | "date" | "datetime" | "boolean"\n    "format": "currency",            // optional \u2014 how that result is DRAWN: "number" | "currency" | "percentage" | "link"\n    "currency": "VND"                // optional\n  } }\n```\n\n**A select reaches a formula as the KEYS of its chosen options**, a list \u2014\nnever their labels, and never their aliases \u2014 and a model has no keys: the\nworkspace mints them when the table is made. So an option is named in a formula\nas `{field:option}`, both aliases, and the copy writes that option\'s key in its\nplace: `includes({kind}, {kind:crate})` for a select holding one or several,\n`{kind}[0] == {kind:crate}` for a single one. A select compared to its own words\n(`{kind} != "Crate"`) matches no row and computes the other branch everywhere,\nso `check` refuses it and names the token. A select looked up from another\nentity is tested there, in a formula of its own, and that result looked up.\n\n`output_type` is what the expression answers WITH; `format` is how it is printed.\nThe platform infers the result at write time and ignores what you declare, so\nthis is a statement the offline checks read \u2014 which is what lets a role or a\nscreen clause accept a computed value: a caption over a derived name\n(`output_type: "text"`), a period over a settled date (`"date"`). A formula\ndeclaring neither says nothing about its result, and every rule that needs one\nrefuses it by name. `lotics scaffold export` writes the result a live workspace\ncomputed, so exporting a workspace fills these in.\n\n### `rollup`\n\nAggregates the records reached through a link on this entity.\n\n```jsonc\n{ "alias": "total_ordered", "label": "Total ordered", "type": "rollup",\n  "source_field_alias": "orders",    // a select_record_link field on THIS entity\n  "aggregate_option": {\n    "operation": "sum",              // count | sum | avg | median | min | max | range |\n                                     // empty | filled | percent_empty | percent_filled |\n                                     // unique | percent_unique |\n                                     // earliest | latest | date_range |\n                                     // checked | unchecked | percent_checked |\n                                     // percent_unchecked\n    "field_key": "amount"            // a field ALIAS on the linked entity ("count" may omit it)\n  },\n  "filter": { /* optional \u2014 see Views; every field_key is an alias on the LINKED entity */ } }\n```\n\nThe operation must be one the aggregated field\'s type allows \u2014 `sum` over a\nnumber, `earliest` over a date, `filled` over anything.\n\n### `lookup`\n\nDisplays a field from the linked records.\n\n```jsonc\n{ "alias": "customer_tier", "label": "Customer tier", "type": "lookup",\n  "source_field_alias": "customer",  // a select_record_link field on THIS entity\n  "lookup_field_alias": "tier",      // a field alias on the linked entity\n  "order_by": { "field_key": "placed_on", "direction": "desc" } }  // optional \u2014 pick the single extreme row\n```\n\n### `autonumber`\n\n```jsonc\n{ "alias": "seq", "label": "No.", "type": "autonumber",\n  "prefix": "SO-",     // optional \u2014 ignored when template is set\n  "padding": 4,        // optional \u2014 1..20, zero-pads the integer\n  "template": "SO-{YEAR}-{N:4}" }  // optional \u2014 {N}, {N:W}, {YEAR}, {YEAR:2}, {MONTH}, {DAY}\n```\n\n## Views\n\nSaved views live under the entity they belong to. Every field reference is a\nfield ALIAS on that entity.\n\n```jsonc\n{\n  "alias": "gold",\n  "label": "Gold customers",\n  "description": "\u2026",                       // optional\n  "columns": [                              // optional \u2014 omit to show every field\n    { "field_alias": "name", "visibility": "visible", "width": 240 },\n    { "field_alias": "tier", "visibility": "hidden" }\n  ],\n  "filters": {                              // optional\n    "node_type": "group",\n    "logic": "and",                         // "and" | "or"\n    "children": [\n      { "node_type": "condition", "type": "select", "field_key": "tier",\n        "operator": "has_any_of", "value": ["gold"] }\n    ]\n  },\n  "sort": [ { "field_key": "name", "order": "asc" } ],  // optional; order is "asc" | "desc" | null\n  "summary": { "amount": "sum" },           // optional \u2014 field alias \u2192 footer operation\n  "frozen_columns": 1                       // optional\n}\n```\n\nA condition\'s `type` is the field\'s type and its `operator` is one that type\nadmits \u2014 `has_any_of` / `has_none_of` / `has_all_of` / `is_empty` /\n`is_not_empty` for a select, `equals` / `greater_than` / `less_than` for a\nnumber, `on` / `before` / `after` / `between` for a date, `contains` /\n`is_any_of` for text. A select condition\'s `value` names option ALIASES.\n\n`columns`, when present, is exhaustive and must not be empty: a view renders\nexactly the entries it holds. Omit the key to show every field.\n\n## Roles\n\nA role becomes a workspace group. Members are added afterwards, in the app.\n\n```jsonc\n{ "alias": "sales", "label": "Sales" }\n```\n\n## Templates\n\nOnly inline `html` and `email` templates \u2014 the rest are file-backed and a model\nhas no bytes. An `html` template renders to a PDF when a workflow generates\nfrom it; `{{name}}` is filled from the workflow\'s data.\n\n```jsonc\n{ "alias": "order_ack", "label": "Order acknowledgement", "type": "email",\n  "content": "<p>Hello {{customer}}\u2026</p>" }\n```\n\nA paper that has to look like a counterparty produced it \u2014 an official letter,\nan acceptance minute, a supplier\'s bill \u2014 is the same `html` template with a\nshell around the body: a letterhead, a reference line, a seal and a signature\nblock, and paper grain over everything. One shell, many bodies; the data is the\nonly thing that changes, so a workflow can re-issue it over any record.\n\n```jsonc\n{ "alias": "cong_van", "label": "C\xF4ng v\u0103n", "type": "html",\n  "content": "\u2026the page below, as one JSON string\u2026" }\n```\n\n```html\n<style>\n    .sheet{position:relative;width:718px;padding:44px 58px 30px;background:#fbfaf6;color:#111;font:14.2px/1.5 \'Liberation Serif\',serif}\n    .grain{position:absolute;inset:0;opacity:.34;mix-blend-mode:multiply;background:url("data:image/svg+xml;utf8,<svg xmlns=\'http://www.w3.org/2000/svg\' width=\'140\' height=\'140\'><filter id=\'f\'><feTurbulence baseFrequency=\'.9\' numOctaves=\'2\'/><feColorMatrix values=\'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 .35 0\'/></filter><rect width=\'140\' height=\'140\' filter=\'url(%23f)\'/></svg>")}\n    .top{display:flex;text-align:center;font-size:13.4px} .top>div{flex:1} .u{display:inline-block;border-bottom:1px solid #111;font-weight:700}\n    .ref{display:flex;text-align:center;font-size:13.4px;margin-top:6px} .ref>div{flex:1} .ref .r{font-style:italic}\n    h1{text-align:center;font-size:15.6px;margin:26px 0 18px} p{text-align:justify;text-indent:26px;margin:0 0 9px}\n    .sig{display:flex;margin-top:20px} .sig .l{flex:1} .sig .r{width:290px;text-align:center;position:relative}\n    .sig .nm{font-weight:700;margin-top:96px} .seal{position:absolute;left:4px;top:8px;width:166px;height:166px;opacity:.66;mix-blend-mode:multiply;transform:rotate(-17deg)}\n  </style>\n  <div class=\'sheet\'><div class=\'grain\'></div>\n    <div class=\'top\'><div><b>{{issuer_parent}}</b><br><span class=\'u\'>{{issuer}}</span></div>\n      <div><b>C\u1ED8NG H\xD2A X\xC3 H\u1ED8I CH\u1EE6 NGH\u0128A VI\u1EC6T NAM</b><br><span class=\'u\'>\u0110\u1ED9c l\u1EADp - T\u1EF1 do - H\u1EA1nh ph\xFAc</span></div></div>\n    <div class=\'ref\'><div>S\u1ED1: {{number}}</div><div class=\'r\'>{{place}}, ng\xE0y {{day}} th\xE1ng {{month}} n\u0103m {{year}}</div></div>\n    <h1>{{title}}</h1>\n    <p>K\xEDnh g\u1EEDi: {{recipient}}.</p>\n    {{{body}}}\n    <div class=\'sig\'><div class=\'l\'><b>N\u01A1i nh\u1EADn:</b><br>- Nh\u01B0 tr\xEAn;<br>- L\u01B0u VT.</div>\n      <div class=\'r\'><img class=\'seal\' src=\'{{seal_url}}\'><b>{{signer_title}}</b><div class=\'nm\'>{{signer}}</div></div></div>\n  </div>\n```\n\n`lotics preview <file.html>` renders any such page to a PNG the way a demo\'s\nprops are made, sized to its content, so a paper can be looked at before it is\nput in a template.\n\n## Rows\n\nFirst records, keyed by entity alias. Up to 200 rows per entity and 2000 across\nthe model, attaching at most 2000 documents between them \u2014 a real data set\nbelongs in an import, not a model.\n\n```jsonc\n"rows": {\n  "customer": [\n    { "ref": "acme", "fields": { "name": "Acme Trading", "tier": "gold" } }\n  ]\n}\n```\n\n`ref` is a local handle (lowercase letters, digits, underscores) that other rows\'\nlink fields address. It is never persisted.\n\nA `files` cell attaches documents: paths relative to this file (no `..`, never\nabsolute), which `check` proves exist and `apply` uploads into the workspace\nbefore any row is written \u2014 a paperwork business seeds its papers with its\nrows. The server accepts only `fil_` ids of files this workspace owns, which is\nwhat the upload leaves behind. After a run that wrote rows, the WORKSPACE holds\nwhich record each row became, under the row\'s own `<entity>:<ref>`:\n`delete_records` over them is how a seeded set is reset, and applying again\nre-dates it.\n\n`fields` is keyed by field alias, and every value is read against the field\'s\nDECLARED type:\n\n| Field type | Value |\n|---|---|\n| `text` / `number` / `boolean` | the value itself |\n| `date` | `"2026-03-14"`, or a relative expression (below) |\n| `select` | the option ALIAS \u2014 `"gold"`, or `["gold","vip"]` for a multi-select |\n| `select_record_link` | `"<entity-alias>:<ref>"` naming another row in this file \u2014 `"customer:acme"`, or an array for several |\n| `select_member` | `"self"` only \u2014 the person applying the model |\n| `files` | paths beside this file \u2014 `["scans/pccc_letter.png"]` \u2014 uploaded by `apply`/`setup` before the rows are posted; or `fil_` ids of files already in this workspace |\n| `formula`, `rollup`, `lookup`, `autonumber` | not allowed \u2014 the platform writes these |\n\n**Documents can be attached on their own, afterwards.** Rows land only into empty\ntables, so a model whose binaries were added after the first apply has no second\napply to carry them: `lotics scaffold apply model.json --documents` writes ONLY\nthe `files` cells, onto the records the first run created, found by each row\'s\nown `ref` in the binding the workspace holds \u2014 so a row added to or removed from\nthe file since changes nothing about the rest. Running it twice attaches nothing\nthe second time: the same path keeps the same file, and a cell is a set.\n\n### Relative dates\n\nA date cell holds a literal `YYYY-MM-DD`, or an expression relative to the day\nthe model is applied, so a screen that opens on "this month" is not empty a month\nlater:\n\n- `@today` \u2014 the day of the run, in the workspace\'s timezone\n- `@month-start` \u2014 the 1st of that month\n- either with a whole-day offset: `@today-14`, `@month-start+9`\n\n`@month-start` exists because `@today-N` cannot promise a month: applied on the\n2nd, `@today-3` lands in the previous one.\n\n## Field roles\n\n`field_roles` names the reporting role a field plays on its entity \u2014 keyed by\nentity alias, then field alias \u2014 so every screen over the entity agrees on\nwhich column names the row and which select is the stage. A shape\'s slot binds\nto it (\xA7 Apps and screens). Like `rows` and `apps`, it is this file\'s: `check`\nproves it and the workspace never sees it. Each role sits on the types that can\nanswer it:\n\n| Role | On | Meaning |\n|---|---|---|\n| `identity` | `text`, `select_record_link`, `formula` | what a PERSON calls the row \u2014 the register\'s first column; a link where the row is "the product, at this branch"; a formula where the name is computed, and then it may not be `format`ted as a figure. NEVER an autonumber: a minted code is a `reference`. One per entity |\n| `reference` | `text`, `autonumber`, `formula` | the key the SYSTEM files the row under \u2014 an order number, a container code \u2014 drawn as the supporting line under the name rather than as a column of its own, and leading where the entity has no `identity` at all. One per entity |\n| `mark` | `files`, or a `lookup`/`rollup` that resolves to one | the row\'s picture \u2014 its own, or the linked record\'s. NEVER A COLUMN: a register draws words, so a mark is projected only where a surface leads with one \u2014 the subject rung of a picture-led grid, and a record\'s itinerary. A child entity\'s mark reaches a record\'s run and nothing else. One per entity |\n| `lifecycle` | single `select` | the ordered stages a row walks; option order is the order. Which of them END the flow is `outcomes`, which parts of the flow they group into is `phases`, and `history` keeps the day each one was reached. One per entity |\n| `category` | single `select`, or a `lookup` that resolves to one | what the row IS \u2014 a kind, a service, a book. One badge in the field\'s own colour, with no ladder behind it and no flow to advance; `icons` gives each option its glyph. Often a fact about the thing the row books rather than about the row, and then it is the lookup that reads it. Repeats: a row can be of two kinds of thing |\n| `measure` | `number`, `formula`, `rollup` | a level read against a limit \u2014 see `against` and `alert`. Money where the model says so, and then it prints as money |\n| `expected_set` | `select` | its OPTIONS are the required set (documents, checks, services); an option no row has is a gap to show, not nothing. A multi-select draws as a ring and a fraction wherever it is drawn \u2014 absence is the information, and a list of what IS there says nothing about what is missing |\n| `amount` | `number`, `formula`, `rollup` | THE money of a ledger row; `signed_by` says which way it moved, `against` names the reference it is quoted off. One per entity |\n| `when` | `date`, or a `formula`/`rollup`/`lookup` that yields one | the ledger or timeline date \u2014 stated, or derived: the day money MOVED is a formula over the two columns that could hold it. `due` makes it a DEADLINE; without it the date is the plain day it is. `until` names the stage of this entity\'s own `lifecycle` at which the countdown is spent, and says `due` by saying so. `from` names the date the deadline\'s window opens on. One per entity |\n| `slot` | single `select`, or a `datetime` `date` | where in the DAY a row sits \u2014 the run it is read in under its day\'s heading on an itinerary. A select\'s option order IS the run\'s order; a time is ordered by the clock. A plain `date` is refused: that is the day itself. One per entity |\n| `party` | `select_record_link`, `select_member` | WHO THE ROW IS FOR \u2014 the counterparty it was transacted with, or the workspace MEMBER whose work it is (a shift, an assignment, a timesheet period). A member is drawn as the person and opens nothing: they have no record in the app. One per entity \u2014 and left off where the `identity` IS the link to them: the row is then NAMED by that record, and a strip under the title would state them twice |\n| `parent` | `select_record_link` | the record this row belongs to \u2014 a line\'s order, a paper\'s case. The parent\'s record shows these rows; the row shows the parent as a fact. One per entity, and it links to an entity this model declares |\n| `contact` | `text` | a way to reach a party \u2014 an address, a number, the town it is in. The record draws them as ONE row of links under the name, on a page and in a drawer alike, so the role sits on every field that is one of them. A row carrying one is SOMEBODY, so a screen over it may lead with the mark (\xA7 `presentation`). Repeats |\n| `currency` | single `select` whose option LABELS are ISO 4217 codes | the money THIS ROW\'s figures are in. Every amount and every money measure on the entity is then printed per row rather than in one code for the whole column, and the select is not drawn as a fact of its own. One per entity |\n| `verdict` | `boolean`, `formula` | a settled pass/fail \u2014 ticked, or computed. TRUE is the PASSING side wherever it is drawn, a register\'s risk flag included, so a field whose true means trouble is the same fact asked the other way round. One per entity |\n| `obligation` | `date` | a day something is OWED by \u2014 a cut-off, a permit expiry, a payment due. It counts down by definition. `satisfied_by` names what CLOSES it (or `until`, the stage the record stops owing it at), `label` what is owed. Repeats: a row owes several things, and a shape that fans them draws one row each |\n| `expires` | `date`, or a `formula`/`rollup`/`lookup` that yields one | the day something the row HOLDS runs out \u2014 a licence, a certificate, an inspection. Read as a COUNTDOWN, never as the date: the days left while it holds, and a renewal owed once it has passed. `warn` (required) is how many days ahead it starts to need attention, which nothing about a date says. Repeats: a machine carries an inspection and an insurance |\n| `origin` | `text`, single `select`, or a one-row `select_record_link` | where the row STARTS. Declared with a `destination` \u2014 a route has two ends, and one alone is refused \u2014 and then every surface over the entity draws the two as ONE reading, `Warehouse 4 \u2192 Site B`: on the register\'s supporting line after the key, and as one column on the child registers and party histories that list these rows. The two fields are then not facts of their own, and a `columns` clause naming either end is refused. One per entity, holding ONE place |\n| `destination` | `text`, single `select`, or a one-row `select_record_link` | where the row ENDS \u2014 the other half of the `origin`\'s route, and read only with it. One per entity, holding ONE place |\n| `body` | `text` | the words a dated entry SAYS \u2014 the note of a call, the text of a message \u2014 plain or markdown alike: the role makes the row an entry, never the format. Undeclared, a log reads the entity\'s first `markdown` text as the entry. One per entity |\n| `recording` | `files` | the audio or video a dated entry IS the record of \u2014 a call, a site walk, a lesson \u2014 played wherever it is read, on the entry and on the record it opens, never listed among its papers: a log\'s attachments are then its first OTHER pile. One per entity |\n| `verbatim` | `text` | what was literally said or written on a dated entry \u2014 a transcript, a pasted exchange \u2014 drawn behind one disclosure wherever it is read, under the entry\'s words and at the foot of its band on the record, never as the words. Refused on the entry\'s own words (its `body`, else the entity\'s first `markdown` text): declare those as the `body`. One per entity |\n\n**`due` is what makes a `when` a deadline.** A date a row is merely filed by \u2014 the\nday a lead arrived, the day a movement happened \u2014 is neither early nor late,\nhowever long ago it was. Without the clause every desk drew every `when` as a\ncountdown and a two-month-old lead read "40 days overdue" on a record nobody was\nlate on. So a bare `when` is a plain date, and `{ "role": "when", "due": true }`\nis the one that counts down. An `obligation` needs no clause: a day something is\nowed by is a deadline already.\n\n**`until` stops a countdown where the work is DONE.** A deadline counts down so\nsomebody acts on it, and a row that has arrived needs nothing: without the clause\na delivered order is tinted for a date it met, and every settled row past its day\njoins the urgent ones in the reader\'s glance. It names one option of the entity\'s\n`lifecycle`; at that stage, at every stage past it and at every `outcome`, the\ndate is drawn as the plain day it is. On a `when` it also says the date is `due`.\n\n**`from` opens a deadline\'s window.** `{ "role": "when", "due": true, "from":\n"starts_on" }` names the date field on the same entity the window opens on. The\nrecord\'s band then reads the window \u2014 both days and how many are left \u2014 and a\ntarget read against the deadline is paced by how far through the window today\nis. The start leaves the facts and is edited in the band, beside the deadline.\nIt takes a stored `date` a person states on the same entity (never one the\nplatform stamps with `derive_from`), and only on a `when` that counts down.\n\n"One per entity" is one COLUMN, never one value on screen. A second counterparty\nor a second parent stays a ROLELESS `select_record_link`: which field fills a\nslot is the screen\'s answer (\xA7 Apps and screens), and the extra link is a fact on\nthe row with its own section on the record, headed by that link\'s own label. A\nrole naming two fields would move the ambiguity into every shape that reads it.\nThe same holds for a link from an entity to ITSELF \u2014 the row a line sits under in\na breakdown, the same item\'s lines in the periods before: it takes no role, and\nthe clause that reads it names it (`nest`, `depends_on`, the rollup a claim\'s\n`previous` sums over).\n\nA COMPUTED field is admitted where its RESULT is what the role needs, and\nrefused where it is not: `identity` and `reference` need `text`, `when` a `date`,\n`mark` `files`. A formula\'s result is its `output_type`; a rollup\'s and a\nlookup\'s is read through the walk. So a formula yielding a number is refused in a\nname\'s place, a lookup landing on anything but `files` is refused as a `mark`, and\na formula declaring NO result is refused by all four \u2014 naming `output_type` as\nthe remedy, because a value drawn as a type nobody stated is the wrong cell with\nnothing saying so. The result also decides the DEVICE every screen draws the value\nwith: a rollup taking the `latest` of a set of dates is drawn as a date, a lookup\nof a select as the words it holds.\n\nA bare role name is the common form. A role that is read against a SECOND field\ntakes the object form:\n\n- **`measure`** names its limit: `against` \u2014 a constant, or a field on the same\n  entity the row states as a number (a `number`, or a formula or rollup whose\n  result is one) \u2014 and `alert`, which side of it needs attention, `over` a\n  capacity or `under` a minimum. The two come together.\n- **`measure`** names what its number COUNTS, where the unit changes how the row\n  is DRAWN rather than how the figure reads: `counts: "days"` spans a stop across\n  that many days of a run, so a three-night stay fills three of its days instead\n  of only the one it starts on, and `counts: "hours"` is how long a stop takes\n  INSIDE its day, stated beside it. Stated, never inferred \u2014 nothing about a `3`\n  says whether it is nights, pallets or hours, and a quantity drawn across a week\n  is a run nobody can read.\n- **`lifecycle`** names the stages that END the flow: `outcomes`, option aliases\n  of that select. A row in one has ARRIVED \u2014 delivered, cancelled, written off \u2014\n  so a desk draws them apart from the ladder instead of chaining them after each\n  other. Not every option may be an outcome, and terminal-ness belongs here, never\n  written into a stage\'s label.\n- **`lifecycle`** groups its stages into the parts of the flow they belong to:\n  `phases`, each a `label` and the `stages` under it. Nine rungs down one column\n  is a list nobody reads as a flow; the same rungs under three headings are three\n  pieces of work, and which belong together is the business\'s answer. Every stage\n  but an `outcome` falls in exactly one \u2014 a stage in two is drawn twice, a stage\n  in none vanishes off the ladder \u2014 and the outcomes may be placed in a phase or\n  left out, and are then read as a last part of their own.\n- **`lifecycle`** says why a row took an outcome: `reasons`, an outcome\'s alias \u2192\n  a text or single select of the entity. The reason is a fact of the ending, so a\n  record offers it only while it stands at that outcome \u2014 on a row still in the\n  flow a tap would record why it ended on a row that has not.\n- **`lifecycle`** keeps every stage the row reached: `history: true`, or\n  `history: "<alias>"` to name the table. A ladder with no history reports where\n  a row IS and nothing about how it got there, which is the whole of what a\n  reader asks a pipeline. It is declared BESIDE `phases`, and refused without\n  them: the rungs a ladder draws are the live select\'s options, which nothing\n  reading a file or an app\'s spec can see, so `phases` is the one statement of\n  what the dates have to cover \u2014 and without it a rung the history cannot reach\n  draws undated on every record with nothing anywhere saying so. The flag is the\n  ONE statement: the model DERIVES a\n  child table from it \u2014 the link back to this record, the stage, the moment it\n  was reached and who moved it \u2014 and `check`, `apply`, `diff` and the app\n  generator all see that table exactly as they see a written one. Nothing else\n  declares it, and a file that also writes it by hand is refused. The generated\n  create stamps the rung the flow opens at and the generated editor stamps every\n  move after it; a stage changed anywhere ELSE is a rung with no date\n  (`docs/platform_gaps.md`). **A first apply backfills nothing** \u2014 `apply` writes\n  rows only into empty tables, and rows that existed before the flag walked their\n  stages before that table existed. The honest backfill is ONE opening row per\n  existing parent, at its FIRST stage, dated when that parent was created (true\n  by construction); the stage it stands on NOW is not dated unless that is also\n  the first. It is a create per parent \u2014 `lotics run create_records` \u2014 and\n  `scaffold apply` prints it as the work it did not do.\n- **`amount`** names the REFERENCE it is read against: `against`, a field on the\n  same entity the row states as a number. A price against the list it is quoted\n  off, a rate against the going one \u2014 and the catalogue item\'s record draws the\n  pair on one axis with the gap said in words. Never a constant (a price typed\n  into the model ages with nothing to update it) and never an `alert`: a limit is\n  a ceiling a row can pass, and beating a reference is the point.\n- **`amount`** names the select that SIGNS it: `signed_by`, a select on the same\n  entity, and `outflow`, the options of that select under which the amount is\n  money going out. Without it every shape over the ledger adds both directions\n  together: a month whose net was small reads as the total of everything that\n  moved, and the trend plots one rising line. The two come together, and\n  `outflow` is some of that select\'s options, never all.\n- **`expected_set`** names what CONDITIONS the set: `required_by`, a field on the\n  same entity, and `options`, which of that field\'s values require which entries.\n  A row whose value is not named requires nothing. Without it the denominator is\n  every option, so a set whose entries are mutually exclusive by kind reads\n  `1 of 4` on every complete row \u2014 a denominator no row can reach is worse than\n  no role. The field is a single `select`, keyed by its option aliases \u2014 or a\n  YES/NO the row answers itself (a `boolean`, or a formula resolving to one),\n  keyed by `"true"` and `"false"`: a check that FAILED owes its consequence \u2014 the\n  photograph, the owner, the day it is due \u2014 and there is no select of the record\n  that says so. `from: "parent"` reads that field off the record these rows hang\n  under instead, through this entity\'s own `parent` link: which documents an order\n  owes is the ORDER\'s type, and the papers carry no column that says it. Which of\n  the two a set takes is the set\'s own shape and not a choice \u2014 a multi-select\n  holds the whole set on one row and is narrowed by that row (`from` omitted), a\n  single select is one entry per row and takes `from: "parent"` \u2014 and the other\n  way round is refused rather than left conditioning nothing.\n- **`category`** names the GLYPH each option wears: `icons`, option alias \u2192 a\n  glyph the kit draws \u2014 a kebab-case name from its curated Lucide set; a name\n  outside it is refused naming the nearest ones. A kind is recognised before it is read, by the\n  same mark wherever it is drawn \u2014 its chip on a row, a filter, an entry of a\n  log \u2014 and a lookup of the category wears the same glyphs, because it holds the\n  same options. Every option names one, or none does: a run of chips where one\n  carries no glyph reads as the one missing something.\n- **`expires`** names its WINDOW: `warn`, the days ahead of the day it runs out\n  that a renewal is started in. A monitored set\'s `level` bound to one draws each\n  unit\'s days left \u2014 tinted inside the window, and read as owed past the day \u2014\n  and `summary.above: "counts"` counts the units inside the window or past it. A\n  formula of days left against a number is the same fact drawn as a meter of\n  1 287 of 60.\n- **`obligation`** names what ENDS it: `satisfied_by`, a `date` or a `files` field\n  on the same entity \u2014 the day it was done, or the paper that proves it \u2014 or,\n  where the business stamps nothing, `until`, the stage of this entity\'s\n  `lifecycle` at which the record stops owing it: a deposit is owed until the\n  order is paid, and nobody records the act of paying twice. One or the other,\n  never neither \u2014 without one every obligation the business ever met stays on the\n  desk. Optionally `label`, what is OWED as the reader says it ("G\u1EEDi SI"), which\n  is not what the column holding the date is called ("SI cut-off").\n\n```jsonc\n"field_roles": {\n  "product": { "name": "identity", "photo": "mark" },\n  "stock":   { "on_hand": { "role": "measure", "against": "minimum", "alert": "under" },\n               "uptime":  { "role": "measure", "against": 80, "alert": "under" } },\n  "order":   { "stage": { "role": "lifecycle", "outcomes": ["delivered", "cancelled"],\n                          // Two pieces of work, and every step dated.\n                          "phases": [{ "label": "Taking it on", "stages": ["placed", "confirmed"] },\n                                     { "label": "Getting it out", "stages": ["picked", "shipped"] }],\n                          "history": true },\n               // A DEADLINE COUNTS DOWN \u2014 `payment.paid_on` below is a plain day.\n               "ship_by": { "role": "when", "due": true },\n               // The day the papers are owed by, and the day they went.\n               "papers_due": { "role": "obligation", "label": "File the papers", "satisfied_by": "papers_sent" },\n               // Nothing stamps a deposit paid \u2014 the order\'s own stage ends it.\n               "deposit_due": { "role": "obligation", "label": "Take the deposit", "until": "delivered" } },\n  // WHICH PAPERS THIS ONE OWES IS THE ORDER\'S OWN TYPE, and no document says it.\n  "document": { "order": "parent",\n                "kind": { "role": "expected_set",\n                          "required_by": { "from": "parent", "field": "kind",\n                                           "options": { "export": ["invoice", "customs"] } } } },\n  // `kind` is the direction select \u2014 options `received` and `paid_out`, no role of its own.\n  // Every figure on a quotation is in the currency that row names.\n  "quote":   { "unit": "currency", "total": "amount" },\n  // What the price is quoted off, so the item\'s page reads one against the other.\n  "service": { "price": { "role": "amount", "against": "list_price" },\n               "kind": { "role": "category", "icons": { "repair": "wrench", "install": "hammer" } } },\n  // The day the money moved is neither early nor late, so it stays a bare `when`.\n  "payment": { "paid_on": "when",\n               "value": { "role": "amount", "signed_by": "kind", "outflow": ["paid_out"] },\n               // A receipt owes a receipt voucher; a payment owes an invoice and a payment voucher.\n               "papers": { "role": "expected_set",\n                           "required_by": { "field": "kind",\n                                            "options": { "received": ["receipt_voucher"],\n                                                         "paid_out": ["invoice", "payment_voucher"] } } } },\n  // A CHECK THAT FAILED OWES ITS CONSEQUENCE \u2014 keyed by the row\'s own answer,\n  // and the answer that owes nothing is omitted rather than named with an empty list.\n  "check":   { "passed": "verdict",\n               "evidence": { "role": "expected_set",\n                             "required_by": { "field": "passed",\n                                              "options": { "false": ["photo", "owner", "due"] } } } }\n}\n```\n\nIn a file that starts from a preset (\xA7 Starting from a preset), `field_roles`\nmay name the preset\'s fields as well as this business\'s own; a role the preset\ndeclares itself is kept unless this file names the same field, and `null`\nclears it.\n\n## Write rules\n\n`write_rules` is what only a CREATE meets \u2014 keyed by entity alias, like\n`field_roles`, and this file\'s in the same way: `check` proves it and the\nworkspace never sees it. An update names one field that moved; a create takes a\ndraft whole, so it has to know which row a name already belongs to, where a\nvalue comes from when nobody types it, and what a figure or a picker may hold.\nThe generator writes one `create_<entity>` workflow and one `New<Entity>Dialog`\nper entity an app can operate, from these clauses and the fields\' own\n`required`.\n\n```jsonc\n"write_rules": {\n  // A customer is RECOGNISED by their address. Where an entity names a customer\n  // as its `party`, the create takes the email instead of a picker, reuses the\n  // row it matches and mints one only where nothing does \u2014 so the book never\n  // grows a second Acme because somebody typed the name differently.\n  "customer": { "natural_key": ["email"] },\n  "order_line": {\n    "fields": {\n      // A line of nothing is not a line. Refused on create and on update, at\n      // the control the figure was typed into.\n      "quantity": { "min": 1, "max": 9999 },\n      // The price is fixed at the moment of ordering \u2014 COPIED off the product,\n      // not looked up for ever after, so the price list moving next week does\n      // not silently reprice an order already placed.\n      "unit_price": { "default_from": "product.price" },\n      // And nothing is sold off an empty shelf. The picker reads only the rows\n      // that answer this, and the write refuses the same rows again \u2014 a caller\n      // who never opened the picker is bound by it too.\n      "product": {\n        "options_where": {\n          "node_type": "group", "logic": "and",\n          "children": [{ "node_type": "condition", "type": "number",\n                         "field_key": "in_stock", "operator": "greater_than", "value": 0 }]\n        }\n      }\n    }\n  }\n}\n```\n\n| Clause | On | Meaning |\n|---|---|---|\n| `natural_key` | the entity | the field aliases a row is recognised by. A `text` key declares `unique: true` on the field itself \u2014 two rows sharing it would make find-or-create pick whichever the read answered first \u2014 and a key is `text` or `number`, because a person types it back |\n| `default_from` | a field | `"<link alias>.<field alias>"` \u2014 the value is copied from the linked row when the row is created, never asked. The link is a one-row link on this entity and `required`, because there has to be a row to read, and the two field types must match |\n| `min` / `max` | a `number` | the figure is refused outside them, on create and on update |\n| `options_where` | a `select_record_link` | an `and` group of plain conditions over the TARGET\'s own fields, each `field_key` a field alias. It narrows the picker\'s read and is refused again where the write lands, so the link is `required` |\n\nA field\'s own `required` is not here: the contract carries it, every write path\nrefuses the row by field name from it, and the generated panel stands its commit\ndown until the same set is filled. `unique` is the text field\'s own clause\n(\xA7 `text`) \u2014 the create says so at the control before the column does.\n\nWhat a create asks is what a person STATES, so an entity stating `writes:\nfalse` (\xA7 Entity) has no create at all. A `default_from` field is not drawn,\na `lifecycle` opens at its first rung, and the stamp an obligation\'s\n`satisfied_by` names is not asked (the row is only now taking that on) \u2014 one\nfact, one place. A field the workspace writes (a formula, a rollup, a lookup, an\nautonumber, a date with `derive_from`) is never an input of a create or an\nupdate, a write in a generated body, or an entry in `lotics.writes`, and its\nrecord fact has no editor. Of the files columns it asks for exactly ONE, the\n`mark`: that pile IS the row, so a register leading with the picture would\notherwise open a faceless row, while every other pile is papers gathered onto a\nrow that exists and a panel asking for all of them is a filing cabinet with a\nSave button. The screen narrows that set where it states a `create` (\xA7 Apps and\nscreens). `scaffold check` prints every clause under its entity in **Who writes\nwhat**.\n\n**The `parent` is prefilled only in the door that mounts the act.** A row opened\nfrom the record it hangs under takes that record from the door it was pressed\nin, so the link is neither asked for nor drawn. The same entity\'s act on its own\nregister has no such row, so there the parent is an ordinary picker the draft\ncannot be committed without \u2014 a payment opened from a money app belongs to a\ncase either way.\n\n## Apps and screens\n\n`apps` is the plan: each app the reader will build, as ONE REGISTER \u2014 a SHAPE\nover an ENTITY \u2014 under `screen`. Nothing here is built by the scaffold: the plan\nis what `lotics scaffold check` prints back, register by register with the field\nin every slot, so it is read and corrected before a screen exists.\n\n**THE PRINTOUT EXPLAINS ITSELF.** Everything the shape and the roles answered by\nthemselves is marked `(default)` \u2014 the door, the tab strip, the band\'s figures,\nwhat the rows lead with, how much room they take, which end the register is read\nfrom, the set a member lens opens on, how many rows a capped history stands at \u2014\nso a clause nobody wrote is never read back as one somebody did. And\n`lotics scaffold check --why` prints the RULE behind every binding and every\nsection, indented under the line it explains: which field filled a slot and what\nit was chosen from, why the record opens where it does, why a child\'s rows are a\nlog rather than a register, why a history is capped and a relation counted.\nEvery sentence is the derivation\'s own, so what the printout explains is what\ngets built.\n\n**THREE THINGS DECIDE EVERY SCREEN AND EVERY RECORD**: the SHAPE, whose slots are\nthe table below; the ROLES the entities declare (\xA7 Field roles), which fill those\nslots and decide what each child\'s rows become; and the CLAUSES, which are where\nthe plan overrides what the two would answer. This index says which is which, so\na clause is reached for only where the first two have no answer.\n\n**What a child\'s rows become.** One section per LINK into the record, and what\nthe CHILD declares decides its kind \u2014 the first line it answers wins.\n\n| Printed as | The child declares | The reader gets |\n|---|---|---|\n| `documents:` | an `expected_set` select, one entry per row | the desk of what is owed, each row\'s files attached to it |\n| `schedule:` | an `obligation` closed by a DATE, on rows with no `lifecycle` of their own | what is planned against time and what slipped \u2014 the ordered stops, the promised day against the day it happened |\n| `log:` | a `body` (else a `markdown` text) and a day, on rows with no `lifecycle` of their own | what happened, in order \u2014 each entry read in full in the words it states, its selects and the parties it was with on its line, its `recording` played under the words and its `verbatim` a disclosure behind them, and a composer that writes the next one, asking what the entry shows. With a `verdict` the rows are a correspondence: read oldest first, the reply marked with it the answer, and whose move it is at the foot; without one, newest first under day heads. An entry the child NAMES (`identity`) opens a record of its own. A one-row link carrying no role is a run of the entry\'s line, read as the name of the row it points at (where it was seen); a link holding several is the other end of a relation and is not |\n| `itinerary:` | a `when` and a `lifecycle`, on rows a JOB\'s record OWNS | the day heads the run, one line per stop, the sum under it |\n| `lines:` | anything else the record owns (`parent`) | the register of the rows it is made of |\n| `history:` | anything else NAMED BY it \u2014 the link is their `party` or their `identity` | the same rows read as that record\'s own history \u2014 on a PROFILE, every one of them stands open at its latest 5, headed by how many there are in all, with the rest a press away |\n| `via <link>:` | a link carrying neither role | the register, headed by that link\'s own label |\n| `related:` | rows of an entity this app lists NOWHERE | one counted line, and a press that opens their register |\n\nA child carrying the BODY and no day is a plain register, and `scaffold check`\nnotes the day it is one short of rather than letting it fall through silently. A\ndated row with no body is not a near miss \u2014 that is every ledger line there is.\n\n**A LOG\'S DAY is the child\'s `when`, unless that `when` counts down** (`due`,\n`until`): a deadline is the day an answer is OWED, so a log stacked on it would\nput the entries nobody has chased at the top. Then \u2014 and where the child declares\nno `when` at all \u2014 the day is the first `date` no role claims. A child carrying a\n`lifecycle` is never a log, on the same rule a schedule reads: it is a thing\nbeing WORKED, and the prose on it is a note about the job.\n\n**A child\'s columns read, and are given up, in one order**: identity \xB7 when \xB7\nlifecycle \xB7 category \xB7 amount \xB7 measure \xB7 expected_set \xB7 party \xB7 contact \xB7\nverdict. The DAY outranks the counterparty because a list of rows belonging to\none record is scanned by when \u2014 the counterparty repeats on every row, and on a\nlog there is none. Ranked the other way, a narrow register shed the date and kept\na column that said the same thing on every line.\n\n**A section names its link where two of them would read alike.** One child can\nreach a record through several links and land under the same heading twice, which\nis the same sentence with nothing saying which rows either holds \u2014 so each of\nthose says the link it is read through (`schedule: Stops via Billed to`), and a\nchild reaching the record once is named by the rows it lists.\n\n**The clauses, by name.** On the APP: `scope`, `reads`. On the `screen`: `record`, `tabs`,\n`slots` (`roles` on a `custom` one), `columns`, `writes` (`false`,\n`"children"` for the rows a record owns and not the record, or `"record"` for the\nrecord and not its rows), `period`, `filters`,\n`summary` (`above`, `totals`, `ageing`, `trend`, `curve`), `facts`, `presentation`\n(`lead`, `density`, `layout`, `until`, `nest`, `depends_on`, `baseline`), `acts`\n(`row`, `record`, `selection`, `export`, `import`), `section_acts`, `sections`, `children`. Every one is optional, every one\nis printed back by `scaffold check`, and a screen that states none gets what its\nshape and its roles answer by themselves.\n\n**ONE APP IS ONE REGISTER AND THE RECORDS IT OPENS.** A second register beside\nit is a second job on one page: the reader arrives on whichever the nav listed\nfirst and decides, every time, which of the two they came for. So an app has one\ndestination and everything else about a row is DISCLOSED by opening it \u2014 the\nfacts by tier, the children as lists, the related as counts, one primary act, and\na filter or a group where a strip of destinations would have been. What used to\nbe a second screen is a section of the record, or another app; a model still\nsaying `screens` is refused by name.\n\n**The unit of an app is a JOB, not a person and not a table.** A job has its\nown outcome (something exists or is settled when it is done), its own subject\n(the record it advances), and an end that does not wait on the rest of the\nwork. Two tasks are ONE job when neither finishes without the other and both\nadvance the same record. One app per job, and that is what makes an app a\nwrite-ownership boundary: what the job settles is its app\'s alone to write,\nplus everything it must read to settle it well. A person holding several jobs\nopens several apps \u2014 one app for everything one person does is the dump. A step\nof the job is a section of the record, never a register beside it; a reference\nthe job needs at hand is read inside the record it is about.\n\n**Two people signing is two jobs**, because the outcome belongs to the signer:\nthe desk that prepares against the gate that releases. So is a different\ncadence \u2014 reference data edited monthly and read by the public site, beside a\ndaily desk \u2014 and a different reader, the owner\'s read-only questions. Device,\nplace and step never split a job. A super app holds more than one job; an\nover-split holds less than one, a job cut by device, place or step. The count\nper workspace falls out of the jobs, typically two to six, and is never the\ninput: review the plan app by app, naming who holds it, the job in one\nsentence, what it writes and what it reads.\n\n**A party is not a job.** The people and companies a job\'s rows name \u2014 the\ncustomers, the suppliers, the carriers \u2014 are not a job of their own, however\nmany rows name them: nobody\'s day is "the customer book". They live inside the\napp whose rows name them: a create takes the party by its natural key, the row\'s\nname opens the party\'s own record (a profile \u2014 how to reach them, what is live\nwith them, their history, their log), and its facts are edited there. A\nparty earns an app of its own only where someone\'s job IS the relationship, with\nan outcome of its own \u2014 an account plan signed, a supplier qualified \u2014 never\n"keeping the book". Two apps for one seller, the deals and the customers, is the\ndump cut in two.\n\n*A two-van appliance repair shop.* The technician\'s job is the call-out: the\noutcome is a visit done, the subject is the call-out record, and quoting it and\nscheduling it are one job, because neither finishes without the other and both\nadvance that record. The owner holds two of his own \u2014 billing the month\n(outcome invoiced, subject the invoice, settled against visits already closed)\nand the price list the booking page quotes from, edited monthly. Three jobs,\nthree apps, and the owner opens two of them.\n\n**Inside a job the caps hold**: six flow stages on a desk, seven facts before a\nrecord\'s fold. Past them, look for the second job hiding inside. And a job\'s app\nis DENSE: every create the job needs lives in it, so its user never leaves it to\ncorrect a figure the screen in front of them is stating \u2014 three workflows is a\nscreen, not a desk.\n\n**A handoff is a stage change.** Where one job ends the record moves stage and\nthe next job\'s desk opens on it; a field two jobs must both write is declared\nshared at the split, naming the stage each may write it in.\n\n**Name an app for the JOB, in the trade\'s own words, never for who it is for.**\nA title on the door says nothing about what the person who opened it came to\ndo, and it is wrong the day the org chart moves.\n\n```jsonc\n"apps": [\n  {\n    "alias": "sales", "name": "Sales",\n    "description": "\u2026", "icon": "briefcase", "theme": { "color": "blue" }, // optional\n    "screen":\n      { "alias": "orders",    "label": "Orders",    "shape": "lifecycle_desk", "entity": "order",\n        "record": "drawer",                  // optional \u2014 "drawer" | "page"; absent, the shape decides\n        "tabs": "stage",                     // optional \u2014 the entity\'s lifecycle, or null; absent, the shape decides. Any other select is a filter\n        "writes": false,                     // optional \u2014 default TRUE; false is a reader, "children" operates only the rows the record owns, "record" only the record\n\n        "period": "due_date",                // optional \u2014 any field whose value is a date, derived ones included\n        "filters": ["kind",                  // optional \u2014 a single-select, or a lens the model states itself\n                    { "label": "Qu\xE1 h\u1EA1n l\u01B0u", "predicates": [\n                      { "label": "\u0110\xE3 qu\xE1", "tone": "red",\n                        "where": { "node_type": "group", "logic": "and", "children": [\n                          { "node_type": "condition", "field_key": "owed", "operator": "greater_than", "value": 0 }] } }] }],\n        "summary": { "totals": ["total"], "above": ["total", { "field": "owed", "at": "end" }],\n                     "ageing": { "amount": "owed", "due": "due_date", "buckets": [30, 60, 90] },\n                     "trend": { "field": "total", "direction": "up" } },  // optional \u2014 see below\n        "facts": { "groups": [{ "caption": "Pricing", "fields": ["rate", "surcharge"] }] },  // optional \u2014 the record\'s named bands\n        "presentation": { "lead": "none", "density": "dense" },  // optional \u2014 how it is DRAWN; absent, what the rows are decides\n        "acts": { "row": [{ "label": "Issue the note", "template": "debit_note", "place": "cta", "confirm": true },\n                          { "kind": "agent", "label": "Read the papers", "agent": "reader", "fills": ["ref", "due_date"] },\n                          { "kind": "workflow", "label": "Hand it to dispatch", "workflow": "hand_to_dispatch",\n                            "inputs": { "order_id": "record", "owed_by": "due_date" },\n                            "asks": { "crew": "crew" },               // optional \u2014 stated in the act\'s panel before it runs\n                            "needs": ["site_phone", "site_email"] }], // optional \u2014 offered only while one of them holds a value\n                  "record": [{ "label": "Print the file", "template": "dossier" }],  // optional \u2014 the record\'s own header menu\n                  "selection": [{ "label": "Statement", "template": "statement" }],  // optional \u2014 the work it hands on\n                  "export": true,                                                    // optional \u2014 the rows in view, saved\n                  "import": { "kind": "import", "label": "Upload the sheet",         // optional \u2014 a file turned into rows\n                              "entity": "order", "key": "code", "columns": ["rate"] } },\n        "section_acts": { "line": [{ "label": "Chase the lines", "template": "chaser" }] },  // optional \u2014 a verb on one section\n        "sections": { "line": { "draw": "worksheet", "cost": "buy_rate", "sell": "rate" },  // optional \u2014 priced lines, worked down in place\n                      "payment": { "draw": "ledger", "summary": ["total", "paid", "outstanding", "due_on"],\n                                   "heading": "Money in" },       // optional on every draw \u2014 the section\'s heading; absent, the child\'s label\n                      "visit": { "draw": "log", "evidence": ["photos"], "line": ["kind", "site"] },  // optional \u2014 where a log\'s entry draws each field (see below)\n                      "pinning": { "draw": "publish", \u2026 },       // optional \u2014 the destinations this record is sent to (see below)\n                      "chase": { "draw": "acts", \u2026 } },          // optional \u2014 acts waiting for a person under this record (see below)\n        "slots": { "identity": "code",       // optional \u2014 slot \u2192 field, where the roles cannot decide alone\n                   "subject": ["customer", "project"],              // \u2026or the TIERS a fold walks down, outermost first\n                   "stage": { "field": "state", "quick": true } },  // \u2026or the field AND the reader\'s own control for it\n        "columns": ["source", "owner"],      // optional \u2014 extra facts after the slots, shed first at narrow width\n        "create": ["code", "customer", "due_date"] }  // optional \u2014 what a NEW row is asked for; absent, every field a person states\n  }\n]\n```\n\nA shape is a proven screen with named SLOTS, each filled by a field carrying a\nrole (\xA7 Field roles). A slot with exactly one candidate on the entity binds by itself;\ntwo candidates need naming in `slots`; a field fills one slot; a required slot\nwith none is refused \u2014 a lifecycle desk over an entity with no `lifecycle`\nselect cannot be built. `"slots": { "party": null }` leaves a slot the shape can\ndo without UNBOUND: the register draws no column for it and gives the width to\n`columns`, while the role goes on being read everywhere else. A required slot\nrefuses it.\n\n**A LIST IS A HIERARCHY, not a set of columns.** A group register\'s `subject`\ntakes one \u2014 `"subject": ["customer", "project", "order"]`, outermost first \u2014 and\nthe register becomes one the reader walks DOWN: it folds by the first tier, a\nnode narrows to the tier inside it, the last tier opens the set behind the\nfigure, and a trail says where they are. Every tier is a field of this entity\ncarrying a role that slot accepts, and none of them fills a second slot. It is\nthe slot\'s own answer that decides: a list on any other is refused, because two\ncolumns in one cell is not a fold. Without it the same business needs a register\nper depth, and the same money is folded twice with nothing saying it is the same\nmoney.\n\n**AND ON A SLOT READ AGAINST A LIMIT A LIST IS SEVERAL MEASURES** \u2014\n`"level": ["received", "invoiced"]`, at most four, each drawn as a named meter\nline inside the ONE column and each read against its OWN `against`/`alert`. A\nrow is regularly scored against more than one target at once, and the second\nreading put in `columns` instead draws a figure bare with the comparison handed\nback to the reader. Every entry states a limit \u2014 a bare measure in the list is\nrefused, naming the clause \u2014 and `quick` is refused beside one, because a typed\nfigure is one cell. The FIRST leads: it is what `summary.above: "counts"` counts\npast-limit rows on and what a live board ranks its exceptions by, both of which\nname one set.\n\n**A QUICK SLOT IS FOR A DECISION THE READER MAKES FROM THE ROW ALONE.** A slot\'s\nvalue in `slots` is normally the field\'s alias; `{"field": \u2026, "quick": true}`\nsays the column is not a reading of that value but the CONTROL for it \u2014 pressed,\nit writes that one field as a diff through the record\'s own update, so the\nregister and the page behind it land the same write. THREE roles are such a\ndecision, and `quick` on any other is refused: a `lifecycle`, which rests as the\nstage\'s own dot and label, takes a rule under it on hover and focus, and opens\nthe field\'s stages with the ones that END the flow last \u2014 ONE control, which IS\nthe reading;\na `verdict`, which is the switch; and a `measure`, which is the figure typed in\nits own cell \u2014 a reading taken per row IS the row, which is what a timesheet\'s\nhours and a count sheet\'s tally are. Everything else is decided against what the\nrecord holds, and the record has to be open. All three carry the record\'s own\nblockers \u2014 a move the ladder holds is a move the cell holds, and it names the\nentries the row still owes \u2014 and an outcome asks before it commits. Add `"order": "sequence"`\nwhere the stages are a WALK rather than a set of destinations: the picker is then\nordered as the walk and the step the row takes next is MARKED in it. It never\nadds a second control \u2014 a column that answered with a reading in some rows and a\nverb in others is two columns about one value. A screen stating `writes: false`\nrefuses `quick`: a reader who may operate nothing has no decision to take.\n\n**THE SLOTS ARE THE ROW\'S ANSWER; `columns` IS ITS CONTEXT.** `"columns":\n["nguon", "phu_trach", "nhu_cau"]` names extra fields of the entity, drawn AFTER\nevery slot and in this order, each by what its column IS \u2014 a chip for a select,\nthe person\'s name for a member, the day for a date, the figure for a number, a\ntick for a boolean, the words for everything else. They are ranked BENEATH every\nslot, so a phone sheds all of them before it sheds any of the shape\'s own\ncolumns. **A COUNT IS NOT A COLUMN**: an entry whose field is a `rollup` that\nCOUNTS rows is read as the thing it counts \u2014 `3 b\xE1o gi\xE1 \u0111ang m\u1EDF`, the number then\nthe column\'s own label \u2014 on the name\'s supporting line at every width, so it\ntakes no seat and a count of nothing draws no run at all. Where the record LISTS\nthose rows, the reading is the press that opens it. At most four, and refused\nwhere one would say what a slot already says,\nover a files field (files are read, so they are a section of the record), over a\ncell holding several (a column of comma lists compares nothing), on a shape whose\nrows are not the entity\'s records in a table, and beside a `presentation.layout`\nthat draws the rows with a device of its own. A fifth fact worth the width is a\nslot the shape is missing \u2014 say so rather than widening this clause.\n\n**A RELATED ROW\'S KIND IS A CHIP.** An entry `{"field": "latest_kind", "age":\n"latest_on", "more": "item_count"}` draws a `lookup` of a related row\'s\n`category` as that category\'s chip \u2014 the option\'s colour and glyph (\xA7 Field\nroles, `icons`) \u2014 followed by how long ago that row happened (`age`, a date read\nover the SAME link, a lookup or a rollup) and how many OTHER rows the link names\n(`more`, a count rollup over the same link, drawn `+N`). Three columns drawn apart\nare a word, a date and a small integer the reader joins by eye. It takes one seat.\nThe chip is ONE row: across a link naming several, the lookup is ordered\n(`order_by`), and `age` dates the row that order picks \u2014 a `latest` (for `desc`)\nor `earliest` (for `asc`) rollup of the order\'s own date, or a lookup ordered the\nsame way. Refused: a field that is no lookup of a category, an unordered lookup\nacross a link naming several rows, an `age` or `more` read over another link or\nthrough a rollup `filter`, an `age` that is not a date or dates another row, a\n`more` that is not a count, an entry stating neither, and a rider named again as a\ncolumn of its own.\n\n**THE DRAFT ASKS WHAT FILES THE ROW; THE RECORD ASKS THE REST.** `"create":\n["ma_ho_so", "khach_hang", "han_xu_ly"]` names the fields a NEW row is asked for,\nin that order. Absent, the draft asks for every field a person states \u2014 which is\none panel for a row somebody has the answers to when they open it, and a wall in\nfront of one that is written over days: a job is named, dated and filed the\nmoment it is taken, and everything else about it is learned afterwards. Whatever\nthis clause leaves out is edited in place on the record, where it is read. It is\nthe SCREEN\'s, and a screen is one register over one entity, so it narrows that\nentity\'s own draft: the rows a record adds under itself are the section\'s, and\ntheir composer asks what the section draws. At most twelve, and refused where an\nalias is not a field of the entity, is named twice, or is one no draft ever asks\n\u2014 a computed value, a minted number, the `lifecycle`\n(the row opens at the flow\'s first rung), a field a `default_from` copies, the\nstamp an `obligation` is closed by, and every files column but the `mark`. A\nlink naming several rows is asked through a picker that takes every row picked.\nA link the row STANDS ON \u2014 its `parent`, its `party` \u2014 is asked as ONE row whatever its\ncardinality, because the create writes one row into it and how many the cell\nholds afterwards is the platform\'s business. The\n`mark` itself may be left out, and then the row\'s face is attached on the record\nlike any other pile. Refused too where it omits a field the row cannot be written\nwithout \u2014 one that is `required`, the link it hangs under, or the key a party is\nrecognised by \u2014 because a draft that cannot save is worse than a long one.\n\n| Shape | Answers | Required | Also fills | Record | Tabs |\n|---|---|---|---|---|---|\n| `lifecycle_desk` | what is stuck, what do I move next | `lifecycle`, `identity` | `mark`, `party`, `amount`, `measure` (level, one or several), `when` | page, or drawer where the entity carries `parent` | the lifecycle\'s stages |\n| `party_register` | who is this, our history, is there a risk | `identity` | `mark`, `contact`, `measure` (worth), `verdict` (risk) | page | none |\n| `offering_register` | what do we offer, at what price, can I sell it | `identity` | `mark`, `amount` (price), `measure` (availability) | page | none |\n| `transaction_ledger` | does this period reconcile, what is unexplained | `when`, `amount` | `identity` (reference \u2014 the line\'s own number), `party`, `lifecycle` (classification), `expected_set` (document) | drawer | none |\n| `monitored_asset_set` | what needs attention, is that number normal | `identity`, `measure` (level, one or several) or `expires` (level, as the days left) | `mark`, `lifecycle` | drawer | none |\n| `obligation_desk` | what is due next, and has it been done | `identity`, and at least one `obligation` on the entity | `when` (runway) | page | none |\n| `trend_deep_dive` | how did the period go, and why | `when` | `measure`, `amount` | drawer | the series, where the model names a select |\n| `reconciliation_desk` | what does not match, and by how much | `identity` (reference), and two figures \u2014 `ours` and `theirs`, each an `amount` or a `measure` | `category` (reason), `verdict`, `when` | drawer, on the PAIR | the dated runs, where the model names a select |\n| `entry_matrix` | one value per subject per period | `identity` (subject), `across` \u2014 a `when`, or a `category` for a fixed column set | `measure` (value), `lifecycle` (state), `category` (note) | drawer, on the cell\'s row | none |\n| `guided_run` | complete an ordered sequence, a step at a time | `identity` (step) | `slot` (sequence), `capture` \u2014 a `measure`, `verdict` or `expected_set` \u2014 `verdict` (gate), `mark` (media) | page: the run IS the record | none |\n| `live_board` | is everything OK, right now | `lifecycle` (state), `identity` | `verdict` (exception), `when` (since), `measure` (level, one or several), `category` (where) | drawer | none |\n| `group_register` | what does each group come to, and what is behind it | `subject` \u2014 a `category`, `party` or `when` | `amount`, `measure`, `identity` (member) | page: a row is an aggregate, and the door is the SET behind it | none |\n| `media_set` | scan a body of pictures by where they belong | `mark` (picture), `identity` | `category` or `party` (group), `when`, `verdict` (current against superseded) | drawer | none |\n| `day_sheet` | what happened on each day | `when` (the day) | `lifecycle` (state), `measure` (level, one or several), `amount`, `category` (note) | page: a day composes several child logs | none |\n| `resource_schedule` | what is on each resource, in what order, under what ceiling | `lane` \u2014 a `party` or a `parent` \u2014 `identity`, `when` (the start) | `measure` (duration), and `load` and `bulk`, each a `measure` read against a ceiling of the LANE\'s \u2014 a vehicle fills by weight and by room and stops at whichever runs out first; `lifecycle` (stage) | drawer, over the lanes | none |\n| `worksheet` | priced lines the reader edits, totalling to one figure | `identity` | `category` (group), `measure` (quantity), and `cost` and `sell`, each an `amount` or a `measure` | drawer, per line | the versions or the jobs, where the model names a select |\n\n**A record is one of five KINDS, and the shape plus the roles decide which.**\nEvery one of them is ONE READING COLUMN, and the ORDER of that column is the\nwhole of what the kind means.\n\n| Kind | The column, top to bottom |\n|---|---|\n| WORK RECORD \u2014 a `lifecycle_desk` over rows that belong to nothing and that nothing transacts with | the one act that moves it \xB7 what it IS \xB7 the papers it owes \xB7 the rows it is made of \xB7 the book of what it came to |\n| LINE \u2014 the same shape over rows carrying `parent` | its ladder \xB7 the arithmetic behind its amount \xB7 the rows and papers under it \xB7 its particulars, last (the key it is filed by is the line under its title) |\n| PROFILE \u2014 a `party_register`, and any shape over an entity whose rows other entities are NAMED by (their `party` or their `identity`) | where it stands \xB7 its history, OPEN, grouped by year \xB7 the rest of its registers \xB7 its facts (the ways to reach it are under its name, its settlement is the band, and a `when` it owes closes that band as a countdown) |\n| CATALOGUE ITEM \u2014 an `offering_register` | its own words (the picture leads the header at media scale, the price is read against its reference in the band) \xB7 what uses it \xB7 its facts |\n| EVIDENCE \u2014 a `transaction_ledger` | the PROOF \xB7 what the paper is, compactly \xB7 the rest \xB7 the links to the record it settles and the party it was with |\n\nNothing in the file states the kind: a clause that could say it could say the\nwrong one, and the model already says it \u2014 `parent` says whether a row stands\nalone, and a link NAMING this record (`party`, `identity`) says whether other\nrows are ABOUT it. So a desk over accounts\nwalking their own stages opens a PROFILE: the quotes and the invoices naming\neach account are what its record is read for, and a work record would have\ncounted them in one line at the foot. `record`\noverrides the DOOR where the shape\'s own answer is not the one wanted \u2014 and its\nthird value, `"expand"`, is not a door at all: the row REVEALS what it holds in\nplace, where there is nothing behind it worth navigating to. A row read that way\nreads as a LINE whatever the shape would have opened: its ladder, the arithmetic\nbehind its amount, then its particulars, because there is no header above it to\nhave stated the name first. It is REFUSED for two reasons, and they are not the\nsame refusal. On a shape whose record is a page by nature \u2014 a `guided_run`, a\n`group_register`, a `day_sheet`, an `obligation_desk` \u2014 because each of those\nstates the opposite where its door is declared: what its row leads to is read\nwhole, not as four more columns than the register had room for. And on a shape\nthat draws its rows with a device of its OWN \u2014 an `entry_matrix`, a `media_set` \u2014\nbecause a cell of a grid and a tile on a wall have no band under them for the row\nto reveal into. For the same reason a revealed register is drawn as a TABLE: a\n`presentation.layout` of anything else is refused, and the reader is not offered\nthe arrangement either, since it would take away the only door the register has.\n\n**`scope` \u2014 the one subject every read of the app narrows to.** Stated on the\nAPP rather than on its screen, because it is not a filter: a record opened under\nit stays under it, the pick survives closing the app, and every app declaring the\nsame `entity` shares one pick per viewer \u2014 which is the whole value, and what\nstops a construction workspace asking which project twelve times. `entity` is the\nmodel\'s entity whose one row the app is read inside, and `param` is what the\napp\'s reads take that row by.\n\n```jsonc\n{ "alias": "site_work", "name": "Site work",\n  "scope": { "entity": "project", "param": "project_id" },\n  "screen": { \u2026 } }\n```\n\nThe register\'s own entity has to REACH it \u2014 its own rows, or rows that name one\nthrough a link \u2014 or the switcher is a control that changes nothing. Until a\nsubject is picked the app reads NOTHING and says which one it is waiting for: an\nunscoped read over a scoped app is every row in the workspace drawn as one\nproject\'s work, which looks correct.\n\n**ONE RECORD SURFACE PER ENTITY, AND ITS KIND IS THE ENTITY\'S.** An app is one\nregister, so the record its rows open is the register\'s own and the kind comes\nfrom that register\'s shape. Another app over the same entity opens the same kind\nof record: a payment read from a cash book and one read from a trend are both\nmovements, and both read proof first. A shape with no kind of its own (a trend, a\nmonitored set, a `custom` screen) says only where the record opens.\n\n**A NAMED PARTY HAS A RECORD SURFACE IN THE APP.** One register, but the party\nits rows name \u2014 by `identity` or by `party` \u2014 opens a record of its own, a\nPROFILE, from the cell that names it and from the record\'s header: the ways to\nreach them, what is live with them, every register that names them at its latest\nfive, their log, their facts. It is the app\'s to write as far as the job\nneeds \u2014 the party\'s facts and its log \u2014 and the writers matrix says so; the\nregister\'s own record stays the register\'s. A party named through a link\ncarrying no role opens nothing, and neither does a party that is a MEMBER \u2014 a\nperson of this workspace has no row in any book the app carries, so the cell and\nthe header state them and stop.\n\n**Two things a register states about a row beyond which field fills which slot.**\nA `measure` is read AGAINST its limit (`against`/`alert`) where the shape\'s slot\ntakes one \u2014 `level`, on a lifecycle desk, a monitored set, a live board and a day\nsheet, a schedule\'s `load` and `bulk`, and every slot of a\n`custom` screen, which composes the frame\'s own column; `worth`, `availability`\nand a trend\'s headline are plain figures, and a limit there would read as a meter\nin the record over a number the row printed bare. And the name carries a\nSUPPORTING LINE where the entity states a key to file the row under: the `parent`\nit belongs to, its `reference`, an `autonumber`, a text formula \u2014 in that order,\nfirst hit wins, never a field a person types prose into. Every record heads with\nthat same key, so the register and the door it opens name one row one way.\n\n**The act that opens a row belongs to a register that LISTS the entity\'s rows**\n\u2014 a desk, a register, a ledger, a monitored set, or a `custom` screen. A shape\nwhose rows are not records has neither that act nor the door a counted line\nelsewhere leads to: an obligation desk\'s rows are deadlines and a trend\'s are\nperiods, so a create pressed there would open a row the screen cannot show. An\nentity whose only app is one of those has no create at all \u2014 give it an app whose\nregister its rows are read in.\n\n**An `obligation_desk`\'s rows are not its entity\'s rows.** The shape fans the\nentity\'s `obligation` fields out \u2014 one row per thing still owed, which is one\nwhose date is SET and whose `satisfied_by` is empty \u2014 so a l\xF4 with four cut-offs\nis four rows, and the three it has met are not there at all. The row\'s name is\nthe obligation\'s, its supporting line the record\'s `identity`, and the door is\nthat record. A `when` bound to `runway` is what the countdown\'s ring is measured\nfrom. Over an entity declaring no `obligation` the shape is refused: there is\nnothing to count down to.\n\n**What a register carries beyond its columns.** Six clauses, each emitted as\nthe prop the kit draws it with; every one is optional and a screen that states\nnone gets a register of columns and nothing else.\n\n- **`period`** \u2014 a field on the entity whose value is a DATE. The toolbar gains a\n  date-range control (this month to start), and the rows it keeps are what the\n  register AND every figure below are computed over, so a band can never be over a\n  different window than the rows under it. Any such field, not only the `when`\n  role, and however the date got there: one table is read two ways (a cost ledger\n  by the day a line arose, the cash book over the same table by the day it\n  settled), a role is one field\'s, and the day money MOVED is often a formula over\n  the two columns that could hold it \u2014 which then declares `output_type: "date"`.\n  A `trend_deep_dive` brings its own period and takes none here; a `live_board`\n  is PERIODLESS and takes none either, for the opposite reason \u2014 it answers what\n  is true NOW, and a date range over it draws what was true in the window in the\n  live state\'s own colours.\n- **`filters`** \u2014 the chips beside the search. A single-`select` field\'s alias\n  \u2014 or a `lookup` of one, read as the looked-up row\'s option \u2014 offers that\n  field\'s own live options; it is the lens a register is read through\n  over and above the one band its strip gives, so the strip\'s own field is\n  refused here (one dimension, one control) and so is a multi-select (a row would\n  answer the chip several ways at once). The rows the register and every figure\n  below are computed over are what the chips AND the period kept.\n  A `select_member` field\'s alias is the third form and asks one question \u2014 whose\n  rows these are: two peers, MINE and ALL, read against the person looking rather\n  than a directory of everybody. `{"field": \u2026, "default": "mine"}` opens the\n  register on the reader\'s own; that form on any other type is refused. Alone of\n  the chips it narrows the READ (a `member` param on the register\'s query), so a\n  desk that opens on the reader\'s work opens on all of it rather than on\n  whichever of their rows the first page happened to hold.\n  A DERIVED LENS is the other form \u2014 `{"label": \u2026, "predicates": [{"label": \u2026,\n  "tone": \u2026, "where": \u2026}]}` \u2014 where the sets a reader narrows by are ones the\n  MODEL names and no column holds: rate validity, plan urgency, free-time\n  overrun. Each `where` is an `and` group of plain conditions over the entity\'s\n  own fields, each `field_key` a field alias, and it is read off the row, so the\n  operators are the comparisons a value answers \u2014 `number` and `text` equality,\n  `number` ordering, `boolean` equality, `select` `has_any_of`/`has_none_of`, and\n  `is_empty`/`is_not_empty` on any of them. Nothing DATED: a relative point needs\n  a clock, and a screen states one date control (`period`), so a second beside it\n  would be two windows with nothing saying which a figure was computed over \u2014 a\n  date question is asked as a column the model derives and read here as a number\n  or a yes/no. `tone` is the option palette\'s, because the chip draws these\n  exactly as it draws a select\'s options. ONE predicate is a chip the reader\n  toggles rather than a list of one. `"sort": {"field": \u2026, "order": "asc"}`\n  reads the rows in that field\'s order while the lens is on \u2014 a worklist, owed\n  soonest first, a row holding none last; refused over a field that is not a\n  date, number or text of this entity.\n- **`summary`** \u2014 what the rows in view come to. `above` is a band OVER the\n  register: `"counts"` for how many rows are in view and, for the FIRST\n  `measure` the model gives a limit, how many are past it (accented only when\n  one is) \u2014 one such set, because a band naming three is the dashboard a\n  register is not; a list of number-field aliases for what they add up to, and a\n  `percentage` named there is refused, since a share summed over the rows in\n  view is a figure of no kind (draw it as a column, whose own total reads the\n  mean). A figure written `{"field": \u2026, "at": "end"}` is a STOCK instead: the\n  reading standing at the END of the window rather than the sum of the readings\n  in it, which is the only way opening + in \u2212 out = closing reconciles \u2014 a month\n  of daily closing stocks added together is thirty warehouses. The band labels it\n  as the snapshot it is, and it is refused on a screen that states no `period`,\n  since there is then no window for it to stand at the end of.\n  `ageing` stands in that same\n  band: an `amount` split by how many days past its `due` date each row is,\n  drawn as a `Breakdown` of the edges in `buckets` (30, 60 and 90 days unless the\n  model states its own, ascending). The ladder is the kit\'s \u2014 its boundary, its\n  words and its ramp \u2014 and it opens with what is NOT YET DUE, because a bar of\n  overdue bands alone is full at every input: a book with one late invoice and a\n  book that has gone entirely bad would paint the same solid width. Against the\n  current money the bar\'s own shape is the reading. A row whose date is empty is\n  in no band. `totals` is what the whole\n  view adds up, and it is drawn in that SAME band above the rows: a register\n  states one aggregate, over the rows the reader can see, in one place, and a\n  closing line under them is a second place to look and a second question about\n  which rows it covers. A closing line belongs to the one device that IS a\n  statement \u2014 a record\'s `Ledger`, whose balance is what it is read for, labelled\n  by its amount\'s own word. Where a shape has no band above (a trend, whose own\n  band is the chart) the figure stands under the register instead. A\n  `transaction_ledger` sums its amount column itself and takes `above` alone. An\n  `obligation_desk`\'s rows are DEADLINES and not records, so its band states\n  `"counts"` \u2014 how many are open \u2014 and a figure list, an `ageing` or a `trend`\n  over it is\n  refused: a l\xF4 with three cut-offs is three rows, and its freight added over\n  them is three times the freight.\n  `trend` is `{"field": \u2026, "direction": "up"|"down"}` and states WHICH WAY that\n  figure moved across the window: the rows in view are cut into the window\'s own\n  buckets \u2014 days over a month, weeks over half a year, months beyond \u2014 and the\n  later half of the CLOSED ones is read against the earlier half, drawn beside\n  the figures as one line, so a window the reader is still inside states the\n  movement of the days that have run rather than a fall into the ones that have\n  not. `direction` is which way is GOOD, which nothing about the number\n  says: a book wants its takings rising and a backlog wants its days falling, and\n  the same arrow is a win on one and an alarm on the other. It needs a `period`\n  to be a window of, and it is refused on a shape that draws its own (a\n  `trend_deep_dive` already draws the series) or that reads none at all (a\n  `live_board` answers what is true now). A window whose earlier half took\n  nothing draws no line: there is no base for a percentage, and 0 % would claim a\n  steadiness nobody measured.\n  `curve` is `{"planned": \u2026, "actual": \u2026}` \u2014 two number fields of the row, each\n  added up to date along the rows\' own date and drawn in that band as two lines:\n  the S-curve a schedule or a budget is judged by, where a row is a period or a\n  piece of work and the running total is the curve\'s own arithmetic. The date is\n  the screen\'s `period` where it states one, else its `when`; a screen reading\n  its rows by no date is refused. The actual line stops at the last date a row\n  stated an actual figure \u2014 drawn on past it, the weeks nobody has worked yet\n  would read as a stall. Refused on the shapes a `trend` is refused on, over the\n  same reasons, and against itself.\n- **`facts`** \u2014 how the RECORD\'s facts are banded. `groups` is a list of\n  `{caption, fields}`: what a set of facts has in common is a sentence about the\n  business and nothing derives it, so a plan that states one gets exactly those\n  bands, in its own order, captioned. EACH BAND IS A SECTION of the record \u2014 its\n  own heading, its own entry in the rail, its own place in the column: under one\n  heading the reader is handed every particular at once, in a caption weight that\n  cannot out-rank the heading above it, with nothing in the rail to reach any of\n  them by. Everything the plan leaves unnamed is the LAST section and carries no\n  heading, since there is no sentence to head "whatever no group claimed" with \u2014\n  ONE section, even where the record\'s own recipe bands what was left in two (an\n  evidence record reads its particulars before the record and the party it was\n  with): both are groups inside it, because the word the kit heads "the rest"\n  with cannot name two entries in the rail. A band marked `last: true` is read\n  AFTER the record\'s own work \u2014 its acts, its rows, its correspondence \u2014 for the\n  particulars a reader checks once they know what is owed (who it is with, where\n  it came from); `folded: true` draws the band closed under its caption, and is\n  read last too. `first: true` reads a band ahead of everything, the stage\n  included \u2014 the facts a verdict is taken on, read before the verdict; a band\n  both first and last is refused. Where `children` names the record\'s relations,\n  their sections read in that order whatever each is drawn as \u2014 a log of the\n  evidence above the acts it decides.\n  A band of more than eight facts is NOTED: a section that long is two. A field the header, the band, the ladder, a required\n  set, the files or a register below already draws is refused: it is not a fact,\n  so a band naming it would either state it twice or draw nothing. Naming any\n  band IS the answer to which facts fold \u2014 see the TIERS below \u2014 so the bands\n  between them hold EVERY fact a person states: a text, a number, a date, a\n  choice or a link the groups leave out is refused by name, because the fold\n  holds only what the platform mints, stamps or works out. An entity whose\n  record shows `rate`, `surcharge`, `note` and a `created_on` stamp is banded\n  as `[{ "caption": "Pricing", "fields": ["rate", "surcharge"] }, { "caption":\n  "Remarks", "fields": ["note"] }]` \u2014 the stamp folds, and a plan naming the\n  first band alone is refused for leaving `note` in none.\n- **`presentation`** \u2014 how the screen and the record it opens are DRAWN, where\n  what the rows are is not the answer wanted. `lead` is what each row leads\n  with: `"mark"` the subject\'s own mark, always spent because a party\'s initials\n  stand in for a picture nobody uploaded; `"picture"` the photograph, spent only\n  on the rows that carry one and, on the record, at media scale above the name;\n  `"paper"` the row\'s own files, drawn as the cards a pile of documents is read\n  as; `"figure"` the amount, with no gutter at all; `"none"` neither. `density` is\n  how many lines a row\'s subject may take \u2014 `"roomy"` two, `"dense"` one.\n  Both default, and the DEFAULT is what the rows are: a party register leads\n  with the mark, an offering register with the picture, a ledger with its\n  figure, and a desk \u2014 rows that are work still to do, scanned \u2014 stands its rows\n  one line each while a record\'s own rows are read roomy. So state it only to\n  differ, and a plan that states nothing still gets screens that vary. A lead\n  the rows cannot carry is refused: a mark, a picture or a paper where no column\n  is drawn as the rows\' mark, a\n  figure where no column is the amount, and the other subject\'s mark (which of\n  the two a row wears is the shape\'s, so the register and the record it opens\n  cannot call one row two kinds of thing). A row carrying a `contact` is\n  SOMEBODY even where nothing names it yet, so `"mark"` \u2014 initials where no\n  picture was uploaded \u2014 is admitted over it; the default stays the picture. A\n  record opened as a drawer leads its bar with that mark where `lead` is\n  `"mark"`, and its files are then no section of their own.\n  `line` is what the line under a register row\'s name says, in place of the key\n  the row is filed under: at most two fields of the entity, each plain words (a\n  `text` with no `format`, or `"text"`) or ONE option of a closed list (a single\n  `select`) \u2014 where somebody works and what they do there, say. It is also what\n  the row is found by. The record keeps its key. Refused: notation, a link, a\n  field holding several values, the row\'s own name, and a field a slot, a column\n  or a chip already draws.\n  `layout` is how the rows are ARRANGED \u2014 `"table"`, `"list"`, `"cards"`,\n  `"gallery"`, `"board"`, `"calendar"`, `"timeline"`, `"gantt"`, `"tree"` \u2014 and\n  it is AFFORDED by what the rows carry, not by the shape: every register affords\n  a table and a list, a `mark` affords the two picture-led grids, a `lifecycle`\n  affords a board, a `when` affords a calendar and a timeline, and a `when`\n  beside a `measure` that `counts` DAYS affords a gantt, because a bar with no\n  length is a calendar drawn sideways and a bar measured in money or litres is a\n  length of another kind. `until` names the date field a bar ENDS on, where the\n  rows state one, and the days measure is what the bar runs for without it. A\n  layout the bound roles do not afford is refused, naming the ones they do.\n  `nest` names a one-row link from the entity to ITSELF \u2014 the row each row sits\n  under, a work breakdown\'s or a cost plan\'s \u2014 and it is what affords `"tree"`:\n  the rows drawn under the row they name, each folding what it holds, the MONEY\n  each row states or works out from its own columns summed up the tree. A rollup\n  is drawn as the row holds it (it already adds up rows of its own, and summed up\n  the tree a parent carrying one would count its children twice), and so is a\n  quantity, since two units have no sum. A row naming no row above it, or one\n  the read does not hold, stands at the top. On a gantt the same `nest` folds a\n  row\'s bars under a summary that spans them, a row stating no day of its own\n  included. Two more clauses are the gantt\'s\n  own and refused anywhere a bar cannot be drawn: `depends_on`, a link from the\n  entity to itself naming the rows that must FINISH before a row starts \u2014 each an\n  arrow into its start, toned where the sequence is broken \u2014 and `baseline`,\n  `{"start": \u2026, "end": \u2026}`, the two date fields the plan was FIXED in, drawn as a\n  ghost under the bar so a slip reads as the gap. A baseline is never the day\n  the bar itself starts on: the plan kept apart from the date that moves is the\n  whole of what it shows. A row not yet started has no bar of its own, and is\n  drawn across its plan until it starts.\n\n  ```jsonc\n  // A work breakdown, laid out as its outline and scheduled against its plan.\n  "presentation": { "layout": "gantt", "nest": "part_of", "depends_on": "after",\n                    "baseline": { "start": "planned_start", "end": "planned_finish" } }\n  ```\n- **`acts`** \u2014 where this screen hands work on: `row` is the \u22EF menu on every row,\n  `record` is the \u22EF on the RECORD\'s own page header \u2014 the same reach as a row\'s,\n  standing where the work is open instead of while a list is scanned, and refused\n  on a record that opens as a drawer, which has no header of its own and whose\n  row already carries the register\'s menu \u2014 and `selection` is the bar over the\n  TICKED rows. `export` is the third reach \u2014\n  the WHOLE VIEW, saved in one press: `true` writes the rows as the register drew\n  them, in the columns it drew, as an `.xlsx`, and\n  `{"template": "\u2026"}` says the layout is the trade\'s and makes the paper with a\n  workflow like any other. It is never a list of columns: which columns the\n  export carries is what the screen already draws, and a second statement of it\n  disagrees the moment a slot moves \u2014 the generator reads them off the drawn\n  slots and writes them into the app, so the sheet\'s headings are the labels the\n  register drew them under.\n  `import` is the reach OPPOSITE it \u2014 a file turned into rows:\n  `{"kind": "import", "label": \u2026, "entity": \u2026, "key": \u2026, "columns": [...]}`. The\n  file is mapped column by column, each row is validated, what would change is\n  previewed, and the commit UPSERTS by `key` \u2014 which is why a sheet sent twice\n  moves no counts. That key is one of the entity\'s own `natural_key` fields\n  (\xA7 Write rules), and an entity declaring none is refused: without a key the\n  second run is a second set of the same rows. `entity` is the register\'s own \u2014\n  an app is one register, and rows filed into another entity are a count nobody\n  on this screen can check. `columns` is what the sheet may fill, in that order;\n  absent, it is every column a person states IN WORDS. A computed one is refused\n  because the workspace writes it, and a link, a member or a files column is\n  refused because a cell of a sheet is words and those hold a row of another\n  table or bytes \u2014 a file reaches another table through the party pattern (a\n  `natural_key` on the target, named rather than picked), which is a create\'s.\n  The generator writes the whole verb, as it does for a paper: an\n  `import_<entity>` workflow that finds the row by `key` and then changes it or\n  opens it, answering which of the two, and the staged run over it \u2014 drop, map,\n  the per-row verdict, the commit. A line whose cell the column cannot hold is\n  refused with the reason and the rest of the sheet still lands. A file MINTS\n  rows of the register, which is the Add many times over, so a screen stating\n  `writes: false` or `"children"` \u2014 which opens no row of its own \u2014 refuses the\n  clause; the `export` beside it stays, because it only reads.\n  Both spreadsheet reaches are read and written IN THE BROWSER, so the generated\n  `src/main.tsx` imports `@lotics/app-runtime/sheets` wherever the plan states\n  one of them and not otherwise; an app that has neither carries no spreadsheet\n  engine at all. An act names ONE of three things, never two:\n  - **`template`** \u2014 an `html` template this model declares (\xA7 Templates). The\n    paper is filled from ONE row in `row`, and from the whole ticked set in\n    `selection`. The generator writes the whole verb \u2014 a `generate_<template>`\n    workflow that reads the row and hands the file back, and a menu item that\n    opens it \u2014 so there is nothing left to bind. An `email` template is sent\n    rather than opened and is refused here; a file-backed template (`excel`,\n    `word`, `pdf-form`) is bytes a model has none of, so those stay the author\'s\n    own `lotics app workflow set`. Two screens over DIFFERENT entities cannot\n    name one template: one paper is filled from one kind of row.\n  - **`{"kind": "agent", \u2026}`** \u2014 a run over ONE row. `agent` is an alias the APP\n    declares (`package.json#lotics.agents`), because an agent is prose and tools\n    rather than anything a workspace model can state \u2014 `lotics app check` refuses\n    one nothing declares, exactly as it refuses a workflow nothing bound. `fills`\n    is the fields the run may write: pressed, the reader watches the run, reviews\n    what it proposes field by field against what the row holds now, and applies\n    the ones they kept as ONE write through the record\'s own update. A run can\n    reach nothing outside `fills`, a computed column there is refused (the\n    workspace writes those), and a screen stating `writes: false` refuses an\n    agent act outright. It belongs in `row`; the selection bar makes ONE paper\n    from many rows, and a run per ticked row is the row\'s own act many times.\n  - **`{"kind": "workflow", "workflow": "\u2026", "inputs": {\u2026}}`** \u2014 the work HANDED\n    ON: a lead becomes an opportunity, an order is split into the orders placed\n    on its suppliers, a request is closed. `workflow` is an alias the APP binds\n    (`package.json#lotics.workflows`), because the rule behind it is the\n    business\'s and no model states one \u2014 so the generator writes NO body and\n    `lotics app check` refuses an alias nothing bound, exactly as it refuses an\n    agent nothing declares. `inputs` is what the press hands that body: the\n    workflow\'s own input name \u2192 `"record"` for the row it was pressed on, or a\n    field of this entity for a value off that row. The value is what the\n    workspace HOLDS \u2014 an option\'s key, a linked row\'s id, the figure \u2014 never the\n    rendering. A files column is refused (the body reads the row\'s files off the\n    row it is handed), a column that is not a field of the entity is refused by\n    name, and one input short of the declaration is refused at the press, so the\n    whole act is dropped rather than shipped half-bound. It runs ON the press:\n    there is nothing to review first, which is the agent arm\'s law, and the\n    body\'s own sentence is what the reader is told either way. It stands in\n    `row`, in `record` and on a `section_acts` band \u2014 each reaches ONE row \u2014 and\n    is refused over the ticked set, where one act makes one paper from many. The\n    row it reaches is the RECORD\'s, so a screen stating `writes: false` or\n    `"children"` refuses a hand-off on every one of those surfaces, exactly as it\n    refuses an agent act.\n  - **`{"kind": "recording", "workflow": "\u2026", "inputs": {\u2026}}`** \u2014 a call, a\n    visit, a walk-through RECORDED onto the row. Pressed, the product\'s own\n    capture dialog asks which of the microphone, the system sound and the screen\n    to take; the member records; once the words are transcribed the platform runs\n    `workflow` with `inputs` and fills its `recording` input itself \u2014 the audio,\n    the video where the screen was kept, the transcript (`""` for a silent\n    recording), the length and when capture started. It is a hand-off whose run\n    waits for the transcript, so it takes the `workflow` arm\'s rules \u2014 an alias\n    the APP binds, `inputs` read off the row, `when`, `needs` and `place`, the\n    same three reaches, refused over the ticked set and on a screen stating\n    `writes: false` or `"children"` \u2014 less three: no `confirm` (the capture\n    dialog is the confirmation), no `asks` and no `moves`. An input named\n    `recording` is refused: the platform alone fills it. The body is the\n    author\'s, and `lotics app check` refuses one whose declaration does not\n    carry `recording` exactly as\n    `{"type": "object", "fields": {"session_id": {"type": "text"}, "audio": {"type": "file"}, "video": {"type": "file", "required": false}, "transcript": {"type": "text"}, "duration_seconds": {"type": "number"}, "recorded_at": {"type": "datetime"}}}`,\n    printing that declaration. The body files `video` where it is present and\n    `audio` otherwise \u2014 never both, they carry the same sound \u2014 into the row\'s\n    `recording` field, and writes `transcript` into its `verbatim` field\n    (\xA7 Field roles). An app opened\n    outside the product, or on an instance without transcription, does not draw\n    the act. `scaffold check` prints it as `"<label>" [records \u2192 <alias>(\u2026)] [you\n    write the body]`.\n\n  **`"when"` stands an act down until the work is ready.** `{ "field": "<the\n  entity\'s lifecycle>", "in": ["<stage>", \u2026] }` offers the verb only while the\n  row stands at one of those stages. A verb that cannot work yet is worse than\n  no verb: the reader presses it, the body refuses, and nothing on the screen\n  ever said the work was not ready. Readiness is what a lifecycle states, so the\n  field named is this entity\'s `lifecycle` and nothing else \u2014 a category says\n  what a row is and a verdict answers a question, and neither moves. Refused: a\n  field that is not the lifecycle, a stage it does not declare, and every stage\n  at once, which is the act with no condition.\n\n  **`"place": "cta"` draws an act ON the row** instead of in its \u22EF \u2014 the one verb\n  a reader presses without opening a menu first. At most one per screen and every\n  other act stays in the menu, because the trailing gutter is paid for by every\n  row: a second is refused with *one verb on the row, the rest in its menu*. The\n  ticked set has no row of its own, so `cta` is refused there.\n\n  **`"confirm": true` asks before the act runs**, with the act\'s own label as the\n  commit word \u2014 for a press that cannot be taken back: something goes public,\n  something leaves the building, a figure is filed with somebody else. Everything\n  else runs on the press, because a dialog in front of a reversible act is one\n  readers learn to dismiss, and then dismiss in front of the one that mattered.\n  It reads the same wherever the verb stands \u2014 a row\'s \u22EF, a row\'s own button, a\n  record\'s menu, a section\'s band \u2014 and `scaffold check` prints it as\n  `[asks first]`.\n\n  **`"needs"` stands an act down until the row HOLDS what it works with.**\n  `["<field>", \u2026]` offers the verb only while at least one of those fields holds a\n  value \u2014 `when` asks where the row stands, this asks what it holds. A hand-off\n  to somebody who reaches a person needs a way to reach them; a paper sent by\n  post needs an address. ANY of them, because one person is reached several ways\n  and one is enough to start. The verb is drawn standing down and names what it\n  waits for, rather than pressed into a refusal. Any field answers, a lookup\n  included \u2014 only whether it holds a value is read. Refused: a field this entity\n  has not got, the same field twice, and `needs` over the ticked set, where rows\n  hold values in some and not in others. `scaffold check` prints it as\n  `[needs <field> or <field>]`.\n\n  **`"asks"` is what the reader STATES before a hand-off runs** \u2014 the workflow\'s\n  own input name \u2192 a field of this entity whose editor the act\'s panel draws,\n  starting at the row\'s value. A hand-off to a person is to WHICH person, and the\n  row cannot answer that: its value is who holds it now. The run is handed what\n  the reader stated beside its `inputs`. The editor is one the panel draws with\n  nothing else in hand \u2014 a text, a number, a date, a yes/no, a select or a member\n  \u2014 so a link (a picker and a read of its own), a pile and a computed field are\n  refused, and so is an input both handed and asked. `workflow` acts only.\n\n  **`"moves"` is the stage the body lands the row at**, where a hand-off moves\n  it at all \u2014 an option of this entity\'s lifecycle, and the ACT\'s alone: no\n  stage picker, ladder, board or verdict moves a row there, or past it, because\n  a row moved there by hand stands with none of what the body writes beside the\n  move. Refused: a stage the lifecycle has not got. `scaffold check` prints it\n  as `[only way to <stage>]`.\n\n  A hand-off\'s BODY is still the author\'s: `lotics app workflow set <alias>`\n  binds it, and `scaffold check` prints the act as `"<label>" \u2192 <alias>(\u2026) [you\n  write the body]` so it is read as work owed rather than as a verb already\n  wired.\n\n  A `selection` act is a `template` and nothing else: an act over many rows makes\n  ONE paper from them. The generator turns the register\'s checkbox gutter\n  on, emits a `generate_<template>` workflow taking the ticked ids, and the body\n  reads each row and passes them as `rows` \u2014 which is what the template iterates\n  (`{{#each rows}}`). One template is one paper AND one reach: naming the same\n  one from a row\'s \u22EF and from the bar is refused, because those are two bodies.\n  A shape whose rows are DERIVED rather than records \u2014 an `obligation_desk` \u2014\n  has no set to tick and refuses the clause. The paper is handed BACK, never\n  filed: a ticked set can hold rows of three different parents, so there is no\n  record on which "this document belongs here" is true.\n\n**`section_acts` puts a verb WHERE ITS EFFECT LANDS.** "Chase the paperwork"\nbelongs on the papers, not in the register\'s \u22EF two surfaces away. It is keyed by\nthe alias each section is DERIVED from \u2014 a field\'s (its progress, its prose, its\nrequired set, its charge, one of its files) or a CHILD ENTITY\'s (its register,\nits desk, its run, its log) \u2014 because the sections come off the roles and the\nkey the app addresses one by does not exist until it is built. An alias naming no\nsection is refused, listing the ones that do; the facts band is what every other\nsection left over, so nothing addresses it. Each act is a `template`, an `agent`,\na `workflow` or a `recording`, exactly as a row\'s is \u2014 the reach is the same one row \u2014 and\n`place: "cta"` is refused: a section is a band with a heading and has no row to\ndraw a verb on. `scaffold check` prints\nwhich section each alias landed on, which is the half an author cannot see in\ntheir own file.\n\n**`children` says WHICH of those sections this app\'s record draws** \u2014 the child\nentity aliases, in the order they are drawn, and only those. Two apps over one\nentity read it for different jobs: the site\'s daily log belongs on the site\nteam\'s record and not on the owner\'s, whose record draws the schedule and the\nmoney. A link into a child left out is not drawn as a fact either. A name that\nis no child of the record, or named twice, is refused naming the children\nthere are.\n\n```jsonc\n"children": ["task", "claim"]    // the schedule, then the claims \u2014 nothing else\n```\n\n**`sections` says HOW one of those sections is DRAWN**, keyed by the CHILD\nENTITY\'s alias \u2014 every one of its readings is over a child\'s ROWS, so a field\'s\nalias names no section this clause can draw and is refused. A clause here\nOUTRANKS the table above:\nthe derivations there recognise a shape off columns that are also ordinary\ncolumns, so a markdown field holding a refusal reads as somebody\'s message. Where\nthis clause names the reading, it is the reading.\n\nEvery reading takes an optional `heading` \u2014 what the section is headed on the\nrecord. The child\'s label names the SET its table holds ("Placements", "Tasks");\na section is read as the question it answers ("Where it goes", "Waiting on us"),\nand where the two differ the heading says the second. `{"heading": "\u2026"}` ALONE\nrenames any section of the rows this record OWNS \u2014 a log, a correspondence, a\nregister \u2014 without changing how the roles draw it; on rows the record merely\nlists it is refused, naming the rows it owns.\n\n`"draw": "ledger"` heads a book of movements with what the record it is against\nis read against: `summary`, number or DATE fields of THIS record, in the order\nthey read \u2014 what is owed, and by when. Each is drawn as the record\'s own band\ndraws it: a measure with a bound is a meter, a date is a countdown, every other\nfigure is an amount. A date the record works TO is the default; a date a right\nRUNS OUT at \u2014 a free cancellation, a quote\'s validity \u2014 is written\n`{ "field": "refund_until", "sense": "expires" }` and reads closed rather than\nlate once it has passed. A\nsection with nothing in it is otherwise a heading, a verb and a void \u2014 and the\nemptiness is exactly when the reader most needs to be told what the rows would\nbe for, so the statement is drawn at nought rows too. The figures are the\nRECORD\'s rather than the child\'s for the same reason: a sum of the rows under it\nis the one statement a book with no rows cannot make.\n\n`"draw": "worksheet"`: the child\'s rows\nare PRICED LINES the reader works down in place, each part of the job footed and\nthe sheet closing under them. `cost` and `sell` name the child\'s two figures,\nwhich is the one thing the roles cannot decide \u2014 an entity carries one `amount`,\nand a line that is costed and sold carries two. Everything else is read off the\nchild\'s own roles: what a line is FOR is its `identity`, how many it is for is\nthe `measure` the pair left, and the part it falls under is its `category`. The\nMARGIN is on none of them, because it is arithmetic over the pair.\n\n`"draw": "claim"`: the child\'s rows are the LINES OF ONE PERIOD\'S CLAIM against\na priced schedule \u2014 each read as what the contract holds, what the periods\nbefore claimed, what this one claims, what that comes to to date, the share done\nand what is left, with a retention held back under the total. Four figures, and\nthree of them are quantities no role tells apart, so the clause names each:\n`quantity` (THIS period\'s, the one cell the reader edits \u2014 a `number` nothing\ncomputes, written through the line\'s own update), `contract` and `price`, and\n`previous` \u2014 what the periods before claimed on the line, cumulative. Every\namount is arithmetic over those four, so no column states one; `unit` optionally\nnames what the line is counted in, the line\'s `reference` is its code, and\n`retention` names a percentage field of THIS record, the share held back.\n\n`previous` is DERIVED, and a `number` there is refused: a cumulative somebody\ntypes is right until the first earlier period is corrected, and wrong on every\nclaim after it with nothing saying so. It is a `rollup` SUMMING THIS PERIOD\'S\nQUANTITY OVER THE SAME ITEM\'S EARLIER LINES \u2014 a line per contract item per\nperiod, each linked (a many-row link of the line to its own entity) to that\nitem\'s line in every period before. Never a lookup of the prior line\'s own\nrunning total: that total is worked out from the lookup, so the column is\ncomputed from itself, has no order to compute in, and is refused as a cycle.\n\n```json\n{\n  "entities": [\n    { "alias": "item", "label": "Items", "fields": [\n      { "alias": "name", "label": "Item", "type": "text", "required": true },\n      { "alias": "unit", "label": "Unit", "type": "text" },\n      { "alias": "quantity", "label": "Contract quantity", "type": "number" },\n      { "alias": "price", "label": "Unit price", "type": "number", "format": "currency", "currency": "USD" } ] },\n    { "alias": "claim", "label": "Claims", "singular": "Claim", "fields": [\n      { "alias": "name", "label": "Claim", "type": "text", "required": true },\n      { "alias": "stage", "label": "Stage", "type": "select", "options": [\n        { "alias": "draft", "label": "Draft", "color": "slate" },\n        { "alias": "certified", "label": "Certified", "color": "green" } ] },\n      { "alias": "retention", "label": "Retention", "type": "number", "format": "percentage" },\n      { "alias": "lines", "label": "Claim lines", "type": "select_record_link", "target_entity": "claim_line",\n        "cardinality": "many", "sync_both_ways": true, "paired_field_alias": "claim" } ] },\n    { "alias": "claim_line", "label": "Claim lines", "fields": [\n      { "alias": "claim", "label": "Claim", "type": "select_record_link", "target_entity": "claim",\n        "cardinality": "one", "required": true, "sync_both_ways": true, "paired_field_alias": "lines" },\n      { "alias": "item", "label": "Item", "type": "select_record_link", "target_entity": "item",\n        "cardinality": "one", "required": true, "display_field_aliases": ["name"] },\n      { "alias": "earlier", "label": "Earlier lines", "type": "select_record_link", "target_entity": "claim_line" },\n      { "alias": "quantity", "label": "This period", "type": "number" },\n      { "alias": "claimed_before", "label": "Claimed before", "type": "rollup", "source_field_alias": "earlier",\n        "aggregate_option": { "operation": "sum", "field_key": "quantity" } },\n      { "alias": "contract_quantity", "label": "Contract quantity", "type": "lookup",\n        "source_field_alias": "item", "lookup_field_alias": "quantity" },\n      { "alias": "unit_price", "label": "Unit price", "type": "lookup", "source_field_alias": "item", "lookup_field_alias": "price" },\n      { "alias": "unit", "label": "Unit", "type": "lookup", "source_field_alias": "item", "lookup_field_alias": "unit" } ] }\n  ],\n  "field_roles": {\n    "item": { "name": "identity" },\n    "claim": { "name": "identity",\n               "stage": { "role": "lifecycle", "outcomes": ["certified"],\n                          "phases": [{ "label": "Claiming", "stages": ["draft"] }], "history": true } },\n    "claim_line": { "item": "identity", "claim": "parent" }\n  },\n  "apps": [\n    { "alias": "claims", "name": "Claims",\n      "screen": { "alias": "claims", "label": "Claims", "shape": "lifecycle_desk", "entity": "claim",\n        "sections": { "claim_line": { "draw": "claim", "quantity": "quantity", "contract": "contract_quantity",\n          "price": "unit_price", "previous": "claimed_before", "unit": "unit", "retention": "retention" } } } }\n  ]\n}\n```\n\nThe workflow that opens a period writes its lines and links each to the same\nitem\'s lines before it; from then on a correction to any period reaches every\nlater claim through the rollup by itself. The draw is over rows the record OWNS,\nlike a sheet\'s.\n\n`"draw": "tree"`: the rows nested under each other through `nest`, a one-row\nlink of the CHILD to itself \u2014 a record\'s breakdown drawn as its outline, each\nrow folding what it holds and the money summed up the tree the way a register\'s\n`layout: "tree"` sums it. Unlike the other draws it is an arrangement and not a\nwrite, so it reads rows reaching the record through any link; a relation the\nrecord only counts has no rows here to nest and is refused.\n\n`"draw": "gantt"`: the rows as bars across the calendar \u2014 a record\'s own\nschedule, drawn by the rules a register\'s `layout: "gantt"` is. Each bar starts\non the child\'s `when` and runs the days its `measure` that `counts` days states,\nor to `until`; `nest`, `depends_on` and `baseline` fold, link and ghost the bars\nexactly as the register\'s clauses of the same names do, over the child\'s own\ncolumns, and are refused for the same reasons. Rows none of which a day or a\nplan places are listed as a register lists them.\n\n`"draw": "curve"`: two number fields of the rows, `planned` and `actual`, each\nadded up to date along the child\'s `when` and drawn as two lines \u2014 the S-curve of\na record\'s own work, read as `summary.curve` reads a register\'s. The actual line\nstops at the last day a row stated one, and a curve against itself, over rows\nwith no `when` or over anything but numbers is refused. Both are arrangements\nlike a tree: they read the rows through any link the record lists them by.\n\n```jsonc\n// A job\'s work breakdown as its schedule, and its value earned against plan.\n"sections": { "task": { "draw": "gantt", "nest": "part_of", "depends_on": "after",\n                        "baseline": { "start": "planned_start", "end": "planned_finish" } } }\n"sections": { "task": { "draw": "curve", "planned": "planned_value", "actual": "earned_value" } }\n```\n\n`"draw": "log"` PLACES a log\'s fields on the entry where the roles\' placement is\nnot the reading. The roles decide the rungs by themselves \u2014 the `identity` leads\nas the entry\'s `name`, the `body` is its `words`, the `recording` is the\n`evidence` under them, the `verbatim` the `detail` behind one fold, and the\nselects, the parties and the `contact` make the supporting `line` \u2014 so the\nclause is for the field a role cannot place: a photo that is the evidence rather\nthan an attachment, a figure worn `trailing` at the head, a line read by two\nwords instead of five. Each rung named replaces that rung whole; a rung left out\nkeeps the roles\' answer; a field the clause places is never also a fact under\nthe words, and one the roles placed on a rung the clause rewrote without it is a\nfact again \u2014 a `verbatim` left off the `detail` is read by its label, and folds\nnothing; and a field it names that the child lacks, or places on two rungs, is\nrefused naming both. `words` may make rows a log that the roles would not \u2014 a\nplain text with no `body` role \u2014 but nothing makes rows with no day one.\n\n```jsonc\n// A site diary: the photos are what the entry shows, the crew count sits at its head,\n// and the line says only what kind of visit it was and where.\n"sections": { "visit": { "draw": "log", "evidence": ["photos"], "trailing": "crew", "line": ["kind", "site"] } }\n```\n\n`"draw": "itinerary"` says WHICH FOUR STATEMENTS each stop of a run is read by:\n`line`, in the order they read, from `when`, `kind`, `provider`, `stage`,\n`duration`, `caption` and `reference`. A stop is one press and its supporting\nline holds to one row at every width, so four is the whole of it \u2014 a fifth is a\nfact the stop\'s own drawer answers. Absent, a stop is read by `when`, `kind`,\n`provider`, `stage`, which is how a travel row reads; a roster is read by its\nhours and a courier\'s run by who is at the door, and nothing derives which:\n\n```jsonc\n// A cleaning round: the hour it takes and the flat it is at say more than the kind.\n"sections": { "visit": { "draw": "itinerary", "line": ["when", "duration", "provider", "stage"] } }\n```\n\nEvery run named is one the stops already carry \u2014 `duration` is the child\'s\n`measure` that `counts` hours, `caption` the second `party` a row names, `kind`\nits `category` \u2014 so a word the child declares no role for is refused rather than\ndrawn as a gap in every line, and so is the same word twice.\n\nA sheet is the WRITE side of a price, so it is the one child section whose cells\nare editors: a figure typed into a cell is written as a diff through the child\'s\nown update, which is the same editor the line\'s own drawer saves through. Every\nother child section is read where it is drawn and edited in the row\'s drawer. A\nline is ADDED from the section\'s heading as every child\'s row is, with the record\nit hangs under as the act\'s own context.\n\n`"draw": "publish"`: the child\'s rows are ONE RECORD STANDING ON N\nDESTINATIONS, and the section is drawn as the strip of those destinations rather\nthan as a register of the rows. A register of them is the same record listed once\nper destination with a stage beside it; what a reader wants is every destination\nthey COULD reach, each wearing what has happened there, and the one press that\nsends the ones that are ready.\n\n```jsonc\n"sections": { "pinning": {\n  "draw": "publish",\n  // The child\'s own lifecycle, all four \u2014 each is a different thing the chip\n  // says, and `queued` is the stage its flow OPENS at (a destination is queued\n  // by opening a row).\n  "states": { "queued": "waiting", "published": "up", "failed": "refused", "by_hand": "by_hand" },\n  "text": "wording",        // optional \u2014 a text on the child, what THIS destination goes out with\n  "permalink": "address",   // optional \u2014 a link-formatted text on the child, where it landed\n  "error": "fault",         // optional \u2014 a text on the child holding the platform\'s own refusal\n  "link": "source",         // optional \u2014 a link-formatted text of THIS record, the card it carries.\n                            // A network that takes a card OR a picture takes neither twice, so a plan\n                            // whose records always carry both leaves the desk nothing it can send there\n  "destination": {\n    // The destination\'s own select, and which of its options the platform can\n    // reach as which network\'s feed. An option this map leaves out is by hand.\n    "network": { "field": "surface", "options": { "page": "facebook", "feed": "instagram" } },\n    "connected": "account", // optional \u2014 a text on the destination; empty means not connected\n    // Which of THIS record\'s bodies each destination receives \u2014 the destination\'s\n    // own select, mapping ITS options to text fields here. One alias\n    // (`"bodies": "wording"`) is the model with a single body.\n    "bodies": { "field": "tongue", "options": { "near": "wording_near", "far": "wording_far" } },\n    "offered": { "field": "standing", "in": ["open"] }  // optional \u2014 which rows the strip offers; absent, every row\n  },\n  "publish": "send_pinnings", // the workflow alias the APP binds \u2014 the generator writes no body\n  "when": { "field": "state", "in": ["ready"] }  // optional \u2014 offer Publish only while THIS record stands there\n} }\n```\n\n`when` is an act\'s `when` (\xA7 Apps and screens, `acts`), read off THIS record\'s\nown lifecycle: a piece still being written is not one to send, and the desk\'s\nPublish is the one press on the page that cannot be taken back. The same refusals\nhold \u2014 a field that is not this entity\'s lifecycle, a stage it does not declare.\n\nEverything else is read off the roles: the child\'s `parent` (the record), its\n`party` (the destination entity), its `lifecycle` and its `when`; the\ndestination\'s `identity`, `mark`, `contact` (where a post put up by hand is\npasted) and `category` (what the strip folds the chips under); and this record\'s\nown `mark` (the pile the post carries). The destinations are read WHOLE, through\na query of their own, because the strip\'s point is the ones this record has not\ngone to yet \u2014 which the child\'s own read structurally cannot answer with. The\nREGISTER\'s row wears one mark per destination its record has reached, read one\npage of rows at a time; the face and the network each mark wears are read across\nthe `party` link by that read itself, so the model declares no lookup for them.\n\nA network the INSTANCE is not configured for is refused when the send\'s body is\nbound (`tool_capability_unavailable`): a check over a file cannot know which\nproviders this instance holds keys for, so the map is proven against the kit\'s\nnetworks alone and the rest is answered where the body is.\n\nA chip IS the draft, which is why the section mounts no Add: pressing an empty\ndestination opens a row, pressing a queued one takes it back, and both are\nworkflows the generator writes and binds. The create takes the RECORD and the\nDESTINATION and nothing else \u2014 every other column of one of these rows is what\nthe send writes back \u2014 and it reads the desk first, refusing a destination this\nrecord already stands on: a surface guards a second press for the life of a\nmount, and a second tab is a second mount. The withdrawal is the ONE generated\nbody that deletes, and it reads the stage first and refuses anything past the\nqueue. A delete names no column, so `app create` declares the child\'s TABLE in\n`package.json#lotics.deletes` beside the columns in `lotics.writes`, and `lotics\napp check` refuses a body that deletes from a table nothing there names. The SEND\nis the author\'s, like every other hand-off: `lotics app check`\nrefuses an alias nothing bound, and the press hands it the record and the rows it\nis sending.\n\nRefused: an alias naming no register of this record, rows the record does not\nOWN for any draw but a tree, a gantt or a curve (a line added to a history\nbelongs to the job it is about, not to what is reading it), a figure that is not a field of the child or whose role is neither\n`amount` nor `measure`, a sheet naming neither figure, one figure priced as both,\na book headed by anything but a number or date field of the record, and a line on\na section this record draws as a register rather than as a run. A desk is refused\nfor rows that name no destination or carry no lifecycle, a state naming an option\nthat lifecycle has not got, a `queued` stage that is not the one the flow opens\nat, a destination that names no row of itself, a network the kit cannot preview,\nan option of the destination\'s own selects it has not got, and a body, an\noverride, a permalink, a refusal, a card address or a connected account that is\nnot a text field of the entity it is named on. A SECOND desk on one record is\nrefused too: the strip is every destination that record can reach, so two are two\nanswers to one question, and a row of the register wears the marks of one.\n\n`"draw": "acts"`: the child\'s rows are ACTS WAITING FOR A PERSON \u2014 a reply to\nwrite, a call to make, a message to send \u2014 and the section is drawn as a queue of\ncards rather than a register: the verb, the words already written, why now, how\nlong is left, where to reach them, and the ways an act ends. An act is an\nintention and what HAPPENED is a row of its own (the touch), so Done opens a\nsheet \u2014 what came of it, what was said, the next step \u2014 and one write files the\ntouch and closes the act.\n\n```jsonc\n"sections": { "task": {\n  "draw": "acts",\n  "heading": "Waiting on us",   // optional\n  // The child\'s own lifecycle, all three \u2014 `queued` is the stage its flow OPENS\n  // at (an act is queued by opening a row).\n  "states": { "queued": "waiting", "done": "done", "skipped": "passed" },\n  "verb": "verb",               // a single select on the child \u2014 which act this is\n  "words": "words",             // a text on the child \u2014 what to send\n  "why": "why_now",             // optional \u2014 a text on the child, why this is worth doing now\n  "reason": "pass_reason",      // optional \u2014 a text or single select on the child, why it was passed over\n  // Where each verb is done: a field of THIS record holding the address \u2014 its\n  // own, or a lookup of the person\'s \u2014 or "<link of the act>.<field>", an address\n  // on the row the act names; and how it is opened: "link" as it stands, "phone"\n  // dialled, "sms" / "email" composed, "zalo" / "whatsapp" a chat opened on the\n  // number. A verb left out is done where the reader already is.\n  "reach": { "reply": { "at": "on_post.url", "by": "link" }, "call": { "at": "prospect_phone", "by": "phone" } },\n  "withhold": "prospect_quiet", // optional \u2014 a yes/no of THIS record; while it reads yes, no act reaches out\n  "log": {\n    "became": "became",         // the child\'s link to the touch it becomes\n    "outcome": "outcome",       // a single select on the touch \u2014 the sheet\'s one-tap answer\n    // optional \u2014 per verb, the answers of `outcome` it can come to; the sheet offers only those and the body refuses the rest\n    "outcomes": { "reply": ["answered", "no_reply"] },\n    "note": "said",             // optional \u2014 a text on the touch; the act\'s own words stand in where none is written\n    "next": { "step": "next_step", "on": "next_on" },  // optional \u2014 texts/dates on the touch; a stated step is queued as the next act\n    "set": { "direction": "out", "channel": { "reply": "in_public", "call": "phone" } },  // optional \u2014 touch selects the verb decides\n    "silent": ["like"],         // optional \u2014 verbs whose doing leaves nothing to answer: closed, and no touch written\n    // optional \u2014 selects on the touch the sheet asks, per verb: one tap for a single select, a toggle per option for a multi-select\n    "ask": { "reply": ["approach", "carried"] },\n    // optional \u2014 links on the touch copied from a row the act names: "<link of the act>.<link on that row>"\n    "copy": { "venue": "on_post.venue" },\n    "moves": { "from": ["fresh"], "to": "working" }  // optional \u2014 stages of THIS record\'s lifecycle: a touch logged at one of `from` lands it at `to`\n  },\n  "cta": true                   // optional \u2014 the register\'s row wears this record\'s NEXT waiting act as its verb\n} }\n```\n\nEverything else is read off the roles: the child\'s `parent` (the record), its\n`party` (who the act is aimed at), its `lifecycle` and its `when` (the day it\nstops being worth doing, counted down on the card); the touch\'s link to this\nrecord, its link to the same party where it keeps one (the one carrying `party`\nwhere it names that entity twice), its `when` (stamped with the moment it is\nlogged), its member (who did it \u2014 the caller, never a value anybody states) and\nits text `identity` (the act\'s `why`, else its words). Where the act names\nnobody, it is done with this record\'s own `party` onto that entity: an act queued\nbefore the person was known is still done with them, and the next act is queued\nwith them.\n\n**AN ACT IS OFTEN ABOUT A ROW OF ITS OWN** \u2014 the post a reply is left under, the\nmessage it answers \u2014 and that row holds where the act is done and where the touch\nit becomes happened. A path `"<link of the act>.<field>"` reads one hop across a\nlink of the ACT holding ONE row (`cardinality: "one"`): in `reach.at` the field is\nthe address, read across the link by every read of the acts, so the card and the\nregister row wearing the next act both open it; in `log.copy` the field is a link\non that row, copied onto the touch\'s link to the same entity as the act is closed.\n`log.ask` names selects of the touch the sheet asks on the verbs listed \u2014 how it\nwas done, what it carried \u2014 each written with the touch, and only on those verbs.\n\nRefused beside the rest below: a path across a link holding several rows or onto a\nfield that row has not got, an address there that holds no words, an asked column\nthat is no select of the touch or one the log already writes, an asked verb that\nis `silent` or no option, an `outcomes` verb that is `silent` or no option or an\nanswer `outcome` does not offer, a copied column that is no link of the touch or is the\ntouch\'s own link to this record or to the person, a copy between links to\ndifferent entities, and a copy of a link naming several rows onto one that holds\none.\n\nThe generator writes and binds three bodies per queue. `create_<child>` opens an\nact from the section\'s heading \u2014 the verb (required), the words, why now and the\nday, never the person or the touch. `log_<child>` is Done: it opens the touch,\nsets the act done AND points it at that touch in ONE update \u2014 a row reading done\nwith nothing it became is exactly the gap it closes, and a table workflow waiting\non that state does not fire a second time \u2014 then queues the next act where the\nsheet states a step, by the verb the reader picked (this one\'s where they picked\nnone). With `moves`, the same run moves the record the act is under to `to`\nwhere it stood at one of `from` \u2014 read before anything is written, and moved\nonly where a touch is: reaching somebody for the first time is a stage of the\nrecord\'s own work, and a stage set by hand afterwards is one nobody sets. A\n`silent` verb\'s act is set done alone and reads done with nothing it became \u2014\nthe state such a table workflow fires on, and no move. `skip_<child>` passes it over,\nwriting the reason only where one is sent; passed-over acts are KEPT, because they\nare evidence about what the queue gets wrong. Both refuse an act that is no\nlonger waiting, read before anything is written. With `cta`, the\nregister reads the waiting acts of every row on the page in one read, soonest due\nfirst, and each row wears its next one as its verb \u2014 the one press that reaches\nthe person; that read and the touches\' own (whose live options colour the sheet)\nare declared beside the record\'s.\n\nA queue is worked IN PLACE on every door, the way a correspondence is from its\ncomposer: an act is added from the heading, its words corrected and it is closed\nfrom its own card, so a record that opens as a drawer carries the queue whole \u2014\nthe sheet that closes an act opens over the drawer.\n\nRefused: a queue on a screen stating `writes: false` (every way an act ends is a\nwrite of its row), rows with no lifecycle, a state naming an option it has not got,\na `queued` stage that is not the one the flow opens at, a verb that is not a\nsingle select beside the lifecycle, words, why or a reason that is not a text (or\nsingle select, for the reason) of the child, a `reach` key that is not a verb\noption or an address that is not a field of THIS record holding words, a\n`withhold` that is not a yes/no of this record, `cta` beside a row act already\nplaced there, and a log whose touch cannot be written: a `became` that is not a\nlink, a touch naming this record through no link or through two, an outcome that\nis not a single select of the touch, a note or step that is not a text, a day that\nis not a date, one column named for two things the log writes (the touch\'s name\nand day, what was said, the next step and its day), a `set` over a column the log\nalready writes or naming an option either select has not got, a `silent` verb\nthat is not an option, and a `moves` that names a stage this record\'s lifecycle\nhas not got (or a record with none), names its `to` among its `from`, lands at a\nstage that ENDS the flow (where the work ends is somebody\'s decision, not a\nreply\'s), lands at a stage only a workflow act\'s `moves` reaches, or moves a\nrecord the screen draws at rest (`writes: "children"`). A SECOND\nqueue on one record is refused: what a record is waiting on is one list read\nsoonest first.\n\n**A CHILD NOBODY REGISTERS IS A NOTE, not a refusal.** Where a record lists a\nchild entity no app is a register of, `scaffold check` says `"<entity>" has no\nregister \u2014 its rows are read here and created nowhere` and the plan printout\nmarks that entity `(no app)`. Rows can arrive from an import or a workflow, so\nit is a reading rather than a rule; what it catches is the register somebody\nmeant to plan and did not. Rows only the automations write (\xA7 Entity) are\nexempt, since nothing should create them. A section the record ADDS to is\nexempt, because its heading is where those rows are typed: the rows a record\nowns on a PAGE, a log on any door \u2014 an entry is written where it is read \u2014 a\nqueue of acts on any door, and a sheet, which opens its own lines. A record\nopening in a DRAWER adds none of its other owned rows, so those are noted like\nanybody else\'s.\n\n`scaffold check` prints every clause a screen states, on its own line under the\nslots, spelling the screen\'s `writes` clause `operable` \u2014 the app manifest\'s\n`lotics.writes` keeps that word, and the two are different facts: `app create`\nSEEDS the manifest from the fields the screens\' own editors write, and from then\non the app owns the declaration `lotics app check` holds its bodies to.\n\nEach shape is a `@lotics/ui` component of the same name (`LifecycleDesk`,\n`PartyRegister`, \u2026) whose props are these slots, so once the tables exist\n`lotics app create <name> --from <this file>#<app alias>` scaffolds the app with\none screen per entry, each slot reading the field the plan bound.\n\n`"shape": "custom"` is the screen no registry row covers: it declares its own\n`roles` (slot name \u2192 role), and it is emitted on `ShapeFrame` \u2014 the one anatomy\nthe six shapes above are each a configuration of \u2014 so its strip, search,\nordinal, fit budget, empty and waiting states and record door are the same ones\nthey have. It opens the record its `record` says, drawer or page, like any other.\nA bound `lifecycle` slot IS its strip, the stages in the field\'s order as on a\ndesk, so such a screen names no `tabs`. Only a lifecycle earns a strip \u2014 each\ntab a queue of work at one stage \u2014 and a screen naming any other select as\n`tabs` is refused: a kind, a book, a channel is a `filters` entry beside the\nsearch. The three shapes whose strip means something of their own take any\nselect: a reconciliation\'s dated runs, a trend\'s series, a worksheet\'s versions.\n\n**An app IS its `app.json`.** `create --from` writes the bound plan \u2014 every\nscreen with its shape and slots, the record each row opens with its sections in\nthe archetype\'s order, the create panels, the acts \u2014 as one JSON document, plus\na five-line `src/main.tsx` that mounts `@lotics/app-runtime` over it and one\n`src/workflows/<alias>.ts` per write. There is no screen source: the runtime\ndraws the spec, so a kit correction reaches every app with its next install.\nWhere the plan has no word for what a screen or a section IS \u2014 or for what a\npaper act should ASK before it is made \u2014 the spec names one of the app\'s own\ncomponents and `src/components/index.ts` registers it, the one file under `src/`\na regeneration never rewrites. `lotics app eject <screen|<section key>|<act\nlabel>>` writes each of those, starting from what the runtime already drew. What\nthe APP does rather than what a screen draws \u2014 a bridge to the page it is framed\nin, a listener \u2014 is one component `app.json#root` names: mounted once around\nevery route, and carried over by every regeneration, since the plan has no word\nfor it.\n\n**How a spec reads a row.** Each query projects its columns under the alias the\nworkspace mints from the field\'s LABEL \u2014 never the alias this file keys it\nunder, which is the model\'s own namespace and which the workspace never saw. So\na field this file calls `partner` and labels `\u0110\u1ED1i t\xE1c` is referenced as\n`doi_tac` throughout the spec. Every id in it is live: the `tbl_` a screen is\nover, the `fld_` of each column, and the `opt_` of every option a role names.\n\n**Every query is described, in the model\'s own language.** The line an agent\nchooses between aliases by is written from this file\'s nouns \u2014 the entity\'s\nlabel, the screen\'s, the link\'s \u2014 and the sentence around them is the language\nthe file is mostly written in, decided the same way a generated write\'s refusals\nare. Hand-editing one is erased by the next regeneration; `lotics app check`\nrefuses an alias that carries none.\n\nA screen is that list and the RECORD it opens, and the record comes off the same\nroles \u2014 nothing to declare for it. It opens with a **header**: the entity\'s\n`identity` as the record\'s name \u2014 whether or not the list has a column for it, so\na ledger\'s and a trend\'s records are named too \u2014 the `mark` beside it on a PAGE,\nwhich is what the subject is recognised by (so the pile below is the papers that\nare left, and a `presentation.lead` spending that gutter on something else leaves\nthe picture in the pile), the `when` this screen reads\nunder it, and ONE headline\nfigure (the `amount` the screen reads, else its `measure`). BOTH DOORS state the\nname: which door a screen uses is a layout answer, and what the record is ABOUT\nis not.\n\n**A JOB\'S HEADER ALSO STATES WHO IT IS FOR.** Where the record is the work itself\n\u2014 a desk\'s rows that belong to nothing, opened on a page \u2014 its `party` is a link\nunder the name, beside the ways to reach the subject, or, where that party is a\nworkspace MEMBER, the person themselves with no door behind them, and it is then\nnot a fact\nas well: a page headed by a code alone said nothing about whose work it is, and\nthe one thing a reader arriving from the desk already knows the row by sat in the\ngrid below as a row among forty. A record opening in a DRAWER has no row of links\nto hang it on, so its party stays a fact; so does a LINE\'s, whose register files\nit under the thing it belongs to and whose party is that parent\'s, restated per\nrow.\n\n**A record whose figures are a SENTENCE states them under the header, in a\nband**, and the header then states neither of them: a job reads what it comes to,\nhow far through it is (the `measure` against its limit), what is left of it (a\nformula that is exactly `{amount} - {measure}`) and how long there is (an\n`obligation`, else its `when`, counted down); a party reads its settlement, the\n`amount` and `measure` roles it carries in the order the model declares them; a\ncatalogue item reads its `amount` against the reference that amount names. Two\nfigures are the floor and four the ceiling \u2014 under two, the header keeps its one.\nA band is a PAGE\'s strip, so a screen whose `record` is a drawer keeps every\nfigure where a drawer reads them. Each figure is drawn exactly once: the limit a\nmeter states is not a fact beside it, and the day a countdown counts to is not\nthe provenance line above it. The band draws them, so the band is where they are\nCHANGED \u2014 a date a person states is edited on the countdown and a limit a person\nstates on the meter, while the level between them is read. The `lifecycle` is\nnot badged there, because the progress section is the rung it stands on. Then\nits sections, in the order its KIND reads them: the\n**facts** (every field neither the header, the band nor another section owns, the\nrow\'s own `parent` among them \u2014 led by the ones THIS screen\'s slots bound, then\nthe key it is filed under, then the order the model declares them in \u2014 a\n`markdown` field among them, drawn across the grid\'s whole row rather than\nwrapped to a third of it), the record\'s own **body** (that same markdown, taken\nas a section instead, ONLY where the kind leads with it: a catalogue item IS its\ndescription, and a job is not its notes), the **charge** (where the `amount` is a formula over exactly one\nquantity and one money field, the line states `quantity \xD7 unit price = amount`\nand neither figure is typed twice \u2014 the section is headed by the amount\'s own\nlabel and the closing row says what the figure IS, so the word is said once),\nthe **progress** (the `lifecycle`\'s stages as a ladder the reader ticks a rung of\nto move the record on, grouped into its `phases` where the model states them, and\neach rung carrying the day it was reached where the lifecycle keeps a\n`history`), a\n**required set** (a multi-select `expected_set`, or a child entity whose rows\ncarry one entry of it each \u2014 that child\'s `files` field is what a paper attaches\nto), the record\'s **own rows** (any other child, its role-bound fields as\ncolumns), and its **files** (every `files` field the header does not lead with,\nthe `mark` first where it keeps one \u2014 a section of\nthe column like any other, straight after the facts it is the evidence for,\nexcept on an EVIDENCE record, which OPENS on the paper it exists for; the\nheading carries the Add verb, and stands it down while the pile is empty, where\nthe drop well is already the door; and a `verdict` whose FORMULA reads one of\nthose files fields is the pile\'s OWN state rather than a fact row \u2014 the file it\nis short, drawn as a ghost, and the mark the rail sends a reader to). A child is\nan entity that LINKS here, ONE SECTION PER LINK: the rows it owns (`parent`), the\nrows NAMED by it (their `party` or their `identity` \u2014 so this record\'s history),\nand the rows reaching it through a link carrying neither role, headed by that\nlink\'s own label. A child hanging off two records therefore declares one `parent` and\nleaves the second relationship a plain link, which still gets its section.\n\n**THE ROWS A RECORD OWNS ARE ADDED AND OPENED FROM THEIR SECTION.** A `parent`\nsection\'s heading carries the Add for its rows, handing the record as the\nparent \u2014 filled, never asked. Every row opens its own record \u2014 a line of a book,\na paper on a desk, a stop on a schedule alike: where this app already routes a\npage for those rows (the register\'s own, under one of them) it is navigated to;\notherwise it is a DRAWER mounted on the record it belongs to, stepped \u25C0 \u25B6 over\nthe section\'s rows as they are drawn, with the row\'s framed editors, its ladder\nand its files, saving through `update_<child>` \u2014 the one editor those rows have,\nwhich any control the section draws over a row writes through too. Never the\n`parent` link itself: it is the key the row is FILED under, stated by the record\nthe drawer was opened from, so it is neither a fact of the drawer nor an input\nof that editor. ONE LEVEL, and only from a PAGE: a child\'s own children draw as\nthe kit\'s panel of the row, with no drawer and no Add, and a register whose own\nrecord is a DRAWER is the same for the children it owns \u2014 a drawer mounts no\ndrawer. The rule is about RECORDS INSIDE RECORDS, not about rows of one kind\nnested by a link of their own: a tree (`layout: "tree"`, `"draw": "tree"`) is one\nlist of one entity, and each of its rows opens the one record surface that entity\nalready has, at whatever depth it is drawn. **A ROW IS ADDED WHERE IT CAN BE OPENED AGAIN**, so those sections lose\ntheir Add with their drawer; a row of the register\'s OWN kind keeps it, because\nthe register\'s list opens it. A correspondence\'s entries open nothing anywhere:\nthe composer under them is the section\'s Add whatever door the record has, and\nthe answer mark is one field of the reply\'s own editor. A queue\'s acts are the\nsame on a drawer: the heading\'s Add opens one, and its card saves its words\nthrough `update_<child>`. The rows a record is merely NAMED by, and those reaching it\nthrough a roleless link, are read only \u2014 a history, never a place to open or\nadd.\n\n**TWO CHILDREN ARE READ ON A TIME AXIS RATHER THAN AS A REGISTER**, and the\nmodel says which by the roles it declares on them. A child carrying an\n`obligation` whose `satisfied_by` is a DATE \u2014 and no `lifecycle`, because an\nentity with stages of its own is a JOB being worked and its rows under another\nrecord are that record\'s lines or its history \u2014 is a **schedule**: what is\nplanned against time, and what slipped. Its rows are the ordered stops, each\nstating the day it was promised for and the day it happened, with the delta\nnamed where the rung was late \u2014 drawn as a register those are two date columns\nand the reader subtracts them by eye, which is exactly what "three days late at\ndischarge" costs to learn. An obligation closed by a FILE says nothing about\nwhen, so those rows stay the register they were.\n\n**A body and a day is a LOG** \u2014 what happened, in order: the entry in the words\nsomebody wrote, filed under the day they wrote it. The body is the child\'s\n`body`, else its first `markdown` text; the format never decides, so a plain-text\nnote declared `body` is an entry and a markdown remarks field on a job is not\n(a `lifecycle` keeps it a register, as it keeps a schedule one). A register of\nentries is a table whose one useful column is the one it cannot draw, so the rows\nare read as one time axis instead: one head per entry, the words under it, and\neverything else the row states placed on the entry. WHO WROTE IT is the\n`select_member` the row names \u2014 a log is kept by the people who work the\nrecord \u2014 and the parties on it are who it was WITH, drawn on the entry\'s line\nbeside the `contact` it reached them at and the files that came with it. The\nother selects are words on that line; the `recording` plays under the words and\nthe `verbatim` waits behind one fold; everything else a person states on the\nentry \u2014 the day\'s headcount, the gear on site, what went wrong \u2014 is drawn under\nits words by its own label, where that entry states it: an entry is the whole\ntouch. Its Add is a composer asking exactly that \u2014 the entry, its name where the\nchild names one, the recording and the verbatim, the day (opening on today), the\nentry\'s own selects and those facts; the record it hangs under is not asked.\n\n**A `verdict` on those rows makes the log a CORRESPONDENCE** \u2014 a question, its\nreplies, and the one reply marked with that yes/no as the ANSWER. It is read\nfrom the question, oldest first, where a log is read from its latest entry under\nday heads. Where no member keeps it the first `party` is who wrote each entry,\nbecause there the other side writes too; a SECOND party is who the entry was\nleft WITH, and the latest one names the ball in court: while nothing answers,\nthe record says whose move it is and counts its own deadline (an `obligation`,\nelse its `when`) against them. Whose move and the clock are read only under the\nrecord that OWNS the messages \u2014 under the party who wrote them the same rows\nare several questions at once, and the last of them says nothing about any \u2014 but\nthe answer mark is a fact of the reply wherever it is read, and it is one field\nof the reply\'s own editor. A NAMED row is an entry that OPENS \u2014 a visit or an\ninspection is a thing in its own right, read in full on a record of its own,\nmounted on the page it is read from as a register\'s row is \u2014 where an entry\nnothing names is corrected where it stands. An entity only the automations\nwrite (`writes: false`) opens that record at rest and composes nothing.\n\n**A PROFILE LEADS WITH ITS LADDER.** An account walks stages like any other work,\nso a profile carrying a `lifecycle` reads `progress` first \u2014 right under the\nband, the same place a job leads with the act that moves it \u2014 and its histories\nfollow. Under them the ladder was seven bands down a page nobody scrolls that\nfar.\n\n**NOTHING SITS BESIDE THE RECORD.** A page is ONE reading column \u2014 its fields,\nits files (a section per `files` field, under its own label), the rows it owns,\nits notes, all sections of it in the archetype\'s order \u2014 over a reserved left gutter holding a floating NAVIGATION RAIL: the way\nback, then one line per section with that section\'s category mark, and nothing\nelse. No files, no counts, no group headings. Too narrow to seat the rail, it is\none pinned bar of the same list across the top. A section HEADING never wears\nthe mark; the rail\'s line for it does.\n\n**A RELATION THE RECORD NEVER ACTS ON CLOSES THE COLUMN.** Every register that\nmerely NAMES the record is one counted line of a single last section: its label,\nhow many rows name this record (a COUNT, never a page of rows measured), and a\npress that opens the register owning them narrowed to this record. An entity\nthis app lists nowhere is a count with no door, and where every count is zero\nthe section is not drawn at all. The one exception is a PROFILE, whose history\nIS its body and stands open in the column.\n\n**Rows the record owns whose `amount` is `signed_by` a direction are a\nBOOK**, drawn as a statement \u2014 each line dated and signed, the balance under\nthem where there is more than one line to add up, labelled by the amount\'s own\nword \u2014 where the same rows on the party they\nwere transacted with stay that party\'s history, which is scanned for the line\nshort of its paperwork rather than struck to a balance. **Rows that carry a\n`when` read as RUNS**: a party\'s history under the year \u2014 and only where the rows\nin hand span more than one, since a subhead over every line of a book names the\nyear and separates nothing \u2014 and a job\'s own rows under the day they fall on,\nwhere some day holds more than one (a row per day keeps its date column), and\nwhich, where those rows also carry a `lifecycle`, is an ITINERARY rather than a\ngrouped table: the day heads the run, each row is one line (its `slot`, its name,\nits party, its stage, its `category` and `reference`, its amount), the figures end\non one edge and the run closes with their sum \u2014 unless the record\'s own BAND is a\nsum rollup over exactly these rows, which states it once already. A `category`\npaints the node the run is read down, in the option\'s own colour; a `reference`\ncloses the line with the code somebody quotes on the phone. **A `mark` LEADS the\nline with the stop\'s own picture** \u2014 a venue, a vehicle, a machine \u2014 and it is the one\nplace on a record where a child entity\'s mark is drawn at all, since no register\ncolumn is ever a picture; a line whose subject holds none is marked with its\n`category`\'s glyph instead, so the run keeps one left edge. All three are\nPROJECTED for the run whether or not the register\'s column budget would have\ndrawn them, and a mark is projected NOWHERE ELSE.\nA line\'s mark is most often the SUBJECT\'s rather than the line\'s own \u2014 the\nservice, the product, the asset it is a line of \u2014 which is a `lookup` through\nthat link onto the subject\'s own `files`, given the role on the line.\n**EACH DAY\'S HEAD CARRIES THE SECTION\'S OWN ADD** as well, handing the panel that\nday, so a line made from Tuesday opens with Tuesday answered; the heading keeps\nthe verb too, for the first line and for a day nothing is planned on yet. **THE\nKEY LEAVES THE COLUMNS where the head states the whole of it** \u2014 a day head does,\na year head states four digits of the date and the day is what the column is\nstill there to carry.\n**A run is READ FROM THE END THE READER WANTS**: a job\'s own rows and an itinerary\nascending, a book, a history and a log descending.\n**A REGISTER WHOSE `when` IS A DEADLINE IS READ FROM THE NEAR END** whatever its\nshape does \u2014 `due` (or an `until` that says where the countdown stops) makes the\ndate a promise, so the rows in breach of it lead and a row nobody dated falls\nlast. A plain `when` keeps the shape\'s own end. `scaffold check` prints the\npromise (`order: Theo d\xF5i ti\u1EBFp, overdue first`).\n\n**A DESK OVER AN ENTITY THAT CARRIES A `slot` IS ITSELF A DAY\'S RUN.** Its own\nregister is drawn under one subhead per day, sorted by that day and then by the\npart of it, and the date column goes \u2014 the subhead states it once for the whole\nrun, and a column repeating it down every line is the same value twice. Without\nit an itinerary was one flat list in whatever order the rows arrived.\nA document desk keeps its head either way \u2014 the entries it owes are its\ncontent, filed or not. The name and whatever figure is left to it are the header\'s\nalone \u2014 it states them in full, so a fact for either would be the same sentence\ntwice.\n\n**A FACT IS PRIMARY OR IT IS PROVENANCE.** An `autonumber`, a date the platform\nstamps (`derive_from`) and a date a formula works out that no role names are what\nthe SYSTEM wrote; they fold, with every optional field this record does not\nstate, behind the grid\'s ONE link. Everything a person types or picks is primary\nand is shown, empty or not, because absence is work somebody owes. **A screen\nthat named `facts.groups` has already said which:** a field in an open group is\nprimary, and one in none \u2014 or in a `folded` group \u2014 folds \u2014 grouping says what the reader decides with, and\nby saying so says the rest are not, which is why `check` refuses a plan whose\ngroups leave a stated field out: the fold is for provenance, never for a fact\nsomebody fills in. A `tier` on a `facts` entry exists only for the case that\nderivation gets provably wrong.\n\n**A `contact` field whose kind the\nmodel decides** \u2014 an email, a number, a place, a `link`-formatted text, or a\nMESSAGING APP its label names (WhatsApp, Zalo, Telegram, Viber, WeChat, Line,\nMessenger) \u2014 leaves the facts too, for the row of links under the name on a\nrecord that opens as a page; one whose kind nothing decides stays a labelled\nfact, because a scheme nobody stated is a link that opens nothing. A handle is\ndrawn under its app\'s name \u2014 the app is what identifies the person there, and a\nbare number beside an envelope says the wrong thing \u2014 and it dials only where its\nvalue IS a number.\n`check` prints the record under each screen\'s slots:\n\n```\n  Orders \u2014 lifecycle desk over Orders (12 rows) \xB7 page \xB7 tabs: Stage (New \u2192 Quoted \u2192 Confirmed \u2192 Shipped \u2192 Done)\n    stage Stage \xB7 identity Order no. \xB7 mark Photo \xB7 party Customer \xB7 amount Total \xB7 level (none \u2014 no field declares "measure") \xB7 when Due\n    record: header (Order no. \xB7 Customer) \xB7 band (Total \xB7 Shipped against Lines \xB7 Due counting down) \xB7 progress: Stage (5 stages) \xB7 facts (Ship to \xB7 \u2026 2 filed) \xB7 files: Photos \xB7 documents: Papers (Kind: 4 required) \xB7 itinerary: Order lines by Ship by at Window, kind Handling, ref Waybill (Product \xB7 Quantity \xB7 Line total) \xB7 related: Visits (count via Order)\n```\n\nThe ORDER of that line is the record\'s own, top to bottom, and it is the KIND\'s,\nand every entry of it is a section of the one column. `related:` is the counted\nline that closes it \u2014 a register the record never acts on, named and counted \u2014\nand `\u2026 N filed` is how many facts fold behind the grid\'s one link.\nA child register whose `amount` is `signed_by` a direction is a BOOK of movements\n\u2014 what the record came to rather than what it is made of \u2014 so it closes the\ncolumn rather than standing among the rows the job is made of.\n\n**A section over a child is named by the CHILD\'s own label**, because the reader\nalready knows which record they are on: "\u0110\u01A1n h\xE0ng", not "\u0110\u01A1n h\xE0ng \u2014 Kh\xE1ch h\xE0ng".\nWhere two links from one entity reach this record, that label names two sections\nand each takes its own link\'s label as a qualifier \u2014 `H\u1ED3 s\u01A1 (\u0110\u01A1n h\xE0ng)` and\n`H\u1ED3 s\u01A1 (\u0110\u01A1n g\u1ED1c)`.\n\nIn that line `documents:` is a `RecordExpectedSet`, and `lines:` a `RecordChildren` over the rows\nthis record owns \u2014 `history:` where they NAME it instead, as their `party` or their `identity`, capped at its latest 5\nwhere the record is a profile (`latest 5 of N by <day>`, the whole of them behind the foot); a required set\nwhose entries are a CHILD entity carrying files takes `kind="files"`, and the entity\'s own\nmulti-select takes `kind="items"`, since nothing attaches to an option.\n\n**A section that knows its size says so.** Where a `measure` on the record is a\n`count` rollup over the very link a rows section hangs on, the limit it is read\n`against` is how many rows that section is OWED: the printout adds `\u2014 expects\n<limit>` and the screen draws that many ghost rows until the first one lands,\ninstead of "nothing here" two bands under a count saying three are outstanding.\n\nA figure printed as `Total (USD)` is MONEY in the currency named \u2014 a `formula`\nstates it in `formula.currency`, and a `rollup` or a `lookup` inherits it from the\nfield it reads, so read those brackets: a rate that should be in dollars and is\nprinted bare will be drawn in the workspace\'s own money. Where the entity carries\na `currency` role, the ROW\'s code outranks the field\'s on every line that states\none, and a line stating none falls back to the field\'s.\n\n**A record surface can be OPERATED, and that is the default.** Every screen with\na record gets a workflow that writes its editable facts \u2014 every field a person\nstates \u2014 so the record\'s values are edited in place and its stage is advanced\nfrom the progress section. `"writes": false` makes one screen a reader: use it\nfor a screen over rows another desk owns, never as the default. A desk nobody\ncan act on is a viewer of state somebody must go and set somewhere else. A\nreader keeps the acts that only READ the row \u2014 its papers and its `export` \u2014\nand refuses every one that writes it: the quick column, the agent act, the\nhand-off on any surface, and the file an `import` would mint rows from.\n\n**`"writes": "children"` splits the record from the rows under it.** The record\nis drawn exactly as `false` draws it \u2014 the same refusals, and the register opens\nno row of its own \u2014 while every section listing the rows that record OWNS keeps\nits Add, its drawer and its own editor. Use it where one desk states the plan\nand another logs against it: the hours typed under a period the office set, the\nitems ticked under a job somebody else opened.\n\n**`"writes": "record"` is the mirror.** The record keeps every editor, its ladder,\nits files, its quick column and its acts, and the register opens rows of its\nown; every section listing the rows that record OWNS is drawn at rest \u2014 no Add,\nno drawer that saves, no composer. Use it on the desk that decides the plan and\nreads what other desks log under it. `lotics app check` refuses a child create\nor a child editor under it, and the app\'s `package.json#lotics.writes` is seeded\nwithout the child tables.\n\n**Which facts those are is the FIELD\'s answer.** Text, number, date, yes/no and\nselect are typed or picked. A `"cardinality": "one"` link is RE-POINTED, through\na picker over the target entity named by its `display_field_aliases` \u2014 else the\ntarget\'s `identity` \u2014 narrowed by what the reader types and carrying that\nentity\'s own `read_scope`, so a link the plan gives neither column is read\ninstead of offering an empty list. A files field is ATTACHED TO and DETACHED\nFROM, as the delta rather than the pile, so two readers filing at once each keep\ntheir file. A link naming SEVERAL rows is written the same way \u2014 the generated\neditor takes the rows added and the rows taken off, never the list \u2014 so two\nreaders adding at once each keep theirs. An `autonumber` and every computed\nfield are read: they are the platform\'s to write.\n\n**A one-link is that fact WHATEVER its sync.** `sync_both_ways` is one relation\nwith a field on each side, and the sides are not the same surface: the record\nthat names ONE row states it as a fact, and the MANY side is the register on the\nother entity\'s record. Declaring both directions does not give this record a\nregister of the single row its own fact already names.\n\n**The write is the record SURFACE\'s.** Its inputs are the fields that surface\noffers to save \u2014 the facts with an editor, the lifecycle its ladder advances, a\nfiles section over a stated field, and what the BAND states rather than\nreads: its countdown\'s date, and the limit under a meter where that limit is a\ncolumn a person types \u2014 never every field a person could in principle type. What\nthe header states, a limit a level folds into a meter among the FACTS, a required\nset with a section of its own and the pile a page\'s mark draws are read there, so\nno input is declared for them. A second screen over the same entity draws no\nsurface of its own and adds nothing.\n\nWhere two operable screens of one plan reach the same entity, `scaffold check`\nnames them and the apps they belong to: two desks writing one record is a\ndecision, and the split is stated on the FIELD in each app\'s\n`package.json#lotics.writes` rather than left to whoever edits second.\n\nThat workflow lands in the app as source, like every other: its body in\n`src/workflows/update_<entity>.ts` and its declaration in\n`package.json#lotics.workflows`. The two together are the binding \u2014 `lotics app\ndeploy` pushes whatever differs from what it last saw live \u2014 so the write is\nversion-controlled and travels with the app rather than being bound by hand\nafterwards.\n\nA `custom` screen declares its slots under `roles` (slot \u2192 role) and they bind\nthe same way:\n\n```jsonc\n{ "alias": "readings", "label": "Readings", "shape": "custom", "entity": "reading",\n  "roles": { "subject": "identity", "reading": "measure" } }\n```\n\n## Applying packages\n\n`apply` copies published packages into the workspace AFTER the model\'s own\ntables exist \u2014 apps over the tables you just described, and any tables of their\nown they still need. Ordered, and run by `lotics setup` and `lotics scaffold\napply` alike.\n\n```jsonc\n"apply": [\n  {\n    "package": "apg_k3nf82ldpq",\n    "bind": {                              // optional \u2014 which of YOUR tables each entity is\n      "company": { "label": "Customers", "fields": { "name": "Company name" } }\n    },\n    "no_sample_data": true                 // optional\n  }\n]\n```\n\n`bind` is keyed by the package\'s entity alias and holds the LABELS this\nworkspace uses: scaffold adopts by label, so binding points the package at the\ntables the model created instead of a second set beside them. Only naming\nmoves \u2014 a bound field must be the TYPE the package declares, or the copy is\nrefused. `lotics library list` is the shelf, and `lotics library show <apg_id>`\nlists the aliases to bind.\n\nEntries run in the order they are written, because a later one may bind onto a\ntable an earlier one created. **A refused entry stops the run and the entries\nbefore it stay** \u2014 they are separate copies, committed as they land, so the\nrefusal names them rather than leaving a caller to re-run the file and copy them\ntwice.\n\n### What a run remembers\n\nThe WORKSPACE remembers what each entity, field, select option, role and\ntemplate alias became here, plus which record each first row landed on and the\nfile each document path was uploaded as. The model file itself holds no live id\n\u2014 it is the portable half, and the same file applies to a demo workspace and to\na customer\'s \u2014 so the join lives where the things it names live, and one model\napplied to two workspaces holds two bindings that know nothing of each other.\n\nIt is the workspace\'s and not the file\'s because a model file is never\ncommitted: memory kept beside it is one author\'s disk, absent for a teammate, on\na second machine or after a delete \u2014 and every one of those goes quietly back to\nbinding by label, which is what grows the second table.\n\nEvery later verb binds through it: `apply`, `diff`, `app create --from`,\n`app regenerate --from` and `workspace build` take the remembered id first and\nfall back to a label only for an alias nothing has bound \u2014 a field you have just\nadded, or a workspace nothing has applied this model to. That is what makes a\nrelabel on EITHER side a rename rather than one thing the workspace lacks and\none the model lacks: `diff` prints one line under the alias\n(`order.state: label: model "Stage" \xB7 workspace "Giai \u0111o\u1EA1n"`), and `apply` binds\nthe thing it has always meant, reports the move and names the command that makes\nthe two agree \u2014 which side is right is yours to decide, not a reason to refuse\nthe run.\n\nA bound target the workspace no longer holds IS a refusal, by name: re-binding\nto whatever carries that label today is how the model comes to point at\nsomebody else\'s table. `lotics run restore_table` puts a deleted table back, and\n`lotics scaffold unbind <kind> <alias>` forgets the binding \u2014 after which the\nnext apply creates a new one and nothing joins it to what was there.\n\n## Presets\n\nA preset is a trade\'s model, published to be READ. An assistant reads it, asks\nat most two questions, picks a variant and writes a `model.json` from it \u2014\nnothing is copied, and a preset is a file rather than anything a workspace\ninstalls.\n\n```jsonc\n"preset": {\n  "name": "Field service",\n  "description": "Jobs, the crew that runs them, and what each one billed.",\n  "questions": ["Do you dispatch crews, or one person per job?"],  // at most 2\n  "variants": {\n    "crews": {\n      "when": "work is dispatched to crews rather than to one person",\n      "entities": [ /* tables this branch ADDS */ ],\n      "fields": { "job": [ /* fields this branch ADDS to `job` */ ] }\n    }\n  }\n}\n```\n\nVariants are **additive only**: a branch adds entities and fields and never\nremoves them, so the base is a model in its own right rather than a draft.\n`lotics scaffold check` proves the base AND every variant merged onto it, so a\npreset ships with every branch already proven \u2014 the branch nobody took is the\none that fails in the workspace of whoever takes it.\n\n`preset` is not scaffolded. `lotics setup` and `lotics scaffold apply` ignore\nit and create the base model\'s tables.\n\n`lotics scaffold export` prints a workspace that already works as one of these\nfiles \u2014 the starting point for a preset or for another business\'s model, never a\nsource of truth: it carries one business\'s words and stops describing that\nworkspace the moment either changes.\n\n## Starting from a preset\n\n`lotics library list` is the shelf of them and `lotics library show <slug>`\nprints one whole: its questions, every table as `alias \xB7 label` with each field\nas `alias:type`, and each variant as `slug \xB7 when` followed by the tables and\nfields that branch adds. When one of them is the trade in front of you, do not\ntranscribe it \u2014 name it:\n\n```jsonc\n{\n  "from": "field_service",\n  "variants": ["crews"],\n  "rename": { "job": { "label": "\u0110\u01A1n h\xE0ng", "fields": { "code": "M\xE3 \u0111\u01A1n" } } },\n  "entities": [ /* a table this business has that the preset does not */ ],\n  "rows": { "job": [ { "ref": "j1", "fields": { "code": "J-1" } } ] },\n  "field_roles": { "job": { "code": "identity" } },\n  "write_rules": { "customer": { "natural_key": ["email"] } },\n  "apps": [ /* the screens this business\'s apps will have */ ]\n}\n```\n\n- **`from`** is the preset\'s SLUG \u2014 its own file name, a lowercase slug. Naming\n  it is what makes `entities` optional; every other rule on this page is\n  unchanged, because the file is resolved into the full form and then checked and\n  applied exactly as one. A slug nothing serves is refused with the ones there\n  are, never resolved against something else.\n- **`variants`** names the branches to merge onto the base, in order. Pick the\n  one whose `when` describes what the person said; a slug the preset does not\n  declare is refused rather than ignored.\n- **`rename`** is keyed by the preset\'s entity alias and holds the labels this\n  business uses \u2014 the same shape `apply[].bind` takes, and the same rule: only\n  naming moves. An alias the preset does not declare, and a label that is\n  already another table\'s, are both refused.\n- **`entities`** are added after the rename, already in this business\'s own\n  words.\n- **`rows`**, **`field_roles`**, **`write_rules`**, **`apps`** and **`apply`**\n  mean exactly what they mean in the full form \u2014 `"rows"` are this business\'s\n  real first records,\n  `"field_roles"` may name the preset\'s fields as well as its own (a role the\n  preset declares itself is kept unless this file names the same field, or\n  clears it with `null`), `"write_rules"` the create-time clauses on either\n  (an entity this file names replaces the preset\'s whole entry for it),\n  `"apps"` the screens it will have (a preset carries none), `"apply"` the\n  packages copied in once its tables exist.\n\nThis is the ONE thing on this page that needs the network: `check` reads the\npreset it names, once. Everything after that read is the same offline check.\n\nWrite the full form when no preset is the trade.\n\n## A complete model\n\n```json\n{\n  "entities": [\n    {\n      "alias": "customer",\n      "label": "Customers",\n      "singular": "Customer",\n      "fields": [\n        { "alias": "name", "label": "Name", "type": "text", "required": true },\n        {\n          "alias": "tier",\n          "label": "Tier",\n          "type": "select",\n          "options": [\n            { "alias": "standard", "label": "Standard", "color": "slate" },\n            { "alias": "gold", "label": "Gold", "color": "amber" }\n          ],\n          "default": ["standard"]\n        },\n        {\n          "alias": "orders",\n          "label": "Orders",\n          "type": "select_record_link",\n          "target_entity": "order",\n          "cardinality": "many",\n          "sync_both_ways": true,\n          "paired_field_alias": "customer",\n          "display_field_aliases": ["code"]\n        },\n        {\n          "alias": "total_ordered",\n          "label": "Total ordered",\n          "type": "rollup",\n          "source_field_alias": "orders",\n          "aggregate_option": { "operation": "sum", "field_key": "amount" }\n        }\n      ],\n      "views": [\n        {\n          "alias": "gold",\n          "label": "Gold customers",\n          "filters": {\n            "node_type": "condition",\n            "type": "select",\n            "field_key": "tier",\n            "operator": "has_any_of",\n            "value": ["gold"]\n          },\n          "sort": [{ "field_key": "name", "order": "asc" }]\n        }\n      ]\n    },\n    {\n      "alias": "order",\n      "label": "Orders",\n      "singular": "Order",\n      "fields": [\n        { "alias": "code", "label": "Order no.", "type": "text", "unique": true },\n        { "alias": "placed_on", "label": "Placed on", "type": "date", "format": "date" },\n        {\n          "alias": "amount",\n          "label": "Amount",\n          "type": "number",\n          "format": "currency",\n          "currency": "VND"\n        },\n        {\n          "alias": "total",\n          "label": "Total with VAT",\n          "type": "formula",\n          "formula": { "expression": "{amount} * 1.1", "format": "currency", "currency": "VND" }\n        },\n        {\n          "alias": "customer",\n          "label": "Customer",\n          "type": "select_record_link",\n          "target_entity": "customer",\n          "cardinality": "one",\n          "sync_both_ways": true,\n          "paired_field_alias": "orders",\n          "display_field_aliases": ["name"]\n        }\n      ]\n    }\n  ],\n  "roles": [{ "alias": "sales", "label": "Sales" }],\n  "field_roles": {\n    "customer": { "name": "identity" },\n    "order": { "code": "identity", "placed_on": "when", "amount": "amount", "customer": "party" }\n  },\n  "apps": [\n    {\n      "alias": "customers",\n      "name": "Customers",\n      "screen": { "alias": "customers", "label": "Customers", "shape": "party_register", "entity": "customer" }\n    },\n    {\n      "alias": "orders",\n      "name": "Orders",\n      "screen": { "alias": "orders", "label": "Orders", "shape": "transaction_ledger", "entity": "order" }\n    }\n  ],\n  "rows": {\n    "customer": [\n      { "ref": "acme", "fields": { "name": "Acme Trading", "tier": "gold" } },\n      { "ref": "bluebird", "fields": { "name": "Bluebird Foods", "tier": "standard" } }\n    ],\n    "order": [\n      {\n        "ref": "so_1001",\n        "fields": {\n          "code": "SO-1001",\n          "placed_on": "@month-start+2",\n          "amount": 4200000,\n          "customer": "customer:acme"\n        }\n      },\n      {\n        "ref": "so_1002",\n        "fields": {\n          "code": "SO-1002",\n          "placed_on": "@today-3",\n          "amount": 1150000,\n          "customer": "customer:bluebird"\n        }\n      }\n    ]\n  }\n}\n```\n\n`lotics scaffold check` on this file reports\n`2 tables, 9 fields, 2 links, 1 view, 1 role, 4 rows, 2 apps`, then\nthe plan:\n\n```\nCustomers\n  Customers \u2014 party register over Customers (2 rows) \xB7 page (default) \xB7 tabs: none (default)\n    identity Name \xB7 mark (none \u2014 no field declares "mark") \xB7 contact (none \u2014 no field declares "contact") \xB7 worth (none \u2014 no field declares "measure") \xB7 risk (none \u2014 no field declares "verdict")\n    presentation: leads with nothing (default), roomy (default) \xB7 above: rows (default)\n    record: header (Name) \xB7 history: Orders (latest 5 (default) of N by Placed on) (Order no. \xB7 Placed on \xB7 Amount (VND)) \xB7 facts (Tier \xB7 Total ordered (VND))\nOrders\n  Orders \u2014 transaction ledger over Orders (2 rows) \xB7 drawer (default) \xB7 tabs: none (default)\n    when Placed on \xB7 amount Amount (VND) \xB7 reference Order no. \xB7 party Customer \xB7 classification (none \u2014 no field declares "lifecycle") \xB7 document (none \u2014 no field declares "expected_set" or "verdict")\n    order: Placed on, newest first (default) \xB7 presentation: leads with the figure (default), roomy (default) \xB7 above: Amount (VND) (default)\n    record: header (Order no. \xB7 Placed on \xB7 Amount (VND)) \xB7 facts (Placed on \xB7 Total with VAT (VND) \xB7 Customer)\n    party: Customers \u2014 opens from Customer (profile: header (Name) \xB7 history: Orders (latest 5 (default) of N by Placed on) (Order no. \xB7 Placed on \xB7 Amount (VND)) \u2014 foot: the whole register, narrowed to this record \xB7 facts (Tier \xB7 Total ordered (VND)))\nWho writes what:\n  Customers (customer, one: Customer): Customers \xB7 written from the rows of Orders: facts\n    Name: required\n  Orders (order, one: Order): Orders\n```\n\nA `party:` line is the record a NAME on a row opens. A party is not a job, so it\ngets no app of its own \u2014 but a clerk reading the orders book presses the\ncustomer and corrects the phone number there, so the app whose rows name a party\ncarries that party\'s own record beside its register\'s. It is printed in the same\ngrammar the `record:` line is, because it is the same kind of surface: a profile,\non a page, its histories capped. Which cells are the door is what `opens from`\nsays \u2014 `the name` where the register\'s subject IS the party.\n\nThe last block is the WRITERS matrix \u2014 one line per record surface the plan\nleaves operable, the word one of its rows is called, and the app whose register\nopens it. Part of the verdict rather than a diagnostic beside it: which desk\nchanges a table is answerable from the plan, and two apps on one line is the\nsplit to state in each of their `package.json#lotics.writes`. A\n`written from the rows of \u2026` clause is the other reach: the party that register\nnames, and what the app can change on it \u2014 counted apart, because several\nregisters naming one account is the model working as designed rather than a\nsplit to declare. A publish desk\'s rows get a clause of their own, because the\npress that withdraws one DELETES it \u2014 the app declares that table in\n`package.json#lotics.deletes`, and `lotics app check` refuses a body that deletes\nfrom a table it does not name. Indented under each entity are the clauses only a\ncreate meets: the cells a row cannot stand without, and what `write_rules` state.\n\nEvery `(none)` is a slot no field fills, and it says WHY: no field declares the\nrole, or several could and the plan named none of them (`(none \u2014 a, b; name\none)`). Read it as the screen a person will see. `above: \u2026 (default)` is the band\nnobody stated \u2014 the shape sums the amount its slot draws, and a plan naming its\nown figures loses the word. Neither\nentity carries a stage, a required set or files, so the rest is facts \u2014 except\nthe sections neither entity declares: the customer\'s `history:` is the orders\nthat name it as their party, and the order\'s `via Orders:` is the customers whose\n`Orders` link names it. **A link is a section, not a fact**, on the side it\npoints AT and on the side that holds it: `Customers.Orders` therefore leaves the\ncustomer\'s facts, because the section below already lists the same relation and\na link fact can only ever show the first of them. Both records state their name\nin the header and nowhere else \u2014 a ledger\'s columns are the date and the figure,\nso `Order no.` is on no column of that list and is still what the drawer behind\na line is called. `Total ordered (VND)` is the rollup inheriting the currency of\nthe column it sums: money is read off the model, never off the field\'s own line.\n';
+var model_reference_default = '# The Lotics workspace model (`model.json`)\n\nOne JSON file describing the tables, fields, options, views, roles and first rows\na workspace starts with. `lotics scaffold check model.json` proves it offline \u2014\nno account, no network. `lotics setup model.json --email you@company.com` creates\nthe account and applies it. `lotics scaffold apply model.json` applies it again,\ninto the workspace the credential names.\n\n**There are two forms of this file.** The full one, below, spells the model out.\nThe `from` one names a published preset and carries only what this business\ndiffers by \u2014 see \xA7 Starting from a preset, and prefer it whenever a preset fits\nthe trade.\n\nApps are PLANNED here and built afterwards: `apps` names each app\'s screens as a\nshape over an entity, checked against the roles `field_roles` gives its fields,\nso the plan is refused before anyone builds a screen (\xA7 Apps and screens). The\nbuilt app lives in the workspace; publishing that workspace as a package is how\nit ships.\n\n## The rules\n\n- **At least one entity, at most 50.** More tables than that is a data model\n  being designed, not scaffolded \u2014 scaffold the rest in a second call.\n- **Adoption is explicit.** `lotics setup` REFUSES an entity whose `label`\n  already names a table in the workspace, naming every colliding label at once.\n  `lotics scaffold apply` adopts those tables and adds the fields, options and\n  views they are missing. Nothing is ever modified or deleted, so applying the\n  same model twice creates nothing the second time.\n- **Adoption is by LABEL, not alias.** Change an entity\'s `label` and the next\n  run asks for a NEW table beside the old one. Renaming a FIELD is\n  `lotics field rename <table> <field> "<new label>" --model <this file>`, which\n  moves the platform, this file and every app bound to it together; deleting is\n  `lotics run delete_table`. Neither goes through the file.\n- **The file\'s own majority is the language.** A model names no locale \u2014 which\n  language it is in is what it mostly says, and `scaffold check` notes the label\n  written the other way. The generated screens read the kit\'s pack, and a\n  generated WRITE cannot: its refusals run on the server, so they are worded in\n  that same majority. Mix the two and the workspace answers in two languages.\n- **`lotics scaffold diff model.json` says where the file and the workspace have\n  come apart**, joined on label, entity then field \u2014 the join adoption itself\n  makes. It exits 1 on any difference, so a model that is about to be published\n  as a preset carries the labels in use rather than the ones it was written with.\n- **Rows land only where every bound table is empty.** One table already holding\n  records and no rows are written anywhere, and the result says\n  `rows_skipped: true`: sample rows landing among a customer\'s real ones cannot\n  be told apart from them.\n- **After the first run the WORKSPACE is the source of truth.** The file is an\n  authoring input, not a mirror \u2014 scaffold never deletes what the file stopped\n  naming.\n- **`lotics scaffold check` decides all of it offline**, and reports every\n  problem in one run rather than the first: an alias that resolves to nothing, a\n  link whose pair is not symmetric, and the rows themselves \u2014 a field the entity\n  does not declare, an option alias the field does not declare, a link naming no\n  row in the file, a `ref` used twice, a date that is not one, a value on a\n  platform-computed field, and a files cell that is neither a relative path\n  beside this file nor a `fil_` id.\n\n## Top level\n\n```jsonc\n{\n  "entities": [ /* the tables */ ],\n  "roles":    [ /* workspace groups to create */ ],    // optional\n  "templates":[ /* inline html / email templates */ ], // optional\n  "rows":     { /* first records, keyed by entity alias */ },  // optional\n  "field_roles": { /* the reporting role each field plays, keyed by entity then field */ }, // optional\n  "write_rules": { /* what a CREATE finds, defaults and refuses, keyed by entity */ }, // optional\n  "apps":     [ /* the screens each app will have, as shapes over entities */ ], // optional\n  "apply":    [ /* published packages to copy in afterwards */ ], // optional\n  "preset":   { /* a trade\'s branches, for a PUBLISHED model */ } // optional\n}\n```\n\nThe other form names a preset instead of restating one:\n\n```jsonc\n{\n  "from":     "field_service",             // the preset this model starts from, by slug\n  "variants": ["crews"],                   // optional \u2014 its branches to merge in, in order\n  "rename":   {                            // optional \u2014 what THIS business calls each table\n    "job": { "label": "\u0110\u01A1n h\xE0ng", "fields": { "code": "M\xE3 \u0111\u01A1n" } }\n  },\n  "entities": [ /* tables the preset does not declare */ ],    // optional\n  "rows":     { /* first records, keyed by entity alias */ },  // optional\n  "field_roles": { /* roles on the preset\'s fields and this business\'s own */ }, // optional\n  "write_rules": { /* create-time clauses on the preset\'s entities and its own */ }, // optional\n  "apps":     [ /* the screens each app will have */ ],        // optional\n  "apply":    [ /* published packages to copy in afterwards */ ] // optional\n}\n```\n\n**A model may not carry** `fixtures`, `knowledge` or `knowledge_expects`, and no\n`excel` / `word` / `pdf-form` template: each of those is content that lives in a\npublished bundle, which a model has none of. `apps` here is a plan of screens,\nnever built code. An unknown top-level key is an error, never ignored.\n\n### Aliases\n\nEvery `alias` is a lowercase slug \u2014 a letter, then letters, digits and\nunderscores (`unit_price`, `so_1001`). Aliases are how the file cross-references\nitself; they are never shown to anyone. `label` is what a person sees.\n\nLabels must be unique within their namespace \u2014 two entities, two fields on one\nentity, two options on one field, two views on one entity, two roles or two\ntemplates cannot share a label, because scaffold matches by label.\n\n## Entity\n\n```jsonc\n{\n  "alias": "order",\n  "label": "Orders",            // the table\'s name, which names the SET it holds\n  "singular": "Order",          // optional \u2014 ONE of them, for the act that opens one\n  "description": "\u2026",           // optional\n  "writes": false,              // optional \u2014 only the workspace\'s automations write these rows\n  "fields": [ /* at least one */ ],\n  "views":  [ /* optional; an entity with none still gets the default grid */ ],\n  "read_scope": { /* optional; absent, everyone with access to the table reads every row */\n    "any": [\n      { "member_of": "sales" },                       // a role alias this model declares\n      { "field": "scope", "is": ["shared"] },         // a single select on this entity, by option alias\n      { "field": "assignee", "is": "self" }           // a select_member on this entity \u2014 the members it names\n    ]\n  },\n  "unique": [["bed", "sown_on"]] // optional \u2014 sets of fields no two live rows share\n}\n```\n\n**`unique` is a set of values no two live rows share.** Each entry names fields\nof this entity holding ONE value \u2014 text, number, date, a single select, a link\nof cardinality `"one"` \u2014 and a create or update landing a second row with the\nsame values is refused. A set of one text field is that field\'s own `unique:\ntrue`, so it is refused here. A create carries each set in the names its panel\nsends, so the panel can name the duplicate before the write does, and `scaffold\ncheck` prints it under *Who writes what* as `unique: Bed + Sown on`.\n\n**`singular` is what a create says.** A register\'s own act and the panel it\nopens name the row being made \u2014 `New Order`, `H\u1ED3 s\u01A1 m\u1EDBi` \u2014 while `label` names\nthe table, so without it the button reads `New Orders`. Nothing derives it\n(English plurals are irregular), and most models need none: a Vietnamese noun is\nthe same word either way. `scaffold check` prints it beside the table under *Who\nwrites what* and NOTES a table that will name the set. An act on a child section\nkeeps the label: it adds a line to the register under the record the reader is\nalready standing in.\n\n**`writes: false` says only the workspace\'s automations write these rows** \u2014 a\nlog of what the system sent, a copy of what another system holds. No app opens,\nedits or files one: a record listing them keeps the section and opens each row\nat rest, with no Add; a screen over the entity operates at most the rows its\nrecord owns; a party of it is picked, never found or minted; and the generator\nwrites no create, no update and no `lotics.writes` entry for it. `scaffold\ncheck` prints it under *Who writes what* as `written by automations` and never\nnotes it as created nowhere. A `lifecycle` on it is refused \u2014 a row walked\nthrough stages is worked by a person \u2014 and so is a publish desk over it. Absent,\npeople write the rows; `true` is not a value.\n\n**`read_scope` is a ROW rule, enforced by the platform.** A row is readable when\nANY clause holds: the reader is in that role\'s group, the named select carries\none of those options, or the named `select_member` column names the reader\n(`"is": "self"`, on a column of one member or several). It is resolved at\nscaffold into the table\'s own row filters, so an app, a workflow reading for a\nviewer, and the API all answer the same rows \u2014 a per-record visibility field the\napp merely honours is a convention, not a gate. `any` may not be empty (a rule\nnobody satisfies hides the table), and every role alias and option alias in it\nmust be one this model declares. Scaffold writes the rule onto a table it\nCREATES; a table it adopted that ALREADY CARRIES a rule keeps that one, because\nthe rule is the workspace\'s own statement about its rows \u2014 and a run whose model\nstates a different rule reports the entity rather than leaving the claim silent.\n\n**An app may state that its sharing is its read gate: `"reads": "shared"`.** An\napp reads as its owner, so the rule reaches a viewer only as the predicate every\nquery and editor guard of every app over the entity carries \u2014 right for a desk of\none\'s own rows, wrong for a desk whose audience its sharing already decides, where\nwidening the rule meant a role group nobody remembers to fill. Stated on an APP,\nits queries, pickers and guards carry no entity\'s rule and whoever the app is\nshared with reads and writes every row it draws; every other app and the table\'s\nown filters keep the rule. Share it deliberately. Refused on an app none of whose\ntables states a `read_scope`; `scaffold check` prints it on the app\'s line and\nnames the app beside the rule it is exempt from.\n\n**The rows under a private record INHERIT its rule.** An entity that states no\n`read_scope` and hangs under one that does \u2014 through its `parent` link, over one\nhop or several \u2014 is read by the ancestor\'s rule, answered through that link, on\nits table\'s own filters and in every query and guard alike; nothing is restated,\nso a child needs none of the ancestor\'s columns. Stating a rule on the child\nkeeps that one instead, an ancestor with no rule passes nothing down, and a row\nhanging further under the scoped one than a row filter reaches is refused by\nname \u2014 state a rule on it. So is a hop over a link that names more than one row:\nthe rule would admit a reader any one of them admits while the editor\'s guard\nreads the first, so give the link `"cardinality": "one"` or state a rule on the\nchild.\n\n**ONLY the `parent` role is walked.** A register a scoped record reaches by any\nother link \u2014 the rows that NAME it \u2014 is read by that record\'s id with no rule\ntravelling to it, so it is refused until it states one of its own.\n\n## Field\n\nEvery field carries `alias`, `label`, an optional `description`, and an optional\n`required` \u2014 the table refuses a new row that leaves it empty, and an edit that\nclears it. So every row in `rows` states each required field it carries (a\ndefault is not applied to them), and a required LINK is written with its row:\nthe entity it names is created first, and entities whose required links name\neach other are refused, since none of their rows could ever be created. `label`\nmay not contain `{` or `}` (formulas reference fields by label at the platform\nlevel).\n\n`default` is the value pre-filled into a NEW record. It applies on create only;\nexisting records are never backfilled. Only the types listed below accept one.\n\n### `text`\n\n```jsonc\n{ "alias": "name", "label": "Name", "type": "text",\n  "unique": false,              // optional \u2014 require distinct values\n  "format": "text",             // optional \u2014 "text" | "link" | "markdown"\n  "default": "" }               // optional\n```\n\n### `number`\n\n```jsonc\n{ "alias": "amount", "label": "Amount", "type": "number",\n  "format": "currency",         // optional \u2014 "number" | "currency" | "percentage"\n  "currency": "VND",            // optional \u2014 ISO 4217\n  "default": 0 }                // optional\n```\n\n`format` is what the number IS, and every surface reads it: `currency` prints as\nmoney in the code the row or the field states, `percentage` as a whole percent\nwith its sign. An ABSENT number is drawn absent \u2014 the one exception is a\n`sum` or count rollup the plan reads as a **`measure`**: that is the thing\naccumulated toward a bound, so nothing accumulated yet is zero and the meter\ndraws it. The same rollup read as an `amount` keeps its blank, and so does every\nother role: nothing added to what a row is WORTH means unpriced, not free. A\n`min`, an `avg`, a percentage of nothing and every FORMULA stay blank in any\nrole, because none of them has an answer to give. This is why the pair on one\nscreen reads two ways \u2014 what has come in against what is owed \u2014 and why a\nmeasure\'s own LIMIT, an amount, leaves an unquoted row out of the count rather\nthan reporting it as nothing collected. **AND WHERE THAT LIMIT IS ABSENT \u2014 OR\nZERO \u2014 THERE IS NO LEVEL AT ALL**: a level is a reading AGAINST a bound, so a row\nthat states no bound, or a bound of nothing, draws nothing \u2014 cell, fact and all \u2014\nrather than a numerator whose whole meaning was the comparison. "Collected 0"\nbeside a blank total reads as money against a job worth nothing, and "0 of 0"\nagainst a count of nothing owed claims a comparison nobody can make. A measure the model gives no limit is a plain figure\nand is unaffected. A share is stored in percent units \u2014 68.1 is 68.1 % \u2014 and the\ncolumn, the fact behind it, the meter it is judged by and the figure over the\nregister all say so.\n\n### `date`\n\n```jsonc\n{ "alias": "placed_on", "label": "Placed on", "type": "date",\n  "format": "date",             // optional \u2014 "date" | "datetime" | "date_range" | "datetime_range"\n  "timezone": "Asia/Ho_Chi_Minh",  // optional \u2014 IANA name\n  "derive_from": "created_at",  // optional \u2014 "created_at" | "updated_at"; makes the field read-only\n  "default": "2026-01-01" }     // optional; refused together with derive_from\n```\n\n### `boolean`\n\n```jsonc\n{ "alias": "paid", "label": "Paid", "type": "boolean", "default": false }\n```\n\n### `select`\n\n```jsonc\n{ "alias": "tier", "label": "Tier", "type": "select",\n  "options": [                                     // at least one\n    { "alias": "standard", "label": "Standard", "color": "slate" },\n    { "alias": "gold",     "label": "Gold",     "color": "amber" }\n  ],\n  "multi": false,               // optional\n  "default": ["standard"] }     // optional \u2014 option ALIASES; one unless multi\n```\n\n`color` is one of: `red`, `orange`, `amber`, `yellow`, `lime`, `green`,\n`emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`,\n`fuchsia`, `pink`, `rose`, `slate`, `gray`, `zinc`, `neutral`, `stone`.\n\n### `select_member`\n\nA person picker over the workspace\'s members. No default: a model cannot name\nmembers of a workspace that does not exist yet.\n\n```jsonc\n{ "alias": "owner", "label": "Owner", "type": "select_member", "multi": false }\n```\n\n### `select_record_link`\n\n```jsonc\n{ "alias": "customer", "label": "Customer", "type": "select_record_link",\n  "target_entity": "customer",        // an entity alias this model declares\n  "cardinality": "one",               // optional \u2014 "one" | "many" (default "many")\n  "sync_both_ways": true,             // optional \u2014 keep a paired field on the target\n  "paired_field_alias": "orders",     // the partner field ON THE TARGET entity\n  "display_field_aliases": ["name"] } // optional \u2014 what the link shows / the picker\'s columns\n```\n\nA two-way link is declared on BOTH sides, each naming the other as its\n`paired_field_alias`; the pair must be symmetric or the model is refused.\n\n**A single-valued link needs no partner.** `"cardinality": "one"` on its own is a\nlink that holds one row \u2014 one customer on an invoice, one project on a device \u2014\nand nothing is created on the target. The mirror invariant belongs to a PAIRED\nlink: pair a link when the target\'s own record should list what points at it, and\nleave it unpaired when it should not. Either way the record plan draws the\nrelation as a section on the side it points at, so an unpaired link costs the\ntarget nothing.\n\n### `files`\n\n```jsonc\n{ "alias": "attachments", "label": "Attachments", "type": "files" }\n```\n\n### `formula`\n\n```jsonc\n{ "alias": "total", "label": "Total", "type": "formula",\n  "formula": {\n    "expression": "{amount} * 1.1",  // fields on THIS entity, by alias, in braces\n    "output_type": "number",         // optional \u2014 what it YIELDS: "number" | "text" | "date" | "datetime" | "boolean"\n    "format": "currency",            // optional \u2014 how that result is DRAWN: "number" | "currency" | "percentage" | "link"\n    "currency": "VND"                // optional\n  } }\n```\n\n**A select reaches a formula as the KEYS of its chosen options**, a list \u2014\nnever their labels, and never their aliases \u2014 and a model has no keys: the\nworkspace mints them when the table is made. So an option is named in a formula\nas `{field:option}`, both aliases, and the copy writes that option\'s key in its\nplace: `includes({kind}, {kind:crate})` for a select holding one or several,\n`{kind}[0] == {kind:crate}` for a single one. A select compared to its own words\n(`{kind} != "Crate"`) matches no row and computes the other branch everywhere,\nso `check` refuses it and names the token. A select looked up from another\nentity is tested there, in a formula of its own, and that result looked up.\n\n`output_type` is what the expression answers WITH; `format` is how it is printed.\nThe platform infers the result at write time and ignores what you declare, so\nthis is a statement the offline checks read \u2014 which is what lets a role or a\nscreen clause accept a computed value: a caption over a derived name\n(`output_type: "text"`), a period over a settled date (`"date"`). A formula\ndeclaring neither says nothing about its result, and every rule that needs one\nrefuses it by name. `lotics scaffold export` writes the result a live workspace\ncomputed, so exporting a workspace fills these in.\n\n### `rollup`\n\nAggregates the records reached through a link on this entity.\n\n```jsonc\n{ "alias": "total_ordered", "label": "Total ordered", "type": "rollup",\n  "source_field_alias": "orders",    // a select_record_link field on THIS entity\n  "aggregate_option": {\n    "operation": "sum",              // count | sum | avg | median | min | max | range |\n                                     // empty | filled | percent_empty | percent_filled |\n                                     // unique | percent_unique |\n                                     // earliest | latest | date_range |\n                                     // checked | unchecked | percent_checked |\n                                     // percent_unchecked\n    "field_key": "amount"            // a field ALIAS on the linked entity ("count" may omit it)\n  },\n  "filter": { /* optional \u2014 see Views; every field_key is an alias on the LINKED entity */ } }\n```\n\nThe operation must be one the aggregated field\'s type allows \u2014 `sum` over a\nnumber, `earliest` over a date, `filled` over anything.\n\n### `lookup`\n\nDisplays a field from the linked records.\n\n```jsonc\n{ "alias": "customer_tier", "label": "Customer tier", "type": "lookup",\n  "source_field_alias": "customer",  // a select_record_link field on THIS entity\n  "lookup_field_alias": "tier",      // a field alias on the linked entity\n  "order_by": { "field_key": "placed_on", "direction": "desc" } }  // optional \u2014 pick the single extreme row\n```\n\n### `autonumber`\n\n```jsonc\n{ "alias": "seq", "label": "No.", "type": "autonumber",\n  "prefix": "SO-",     // optional \u2014 ignored when template is set\n  "padding": 4,        // optional \u2014 1..20, zero-pads the integer\n  "template": "SO-{YEAR}-{N:4}" }  // optional \u2014 {N}, {N:W}, {YEAR}, {YEAR:2}, {MONTH}, {DAY}\n```\n\n## Views\n\nSaved views live under the entity they belong to. Every field reference is a\nfield ALIAS on that entity.\n\n```jsonc\n{\n  "alias": "gold",\n  "label": "Gold customers",\n  "description": "\u2026",                       // optional\n  "columns": [                              // optional \u2014 omit to show every field\n    { "field_alias": "name", "visibility": "visible", "width": 240 },\n    { "field_alias": "tier", "visibility": "hidden" }\n  ],\n  "filters": {                              // optional\n    "node_type": "group",\n    "logic": "and",                         // "and" | "or"\n    "children": [\n      { "node_type": "condition", "type": "select", "field_key": "tier",\n        "operator": "has_any_of", "value": ["gold"] }\n    ]\n  },\n  "sort": [ { "field_key": "name", "order": "asc" } ],  // optional; order is "asc" | "desc" | null\n  "summary": { "amount": "sum" },           // optional \u2014 field alias \u2192 footer operation\n  "frozen_columns": 1                       // optional\n}\n```\n\nA condition\'s `type` is the field\'s type and its `operator` is one that type\nadmits \u2014 `has_any_of` / `has_none_of` / `has_all_of` / `is_empty` /\n`is_not_empty` for a select, `equals` / `greater_than` / `less_than` for a\nnumber, `on` / `before` / `after` / `between` for a date, `contains` /\n`is_any_of` for text. A select condition\'s `value` names option ALIASES.\n\n`columns`, when present, is exhaustive and must not be empty: a view renders\nexactly the entries it holds. Omit the key to show every field.\n\n## Roles\n\nA role becomes a workspace group. Members are added afterwards, in the app.\n\n```jsonc\n{ "alias": "sales", "label": "Sales" }\n```\n\n## Templates\n\nOnly inline `html` and `email` templates \u2014 the rest are file-backed and a model\nhas no bytes. An `html` template renders to a PDF when a workflow generates\nfrom it; `{{name}}` is filled from the workflow\'s data.\n\n```jsonc\n{ "alias": "order_ack", "label": "Order acknowledgement", "type": "email",\n  "content": "<p>Hello {{customer}}\u2026</p>" }\n```\n\nA paper that has to look like a counterparty produced it \u2014 an official letter,\nan acceptance minute, a supplier\'s bill \u2014 is the same `html` template with a\nshell around the body: a letterhead, a reference line, a seal and a signature\nblock, and paper grain over everything. One shell, many bodies; the data is the\nonly thing that changes, so a workflow can re-issue it over any record.\n\n```jsonc\n{ "alias": "cong_van", "label": "C\xF4ng v\u0103n", "type": "html",\n  "content": "\u2026the page below, as one JSON string\u2026" }\n```\n\n```html\n<style>\n    .sheet{position:relative;width:718px;padding:44px 58px 30px;background:#fbfaf6;color:#111;font:14.2px/1.5 \'Liberation Serif\',serif}\n    .grain{position:absolute;inset:0;opacity:.34;mix-blend-mode:multiply;background:url("data:image/svg+xml;utf8,<svg xmlns=\'http://www.w3.org/2000/svg\' width=\'140\' height=\'140\'><filter id=\'f\'><feTurbulence baseFrequency=\'.9\' numOctaves=\'2\'/><feColorMatrix values=\'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 .35 0\'/></filter><rect width=\'140\' height=\'140\' filter=\'url(%23f)\'/></svg>")}\n    .top{display:flex;text-align:center;font-size:13.4px} .top>div{flex:1} .u{display:inline-block;border-bottom:1px solid #111;font-weight:700}\n    .ref{display:flex;text-align:center;font-size:13.4px;margin-top:6px} .ref>div{flex:1} .ref .r{font-style:italic}\n    h1{text-align:center;font-size:15.6px;margin:26px 0 18px} p{text-align:justify;text-indent:26px;margin:0 0 9px}\n    .sig{display:flex;margin-top:20px} .sig .l{flex:1} .sig .r{width:290px;text-align:center;position:relative}\n    .sig .nm{font-weight:700;margin-top:96px} .seal{position:absolute;left:4px;top:8px;width:166px;height:166px;opacity:.66;mix-blend-mode:multiply;transform:rotate(-17deg)}\n  </style>\n  <div class=\'sheet\'><div class=\'grain\'></div>\n    <div class=\'top\'><div><b>{{issuer_parent}}</b><br><span class=\'u\'>{{issuer}}</span></div>\n      <div><b>C\u1ED8NG H\xD2A X\xC3 H\u1ED8I CH\u1EE6 NGH\u0128A VI\u1EC6T NAM</b><br><span class=\'u\'>\u0110\u1ED9c l\u1EADp - T\u1EF1 do - H\u1EA1nh ph\xFAc</span></div></div>\n    <div class=\'ref\'><div>S\u1ED1: {{number}}</div><div class=\'r\'>{{place}}, ng\xE0y {{day}} th\xE1ng {{month}} n\u0103m {{year}}</div></div>\n    <h1>{{title}}</h1>\n    <p>K\xEDnh g\u1EEDi: {{recipient}}.</p>\n    {{{body}}}\n    <div class=\'sig\'><div class=\'l\'><b>N\u01A1i nh\u1EADn:</b><br>- Nh\u01B0 tr\xEAn;<br>- L\u01B0u VT.</div>\n      <div class=\'r\'><img class=\'seal\' src=\'{{seal_url}}\'><b>{{signer_title}}</b><div class=\'nm\'>{{signer}}</div></div></div>\n  </div>\n```\n\n`lotics preview <file.html>` renders any such page to a PNG the way a demo\'s\nprops are made, sized to its content, so a paper can be looked at before it is\nput in a template.\n\n## Rows\n\nFirst records, keyed by entity alias. Up to 200 rows per entity and 2000 across\nthe model, attaching at most 2000 documents between them \u2014 a real data set\nbelongs in an import, not a model.\n\n```jsonc\n"rows": {\n  "customer": [\n    { "ref": "acme", "fields": { "name": "Acme Trading", "tier": "gold" } }\n  ]\n}\n```\n\n`ref` is a local handle (lowercase letters, digits, underscores) that other rows\'\nlink fields address. It is never persisted.\n\nA `files` cell attaches documents: paths relative to this file (no `..`, never\nabsolute), which `check` proves exist and `apply` uploads into the workspace\nbefore any row is written \u2014 a paperwork business seeds its papers with its\nrows. The server accepts only `fil_` ids of files this workspace owns, which is\nwhat the upload leaves behind. After a run that wrote rows, the WORKSPACE holds\nwhich record each row became, under the row\'s own `<entity>:<ref>`:\n`delete_records` over them is how a seeded set is reset, and applying again\nre-dates it.\n\n`fields` is keyed by field alias, and every value is read against the field\'s\nDECLARED type:\n\n| Field type | Value |\n|---|---|\n| `text` / `number` / `boolean` | the value itself |\n| `date` | `"2026-03-14"`, or a relative expression (below) |\n| `select` | the option ALIAS \u2014 `"gold"`, or `["gold","vip"]` for a multi-select |\n| `select_record_link` | `"<entity-alias>:<ref>"` naming another row in this file \u2014 `"customer:acme"`, or an array for several |\n| `select_member` | `"self"` only \u2014 the person applying the model |\n| `files` | paths beside this file \u2014 `["scans/pccc_letter.png"]` \u2014 uploaded by `apply`/`setup` before the rows are posted; or `fil_` ids of files already in this workspace |\n| `formula`, `rollup`, `lookup`, `autonumber` | not allowed \u2014 the platform writes these |\n\n**Documents can be attached on their own, afterwards.** Rows land only into empty\ntables, so a model whose binaries were added after the first apply has no second\napply to carry them: `lotics scaffold apply model.json --documents` writes ONLY\nthe `files` cells, onto the records the first run created, found by each row\'s\nown `ref` in the binding the workspace holds \u2014 so a row added to or removed from\nthe file since changes nothing about the rest. Running it twice attaches nothing\nthe second time: the same path keeps the same file, and a cell is a set.\n\n### Relative dates\n\nA date cell holds a literal `YYYY-MM-DD`, or an expression relative to the day\nthe model is applied, so a screen that opens on "this month" is not empty a month\nlater:\n\n- `@today` \u2014 the day of the run, in the workspace\'s timezone\n- `@month-start` \u2014 the 1st of that month\n- either with a whole-day offset: `@today-14`, `@month-start+9`\n\n`@month-start` exists because `@today-N` cannot promise a month: applied on the\n2nd, `@today-3` lands in the previous one.\n\n## Field roles\n\n`field_roles` names the reporting role a field plays on its entity \u2014 keyed by\nentity alias, then field alias \u2014 so every screen over the entity agrees on\nwhich column names the row and which select is the stage. A shape\'s slot binds\nto it (\xA7 Apps and screens). Like `rows` and `apps`, it is this file\'s: `check`\nproves it and the workspace never sees it. Each role sits on the types that can\nanswer it:\n\n| Role | On | Meaning |\n|---|---|---|\n| `identity` | `text`, `select_record_link`, `formula` | what a PERSON calls the row \u2014 the register\'s first column; a link where the row is "the product, at this branch"; a formula where the name is computed, and then it may not be `format`ted as a figure. NEVER an autonumber: a minted code is a `reference`. One per entity |\n| `reference` | `text`, `autonumber`, `formula` | the key the SYSTEM files the row under \u2014 an order number, a container code \u2014 drawn as the supporting line under the name rather than as a column of its own, and leading where the entity has no `identity` at all. One per entity |\n| `mark` | `files`, or a `lookup`/`rollup` that resolves to one | the row\'s picture \u2014 its own, or the linked record\'s. NEVER A COLUMN: a register draws words, so a mark is projected only where a surface leads with one \u2014 the subject rung of a picture-led grid, and a record\'s itinerary. A child entity\'s mark reaches a record\'s run and nothing else. One per entity |\n| `lifecycle` | single `select` | the ordered stages a row walks; option order is the order. Which of them END the flow is `outcomes`, which parts of the flow they group into is `phases`, and `history` keeps the day each one was reached. One per entity |\n| `category` | single `select`, or a `lookup` that resolves to one | what the row IS \u2014 a kind, a service, a book. One badge in the field\'s own colour, with no ladder behind it and no flow to advance; `icons` gives each option its glyph. Often a fact about the thing the row books rather than about the row, and then it is the lookup that reads it. Repeats: a row can be of two kinds of thing |\n| `measure` | `number`, `formula`, `rollup` | a level read against a limit \u2014 see `against` and `alert`. Money where the model says so, and then it prints as money |\n| `expected_set` | `select` | its OPTIONS are the required set (documents, checks, services); an option no row has is a gap to show, not nothing. A multi-select draws as a ring and a fraction wherever it is drawn \u2014 absence is the information, and a list of what IS there says nothing about what is missing |\n| `amount` | `number`, `formula`, `rollup` | THE money of a ledger row; `signed_by` says which way it moved, `against` names the reference it is quoted off. One per entity |\n| `when` | `date`, or a `formula`/`rollup`/`lookup` that yields one | the ledger or timeline date \u2014 stated, or derived: the day money MOVED is a formula over the two columns that could hold it. `due` makes it a DEADLINE; without it the date is the plain day it is. `until` names the stage of this entity\'s own `lifecycle` at which the countdown is spent, and says `due` by saying so. `from` names the date the deadline\'s window opens on. One per entity |\n| `slot` | single `select`, or a `datetime` `date` | where in the DAY a row sits \u2014 the run it is read in under its day\'s heading on an itinerary. A select\'s option order IS the run\'s order; a time is ordered by the clock. A plain `date` is refused: that is the day itself. One per entity |\n| `party` | `select_record_link`, `select_member` | WHO THE ROW IS FOR \u2014 the counterparty it was transacted with, or the workspace MEMBER whose work it is (a shift, an assignment, a timesheet period). A member is drawn as the person and opens nothing: they have no record in the app. One per entity \u2014 and left off where the `identity` IS the link to them: the row is then NAMED by that record, and a strip under the title would state them twice |\n| `parent` | `select_record_link` | the record this row belongs to \u2014 a line\'s order, a paper\'s case. The parent\'s record shows these rows; the row shows the parent as a fact. One per entity, and it links to an entity this model declares |\n| `contact` | `text` | a way to reach a party \u2014 an address, a number, the town it is in. The record draws them as ONE row of links under the name, on a page and in a drawer alike, so the role sits on every field that is one of them. A row carrying one is SOMEBODY, so a screen over it may lead with the mark (\xA7 `presentation`). Repeats |\n| `currency` | single `select` whose option LABELS are ISO 4217 codes | the money THIS ROW\'s figures are in. Every amount and every money measure on the entity is then printed per row rather than in one code for the whole column, and the select is not drawn as a fact of its own. One per entity |\n| `verdict` | `boolean`, `formula` | a settled pass/fail \u2014 ticked, or computed. TRUE is the PASSING side wherever it is drawn, a register\'s risk flag included, so a field whose true means trouble is the same fact asked the other way round. One per entity |\n| `obligation` | `date` | a day something is OWED by \u2014 a cut-off, a permit expiry, a payment due. It counts down by definition. `satisfied_by` names what CLOSES it (or `until`, the stage the record stops owing it at), `label` what is owed. Repeats: a row owes several things, and a shape that fans them draws one row each |\n| `expires` | `date`, or a `formula`/`rollup`/`lookup` that yields one | the day something the row HOLDS runs out \u2014 a licence, a certificate, an inspection. Read as a COUNTDOWN, never as the date: the days left while it holds, and a renewal owed once it has passed. `warn` (required) is how many days ahead it starts to need attention, which nothing about a date says. Repeats: a machine carries an inspection and an insurance |\n| `origin` | `text`, single `select`, or a one-row `select_record_link` | where the row STARTS. Declared with a `destination` \u2014 a route has two ends, and one alone is refused \u2014 and then every surface over the entity draws the two as ONE reading, `Warehouse 4 \u2192 Site B`: on the register\'s supporting line after the key, and as one column on the child registers and party histories that list these rows. The two fields are then not facts of their own, and a `columns` clause naming either end is refused. One per entity, holding ONE place |\n| `destination` | `text`, single `select`, or a one-row `select_record_link` | where the row ENDS \u2014 the other half of the `origin`\'s route, and read only with it. One per entity, holding ONE place |\n| `body` | `text` | the words a dated entry SAYS \u2014 the note of a call, the text of a message \u2014 plain or markdown alike: the role makes the row an entry, never the format. Undeclared, a log reads the entity\'s first `markdown` text as the entry. One per entity |\n| `recording` | `files` | the audio or video a dated entry IS the record of \u2014 a call, a site walk, a lesson \u2014 played wherever it is read, on the entry and on the record it opens, never listed among its papers: a log\'s attachments are then its first OTHER pile. One per entity |\n| `verbatim` | `text` | what was literally said or written on a dated entry \u2014 a transcript, a pasted exchange \u2014 drawn behind one disclosure wherever it is read, under the entry\'s words and at the foot of its band on the record, never as the words. Refused on the entry\'s own words (its `body`, else the entity\'s first `markdown` text): declare those as the `body`. One per entity |\n\n**`due` is what makes a `when` a deadline.** A date a row is merely filed by \u2014 the\nday a lead arrived, the day a movement happened \u2014 is neither early nor late,\nhowever long ago it was. Without the clause every desk drew every `when` as a\ncountdown and a two-month-old lead read "40 days overdue" on a record nobody was\nlate on. So a bare `when` is a plain date, and `{ "role": "when", "due": true }`\nis the one that counts down. An `obligation` needs no clause: a day something is\nowed by is a deadline already.\n\n**`until` stops a countdown where the work is DONE.** A deadline counts down so\nsomebody acts on it, and a row that has arrived needs nothing: without the clause\na delivered order is tinted for a date it met, and every settled row past its day\njoins the urgent ones in the reader\'s glance. It names one option of the entity\'s\n`lifecycle`; at that stage, at every stage past it and at every `outcome`, the\ndate is drawn as the plain day it is. On a `when` it also says the date is `due`.\n\n**`from` opens a deadline\'s window.** `{ "role": "when", "due": true, "from":\n"starts_on" }` names the date field on the same entity the window opens on. The\nrecord\'s band then reads the window \u2014 both days and how many are left \u2014 and a\ntarget read against the deadline is paced by how far through the window today\nis. The start leaves the facts and is edited in the band, beside the deadline.\nIt takes a stored `date` a person states on the same entity (never one the\nplatform stamps with `derive_from`), and only on a `when` that counts down.\n\n"One per entity" is one COLUMN, never one value on screen. A second counterparty\nor a second parent stays a ROLELESS `select_record_link`: which field fills a\nslot is the screen\'s answer (\xA7 Apps and screens), and the extra link is a fact on\nthe row with its own section on the record, headed by that link\'s own label. A\nrole naming two fields would move the ambiguity into every shape that reads it.\nThe same holds for a link from an entity to ITSELF \u2014 the row a line sits under in\na breakdown, the same item\'s lines in the periods before: it takes no role, and\nthe clause that reads it names it (`nest`, `depends_on`, the rollup a claim\'s\n`previous` sums over).\n\nA COMPUTED field is admitted where its RESULT is what the role needs, and\nrefused where it is not: `identity` and `reference` need `text`, `when` a `date`,\n`mark` `files`. A formula\'s result is its `output_type`; a rollup\'s and a\nlookup\'s is read through the walk. So a formula yielding a number is refused in a\nname\'s place, a lookup landing on anything but `files` is refused as a `mark`, and\na formula declaring NO result is refused by all four \u2014 naming `output_type` as\nthe remedy, because a value drawn as a type nobody stated is the wrong cell with\nnothing saying so. The result also decides the DEVICE every screen draws the value\nwith: a rollup taking the `latest` of a set of dates is drawn as a date, a lookup\nof a select as the words it holds.\n\nA bare role name is the common form. A role that is read against a SECOND field\ntakes the object form:\n\n- **`measure`** names its limit: `against` \u2014 a constant, or a field on the same\n  entity the row states as a number (a `number`, or a formula or rollup whose\n  result is one) \u2014 and `alert`, which side of it needs attention, `over` a\n  capacity or `under` a minimum. The two come together.\n- **`measure`** names what its number COUNTS, where the unit changes how the row\n  is DRAWN rather than how the figure reads: `counts: "days"` spans a stop across\n  that many days of a run, so a three-night stay fills three of its days instead\n  of only the one it starts on, and `counts: "hours"` is how long a stop takes\n  INSIDE its day, stated beside it. Stated, never inferred \u2014 nothing about a `3`\n  says whether it is nights, pallets or hours, and a quantity drawn across a week\n  is a run nobody can read.\n- **`lifecycle`** names the stages that END the flow: `outcomes`, option aliases\n  of that select. A row in one has ARRIVED \u2014 delivered, cancelled, written off \u2014\n  so a desk draws them apart from the ladder instead of chaining them after each\n  other. Not every option may be an outcome, and terminal-ness belongs here, never\n  written into a stage\'s label.\n- **`lifecycle`** groups its stages into the parts of the flow they belong to:\n  `phases`, each a `label` and the `stages` under it. Nine rungs down one column\n  is a list nobody reads as a flow; the same rungs under three headings are three\n  pieces of work, and which belong together is the business\'s answer. Every stage\n  but an `outcome` falls in exactly one \u2014 a stage in two is drawn twice, a stage\n  in none vanishes off the ladder \u2014 and the outcomes may be placed in a phase or\n  left out, and are then read as a last part of their own.\n- **`lifecycle`** says why a row took an outcome: `reasons`, an outcome\'s alias \u2192\n  a text or single select of the entity. The reason is a fact of the ending, so a\n  record offers it only while it stands at that outcome \u2014 on a row still in the\n  flow a tap would record why it ended on a row that has not.\n- **`lifecycle`** keeps every stage the row reached: `history: true`, or\n  `history: "<alias>"` to name the table. A ladder with no history reports where\n  a row IS and nothing about how it got there, which is the whole of what a\n  reader asks a pipeline. It is declared BESIDE `phases`, and refused without\n  them: the rungs a ladder draws are the live select\'s options, which nothing\n  reading a file or an app\'s spec can see, so `phases` is the one statement of\n  what the dates have to cover \u2014 and without it a rung the history cannot reach\n  draws undated on every record with nothing anywhere saying so. The flag is the\n  ONE statement: the model DERIVES a\n  child table from it \u2014 the link back to this record, the stage, the moment it\n  was reached and who moved it \u2014 and `check`, `apply`, `diff` and the app\n  generator all see that table exactly as they see a written one. Nothing else\n  declares it, and a file that also writes it by hand is refused. The generated\n  create stamps the rung the flow opens at and the generated editor stamps every\n  move after it; a stage changed anywhere ELSE is a rung with no date\n  (`docs/platform_gaps.md`). **A first apply backfills nothing** \u2014 `apply` writes\n  rows only into empty tables, and rows that existed before the flag walked their\n  stages before that table existed. The honest backfill is ONE opening row per\n  existing parent, at its FIRST stage, dated when that parent was created (true\n  by construction); the stage it stands on NOW is not dated unless that is also\n  the first. It is a create per parent \u2014 `lotics run create_records` \u2014 and\n  `scaffold apply` prints it as the work it did not do.\n- **`amount`** names the REFERENCE it is read against: `against`, a field on the\n  same entity the row states as a number. A price against the list it is quoted\n  off, a rate against the going one \u2014 and the catalogue item\'s record draws the\n  pair on one axis with the gap said in words. Never a constant (a price typed\n  into the model ages with nothing to update it) and never an `alert`: a limit is\n  a ceiling a row can pass, and beating a reference is the point.\n- **`amount`** names the select that SIGNS it: `signed_by`, a select on the same\n  entity, and `outflow`, the options of that select under which the amount is\n  money going out. Without it every shape over the ledger adds both directions\n  together: a month whose net was small reads as the total of everything that\n  moved, and the trend plots one rising line. The two come together, and\n  `outflow` is some of that select\'s options, never all.\n- **`expected_set`** names what CONDITIONS the set: `required_by`, a field on the\n  same entity, and `options`, which of that field\'s values require which entries.\n  A row whose value is not named requires nothing. Without it the denominator is\n  every option, so a set whose entries are mutually exclusive by kind reads\n  `1 of 4` on every complete row \u2014 a denominator no row can reach is worse than\n  no role. The field is a single `select`, keyed by its option aliases \u2014 or a\n  YES/NO the row answers itself (a `boolean`, or a formula resolving to one),\n  keyed by `"true"` and `"false"`: a check that FAILED owes its consequence \u2014 the\n  photograph, the owner, the day it is due \u2014 and there is no select of the record\n  that says so. `from: "parent"` reads that field off the record these rows hang\n  under instead, through this entity\'s own `parent` link: which documents an order\n  owes is the ORDER\'s type, and the papers carry no column that says it. Which of\n  the two a set takes is the set\'s own shape and not a choice \u2014 a multi-select\n  holds the whole set on one row and is narrowed by that row (`from` omitted), a\n  single select is one entry per row and takes `from: "parent"` \u2014 and the other\n  way round is refused rather than left conditioning nothing.\n- **`category`** names the GLYPH each option wears: `icons`, option alias \u2192 a\n  glyph the kit draws \u2014 a kebab-case name from its curated Lucide set; a name\n  outside it is refused naming the nearest ones. A kind is recognised before it is read, by the\n  same mark wherever it is drawn \u2014 its chip on a row, a filter, an entry of a\n  log \u2014 and a lookup of the category wears the same glyphs, because it holds the\n  same options. Every option names one, or none does: a run of chips where one\n  carries no glyph reads as the one missing something.\n- **`expires`** names its WINDOW: `warn`, the days ahead of the day it runs out\n  that a renewal is started in. A monitored set\'s `level` bound to one draws each\n  unit\'s days left \u2014 tinted inside the window, and read as owed past the day \u2014\n  and `summary.above: "counts"` counts the units inside the window or past it. A\n  formula of days left against a number is the same fact drawn as a meter of\n  1 287 of 60.\n- **`obligation`** names what ENDS it: `satisfied_by`, a `date` or a `files` field\n  on the same entity \u2014 the day it was done, or the paper that proves it \u2014 or,\n  where the business stamps nothing, `until`, the stage of this entity\'s\n  `lifecycle` at which the record stops owing it: a deposit is owed until the\n  order is paid, and nobody records the act of paying twice. One or the other,\n  never neither \u2014 without one every obligation the business ever met stays on the\n  desk. Optionally `label`, what is OWED as the reader says it ("G\u1EEDi SI"), which\n  is not what the column holding the date is called ("SI cut-off").\n\n```jsonc\n"field_roles": {\n  "product": { "name": "identity", "photo": "mark" },\n  "stock":   { "on_hand": { "role": "measure", "against": "minimum", "alert": "under" },\n               "uptime":  { "role": "measure", "against": 80, "alert": "under" } },\n  "order":   { "stage": { "role": "lifecycle", "outcomes": ["delivered", "cancelled"],\n                          // Two pieces of work, and every step dated.\n                          "phases": [{ "label": "Taking it on", "stages": ["placed", "confirmed"] },\n                                     { "label": "Getting it out", "stages": ["picked", "shipped"] }],\n                          "history": true },\n               // A DEADLINE COUNTS DOWN \u2014 `payment.paid_on` below is a plain day.\n               "ship_by": { "role": "when", "due": true },\n               // The day the papers are owed by, and the day they went.\n               "papers_due": { "role": "obligation", "label": "File the papers", "satisfied_by": "papers_sent" },\n               // Nothing stamps a deposit paid \u2014 the order\'s own stage ends it.\n               "deposit_due": { "role": "obligation", "label": "Take the deposit", "until": "delivered" } },\n  // WHICH PAPERS THIS ONE OWES IS THE ORDER\'S OWN TYPE, and no document says it.\n  "document": { "order": "parent",\n                "kind": { "role": "expected_set",\n                          "required_by": { "from": "parent", "field": "kind",\n                                           "options": { "export": ["invoice", "customs"] } } } },\n  // `kind` is the direction select \u2014 options `received` and `paid_out`, no role of its own.\n  // Every figure on a quotation is in the currency that row names.\n  "quote":   { "unit": "currency", "total": "amount" },\n  // What the price is quoted off, so the item\'s page reads one against the other.\n  "service": { "price": { "role": "amount", "against": "list_price" },\n               "kind": { "role": "category", "icons": { "repair": "wrench", "install": "hammer" } } },\n  // The day the money moved is neither early nor late, so it stays a bare `when`.\n  "payment": { "paid_on": "when",\n               "value": { "role": "amount", "signed_by": "kind", "outflow": ["paid_out"] },\n               // A receipt owes a receipt voucher; a payment owes an invoice and a payment voucher.\n               "papers": { "role": "expected_set",\n                           "required_by": { "field": "kind",\n                                            "options": { "received": ["receipt_voucher"],\n                                                         "paid_out": ["invoice", "payment_voucher"] } } } },\n  // A CHECK THAT FAILED OWES ITS CONSEQUENCE \u2014 keyed by the row\'s own answer,\n  // and the answer that owes nothing is omitted rather than named with an empty list.\n  "check":   { "passed": "verdict",\n               "evidence": { "role": "expected_set",\n                             "required_by": { "field": "passed",\n                                              "options": { "false": ["photo", "owner", "due"] } } } }\n}\n```\n\nIn a file that starts from a preset (\xA7 Starting from a preset), `field_roles`\nmay name the preset\'s fields as well as this business\'s own; a role the preset\ndeclares itself is kept unless this file names the same field, and `null`\nclears it.\n\n## Write rules\n\n`write_rules` is what only a CREATE meets \u2014 keyed by entity alias, like\n`field_roles`, and this file\'s in the same way: `check` proves it and the\nworkspace never sees it. An update names one field that moved; a create takes a\ndraft whole, so it has to know which row a name already belongs to, where a\nvalue comes from when nobody types it, and what a figure or a picker may hold.\nThe generator writes one `create_<entity>` workflow and one `New<Entity>Dialog`\nper entity an app can operate, from these clauses and the fields\' own\n`required`.\n\n```jsonc\n"write_rules": {\n  // A customer is RECOGNISED by their address. Where an entity names a customer\n  // as its `party`, the create takes the email instead of a picker, reuses the\n  // row it matches and mints one only where nothing does \u2014 so the book never\n  // grows a second Acme because somebody typed the name differently.\n  "customer": { "natural_key": ["email"] },\n  "order_line": {\n    "fields": {\n      // A line of nothing is not a line. Refused on create and on update, at\n      // the control the figure was typed into.\n      "quantity": { "min": 1, "max": 9999 },\n      // The price is fixed at the moment of ordering \u2014 COPIED off the product,\n      // not looked up for ever after, so the price list moving next week does\n      // not silently reprice an order already placed.\n      "unit_price": { "default_from": "product.price" },\n      // And nothing is sold off an empty shelf. The picker reads only the rows\n      // that answer this, and the write refuses the same rows again \u2014 a caller\n      // who never opened the picker is bound by it too.\n      "product": {\n        "options_where": {\n          "node_type": "group", "logic": "and",\n          "children": [{ "node_type": "condition", "type": "number",\n                         "field_key": "in_stock", "operator": "greater_than", "value": 0 }]\n        }\n      }\n    }\n  }\n}\n```\n\n| Clause | On | Meaning |\n|---|---|---|\n| `natural_key` | the entity | the field aliases a row is recognised by. A `text` key declares `unique: true` on the field itself \u2014 two rows sharing it would make find-or-create pick whichever the read answered first \u2014 and a key is `text` or `number`, because a person types it back |\n| `default_from` | a field | `"<link alias>.<field alias>"` \u2014 the value is copied from the linked row when the row is created, never asked. The link is a one-row link on this entity and `required`, because there has to be a row to read, and the two field types must match |\n| `min` / `max` | a `number` | the figure is refused outside them, on create and on update |\n| `options_where` | a `select_record_link` | an `and` group of plain conditions over the TARGET\'s own fields, each `field_key` a field alias. It narrows the picker\'s read and is refused again where the write lands, so the link is `required` |\n\nA field\'s own `required` is not here: the contract carries it, every write path\nrefuses the row by field name from it, and the generated panel stands its commit\ndown until the same set is filled. `unique` is the text field\'s own clause\n(\xA7 `text`) \u2014 the create says so at the control before the column does.\n\nWhat a create asks is what a person STATES, so an entity stating `writes:\nfalse` (\xA7 Entity) has no create at all. A `default_from` field is not drawn,\na `lifecycle` opens at its first rung, and the stamp an obligation\'s\n`satisfied_by` names is not asked (the row is only now taking that on) \u2014 one\nfact, one place. A field the workspace writes (a formula, a rollup, a lookup, an\nautonumber, a date with `derive_from`) is never an input of a create or an\nupdate, a write in a generated body, or an entry in `lotics.writes`, and its\nrecord fact has no editor. Of the files columns it asks for exactly ONE, the\n`mark`: that pile IS the row, so a register leading with the picture would\notherwise open a faceless row, while every other pile is papers gathered onto a\nrow that exists and a panel asking for all of them is a filing cabinet with a\nSave button. The screen narrows that set where it states a `create` (\xA7 Apps and\nscreens). `scaffold check` prints every clause under its entity in **Who writes\nwhat**.\n\n**The `parent` is prefilled only in the door that mounts the act.** A row opened\nfrom the record it hangs under takes that record from the door it was pressed\nin, so the link is neither asked for nor drawn. The same entity\'s act on its own\nregister has no such row, so there the parent is an ordinary picker the draft\ncannot be committed without \u2014 a payment opened from a money app belongs to a\ncase either way.\n\n## Apps and screens\n\n`apps` is the plan: each app the reader will build, as ONE REGISTER \u2014 a SHAPE\nover an ENTITY \u2014 under `screen`. Nothing here is built by the scaffold: the plan\nis what `lotics scaffold check` prints back, register by register with the field\nin every slot, so it is read and corrected before a screen exists.\n\n**THE PRINTOUT EXPLAINS ITSELF.** Everything the shape and the roles answered by\nthemselves is marked `(default)` \u2014 the door, the tab strip, the band\'s figures,\nwhat the rows lead with, how much room they take, which end the register is read\nfrom, the set a member lens opens on, how many rows a capped history stands at \u2014\nso a clause nobody wrote is never read back as one somebody did. And\n`lotics scaffold check --why` prints the RULE behind every binding and every\nsection, indented under the line it explains: which field filled a slot and what\nit was chosen from, why the record opens where it does, why a child\'s rows are a\nlog rather than a register, why a history is capped and a relation counted.\nEvery sentence is the derivation\'s own, so what the printout explains is what\ngets built.\n\n**THREE THINGS DECIDE EVERY SCREEN AND EVERY RECORD**: the SHAPE, whose slots are\nthe table below; the ROLES the entities declare (\xA7 Field roles), which fill those\nslots and decide what each child\'s rows become; and the CLAUSES, which are where\nthe plan overrides what the two would answer. This index says which is which, so\na clause is reached for only where the first two have no answer.\n\n**What a child\'s rows become.** One section per LINK into the record, and what\nthe CHILD declares decides its kind \u2014 the first line it answers wins.\n\n| Printed as | The child declares | The reader gets |\n|---|---|---|\n| `documents:` | an `expected_set` select, one entry per row | the desk of what is owed, each row\'s files attached to it |\n| `schedule:` | an `obligation` closed by a DATE, on rows with no `lifecycle` of their own | what is planned against time and what slipped \u2014 the ordered stops, the promised day against the day it happened |\n| `log:` | a `body` (else a `markdown` text) and a day, on rows with no `lifecycle` of their own | what happened, in order \u2014 each entry read in full in the words it states, its selects and the parties it was with on its line, its `recording` played under the words and its `verbatim` a disclosure behind them, and a composer that writes the next one, asking what the entry shows. With a `verdict` the rows are a correspondence: read oldest first, the reply marked with it the answer, and whose move it is at the foot; without one, newest first under day heads. An entry the child NAMES (`identity`) opens a record of its own |\n| `itinerary:` | a `when` and a `lifecycle`, on rows a JOB\'s record OWNS | the day heads the run, one stop per row \u2014 its name, its supporting lines, its stage as the status at the right \u2014 and the sum under it |\n| `book:` | an `amount` that is `signed_by` a select, on rows the record owns (`parent`) \u2014 or a `ledger` clause | the book of movements, closing on its total read against the record\'s `rollup` that sums them, where it carries one || `lines:` | anything else the record owns (`parent`) | the register of the rows it is made of |\n| `history:` | anything else NAMED BY it \u2014 the link is their `party` or their `identity` | the same rows read as that record\'s own history \u2014 on a PROFILE, every one of them stands open at its latest 5, headed by how many there are in all, with the rest a press away |\n| `via <link>:` | a link carrying neither role | the register, headed by that link\'s own label |\n| `related:` | rows of an entity this app lists NOWHERE | one counted line, and a press that opens their register |\n\nA child carrying the BODY and no day is a plain register, and `scaffold check`\nnotes the day it is one short of rather than letting it fall through silently. A\ndated row with no body is not a near miss \u2014 that is every ledger line there is.\n\n**A LOG\'S DAY is the child\'s `when`, unless that `when` counts down** (`due`,\n`until`): a deadline is the day an answer is OWED, so a log stacked on it would\nput the entries nobody has chased at the top. Then \u2014 and where the child declares\nno `when` at all \u2014 the day is the first `date` no role claims. A child carrying a\n`lifecycle` is never a log, on the same rule a schedule reads: it is a thing\nbeing WORKED, and the prose on it is a note about the job.\n\n**A child\'s columns read, and are given up, in one order**: identity \xB7 when \xB7\nlifecycle \xB7 category \xB7 amount \xB7 measure \xB7 expected_set \xB7 party \xB7 contact \xB7\nverdict. The DAY outranks the counterparty because a list of rows belonging to\none record is scanned by when \u2014 the counterparty repeats on every row, and on a\nlog there is none. Ranked the other way, a narrow register shed the date and kept\na column that said the same thing on every line.\n\n**A section names its link where two of them would read alike.** One child can\nreach a record through several links and land under the same heading twice, which\nis the same sentence with nothing saying which rows either holds \u2014 so each of\nthose says the link it is read through (`schedule: Stops via Billed to`), and a\nchild reaching the record once is named by the rows it lists.\n\n**The clauses, by name.** On the APP: `scope`, `reads`. On the `screen`: `record`, `tabs`,\n`slots` (`roles` on a `custom` one), `columns`, `writes` (`false`,\n`"children"` for the rows a record owns and not the record, or `"record"` for the\nrecord and not its rows), `period`, `filters`,\n`summary` (`above`, `totals`, `ageing`, `trend`, `curve`), `facts`, `presentation`\n(`lead`, `density`, `layout`, `until`, `nest`, `depends_on`, `baseline`), `acts`\n(`row`, `record`, `selection`, `export`, `import`), `section_acts`, `sections`, `children`. Every one is optional, every one\nis printed back by `scaffold check`, and a screen that states none gets what its\nshape and its roles answer by themselves.\n\n**ONE APP IS ONE REGISTER AND THE RECORDS IT OPENS.** A second register beside\nit is a second job on one page: the reader arrives on whichever the nav listed\nfirst and decides, every time, which of the two they came for. So an app has one\ndestination and everything else about a row is DISCLOSED by opening it \u2014 the\nfacts by tier, the children as lists, the related as counts, one primary act, and\na filter or a group where a strip of destinations would have been. What used to\nbe a second screen is a section of the record, or another app; a model still\nsaying `screens` is refused by name.\n\n**The unit of an app is a JOB, not a person and not a table.** A job has its\nown outcome (something exists or is settled when it is done), its own subject\n(the record it advances), and an end that does not wait on the rest of the\nwork. Two tasks are ONE job when neither finishes without the other and both\nadvance the same record. One app per job, and that is what makes an app a\nwrite-ownership boundary: what the job settles is its app\'s alone to write,\nplus everything it must read to settle it well. A person holding several jobs\nopens several apps \u2014 one app for everything one person does is the dump. A step\nof the job is a section of the record, never a register beside it; a reference\nthe job needs at hand is read inside the record it is about.\n\n**Two people signing is two jobs**, because the outcome belongs to the signer:\nthe desk that prepares against the gate that releases. So is a different\ncadence \u2014 reference data edited monthly and read by the public site, beside a\ndaily desk \u2014 and a different reader, the owner\'s read-only questions. Device,\nplace and step never split a job. A super app holds more than one job; an\nover-split holds less than one, a job cut by device, place or step. The count\nper workspace falls out of the jobs, typically two to six, and is never the\ninput: review the plan app by app, naming who holds it, the job in one\nsentence, what it writes and what it reads.\n\n**A party is not a job.** The people and companies a job\'s rows name \u2014 the\ncustomers, the suppliers, the carriers \u2014 are not a job of their own, however\nmany rows name them: nobody\'s day is "the customer book". They live inside the\napp whose rows name them: a create takes the party by its natural key, the row\'s\nname opens the party\'s own record (a profile \u2014 how to reach them, what is live\nwith them, their history, their log), and its facts are edited there. A\nparty earns an app of its own only where someone\'s job IS the relationship, with\nan outcome of its own \u2014 an account plan signed, a supplier qualified \u2014 never\n"keeping the book". Two apps for one seller, the deals and the customers, is the\ndump cut in two.\n\n*A two-van appliance repair shop.* The technician\'s job is the call-out: the\noutcome is a visit done, the subject is the call-out record, and quoting it and\nscheduling it are one job, because neither finishes without the other and both\nadvance that record. The owner holds two of his own \u2014 billing the month\n(outcome invoiced, subject the invoice, settled against visits already closed)\nand the price list the booking page quotes from, edited monthly. Three jobs,\nthree apps, and the owner opens two of them.\n\n**Inside a job the caps hold**: six flow stages on a desk, seven facts before a\nrecord\'s fold. Past them, look for the second job hiding inside. And a job\'s app\nis DENSE: every create the job needs lives in it, so its user never leaves it to\ncorrect a figure the screen in front of them is stating \u2014 three workflows is a\nscreen, not a desk.\n\n**A handoff is a stage change.** Where one job ends the record moves stage and\nthe next job\'s desk opens on it; a field two jobs must both write is declared\nshared at the split, naming the stage each may write it in.\n\n**Name an app for the JOB, in the trade\'s own words, never for who it is for.**\nA title on the door says nothing about what the person who opened it came to\ndo, and it is wrong the day the org chart moves.\n\n```jsonc\n"apps": [\n  {\n    "alias": "sales", "name": "Sales",\n    "description": "\u2026", "icon": "briefcase", "theme": { "color": "blue" }, // optional\n    "screen":\n      { "alias": "orders",    "label": "Orders",    "shape": "lifecycle_desk", "entity": "order",\n        "record": "drawer",                  // optional \u2014 "drawer" | "page"; absent, the shape decides\n        "tabs": "stage",                     // optional \u2014 the entity\'s lifecycle, or null; absent, the shape decides. Any other select is a filter\n        "writes": false,                     // optional \u2014 default TRUE; false is a reader, "children" operates only the rows the record owns, "record" only the record\n\n        "period": "due_date",                // optional \u2014 any field whose value is a date, derived ones included\n        "filters": ["kind",                  // optional \u2014 a single-select, or a lens the model states itself\n                    { "label": "Qu\xE1 h\u1EA1n l\u01B0u", "predicates": [\n                      { "label": "\u0110\xE3 qu\xE1", "tone": "red",\n                        "where": { "node_type": "group", "logic": "and", "children": [\n                          { "node_type": "condition", "field_key": "owed", "operator": "greater_than", "value": 0 }] } }] }],\n        "summary": { "totals": ["total"], "above": ["total", { "field": "owed", "at": "end" }],\n                     "ageing": { "amount": "owed", "due": "due_date", "buckets": [30, 60, 90] },\n                     "trend": { "field": "total", "direction": "up" } },  // optional \u2014 see below\n        "facts": { "groups": [{ "caption": "Pricing", "fields": ["rate", "surcharge"] }] },  // optional \u2014 the record\'s named bands\n        "presentation": { "lead": "none", "density": "dense" },  // optional \u2014 how it is DRAWN; absent, what the rows are decides\n        "acts": { "row": [{ "label": "Issue the note", "template": "debit_note", "place": "cta", "confirm": true },\n                          { "kind": "agent", "label": "Read the papers", "agent": "reader", "fills": ["ref", "due_date"] },\n                          { "kind": "workflow", "label": "Hand it to dispatch", "workflow": "hand_to_dispatch",\n                            "inputs": { "order_id": "record", "owed_by": "due_date" },\n                            "asks": { "crew": "crew" },               // optional \u2014 stated in the act\'s panel before it runs\n                            "needs": ["site_phone", "site_email"] }], // optional \u2014 offered only while one of them holds a value\n                  "record": [{ "label": "Print the file", "template": "dossier" }],  // optional \u2014 the record\'s own header menu\n                  "selection": [{ "label": "Statement", "template": "statement" }],  // optional \u2014 the work it hands on\n                  "export": true,                                                    // optional \u2014 the rows in view, saved\n                  "import": { "kind": "import", "label": "Upload the sheet",         // optional \u2014 a file turned into rows\n                              "entity": "order", "key": "code", "columns": ["rate"] } },\n        "section_acts": { "line": [{ "label": "Chase the lines", "template": "chaser" }] },  // optional \u2014 a verb on one section\n        "sections": { "line": { "draw": "worksheet", "cost": "buy_rate", "sell": "rate" },  // optional \u2014 priced lines, worked down in place\n                      "payment": { "draw": "ledger", "heading": "Money in" },  // optional \u2014 a book, closed on its total against what the record owes; `heading` optional on every draw\n                      "stop": { "heading": "The move", "facts": ["pack_on", "deliver_on"] },  // optional \u2014 the record\'s facts that frame these rows, drawn over them (see below)\n                      "visit": { "draw": "log", "evidence": ["photos"], "lines": [["kind", "site"]] },  // optional \u2014 where a log\'s entry or a run\'s stop draws each field (see below)\n                      "pinning": { "draw": "publish", \u2026 },       // optional \u2014 the destinations this record is sent to (see below)\n                      "chase": { "draw": "acts", \u2026 } },          // optional \u2014 acts waiting for a person under this record (see below)        "slots": { "identity": "code",       // optional \u2014 slot \u2192 field, where the roles cannot decide alone\n                   "subject": ["customer", "project"],              // \u2026or the TIERS a fold walks down, outermost first\n                   "stage": { "field": "state", "quick": true } },  // \u2026or the field AND the reader\'s own control for it\n        "columns": ["source", "owner"],      // optional \u2014 extra facts after the slots, shed first at narrow width\n        "create": ["code", "customer", "due_date"] }  // optional \u2014 what a NEW row is asked for; absent, every field a person states\n  }\n]\n```\n\nA shape is a proven screen with named SLOTS, each filled by a field carrying a\nrole (\xA7 Field roles). A slot with exactly one candidate on the entity binds by itself;\ntwo candidates need naming in `slots`; a field fills one slot; a required slot\nwith none is refused \u2014 a lifecycle desk over an entity with no `lifecycle`\nselect cannot be built. `"slots": { "party": null }` leaves a slot the shape can\ndo without UNBOUND: the register draws no column for it and gives the width to\n`columns`, while the role goes on being read everywhere else. A required slot\nrefuses it.\n\n**A LIST IS A HIERARCHY, not a set of columns.** A group register\'s `subject`\ntakes one \u2014 `"subject": ["customer", "project", "order"]`, outermost first \u2014 and\nthe register becomes one the reader walks DOWN: it folds by the first tier, a\nnode narrows to the tier inside it, the last tier opens the set behind the\nfigure, and a trail says where they are. Every tier is a field of this entity\ncarrying a role that slot accepts, and none of them fills a second slot. It is\nthe slot\'s own answer that decides: a list on any other is refused, because two\ncolumns in one cell is not a fold. Without it the same business needs a register\nper depth, and the same money is folded twice with nothing saying it is the same\nmoney.\n\n**AND ON A SLOT READ AGAINST A LIMIT A LIST IS SEVERAL MEASURES** \u2014\n`"level": ["received", "invoiced"]`, at most four, each drawn as a named meter\nline inside the ONE column and each read against its OWN `against`/`alert`. A\nrow is regularly scored against more than one target at once, and the second\nreading put in `columns` instead draws a figure bare with the comparison handed\nback to the reader. Every entry states a limit \u2014 a bare measure in the list is\nrefused, naming the clause \u2014 and `quick` is refused beside one, because a typed\nfigure is one cell. The FIRST leads: it is what `summary.above: "counts"` counts\npast-limit rows on and what a live board ranks its exceptions by, both of which\nname one set.\n\n**A QUICK SLOT IS FOR A DECISION THE READER MAKES FROM THE ROW ALONE.** A slot\'s\nvalue in `slots` is normally the field\'s alias; `{"field": \u2026, "quick": true}`\nsays the column is not a reading of that value but the CONTROL for it \u2014 pressed,\nit writes that one field as a diff through the record\'s own update, so the\nregister and the page behind it land the same write. THREE roles are such a\ndecision, and `quick` on any other is refused: a `lifecycle`, which rests as the\nstage\'s own dot and label, takes a rule under it on hover and focus, and opens\nthe field\'s stages with the ones that END the flow last \u2014 ONE control, which IS\nthe reading;\na `verdict`, which is the switch; and a `measure`, which is the figure typed in\nits own cell \u2014 a reading taken per row IS the row, which is what a timesheet\'s\nhours and a count sheet\'s tally are. Everything else is decided against what the\nrecord holds, and the record has to be open. All three carry the record\'s own\nblockers \u2014 a move the ladder holds is a move the cell holds, and it names the\nentries the row still owes \u2014 and an outcome asks before it commits. Add `"order": "sequence"`\nwhere the stages are a WALK rather than a set of destinations: the picker is then\nordered as the walk and the step the row takes next is MARKED in it. It never\nadds a second control \u2014 a column that answered with a reading in some rows and a\nverb in others is two columns about one value. A screen stating `writes: false`\nrefuses `quick`: a reader who may operate nothing has no decision to take.\n\n**THE SLOTS ARE THE ROW\'S ANSWER; `columns` IS ITS CONTEXT.** `"columns":\n["nguon", "phu_trach", "nhu_cau"]` names extra fields of the entity, drawn AFTER\nevery slot and in this order, each by what its column IS \u2014 a chip for a select,\nthe person\'s name for a member, the day for a date, the figure for a number, a\ntick for a boolean, the words for everything else. They are ranked BENEATH every\nslot, so a phone sheds all of them before it sheds any of the shape\'s own\ncolumns. **A COUNT IS NOT A COLUMN**: an entry whose field is a `rollup` that\nCOUNTS rows is read as the thing it counts \u2014 `3 b\xE1o gi\xE1 \u0111ang m\u1EDF`, the number then\nthe column\'s own label \u2014 on the name\'s supporting line at every width, so it\ntakes no seat and a count of nothing draws no run at all. Where the record LISTS\nthose rows, the reading is the press that opens it. At most four, and refused\nwhere one would say what a slot already says,\nover a files field (files are read, so they are a section of the record), over a\ncell holding several (a column of comma lists compares nothing), on a shape whose\nrows are not the entity\'s records in a table, and beside a `presentation.layout`\nthat draws the rows with a device of its own. A fifth fact worth the width is a\nslot the shape is missing \u2014 say so rather than widening this clause.\n\n**A RELATED ROW\'S KIND IS A CHIP.** An entry `{"field": "latest_kind", "age":\n"latest_on", "more": "item_count"}` draws a `lookup` of a related row\'s\n`category` as that category\'s chip \u2014 the option\'s colour and glyph (\xA7 Field\nroles, `icons`) \u2014 followed by how long ago that row happened (`age`, a date read\nover the SAME link, a lookup or a rollup) and how many OTHER rows the link names\n(`more`, a count rollup over the same link, drawn `+N`). Three columns drawn apart\nare a word, a date and a small integer the reader joins by eye. It takes one seat.\nThe chip is ONE row: across a link naming several, the lookup is ordered\n(`order_by`), and `age` dates the row that order picks \u2014 a `latest` (for `desc`)\nor `earliest` (for `asc`) rollup of the order\'s own date, or a lookup ordered the\nsame way. Refused: a field that is no lookup of a category, an unordered lookup\nacross a link naming several rows, an `age` or `more` read over another link or\nthrough a rollup `filter`, an `age` that is not a date or dates another row, a\n`more` that is not a count, an entry stating neither, and a rider named again as a\ncolumn of its own.\n\n**THE DRAFT ASKS WHAT FILES THE ROW; THE RECORD ASKS THE REST.** `"create":\n["ma_ho_so", "khach_hang", "han_xu_ly"]` names the fields a NEW row is asked for,\nin that order. Absent, the draft asks for every field a person states \u2014 which is\none panel for a row somebody has the answers to when they open it, and a wall in\nfront of one that is written over days: a job is named, dated and filed the\nmoment it is taken, and everything else about it is learned afterwards. Whatever\nthis clause leaves out is edited in place on the record, where it is read. It is\nthe SCREEN\'s, and a screen is one register over one entity, so it narrows that\nentity\'s own draft: the rows a record adds under itself are the section\'s, and\ntheir composer asks what the section draws. At most twelve, and refused where an\nalias is not a field of the entity, is named twice, or is one no draft ever asks\n\u2014 a computed value, a minted number, the `lifecycle`\n(the row opens at the flow\'s first rung), a field a `default_from` copies, the\nstamp an `obligation` is closed by, and every files column but the `mark`. A\nlink naming several rows is asked through a picker that takes every row picked.\nA link the row STANDS ON \u2014 its `parent`, its `party` \u2014 is asked as ONE row whatever its\ncardinality, because the create writes one row into it and how many the cell\nholds afterwards is the platform\'s business. The\n`mark` itself may be left out, and then the row\'s face is attached on the record\nlike any other pile. Refused too where it omits a field the row cannot be written\nwithout \u2014 one that is `required`, the link it hangs under, or the key a party is\nrecognised by \u2014 because a draft that cannot save is worse than a long one.\n\n| Shape | Answers | Required | Also fills | Record | Tabs |\n|---|---|---|---|---|---|\n| `lifecycle_desk` | what is stuck, what do I move next | `lifecycle`, `identity` | `mark`, `party`, `amount`, `measure` (level, one or several), `when` | page, or drawer where the entity carries `parent` | the lifecycle\'s stages |\n| `party_register` | who is this, our history, is there a risk | `identity` | `mark`, `contact`, `measure` (worth), `verdict` (risk) | page | none |\n| `offering_register` | what do we offer, at what price, can I sell it | `identity` | `mark`, `amount` (price), `measure` (availability) | page | none |\n| `transaction_ledger` | does this period reconcile, what is unexplained | `when`, `amount` | `identity` (reference \u2014 the line\'s own number), `party`, `lifecycle` (classification), `expected_set` (document) | drawer | none |\n| `monitored_asset_set` | what needs attention, is that number normal | `identity`, `measure` (level, one or several) or `expires` (level, as the days left) | `mark`, `lifecycle` | drawer | none |\n| `obligation_desk` | what is due next, and has it been done | `identity`, and at least one `obligation` on the entity | `when` (runway) | page | none |\n| `trend_deep_dive` | how did the period go, and why | `when` | `measure`, `amount` | drawer | the series, where the model names a select |\n| `reconciliation_desk` | what does not match, and by how much | `identity` (reference), and two figures \u2014 `ours` and `theirs`, each an `amount` or a `measure` | `category` (reason), `verdict`, `when` | drawer, on the PAIR | the dated runs, where the model names a select |\n| `entry_matrix` | one value per subject per period | `identity` (subject), `across` \u2014 a `when`, or a `category` for a fixed column set | `measure` (value), `lifecycle` (state), `category` (note) | drawer, on the cell\'s row | none |\n| `guided_run` | complete an ordered sequence, a step at a time | `identity` (step) | `slot` (sequence), `capture` \u2014 a `measure`, `verdict` or `expected_set` \u2014 `verdict` (gate), `mark` (media) | page: the run IS the record | none |\n| `live_board` | is everything OK, right now | `lifecycle` (state), `identity` | `verdict` (exception), `when` (since), `measure` (level, one or several), `category` (where) | drawer | none |\n| `group_register` | what does each group come to, and what is behind it | `subject` \u2014 a `category`, `party` or `when` | `amount`, `measure`, `identity` (member) | page: a row is an aggregate, and the door is the SET behind it | none |\n| `media_set` | scan a body of pictures by where they belong | `mark` (picture), `identity` | `category` or `party` (group), `when`, `verdict` (current against superseded) | drawer | none |\n| `day_sheet` | what happened on each day | `when` (the day) | `lifecycle` (state), `measure` (level, one or several), `amount`, `category` (note) | page: a day composes several child logs | none |\n| `resource_schedule` | what is on each resource, in what order, under what ceiling | `lane` \u2014 a `party` or a `parent` \u2014 `identity`, `when` (the start) | `measure` (duration), and `load` and `bulk`, each a `measure` read against a ceiling of the LANE\'s \u2014 a vehicle fills by weight and by room and stops at whichever runs out first; `lifecycle` (stage) | drawer, over the lanes | none |\n| `worksheet` | priced lines the reader edits, totalling to one figure | `identity` | `category` (group), `measure` (quantity), and `cost` and `sell`, each an `amount` or a `measure` | drawer, per line | the versions or the jobs, where the model names a select |\n\n**A record is one of five KINDS, and the shape plus the roles decide which.**\nEvery one of them is ONE READING COLUMN, and the ORDER of that column is the\nwhole of what the kind means.\n\n| Kind | The column, top to bottom |\n|---|---|\n| WORK RECORD \u2014 a `lifecycle_desk` over rows that belong to nothing and that nothing transacts with | the one act that moves it \xB7 what it IS \xB7 the papers it owes \xB7 the rows it is made of \xB7 the book of what it came to |\n| LINE \u2014 the same shape over rows carrying `parent` | its ladder \xB7 the arithmetic behind its amount \xB7 the rows and papers under it \xB7 its particulars, last (the key it is filed by is the line under its title) |\n| PROFILE \u2014 a `party_register`, and any shape over an entity whose rows other entities are NAMED by (their `party` or their `identity`) | where it stands \xB7 its history, OPEN, grouped by year \xB7 the rest of its registers \xB7 its facts (the ways to reach it are under its name, its settlement is the band, and a `when` it owes closes that band as a countdown) |\n| CATALOGUE ITEM \u2014 an `offering_register` | its own words (the picture leads the header at media scale, the price is read against its reference in the band) \xB7 what uses it \xB7 its facts |\n| EVIDENCE \u2014 a `transaction_ledger` | the PROOF \xB7 what the paper is, compactly \xB7 the rest \xB7 the links to the record it settles and the party it was with |\n\nNothing in the file states the kind: a clause that could say it could say the\nwrong one, and the model already says it \u2014 `parent` says whether a row stands\nalone, and a link NAMING this record (`party`, `identity`) says whether other\nrows are ABOUT it. So a desk over accounts\nwalking their own stages opens a PROFILE: the quotes and the invoices naming\neach account are what its record is read for, and a work record would have\ncounted them in one line at the foot. `record`\noverrides the DOOR where the shape\'s own answer is not the one wanted \u2014 and its\nthird value, `"expand"`, is not a door at all: the row REVEALS what it holds in\nplace, where there is nothing behind it worth navigating to. A row read that way\nreads as a LINE whatever the shape would have opened: its ladder, the arithmetic\nbehind its amount, then its particulars, because there is no header above it to\nhave stated the name first. It is REFUSED for two reasons, and they are not the\nsame refusal. On a shape whose record is a page by nature \u2014 a `guided_run`, a\n`group_register`, a `day_sheet`, an `obligation_desk` \u2014 because each of those\nstates the opposite where its door is declared: what its row leads to is read\nwhole, not as four more columns than the register had room for. And on a shape\nthat draws its rows with a device of its OWN \u2014 an `entry_matrix`, a `media_set` \u2014\nbecause a cell of a grid and a tile on a wall have no band under them for the row\nto reveal into. For the same reason a revealed register is drawn as a TABLE: a\n`presentation.layout` of anything else is refused, and the reader is not offered\nthe arrangement either, since it would take away the only door the register has.\n\n**`scope` \u2014 the one subject every read of the app narrows to.** Stated on the\nAPP rather than on its screen, because it is not a filter: a record opened under\nit stays under it, the pick survives closing the app, and every app declaring the\nsame `entity` shares one pick per viewer \u2014 which is the whole value, and what\nstops a construction workspace asking which project twelve times. `entity` is the\nmodel\'s entity whose one row the app is read inside, and `param` is what the\napp\'s reads take that row by.\n\n```jsonc\n{ "alias": "site_work", "name": "Site work",\n  "scope": { "entity": "project", "param": "project_id" },\n  "screen": { \u2026 } }\n```\n\nThe register\'s own entity has to REACH it \u2014 its own rows, or rows that name one\nthrough a link \u2014 or the switcher is a control that changes nothing. Until a\nsubject is picked the app reads NOTHING and says which one it is waiting for: an\nunscoped read over a scoped app is every row in the workspace drawn as one\nproject\'s work, which looks correct.\n\n**ONE RECORD SURFACE PER ENTITY, AND ITS KIND IS THE ENTITY\'S.** An app is one\nregister, so the record its rows open is the register\'s own and the kind comes\nfrom that register\'s shape. Another app over the same entity opens the same kind\nof record: a payment read from a cash book and one read from a trend are both\nmovements, and both read proof first. A shape with no kind of its own (a trend, a\nmonitored set, a `custom` screen) says only where the record opens.\n\n**A NAMED PARTY HAS A RECORD SURFACE IN THE APP.** One register, but the party\nits rows name \u2014 by `identity` or by `party` \u2014 opens a record of its own, a\nPROFILE, from the cell that names it and from the record\'s header: the ways to\nreach them, what is live with them, every register that names them at its latest\nfive, their log, their facts. It is the app\'s to write as far as the job\nneeds \u2014 the party\'s facts and its log \u2014 and the writers matrix says so; the\nregister\'s own record stays the register\'s. A party named through a link\ncarrying no role opens nothing, and neither does a party that is a MEMBER \u2014 a\nperson of this workspace has no row in any book the app carries, so the cell and\nthe header state them and stop.\n\n**Two things a register states about a row beyond which field fills which slot.**\nA `measure` is read AGAINST its limit (`against`/`alert`) where the shape\'s slot\ntakes one \u2014 `level`, on a lifecycle desk, a monitored set, a live board and a day\nsheet, a schedule\'s `load` and `bulk`, and every slot of a\n`custom` screen, which composes the frame\'s own column; `worth`, `availability`\nand a trend\'s headline are plain figures, and a limit there would read as a meter\nin the record over a number the row printed bare. And the name carries a\nSUPPORTING LINE where the entity states a key to file the row under: the `parent`\nit belongs to, its `reference`, an `autonumber`, a text formula \u2014 in that order,\nfirst hit wins, never a field a person types prose into. Every record heads with\nthat same key, so the register and the door it opens name one row one way.\n\n**The act that opens a row belongs to a register that LISTS the entity\'s rows**\n\u2014 a desk, a register, a ledger, a monitored set, or a `custom` screen. A shape\nwhose rows are not records has neither that act nor the door a counted line\nelsewhere leads to: an obligation desk\'s rows are deadlines and a trend\'s are\nperiods, so a create pressed there would open a row the screen cannot show. An\nentity whose only app is one of those has no create at all \u2014 give it an app whose\nregister its rows are read in.\n\n**An `obligation_desk`\'s rows are not its entity\'s rows.** The shape fans the\nentity\'s `obligation` fields out \u2014 one row per thing still owed, which is one\nwhose date is SET and whose `satisfied_by` is empty \u2014 so a l\xF4 with four cut-offs\nis four rows, and the three it has met are not there at all. The row\'s name is\nthe obligation\'s, its supporting line the record\'s `identity`, and the door is\nthat record. A `when` bound to `runway` is what the countdown\'s ring is measured\nfrom. Over an entity declaring no `obligation` the shape is refused: there is\nnothing to count down to.\n\n**What a register carries beyond its columns.** Six clauses, each emitted as\nthe prop the kit draws it with; every one is optional and a screen that states\nnone gets a register of columns and nothing else.\n\n- **`period`** \u2014 a field on the entity whose value is a DATE. The toolbar gains a\n  date-range control (this month to start), and the rows it keeps are what the\n  register AND every figure below are computed over, so a band can never be over a\n  different window than the rows under it. Any such field, not only the `when`\n  role, and however the date got there: one table is read two ways (a cost ledger\n  by the day a line arose, the cash book over the same table by the day it\n  settled), a role is one field\'s, and the day money MOVED is often a formula over\n  the two columns that could hold it \u2014 which then declares `output_type: "date"`.\n  A `trend_deep_dive` brings its own period and takes none here; a `live_board`\n  is PERIODLESS and takes none either, for the opposite reason \u2014 it answers what\n  is true NOW, and a date range over it draws what was true in the window in the\n  live state\'s own colours.\n- **`filters`** \u2014 the chips beside the search. A single-`select` field\'s alias\n  \u2014 or a `lookup` of one, read as the looked-up row\'s option \u2014 offers that\n  field\'s own live options; it is the lens a register is read through\n  over and above the one band its strip gives, so the strip\'s own field is\n  refused here (one dimension, one control) and so is a multi-select (a row would\n  answer the chip several ways at once). The rows the register and every figure\n  below are computed over are what the chips AND the period kept.\n  A `select_member` field\'s alias is the third form and asks one question \u2014 whose\n  rows these are: two peers, MINE and ALL, read against the person looking rather\n  than a directory of everybody. `{"field": \u2026, "default": "mine"}` opens the\n  register on the reader\'s own; that form on any other type is refused. Alone of\n  the chips it narrows the READ (a `member` param on the register\'s query), so a\n  desk that opens on the reader\'s work opens on all of it rather than on\n  whichever of their rows the first page happened to hold.\n  A DERIVED LENS is the other form \u2014 `{"label": \u2026, "predicates": [{"label": \u2026,\n  "tone": \u2026, "where": \u2026}]}` \u2014 where the sets a reader narrows by are ones the\n  MODEL names and no column holds: rate validity, plan urgency, free-time\n  overrun. Each `where` is an `and` group of plain conditions over the entity\'s\n  own fields, each `field_key` a field alias, and it is read off the row, so the\n  operators are the comparisons a value answers \u2014 `number` and `text` equality,\n  `number` ordering, `boolean` equality, `select` `has_any_of`/`has_none_of`, and\n  `is_empty`/`is_not_empty` on any of them. Nothing DATED: a relative point needs\n  a clock, and a screen states one date control (`period`), so a second beside it\n  would be two windows with nothing saying which a figure was computed over \u2014 a\n  date question is asked as a column the model derives and read here as a number\n  or a yes/no. `tone` is the option palette\'s, because the chip draws these\n  exactly as it draws a select\'s options. ONE predicate is a chip the reader\n  toggles rather than a list of one. `"sort": {"field": \u2026, "order": "asc"}`\n  reads the rows in that field\'s order while the lens is on \u2014 a worklist, owed\n  soonest first, a row holding none last; refused over a field that is not a\n  date, number or text of this entity.\n- **`summary`** \u2014 what the rows in view come to. `above` is a band OVER the\n  register: `"counts"` for how many rows are in view and, for the FIRST\n  `measure` the model gives a limit, how many are past it (accented only when\n  one is) \u2014 one such set, because a band naming three is the dashboard a\n  register is not; a list of number-field aliases for what they add up to, and a\n  `percentage` named there is refused, since a share summed over the rows in\n  view is a figure of no kind (draw it as a column, whose own total reads the\n  mean). A figure written `{"field": \u2026, "at": "end"}` is a STOCK instead: the\n  reading standing at the END of the window rather than the sum of the readings\n  in it, which is the only way opening + in \u2212 out = closing reconciles \u2014 a month\n  of daily closing stocks added together is thirty warehouses. The band labels it\n  as the snapshot it is, and it is refused on a screen that states no `period`,\n  since there is then no window for it to stand at the end of.\n  `ageing` stands in that same\n  band: an `amount` split by how many days past its `due` date each row is,\n  drawn as a `Breakdown` of the edges in `buckets` (30, 60 and 90 days unless the\n  model states its own, ascending). The ladder is the kit\'s \u2014 its boundary, its\n  words and its ramp \u2014 and it opens with what is NOT YET DUE, because a bar of\n  overdue bands alone is full at every input: a book with one late invoice and a\n  book that has gone entirely bad would paint the same solid width. Against the\n  current money the bar\'s own shape is the reading. A row whose date is empty is\n  in no band. `totals` is what the whole\n  view adds up, and it is drawn in that SAME band above the rows: a register\n  states one aggregate, over the rows the reader can see, in one place, and a\n  closing line under them is a second place to look and a second question about\n  which rows it covers. A closing line belongs to the one device that IS a\n  statement \u2014 a record\'s `Ledger`, whose balance is what it is read for, labelled\n  by its amount\'s own word. Where a shape has no band above (a trend, whose own\n  band is the chart) the figure stands under the register instead. A\n  `transaction_ledger` sums its amount column itself and takes `above` alone. An\n  `obligation_desk`\'s rows are DEADLINES and not records, so its band states\n  `"counts"` \u2014 how many are open \u2014 and a figure list, an `ageing` or a `trend`\n  over it is\n  refused: a l\xF4 with three cut-offs is three rows, and its freight added over\n  them is three times the freight.\n  `trend` is `{"field": \u2026, "direction": "up"|"down"}` and states WHICH WAY that\n  figure moved across the window: the rows in view are cut into the window\'s own\n  buckets \u2014 days over a month, weeks over half a year, months beyond \u2014 and the\n  later half of the CLOSED ones is read against the earlier half, drawn beside\n  the figures as one line, so a window the reader is still inside states the\n  movement of the days that have run rather than a fall into the ones that have\n  not. `direction` is which way is GOOD, which nothing about the number\n  says: a book wants its takings rising and a backlog wants its days falling, and\n  the same arrow is a win on one and an alarm on the other. It needs a `period`\n  to be a window of, and it is refused on a shape that draws its own (a\n  `trend_deep_dive` already draws the series) or that reads none at all (a\n  `live_board` answers what is true now). A window whose earlier half took\n  nothing draws no line: there is no base for a percentage, and 0 % would claim a\n  steadiness nobody measured.\n  `curve` is `{"planned": \u2026, "actual": \u2026}` \u2014 two number fields of the row, each\n  added up to date along the rows\' own date and drawn in that band as two lines:\n  the S-curve a schedule or a budget is judged by, where a row is a period or a\n  piece of work and the running total is the curve\'s own arithmetic. The date is\n  the screen\'s `period` where it states one, else its `when`; a screen reading\n  its rows by no date is refused. The actual line stops at the last date a row\n  stated an actual figure \u2014 drawn on past it, the weeks nobody has worked yet\n  would read as a stall. Refused on the shapes a `trend` is refused on, over the\n  same reasons, and against itself.\n- **`facts`** \u2014 how the RECORD\'s facts are banded. `groups` is a list of\n  `{caption, fields}`: what a set of facts has in common is a sentence about the\n  business and nothing derives it, so a plan that states one gets exactly those\n  bands, in its own order, captioned. EACH BAND IS A SECTION of the record \u2014 its\n  own heading, its own entry in the rail, its own place in the column: under one\n  heading the reader is handed every particular at once, in a caption weight that\n  cannot out-rank the heading above it, with nothing in the rail to reach any of\n  them by. Everything the plan leaves unnamed is the LAST section and carries no\n  heading, since there is no sentence to head "whatever no group claimed" with \u2014\n  ONE section, even where the record\'s own recipe bands what was left in two (an\n  evidence record reads its particulars before the record and the party it was\n  with): both are groups inside it, because the word the kit heads "the rest"\n  with cannot name two entries in the rail. A band marked `last: true` is read\n  AFTER the record\'s own work \u2014 its acts, its rows, its correspondence \u2014 for the\n  particulars a reader checks once they know what is owed (who it is with, where\n  it came from); `folded: true` draws the band closed under its caption, and is\n  read last too. `first: true` reads a band ahead of everything, the stage\n  included \u2014 the facts a verdict is taken on, read before the verdict; a band\n  both first and last is refused. Where `children` names the record\'s relations,\n  their sections read in that order whatever each is drawn as \u2014 a log of the\n  evidence above the acts it decides.\n  A band of more than eight facts is NOTED: a section that long is two. A field the header, the band, the ladder, a required\n  set, the files or a register below already draws is refused: it is not a fact,\n  so a band naming it would either state it twice or draw nothing. Naming any\n  band IS the answer to which facts fold \u2014 see the TIERS below \u2014 so the bands\n  between them hold EVERY fact a person states: a text, a number, a date, a\n  choice or a link the groups leave out is refused by name, because the fold\n  holds only what the platform mints, stamps or works out. An entity whose\n  record shows `rate`, `surcharge`, `note` and a `created_on` stamp is banded\n  as `[{ "caption": "Pricing", "fields": ["rate", "surcharge"] }, { "caption":\n  "Remarks", "fields": ["note"] }]` \u2014 the stamp folds, and a plan naming the\n  first band alone is refused for leaving `note` in none.\n- **`presentation`** \u2014 how the screen and the record it opens are DRAWN, where\n  what the rows are is not the answer wanted. `lead` is what each row leads\n  with: `"mark"` the subject\'s own mark, always spent because a party\'s initials\n  stand in for a picture nobody uploaded; `"picture"` the photograph, spent only\n  on the rows that carry one and, on the record, at media scale above the name;\n  `"paper"` the row\'s own files, drawn as the cards a pile of documents is read\n  as; `"figure"` the amount, with no gutter at all; `"none"` neither. `density` is\n  how many lines a row\'s subject may take \u2014 `"roomy"` two, `"dense"` one.\n  Both default, and the DEFAULT is what the rows are: a party register leads\n  with the mark, an offering register with the picture, a ledger with its\n  figure, and a desk \u2014 rows that are work still to do, scanned \u2014 stands its rows\n  one line each while a record\'s own rows are read roomy. So state it only to\n  differ, and a plan that states nothing still gets screens that vary. A lead\n  the rows cannot carry is refused: a mark, a picture or a paper where no column\n  is drawn as the rows\' mark, a\n  figure where no column is the amount, and the other subject\'s mark (which of\n  the two a row wears is the shape\'s, so the register and the record it opens\n  cannot call one row two kinds of thing). A row carrying a `contact` is\n  SOMEBODY even where nothing names it yet, so `"mark"` \u2014 initials where no\n  picture was uploaded \u2014 is admitted over it; the default stays the picture. A\n  record opened as a drawer leads its bar with that mark where `lead` is\n  `"mark"`, and its files are then no section of their own.\n  `line` is what the line under a register row\'s name says, in place of the key\n  the row is filed under: at most two fields of the entity, each plain words (a\n  `text` with no `format`, or `"text"`) or ONE option of a closed list (a single\n  `select`) \u2014 where somebody works and what they do there, say. It is also what\n  the row is found by. The record keeps its key. Refused: notation, a link, a\n  field holding several values, the row\'s own name, and a field a slot, a column\n  or a chip already draws.\n  `layout` is how the rows are ARRANGED \u2014 `"table"`, `"list"`, `"cards"`,\n  `"gallery"`, `"board"`, `"calendar"`, `"timeline"`, `"gantt"`, `"tree"` \u2014 and\n  it is AFFORDED by what the rows carry, not by the shape: every register affords\n  a table and a list, a `mark` affords the two picture-led grids, a `lifecycle`\n  affords a board, a `when` affords a calendar and a timeline, and a `when`\n  beside a `measure` that `counts` DAYS affords a gantt, because a bar with no\n  length is a calendar drawn sideways and a bar measured in money or litres is a\n  length of another kind. `until` names the date field a bar ENDS on, where the\n  rows state one, and the days measure is what the bar runs for without it. A\n  layout the bound roles do not afford is refused, naming the ones they do.\n  `nest` names a one-row link from the entity to ITSELF \u2014 the row each row sits\n  under, a work breakdown\'s or a cost plan\'s \u2014 and it is what affords `"tree"`:\n  the rows drawn under the row they name, each folding what it holds, the MONEY\n  each row states or works out from its own columns summed up the tree. A rollup\n  is drawn as the row holds it (it already adds up rows of its own, and summed up\n  the tree a parent carrying one would count its children twice), and so is a\n  quantity, since two units have no sum. A row naming no row above it, or one\n  the read does not hold, stands at the top. On a gantt the same `nest` folds a\n  row\'s bars under a summary that spans them, a row stating no day of its own\n  included. Two more clauses are the gantt\'s\n  own and refused anywhere a bar cannot be drawn: `depends_on`, a link from the\n  entity to itself naming the rows that must FINISH before a row starts \u2014 each an\n  arrow into its start, toned where the sequence is broken \u2014 and `baseline`,\n  `{"start": \u2026, "end": \u2026}`, the two date fields the plan was FIXED in, drawn as a\n  ghost under the bar so a slip reads as the gap. A baseline is never the day\n  the bar itself starts on: the plan kept apart from the date that moves is the\n  whole of what it shows. A row not yet started has no bar of its own, and is\n  drawn across its plan until it starts.\n\n  ```jsonc\n  // A work breakdown, laid out as its outline and scheduled against its plan.\n  "presentation": { "layout": "gantt", "nest": "part_of", "depends_on": "after",\n                    "baseline": { "start": "planned_start", "end": "planned_finish" } }\n  ```\n- **`acts`** \u2014 where this screen hands work on: `row` is the \u22EF menu on every row,\n  `record` is the \u22EF on the RECORD\'s own page header \u2014 the same reach as a row\'s,\n  standing where the work is open instead of while a list is scanned, and refused\n  on a record that opens as a drawer, which has no header of its own and whose\n  row already carries the register\'s menu \u2014 and `selection` is the bar over the\n  TICKED rows. `export` is the third reach \u2014\n  the WHOLE VIEW, saved in one press: `true` writes the rows as the register drew\n  them, in the columns it drew, as an `.xlsx`, and\n  `{"template": "\u2026"}` says the layout is the trade\'s and makes the paper with a\n  workflow like any other. It is never a list of columns: which columns the\n  export carries is what the screen already draws, and a second statement of it\n  disagrees the moment a slot moves \u2014 the generator reads them off the drawn\n  slots and writes them into the app, so the sheet\'s headings are the labels the\n  register drew them under.\n  `import` is the reach OPPOSITE it \u2014 a file turned into rows:\n  `{"kind": "import", "label": \u2026, "entity": \u2026, "key": \u2026, "columns": [...]}`. The\n  file is mapped column by column, each row is validated, what would change is\n  previewed, and the commit UPSERTS by `key` \u2014 which is why a sheet sent twice\n  moves no counts. That key is one of the entity\'s own `natural_key` fields\n  (\xA7 Write rules), and an entity declaring none is refused: without a key the\n  second run is a second set of the same rows. `entity` is the register\'s own \u2014\n  an app is one register, and rows filed into another entity are a count nobody\n  on this screen can check. `columns` is what the sheet may fill, in that order;\n  absent, it is every column a person states IN WORDS. A computed one is refused\n  because the workspace writes it, and a link, a member or a files column is\n  refused because a cell of a sheet is words and those hold a row of another\n  table or bytes \u2014 a file reaches another table through the party pattern (a\n  `natural_key` on the target, named rather than picked), which is a create\'s.\n  The generator writes the whole verb, as it does for a paper: an\n  `import_<entity>` workflow that finds the row by `key` and then changes it or\n  opens it, answering which of the two, and the staged run over it \u2014 drop, map,\n  the per-row verdict, the commit. A line whose cell the column cannot hold is\n  refused with the reason and the rest of the sheet still lands. A file MINTS\n  rows of the register, which is the Add many times over, so a screen stating\n  `writes: false` or `"children"` \u2014 which opens no row of its own \u2014 refuses the\n  clause; the `export` beside it stays, because it only reads.\n  Both spreadsheet reaches are read and written IN THE BROWSER, so the generated\n  `src/main.tsx` imports `@lotics/app-runtime/sheets` wherever the plan states\n  one of them and not otherwise; an app that has neither carries no spreadsheet\n  engine at all. An act names ONE of three things, never two:\n  - **`template`** \u2014 an `html` template this model declares (\xA7 Templates). The\n    paper is filled from ONE row in `row`, and from the whole ticked set in\n    `selection`. The generator writes the whole verb \u2014 a `generate_<template>`\n    workflow that reads the row and hands the file back, and a menu item that\n    opens it \u2014 so there is nothing left to bind. An `email` template is sent\n    rather than opened and is refused here; a file-backed template (`excel`,\n    `word`, `pdf-form`) is bytes a model has none of, so those stay the author\'s\n    own `lotics app workflow set`. Two screens over DIFFERENT entities cannot\n    name one template: one paper is filled from one kind of row.\n  - **`{"kind": "agent", \u2026}`** \u2014 a run over ONE row. `agent` is an alias the APP\n    declares (`package.json#lotics.agents`), because an agent is prose and tools\n    rather than anything a workspace model can state \u2014 `lotics app check` refuses\n    one nothing declares, exactly as it refuses a workflow nothing bound. `fills`\n    is the fields the run may write: pressed, the reader watches the run, reviews\n    what it proposes field by field against what the row holds now, and applies\n    the ones they kept as ONE write through the record\'s own update. A run can\n    reach nothing outside `fills`, a computed column there is refused (the\n    workspace writes those), and a screen stating `writes: false` refuses an\n    agent act outright. It belongs in `row`; the selection bar makes ONE paper\n    from many rows, and a run per ticked row is the row\'s own act many times.\n  - **`{"kind": "workflow", "workflow": "\u2026", "inputs": {\u2026}}`** \u2014 the work HANDED\n    ON: a lead becomes an opportunity, an order is split into the orders placed\n    on its suppliers, a request is closed. `workflow` is an alias the APP binds\n    (`package.json#lotics.workflows`), because the rule behind it is the\n    business\'s and no model states one \u2014 so the generator writes NO body and\n    `lotics app check` refuses an alias nothing bound, exactly as it refuses an\n    agent nothing declares. `inputs` is what the press hands that body: the\n    workflow\'s own input name \u2192 `"record"` for the row it was pressed on, or a\n    field of this entity for a value off that row. The value is what the\n    workspace HOLDS \u2014 an option\'s key, a linked row\'s id, the figure \u2014 never the\n    rendering. A files column is refused (the body reads the row\'s files off the\n    row it is handed), a column that is not a field of the entity is refused by\n    name, and one input short of the declaration is refused at the press, so the\n    whole act is dropped rather than shipped half-bound. It runs ON the press:\n    there is nothing to review first, which is the agent arm\'s law, and the\n    body\'s own sentence is what the reader is told either way. It stands in\n    `row`, in `record` and on a `section_acts` band \u2014 each reaches ONE row \u2014 and\n    is refused over the ticked set, where one act makes one paper from many. The\n    row it reaches is the RECORD\'s, so a screen stating `writes: false` or\n    `"children"` refuses a hand-off on every one of those surfaces, exactly as it\n    refuses an agent act.\n  - **`{"kind": "recording", "workflow": "\u2026", "inputs": {\u2026}}`** \u2014 a call, a\n    visit, a walk-through RECORDED onto the row. Pressed, the product\'s own\n    capture dialog asks which of the microphone, the system sound and the screen\n    to take; the member records; once the words are transcribed the platform runs\n    `workflow` with `inputs` and fills its `recording` input itself \u2014 the audio,\n    the video where the screen was kept, the transcript (`""` for a silent\n    recording), the length and when capture started. It is a hand-off whose run\n    waits for the transcript, so it takes the `workflow` arm\'s rules \u2014 an alias\n    the APP binds, `inputs` read off the row, `when`, `needs` and `place`, the\n    same three reaches, refused over the ticked set and on a screen stating\n    `writes: false` or `"children"` \u2014 less three: no `confirm` (the capture\n    dialog is the confirmation), no `asks` and no `moves`. An input named\n    `recording` is refused: the platform alone fills it. The body is the\n    author\'s, and `lotics app check` refuses one whose declaration does not\n    carry `recording` exactly as\n    `{"type": "object", "fields": {"session_id": {"type": "text"}, "audio": {"type": "file"}, "video": {"type": "file", "required": false}, "transcript": {"type": "text"}, "duration_seconds": {"type": "number"}, "recorded_at": {"type": "datetime"}}}`,\n    printing that declaration. The body files `video` where it is present and\n    `audio` otherwise \u2014 never both, they carry the same sound \u2014 into the row\'s\n    `recording` field, and writes `transcript` into its `verbatim` field\n    (\xA7 Field roles). An app opened\n    outside the product, or on an instance without transcription, does not draw\n    the act. `scaffold check` prints it as `"<label>" [records \u2192 <alias>(\u2026)] [you\n    write the body]`.\n\n  **`"when"` stands an act down until the work is ready.** `{ "field": "<the\n  entity\'s lifecycle>", "in": ["<stage>", \u2026] }` offers the verb only while the\n  row stands at one of those stages. A verb that cannot work yet is worse than\n  no verb: the reader presses it, the body refuses, and nothing on the screen\n  ever said the work was not ready. Readiness is what a lifecycle states, so the\n  field named is this entity\'s `lifecycle` and nothing else \u2014 a category says\n  what a row is and a verdict answers a question, and neither moves. Refused: a\n  field that is not the lifecycle, a stage it does not declare, and every stage\n  at once, which is the act with no condition.\n\n  **`"place": "cta"` draws an act ON the row** instead of in its \u22EF \u2014 the one verb\n  a reader presses without opening a menu first. At most one per screen and every\n  other act stays in the menu, because the trailing gutter is paid for by every\n  row: a second is refused with *one verb on the row, the rest in its menu*. The\n  ticked set has no row of its own, so `cta` is refused there.\n\n  **`"confirm": true` asks before the act runs**, with the act\'s own label as the\n  commit word \u2014 for a press that cannot be taken back: something goes public,\n  something leaves the building, a figure is filed with somebody else. Everything\n  else runs on the press, because a dialog in front of a reversible act is one\n  readers learn to dismiss, and then dismiss in front of the one that mattered.\n  It reads the same wherever the verb stands \u2014 a row\'s \u22EF, a row\'s own button, a\n  record\'s menu, a section\'s band \u2014 and `scaffold check` prints it as\n  `[asks first]`.\n\n  **`"needs"` stands an act down until the row HOLDS what it works with.**\n  `["<field>", \u2026]` offers the verb only while at least one of those fields holds a\n  value \u2014 `when` asks where the row stands, this asks what it holds. A hand-off\n  to somebody who reaches a person needs a way to reach them; a paper sent by\n  post needs an address. ANY of them, because one person is reached several ways\n  and one is enough to start. The verb is drawn standing down and names what it\n  waits for, rather than pressed into a refusal. Any field answers, a lookup\n  included \u2014 only whether it holds a value is read. Refused: a field this entity\n  has not got, the same field twice, and `needs` over the ticked set, where rows\n  hold values in some and not in others. `scaffold check` prints it as\n  `[needs <field> or <field>]`.\n\n  **`"asks"` is what the reader STATES before a hand-off runs** \u2014 the workflow\'s\n  own input name \u2192 a field of this entity whose editor the act\'s panel draws,\n  starting at the row\'s value. A hand-off to a person is to WHICH person, and the\n  row cannot answer that: its value is who holds it now. The run is handed what\n  the reader stated beside its `inputs`. The editor is one the panel draws with\n  nothing else in hand \u2014 a text, a number, a date, a yes/no, a select or a member\n  \u2014 so a link (a picker and a read of its own), a pile and a computed field are\n  refused, and so is an input both handed and asked. `workflow` acts only.\n\n  **`"moves"` is the stage the body lands the row at**, where a hand-off moves\n  it at all \u2014 an option of this entity\'s lifecycle, and the ACT\'s alone: no\n  stage picker, ladder, board or verdict moves a row there, or past it, because\n  a row moved there by hand stands with none of what the body writes beside the\n  move. Refused: a stage the lifecycle has not got. `scaffold check` prints it\n  as `[only way to <stage>]`.\n\n  A hand-off\'s BODY is still the author\'s: `lotics app workflow set <alias>`\n  binds it, and `scaffold check` prints the act as `"<label>" \u2192 <alias>(\u2026) [you\n  write the body]` so it is read as work owed rather than as a verb already\n  wired.\n\n  A `selection` act is a `template` and nothing else: an act over many rows makes\n  ONE paper from them. The generator turns the register\'s checkbox gutter\n  on, emits a `generate_<template>` workflow taking the ticked ids, and the body\n  reads each row and passes them as `rows` \u2014 which is what the template iterates\n  (`{{#each rows}}`). One template is one paper AND one reach: naming the same\n  one from a row\'s \u22EF and from the bar is refused, because those are two bodies.\n  A shape whose rows are DERIVED rather than records \u2014 an `obligation_desk` \u2014\n  has no set to tick and refuses the clause. The paper is handed BACK, never\n  filed: a ticked set can hold rows of three different parents, so there is no\n  record on which "this document belongs here" is true.\n\n**`section_acts` puts a verb WHERE ITS EFFECT LANDS.** "Chase the paperwork"\nbelongs on the papers, not in the register\'s \u22EF two surfaces away. It is keyed by\nthe alias each section is DERIVED from \u2014 a field\'s (its progress, its prose, its\nrequired set, its charge, one of its files) or a CHILD ENTITY\'s (its register,\nits desk, its run, its log) \u2014 because the sections come off the roles and the\nkey the app addresses one by does not exist until it is built. An alias naming no\nsection is refused, listing the ones that do; the facts band is what every other\nsection left over, so nothing addresses it. Each act is a `template`, an `agent`,\na `workflow` or a `recording`, exactly as a row\'s is \u2014 the reach is the same one row \u2014 and\n`place: "cta"` is refused: a section is a band with a heading and has no row to\ndraw a verb on. `scaffold check` prints\nwhich section each alias landed on, which is the half an author cannot see in\ntheir own file.\n\n**`children` says WHICH of those sections this app\'s record draws** \u2014 the child\nentity aliases, in the order they are drawn, and only those. Two apps over one\nentity read it for different jobs: the site\'s daily log belongs on the site\nteam\'s record and not on the owner\'s, whose record draws the schedule and the\nmoney. A link into a child left out is not drawn as a fact either. A name that\nis no child of the record, or named twice, is refused naming the children\nthere are.\n\n```jsonc\n"children": ["task", "claim"]    // the schedule, then the claims \u2014 nothing else\n```\n\n**`sections` says HOW one of those sections is DRAWN**, keyed by the CHILD\nENTITY\'s alias \u2014 every one of its readings is over a child\'s ROWS, so a field\'s\nalias names no section this clause can draw and is refused. A clause here\nOUTRANKS the table above:\nthe derivations there recognise a shape off columns that are also ordinary\ncolumns, so a markdown field holding a refusal reads as somebody\'s message. Where\nthis clause names the reading, it is the reading.\n\nEvery reading takes an optional `heading` \u2014 what the section is headed on the\nrecord. The child\'s label names the SET its table holds ("Placements", "Tasks");\na section is read as the question it answers ("Where it goes", "Waiting on us"),\nand where the two differ the heading says the second. `{"heading": "\u2026"}` ALONE\nrenames any section of the rows this record OWNS \u2014 a log, a correspondence, a\nregister \u2014 without changing how the roles draw it; on rows the record merely\nlists it is refused, naming the rows it owns.\n\n`facts` names fields of THE RECORD drawn at the head of the section, above its\nrows \u2014 the facts those rows are read against: a job\'s window over its visits, a\nquote\'s figure over its payments. One section, because a reader reads the rows\nagainst them; a band of the same dates elsewhere on the record is read apart\nfrom the rows it frames. A field named here is filed here: it leaves the\nrecord\'s facts, counts as filed for `facts.groups`, and the clause\'s `heading`\nnames the section it and the rows make. It stands alone or beside `ledger`,\n`itinerary`, `worksheet`, `claim`, `tree`, `gantt` and `curve` \u2014 a register, a\nrun or a book of rows the record OWNS; a log, a schedule, a desk and a queue draw\nno head. Refused: a name that is no field of the record, a field another section\nalready states (the header\'s name, the ladder, a pile), the limit a fact\'s level\nalready reads its measure against, one named twice or also in a band \u2014 naming\nboth \u2014 and a clause over rows the record does not own or draws as one counted\nline.\n\n```jsonc\n// A removal job: the move\'s window frames its stops, read top to bottom as one section.\n"sections": { "stop": { "heading": "The move", "facts": ["pack_on", "deliver_on", "crew_size"] } }\n```\n\n`"draw": "ledger"` reads the rows as a book of movements where the roles alone\nwould read a register. A book derives no head from its rows: the record\'s\nfigures are the header band\'s and the facts\', and a figure is drawn once per\nrecord \u2014 `facts` moves one of them over the book, out of the band.\nThe book closes on its own total, read AGAINST what the record OWES \u2014 the limit\nthe record\'s `rollup` over these rows is a `measure` against (`field_roles`:\n`{ "role": "measure", "against": "<owed>" }`) \u2014 where the record carries one;\nthe binder emits that column as the section\'s `against`, and the balance line\nunder the rows reads the total against it. A total read against its own sum\nwould balance at zero by construction, so a rollup no measure reads closes the\nbook on its total alone. A `summary` on this clause is refused naming `against`.\n`"draw": "worksheet"`: the child\'s rows\nare PRICED LINES the reader works down in place, each part of the job footed and\nthe sheet closing under them. `cost` and `sell` name the child\'s two figures,\nwhich is the one thing the roles cannot decide \u2014 an entity carries one `amount`,\nand a line that is costed and sold carries two. Everything else is read off the\nchild\'s own roles: what a line is FOR is its `identity`, how many it is for is\nthe `measure` the pair left, and the part it falls under is its `category`. The\nMARGIN is on none of them, because it is arithmetic over the pair.\n\n`"draw": "claim"`: the child\'s rows are the LINES OF ONE PERIOD\'S CLAIM against\na priced schedule \u2014 each read as what the contract holds, what the periods\nbefore claimed, what this one claims, what that comes to to date, the share done\nand what is left, with a retention held back under the total. Four figures, and\nthree of them are quantities no role tells apart, so the clause names each:\n`quantity` (THIS period\'s, the one cell the reader edits \u2014 a `number` nothing\ncomputes, written through the line\'s own update), `contract` and `price`, and\n`previous` \u2014 what the periods before claimed on the line, cumulative. Every\namount is arithmetic over those four, so no column states one; `unit` optionally\nnames what the line is counted in, the line\'s `reference` is its code, and\n`retention` names a percentage field of THIS record, the share held back.\n\n`previous` is DERIVED, and a `number` there is refused: a cumulative somebody\ntypes is right until the first earlier period is corrected, and wrong on every\nclaim after it with nothing saying so. It is a `rollup` SUMMING THIS PERIOD\'S\nQUANTITY OVER THE SAME ITEM\'S EARLIER LINES \u2014 a line per contract item per\nperiod, each linked (a many-row link of the line to its own entity) to that\nitem\'s line in every period before. Never a lookup of the prior line\'s own\nrunning total: that total is worked out from the lookup, so the column is\ncomputed from itself, has no order to compute in, and is refused as a cycle.\n\n```json\n{\n  "entities": [\n    { "alias": "item", "label": "Items", "fields": [\n      { "alias": "name", "label": "Item", "type": "text", "required": true },\n      { "alias": "unit", "label": "Unit", "type": "text" },\n      { "alias": "quantity", "label": "Contract quantity", "type": "number" },\n      { "alias": "price", "label": "Unit price", "type": "number", "format": "currency", "currency": "USD" } ] },\n    { "alias": "claim", "label": "Claims", "singular": "Claim", "fields": [\n      { "alias": "name", "label": "Claim", "type": "text", "required": true },\n      { "alias": "stage", "label": "Stage", "type": "select", "options": [\n        { "alias": "draft", "label": "Draft", "color": "slate" },\n        { "alias": "certified", "label": "Certified", "color": "green" } ] },\n      { "alias": "retention", "label": "Retention", "type": "number", "format": "percentage" },\n      { "alias": "lines", "label": "Claim lines", "type": "select_record_link", "target_entity": "claim_line",\n        "cardinality": "many", "sync_both_ways": true, "paired_field_alias": "claim" } ] },\n    { "alias": "claim_line", "label": "Claim lines", "fields": [\n      { "alias": "claim", "label": "Claim", "type": "select_record_link", "target_entity": "claim",\n        "cardinality": "one", "required": true, "sync_both_ways": true, "paired_field_alias": "lines" },\n      { "alias": "item", "label": "Item", "type": "select_record_link", "target_entity": "item",\n        "cardinality": "one", "required": true, "display_field_aliases": ["name"] },\n      { "alias": "earlier", "label": "Earlier lines", "type": "select_record_link", "target_entity": "claim_line" },\n      { "alias": "quantity", "label": "This period", "type": "number" },\n      { "alias": "claimed_before", "label": "Claimed before", "type": "rollup", "source_field_alias": "earlier",\n        "aggregate_option": { "operation": "sum", "field_key": "quantity" } },\n      { "alias": "contract_quantity", "label": "Contract quantity", "type": "lookup",\n        "source_field_alias": "item", "lookup_field_alias": "quantity" },\n      { "alias": "unit_price", "label": "Unit price", "type": "lookup", "source_field_alias": "item", "lookup_field_alias": "price" },\n      { "alias": "unit", "label": "Unit", "type": "lookup", "source_field_alias": "item", "lookup_field_alias": "unit" } ] }\n  ],\n  "field_roles": {\n    "item": { "name": "identity" },\n    "claim": { "name": "identity",\n               "stage": { "role": "lifecycle", "outcomes": ["certified"],\n                          "phases": [{ "label": "Claiming", "stages": ["draft"] }], "history": true } },\n    "claim_line": { "item": "identity", "claim": "parent" }\n  },\n  "apps": [\n    { "alias": "claims", "name": "Claims",\n      "screen": { "alias": "claims", "label": "Claims", "shape": "lifecycle_desk", "entity": "claim",\n        "sections": { "claim_line": { "draw": "claim", "quantity": "quantity", "contract": "contract_quantity",\n          "price": "unit_price", "previous": "claimed_before", "unit": "unit", "retention": "retention" } } } }\n  ]\n}\n```\n\nThe workflow that opens a period writes its lines and links each to the same\nitem\'s lines before it; from then on a correction to any period reaches every\nlater claim through the rollup by itself. The draw is over rows the record OWNS,\nlike a sheet\'s.\n\n`"draw": "tree"`: the rows nested under each other through `nest`, a one-row\nlink of the CHILD to itself \u2014 a record\'s breakdown drawn as its outline, each\nrow folding what it holds and the money summed up the tree the way a register\'s\n`layout: "tree"` sums it. Unlike the other draws it is an arrangement and not a\nwrite, so it reads rows reaching the record through any link; a relation the\nrecord only counts has no rows here to nest and is refused.\n\n`"draw": "gantt"`: the rows as bars across the calendar \u2014 a record\'s own\nschedule, drawn by the rules a register\'s `layout: "gantt"` is. Each bar starts\non the child\'s `when` and runs the days its `measure` that `counts` days states,\nor to `until`; `nest`, `depends_on` and `baseline` fold, link and ghost the bars\nexactly as the register\'s clauses of the same names do, over the child\'s own\ncolumns, and are refused for the same reasons. Rows none of which a day or a\nplan places are listed as a register lists them.\n\n`"draw": "curve"`: two number fields of the rows, `planned` and `actual`, each\nadded up to date along the child\'s `when` and drawn as two lines \u2014 the S-curve of\na record\'s own work, read as `summary.curve` reads a register\'s. The actual line\nstops at the last day a row stated one, and a curve against itself, over rows\nwith no `when` or over anything but numbers is refused. Both are arrangements\nlike a tree: they read the rows through any link the record lists them by.\n\n```jsonc\n// A job\'s work breakdown as its schedule, and its value earned against plan.\n"sections": { "task": { "draw": "gantt", "nest": "part_of", "depends_on": "after",\n                        "baseline": { "start": "planned_start", "end": "planned_finish" } } }\n"sections": { "task": { "draw": "curve", "planned": "planned_value", "actual": "earned_value" } }\n```\n\n`"draw": "log"` and `"draw": "itinerary"` PLACE a child\'s fields on the entry\nits rows are read as, where the roles\' placement is not the reading. A log\'s\nentry and a run\'s stop are ONE anatomy \u2014 a `name` that leads, `words` under it,\nat most two supporting `lines` of at most four fields each, a `badge` at the\nright that is one select\'s option, a `figure` at the head, `evidence` shown\nunder the words and `detail` behind one fold \u2014 and the roles decide every rung\nby themselves. On a LOG the `identity` leads, the `body` is the words, the\n`recording` is the evidence, the `verbatim` the detail, the selects, the parties\nand the `contact` make the one line, the `amount` is the figure, and nothing\nwears the badge \u2014 an entry has no stage. On a RUN the `identity` leads, the\n`slot` and the first `party` make the first line, the `amount` is a second line\nof money words, and the `lifecycle` wears the badge. The `category` is on no\nrung: the name and the mark already say what the stop is and its own record has\nthe rest, so a clause places it where a business reads its stops by kind. The\nentry\'s day is its axis and never a run of a line.\n\nSo the clause is for the field a role cannot place: a photo that is the\nevidence rather than an attachment, a headcount worn as the `figure`, a line read\nby two words instead of five, a stop\'s hours or its kind on its line.\nEach rung named replaces that rung whole; a rung left out keeps the roles\'\nanswer minus whatever the clause placed elsewhere, so a field is drawn once on\nan entry \u2014 an `amount` the clause reads on a line is no longer the figure at the\nhead. A field the clause places is never also a fact under the words, and one\nthe roles placed on a rung the clause rewrote without it is a fact again \u2014 a\n`verbatim` left off the `detail` is read by its label, and folds nothing. A\nfield the child lacks, one placed on two rungs, the entry\'s own day on any rung\n(the surface that stacks the entries draws it already), a `badge` that is not a\nsingle select, a `figure` that is not a number, and on a run the stage on any\nrung but the badge or a line, or a `badge` naming another select while no line\nreads the stage, are each refused naming the places. `words` may make rows a log that the roles would not \u2014 a plain text with\nno `body` role \u2014 but nothing makes rows with no day one.\n\n```jsonc\n// A site diary: the photos are what the entry shows, the crew count sits at its head,\n// and the line says only what kind of visit it was and where.\n"sections": { "visit": { "draw": "log", "evidence": ["photos"], "figure": "crew", "lines": [["kind", "site"]] } }\n```\n\n```jsonc\n// A cleaning round: the stop is read by its hours and the flat, and the stage stays on the badge.\n"sections": { "visit": { "draw": "itinerary", "lines": [["hours", "flat"]] } }\n// A fitting run read by its stage on the line, with the kind of job as the badge.\n"sections": { "fitting": { "draw": "itinerary", "lines": [["window", "fitter", "status"], ["line_total"]], "badge": "handling" } }\n```\n\nA sheet is the WRITE side of a price, so it is the one child section whose cells\nare editors: a figure typed into a cell is written as a diff through the child\'s\nown update, which is the same editor the line\'s own drawer saves through. Every\nother child section is read where it is drawn and edited in the row\'s drawer. A\nline is ADDED from the section\'s heading as every child\'s row is, with the record\nit hangs under as the act\'s own context.\n\n`"draw": "publish"`: the child\'s rows are ONE RECORD STANDING ON N\nDESTINATIONS, and the section is drawn as the strip of those destinations rather\nthan as a register of the rows. A register of them is the same record listed once\nper destination with a stage beside it; what a reader wants is every destination\nthey COULD reach, each wearing what has happened there, and the one press that\nsends the ones that are ready.\n\n```jsonc\n"sections": { "pinning": {\n  "draw": "publish",\n  // The child\'s own lifecycle, all four \u2014 each is a different thing the chip\n  // says, and `queued` is the stage its flow OPENS at (a destination is queued\n  // by opening a row).\n  "states": { "queued": "waiting", "published": "up", "failed": "refused", "by_hand": "by_hand" },\n  "text": "wording",        // optional \u2014 a text on the child, what THIS destination goes out with\n  "permalink": "address",   // optional \u2014 a link-formatted text on the child, where it landed\n  "error": "fault",         // optional \u2014 a text on the child holding the platform\'s own refusal\n  "link": "source",         // optional \u2014 a link-formatted text of THIS record, the card it carries.\n                            // A network that takes a card OR a picture takes neither twice, so a plan\n                            // whose records always carry both leaves the desk nothing it can send there\n  "destination": {\n    // The destination\'s own select, and which of its options the platform can\n    // reach as which network\'s feed. An option this map leaves out is by hand.\n    "network": { "field": "surface", "options": { "page": "facebook", "feed": "instagram" } },\n    "connected": "account", // optional \u2014 a text on the destination; empty means not connected\n    // Which of THIS record\'s bodies each destination receives \u2014 the destination\'s\n    // own select, mapping ITS options to text fields here. One alias\n    // (`"bodies": "wording"`) is the model with a single body.\n    "bodies": { "field": "tongue", "options": { "near": "wording_near", "far": "wording_far" } },\n    "offered": { "field": "standing", "in": ["open"] }  // optional \u2014 which rows the strip offers; absent, every row\n  },\n  "publish": "send_pinnings", // the workflow alias the APP binds \u2014 the generator writes no body\n  "when": { "field": "state", "in": ["ready"] }  // optional \u2014 offer Publish only while THIS record stands there\n} }\n```\n\n`when` is an act\'s `when` (\xA7 Apps and screens, `acts`), read off THIS record\'s\nown lifecycle: a piece still being written is not one to send, and the desk\'s\nPublish is the one press on the page that cannot be taken back. The same refusals\nhold \u2014 a field that is not this entity\'s lifecycle, a stage it does not declare.\n\nEverything else is read off the roles: the child\'s `parent` (the record), its\n`party` (the destination entity), its `lifecycle` and its `when`; the\ndestination\'s `identity`, `mark`, `contact` (where a post put up by hand is\npasted) and `category` (what the strip folds the chips under); and this record\'s\nown `mark` (the pile the post carries). The destinations are read WHOLE, through\na query of their own, because the strip\'s point is the ones this record has not\ngone to yet \u2014 which the child\'s own read structurally cannot answer with. The\nREGISTER\'s row wears one mark per destination its record has reached, read one\npage of rows at a time; the face and the network each mark wears are read across\nthe `party` link by that read itself, so the model declares no lookup for them.\n\nA network the INSTANCE is not configured for is refused when the send\'s body is\nbound (`tool_capability_unavailable`): a check over a file cannot know which\nproviders this instance holds keys for, so the map is proven against the kit\'s\nnetworks alone and the rest is answered where the body is.\n\nA chip IS the draft, which is why the section mounts no Add: pressing an empty\ndestination opens a row, pressing a queued one takes it back, and both are\nworkflows the generator writes and binds. The create takes the RECORD and the\nDESTINATION and nothing else \u2014 every other column of one of these rows is what\nthe send writes back \u2014 and it reads the desk first, refusing a destination this\nrecord already stands on: a surface guards a second press for the life of a\nmount, and a second tab is a second mount. The withdrawal is the ONE generated\nbody that deletes, and it reads the stage first and refuses anything past the\nqueue. A delete names no column, so `app create` declares the child\'s TABLE in\n`package.json#lotics.deletes` beside the columns in `lotics.writes`, and `lotics\napp check` refuses a body that deletes from a table nothing there names. The SEND\nis the author\'s, like every other hand-off: `lotics app check`\nrefuses an alias nothing bound, and the press hands it the record and the rows it\nis sending.\n\nRefused: an alias naming no register of this record, rows the record does not\nOWN for any draw but a tree, a gantt or a curve (a line added to a history\nbelongs to the job it is about, not to what is reading it), a figure that is not a field of the child or whose role is neither\n`amount` nor `measure`, a sheet naming neither figure, one figure priced as both,\na book headed with a `summary`, and a placement over a section this record\ndraws as a register rather than as a run. A desk is refused\nfor rows that name no destination or carry no lifecycle, a state naming an option\nthat lifecycle has not got, a `queued` stage that is not the one the flow opens\nat, a destination that names no row of itself, a network the kit cannot preview,\nan option of the destination\'s own selects it has not got, and a body, an\noverride, a permalink, a refusal, a card address or a connected account that is\nnot a text field of the entity it is named on. A SECOND desk on one record is\nrefused too: the strip is every destination that record can reach, so two are two\nanswers to one question, and a row of the register wears the marks of one.\n\n`"draw": "acts"`: the child\'s rows are ACTS WAITING FOR A PERSON \u2014 a reply to\nwrite, a call to make, a message to send \u2014 and the section is drawn as a queue of\ncards rather than a register: the verb, the words already written, why now, how\nlong is left, where to reach them, and the ways an act ends. An act is an\nintention and what HAPPENED is a row of its own (the touch), so Done opens a\nsheet \u2014 what came of it, what was said, the next step \u2014 and one write files the\ntouch and closes the act.\n\n```jsonc\n"sections": { "task": {\n  "draw": "acts",\n  "heading": "Waiting on us",   // optional\n  // The child\'s own lifecycle, all three \u2014 `queued` is the stage its flow OPENS\n  // at (an act is queued by opening a row).\n  "states": { "queued": "waiting", "done": "done", "skipped": "passed" },\n  "verb": "verb",               // a single select on the child \u2014 which act this is\n  "words": "words",             // a text on the child \u2014 what to send\n  "why": "why_now",             // optional \u2014 a text on the child, why this is worth doing now\n  "reason": "pass_reason",      // optional \u2014 a text or single select on the child, why it was passed over\n  // Where each verb is done: a field of THIS record holding the address \u2014 its\n  // own, or a lookup of the person\'s \u2014 or "<link of the act>.<field>", an address\n  // on the row the act names; and how it is opened: "link" as it stands, "phone"\n  // dialled, "sms" / "email" composed, "zalo" / "whatsapp" a chat opened on the\n  // number. A verb left out is done where the reader already is.\n  "reach": { "reply": { "at": "on_post.url", "by": "link" }, "call": { "at": "prospect_phone", "by": "phone" } },\n  "withhold": "prospect_quiet", // optional \u2014 a yes/no of THIS record; while it reads yes, no act reaches out\n  "log": {\n    "became": "became",         // the child\'s link to the touch it becomes\n    "outcome": "outcome",       // a single select on the touch \u2014 the sheet\'s one-tap answer\n    // optional \u2014 per verb, the answers of `outcome` it can come to; the sheet offers only those and the body refuses the rest\n    "outcomes": { "reply": ["answered", "no_reply"] },\n    "note": "said",             // optional \u2014 a text on the touch; the act\'s own words stand in where none is written\n    "next": { "step": "next_step", "on": "next_on" },  // optional \u2014 texts/dates on the touch; a stated step is queued as the next act\n    "set": { "direction": "out", "channel": { "reply": "in_public", "call": "phone" } },  // optional \u2014 touch selects the verb decides\n    "silent": ["like"],         // optional \u2014 verbs whose doing leaves nothing to answer: closed, and no touch written\n    // optional \u2014 selects on the touch the sheet asks, per verb: one tap for a single select, a toggle per option for a multi-select\n    "ask": { "reply": ["approach", "carried"] },\n    // optional \u2014 links on the touch copied from a row the act names: "<link of the act>.<link on that row>"\n    "copy": { "venue": "on_post.venue" },\n    "moves": { "from": ["fresh"], "to": "working" }  // optional \u2014 stages of THIS record\'s lifecycle: a touch logged at one of `from` lands it at `to`\n  },\n  "cta": true                   // optional \u2014 the register\'s row wears this record\'s NEXT waiting act as its verb\n} }\n```\n\nEverything else is read off the roles: the child\'s `parent` (the record), its\n`party` (who the act is aimed at), its `lifecycle` and its `when` (the day it\nstops being worth doing, counted down on the card); the touch\'s link to this\nrecord, its link to the same party where it keeps one (the one carrying `party`\nwhere it names that entity twice), its `when` (stamped with the moment it is\nlogged), its member (who did it \u2014 the caller, never a value anybody states) and\nits text `identity` (the act\'s `why`, else its words). Where the act names\nnobody, it is done with this record\'s own `party` onto that entity: an act queued\nbefore the person was known is still done with them, and the next act is queued\nwith them.\n\n**AN ACT IS OFTEN ABOUT A ROW OF ITS OWN** \u2014 the post a reply is left under, the\nmessage it answers \u2014 and that row holds where the act is done and where the touch\nit becomes happened. A path `"<link of the act>.<field>"` reads one hop across a\nlink of the ACT holding ONE row (`cardinality: "one"`): in `reach.at` the field is\nthe address, read across the link by every read of the acts, so the card and the\nregister row wearing the next act both open it; in `log.copy` the field is a link\non that row, copied onto the touch\'s link to the same entity as the act is closed.\n`log.ask` names selects of the touch the sheet asks on the verbs listed \u2014 how it\nwas done, what it carried \u2014 each written with the touch, and only on those verbs.\n\nRefused beside the rest below: a path across a link holding several rows or onto a\nfield that row has not got, an address there that holds no words, an asked column\nthat is no select of the touch or one the log already writes, an asked verb that\nis `silent` or no option, an `outcomes` verb that is `silent` or no option or an\nanswer `outcome` does not offer, a copied column that is no link of the touch or is the\ntouch\'s own link to this record or to the person, a copy between links to\ndifferent entities, and a copy of a link naming several rows onto one that holds\none.\n\nThe generator writes and binds three bodies per queue. `create_<child>` opens an\nact from the section\'s heading \u2014 the verb (required), the words, why now and the\nday, never the person or the touch. `log_<child>` is Done: it opens the touch,\nsets the act done AND points it at that touch in ONE update \u2014 a row reading done\nwith nothing it became is exactly the gap it closes, and a table workflow waiting\non that state does not fire a second time \u2014 then queues the next act where the\nsheet states a step, by the verb the reader picked (this one\'s where they picked\nnone). With `moves`, the same run moves the record the act is under to `to`\nwhere it stood at one of `from` \u2014 read before anything is written, and moved\nonly where a touch is: reaching somebody for the first time is a stage of the\nrecord\'s own work, and a stage set by hand afterwards is one nobody sets. A\n`silent` verb\'s act is set done alone and reads done with nothing it became \u2014\nthe state such a table workflow fires on, and no move. `skip_<child>` passes it over,\nwriting the reason only where one is sent; passed-over acts are KEPT, because they\nare evidence about what the queue gets wrong. Both refuse an act that is no\nlonger waiting, read before anything is written. With `cta`, the\nregister reads the waiting acts of every row on the page in one read, soonest due\nfirst, and each row wears its next one as its verb \u2014 the one press that reaches\nthe person; that read and the touches\' own (whose live options colour the sheet)\nare declared beside the record\'s.\n\nA queue is worked IN PLACE on every door, the way a correspondence is from its\ncomposer: an act is added from the heading, its words corrected and it is closed\nfrom its own card, so a record that opens as a drawer carries the queue whole \u2014\nthe sheet that closes an act opens over the drawer.\n\nRefused: a queue on a screen stating `writes: false` (every way an act ends is a\nwrite of its row), rows with no lifecycle, a state naming an option it has not got,\na `queued` stage that is not the one the flow opens at, a verb that is not a\nsingle select beside the lifecycle, words, why or a reason that is not a text (or\nsingle select, for the reason) of the child, a `reach` key that is not a verb\noption or an address that is not a field of THIS record holding words, a\n`withhold` that is not a yes/no of this record, `cta` beside a row act already\nplaced there, and a log whose touch cannot be written: a `became` that is not a\nlink, a touch naming this record through no link or through two, an outcome that\nis not a single select of the touch, a note or step that is not a text, a day that\nis not a date, one column named for two things the log writes (the touch\'s name\nand day, what was said, the next step and its day), a `set` over a column the log\nalready writes or naming an option either select has not got, a `silent` verb\nthat is not an option, and a `moves` that names a stage this record\'s lifecycle\nhas not got (or a record with none), names its `to` among its `from`, lands at a\nstage that ENDS the flow (where the work ends is somebody\'s decision, not a\nreply\'s), lands at a stage only a workflow act\'s `moves` reaches, or moves a\nrecord the screen draws at rest (`writes: "children"`). A SECOND\nqueue on one record is refused: what a record is waiting on is one list read\nsoonest first.\n\n**A CHILD NOBODY REGISTERS IS A NOTE, not a refusal.** Where a record lists a\nchild entity no app is a register of, `scaffold check` says `"<entity>" has no\nregister \u2014 its rows are read here and created nowhere` and the plan printout\nmarks that entity `(no app)`. Rows can arrive from an import or a workflow, so\nit is a reading rather than a rule; what it catches is the register somebody\nmeant to plan and did not. Rows only the automations write (\xA7 Entity) are\nexempt, since nothing should create them. A section the record ADDS to is\nexempt, because its heading is where those rows are typed: the rows a record\nowns on a PAGE, a log on any door \u2014 an entry is written where it is read \u2014 a\nqueue of acts on any door, and a sheet, which opens its own lines. A record\nopening in a DRAWER adds none of its other owned rows, so those are noted like\nanybody else\'s.\n\n`scaffold check` prints every clause a screen states, on its own line under the\nslots, spelling the screen\'s `writes` clause `operable` \u2014 the app manifest\'s\n`lotics.writes` keeps that word, and the two are different facts: `app create`\nSEEDS the manifest from the fields the screens\' own editors write, and from then\non the app owns the declaration `lotics app check` holds its bodies to.\n\nEach shape is a `@lotics/ui` component of the same name (`LifecycleDesk`,\n`PartyRegister`, \u2026) whose props are these slots, so once the tables exist\n`lotics app create <name> --from <this file>#<app alias>` scaffolds the app with\none screen per entry, each slot reading the field the plan bound.\n\n`"shape": "custom"` is the screen no registry row covers: it declares its own\n`roles` (slot name \u2192 role), and it is emitted on `ShapeFrame` \u2014 the one anatomy\nthe six shapes above are each a configuration of \u2014 so its strip, search,\nordinal, fit budget, empty and waiting states and record door are the same ones\nthey have. It opens the record its `record` says, drawer or page, like any other.\nA bound `lifecycle` slot IS its strip, the stages in the field\'s order as on a\ndesk, so such a screen names no `tabs`. Only a lifecycle earns a strip \u2014 each\ntab a queue of work at one stage \u2014 and a screen naming any other select as\n`tabs` is refused: a kind, a book, a channel is a `filters` entry beside the\nsearch. The three shapes whose strip means something of their own take any\nselect: a reconciliation\'s dated runs, a trend\'s series, a worksheet\'s versions.\n\n**An app IS its `app.json`.** `create --from` writes the bound plan \u2014 every\nscreen with its shape and slots, the record each row opens with its sections in\nthe archetype\'s order, the create panels, the acts \u2014 as one JSON document, plus\na five-line `src/main.tsx` that mounts `@lotics/app-runtime` over it and one\n`src/workflows/<alias>.ts` per write. There is no screen source: the runtime\ndraws the spec, so a kit correction reaches every app with its next install.\nWhere the plan has no word for what a screen or a section IS \u2014 or for what a\npaper act should ASK before it is made \u2014 the spec names one of the app\'s own\ncomponents and `src/components/index.ts` registers it, the one file under `src/`\na regeneration never rewrites. `lotics app eject <screen|<section key>|<act\nlabel>>` writes each of those, starting from what the runtime already drew. What\nthe APP does rather than what a screen draws \u2014 a bridge to the page it is framed\nin, a listener \u2014 is one component `app.json#root` names: mounted once around\nevery route, and carried over by every regeneration, since the plan has no word\nfor it.\n\n**How a spec reads a row.** Each query projects its columns under the alias the\nworkspace mints from the field\'s LABEL \u2014 never the alias this file keys it\nunder, which is the model\'s own namespace and which the workspace never saw. So\na field this file calls `partner` and labels `\u0110\u1ED1i t\xE1c` is referenced as\n`doi_tac` throughout the spec. Every id in it is live: the `tbl_` a screen is\nover, the `fld_` of each column, and the `opt_` of every option a role names.\n\n**Every query is described, in the model\'s own language.** The line an agent\nchooses between aliases by is written from this file\'s nouns \u2014 the entity\'s\nlabel, the screen\'s, the link\'s \u2014 and the sentence around them is the language\nthe file is mostly written in, decided the same way a generated write\'s refusals\nare. Hand-editing one is erased by the next regeneration; `lotics app check`\nrefuses an alias that carries none.\n\nA screen is that list and the RECORD it opens, and the record comes off the same\nroles \u2014 nothing to declare for it. It opens with a **header**: the entity\'s\n`identity` as the record\'s name \u2014 whether or not the list has a column for it, so\na ledger\'s and a trend\'s records are named too \u2014 the `mark` beside it on a PAGE,\nwhich is what the subject is recognised by (so the pile below is the papers that\nare left, and a `presentation.lead` spending that gutter on something else leaves\nthe picture in the pile), the `when` this screen reads\nunder it, and ONE headline\nfigure (the `amount` the screen reads, else its `measure`). BOTH DOORS state the\nname: which door a screen uses is a layout answer, and what the record is ABOUT\nis not.\n\n**A JOB\'S HEADER ALSO STATES WHO IT IS FOR.** Where the record is the work itself\n\u2014 a desk\'s rows that belong to nothing, opened on a page \u2014 its `party` is a link\nunder the name, beside the ways to reach the subject, or, where that party is a\nworkspace MEMBER, the person themselves with no door behind them, and it is then\nnot a fact\nas well: a page headed by a code alone said nothing about whose work it is, and\nthe one thing a reader arriving from the desk already knows the row by sat in the\ngrid below as a row among forty. A record opening in a DRAWER has no row of links\nto hang it on, so its party stays a fact; so does a LINE\'s, whose register files\nit under the thing it belongs to and whose party is that parent\'s, restated per\nrow.\n\n**A record whose figures are a SENTENCE states them under the header, in a\nband**, and the header then states neither of them: a job reads what it comes to,\nhow far through it is (the `measure` against its limit), what is left of it (a\nformula that is exactly `{amount} - {measure}`) and how long there is (an\n`obligation`, else its `when`, counted down); a party reads its settlement, the\n`amount` and `measure` roles it carries in the order the model declares them; a\ncatalogue item reads its `amount` against the reference that amount names. Two\nfigures are the floor and four the ceiling \u2014 under two, the header keeps its one.\nA band is a PAGE\'s strip, so a screen whose `record` is a drawer keeps every\nfigure where a drawer reads them. Each figure is drawn exactly once: the limit a\nmeter states is not a fact beside it, and the day a countdown counts to is not\nthe provenance line above it. The band draws them, so the band is where they are\nCHANGED \u2014 a date a person states is edited on the countdown and a limit a person\nstates on the meter, while the level between them is read. The `lifecycle` is\nnot badged there, because the progress section is the rung it stands on. Then\nits sections, in the order its KIND reads them: the\n**facts** (every field neither the header, the band nor another section owns, the\nrow\'s own `parent` among them \u2014 led by the ones THIS screen\'s slots bound, then\nthe key it is filed under, then the order the model declares them in \u2014 a\n`markdown` field among them, drawn across the grid\'s whole row rather than\nwrapped to a third of it), the record\'s own **body** (that same markdown, taken\nas a section instead, ONLY where the kind leads with it: a catalogue item IS its\ndescription, and a job is not its notes), the **charge** (where the `amount` is a formula over exactly one\nquantity and one money field, the line states `quantity \xD7 unit price = amount`\nand neither figure is typed twice \u2014 the section is headed by the amount\'s own\nlabel and the closing row says what the figure IS, so the word is said once),\nthe **progress** (the `lifecycle`\'s stages as a ladder the reader ticks a rung of\nto move the record on, grouped into its `phases` where the model states them, and\neach rung carrying the day it was reached where the lifecycle keeps a\n`history`), a\n**required set** (a multi-select `expected_set`, or a child entity whose rows\ncarry one entry of it each \u2014 that child\'s `files` field is what a paper attaches\nto), the record\'s **own rows** (any other child, its role-bound fields as\ncolumns), and its **files** (every `files` field the header does not lead with,\nthe `mark` first where it keeps one \u2014 a section of\nthe column like any other, straight after the facts it is the evidence for,\nexcept on an EVIDENCE record, which OPENS on the paper it exists for; the\nheading carries the Add verb, and stands it down while the pile is empty, where\nthe drop well is already the door; and a `verdict` whose FORMULA reads one of\nthose files fields is the pile\'s OWN state rather than a fact row \u2014 the file it\nis short, drawn as a ghost, and the mark the rail sends a reader to). A child is\nan entity that LINKS here, ONE SECTION PER LINK: the rows it owns (`parent`), the\nrows NAMED by it (their `party` or their `identity` \u2014 so this record\'s history),\nand the rows reaching it through a link carrying neither role, headed by that\nlink\'s own label. A child hanging off two records therefore declares one `parent` and\nleaves the second relationship a plain link, which still gets its section.\n\n**THE ROWS A RECORD OWNS ARE ADDED AND OPENED FROM THEIR SECTION.** A `parent`\nsection\'s heading carries the Add for its rows, handing the record as the\nparent \u2014 filled, never asked. Every row opens its own record \u2014 a line of a book,\na paper on a desk, a stop on a schedule alike: where this app already routes a\npage for those rows (the register\'s own, under one of them) it is navigated to;\notherwise it is a DRAWER mounted on the record it belongs to, stepped \u25C0 \u25B6 over\nthe section\'s rows as they are drawn, with the row\'s framed editors, its ladder\nand its files, saving through `update_<child>` \u2014 the one editor those rows have,\nwhich any control the section draws over a row writes through too. Never the\n`parent` link itself: it is the key the row is FILED under, stated by the record\nthe drawer was opened from, so it is neither a fact of the drawer nor an input\nof that editor. ONE LEVEL, and only from a PAGE: a child\'s own children draw as\nthe kit\'s panel of the row, with no drawer and no Add, and a register whose own\nrecord is a DRAWER is the same for the children it owns \u2014 a drawer mounts no\ndrawer. The rule is about RECORDS INSIDE RECORDS, not about rows of one kind\nnested by a link of their own: a tree (`layout: "tree"`, `"draw": "tree"`) is one\nlist of one entity, and each of its rows opens the one record surface that entity\nalready has, at whatever depth it is drawn. **A ROW IS ADDED WHERE IT CAN BE OPENED AGAIN**, so those sections lose\ntheir Add with their drawer; a row of the register\'s OWN kind keeps it, because\nthe register\'s list opens it. A correspondence\'s entries open nothing anywhere:\nthe composer under them is the section\'s Add whatever door the record has, and\nthe answer mark is one field of the reply\'s own editor. A queue\'s acts are the\nsame on a drawer: the heading\'s Add opens one, and its card saves its words\nthrough `update_<child>`. The rows a record is merely NAMED by, and those reaching it\nthrough a roleless link, are read only \u2014 a history, never a place to open or\nadd.\n\n**TWO CHILDREN ARE READ ON A TIME AXIS RATHER THAN AS A REGISTER**, and the\nmodel says which by the roles it declares on them. A child carrying an\n`obligation` whose `satisfied_by` is a DATE \u2014 and no `lifecycle`, because an\nentity with stages of its own is a JOB being worked and its rows under another\nrecord are that record\'s lines or its history \u2014 is a **schedule**: what is\nplanned against time, and what slipped. Its rows are the ordered stops, each\nstating the day it was promised for and the day it happened, with the delta\nnamed where the rung was late \u2014 drawn as a register those are two date columns\nand the reader subtracts them by eye, which is exactly what "three days late at\ndischarge" costs to learn. An obligation closed by a FILE says nothing about\nwhen, so those rows stay the register they were.\n\n**A body and a day is a LOG** \u2014 what happened, in order: the entry in the words\nsomebody wrote, filed under the day they wrote it. The body is the child\'s\n`body`, else its first `markdown` text; the format never decides, so a plain-text\nnote declared `body` is an entry and a markdown remarks field on a job is not\n(a `lifecycle` keeps it a register, as it keeps a schedule one). A register of\nentries is a table whose one useful column is the one it cannot draw, so the rows\nare read as one time axis instead: one head per entry, the words under it, and\neverything else the row states placed on the entry. WHO WROTE IT is the\n`select_member` the row names \u2014 a log is kept by the people who work the\nrecord \u2014 and the parties on it are who it was WITH, drawn on the entry\'s line\nbeside the `contact` it reached them at and the files that came with it. The\nother selects are words on that line; the `recording` plays under the words and\nthe `verbatim` waits behind one fold; everything else a person states on the\nentry \u2014 the day\'s headcount, the gear on site, what went wrong \u2014 is drawn under\nits words by its own label, where that entry states it: an entry is the whole\ntouch. Its Add is a composer asking exactly that \u2014 the entry, its name where the\nchild names one, the recording and the verbatim, the day (opening on today), the\nentry\'s own selects and those facts; the record it hangs under is not asked.\n\n**A `verdict` on those rows makes the log a CORRESPONDENCE** \u2014 a question, its\nreplies, and the one reply marked with that yes/no as the ANSWER. It is read\nfrom the question, oldest first, where a log is read from its latest entry under\nday heads. Where no member keeps it the first `party` is who wrote each entry,\nbecause there the other side writes too; a SECOND party is who the entry was\nleft WITH, and the latest one names the ball in court: while nothing answers,\nthe record says whose move it is and counts its own deadline (an `obligation`,\nelse its `when`) against them. Whose move and the clock are read only under the\nrecord that OWNS the messages \u2014 under the party who wrote them the same rows\nare several questions at once, and the last of them says nothing about any \u2014 but\nthe answer mark is a fact of the reply wherever it is read, and it is one field\nof the reply\'s own editor. A NAMED row is an entry that OPENS \u2014 a visit or an\ninspection is a thing in its own right, read in full on a record of its own,\nmounted on the page it is read from as a register\'s row is \u2014 where an entry\nnothing names is corrected where it stands. An entity only the automations\nwrite (`writes: false`) opens that record at rest and composes nothing.\n\n**A PROFILE LEADS WITH ITS LADDER.** An account walks stages like any other work,\nso a profile carrying a `lifecycle` reads `progress` first \u2014 right under the\nband, the same place a job leads with the act that moves it \u2014 and its histories\nfollow. Under them the ladder was seven bands down a page nobody scrolls that\nfar.\n\n**NOTHING SITS BESIDE THE RECORD.** A page is ONE reading column \u2014 its fields,\nits files (a section per `files` field, under its own label), the rows it owns,\nits notes, all sections of it in the archetype\'s order \u2014 over a reserved left gutter holding a floating NAVIGATION RAIL: the way\nback, then one line per section with that section\'s category mark, and nothing\nelse. No files, no counts, no group headings. Too narrow to seat the rail, it is\none pinned bar of the same list across the top. A section HEADING never wears\nthe mark; the rail\'s line for it does.\n\n**A RELATION THE RECORD NEVER ACTS ON CLOSES THE COLUMN.** Every register that\nmerely NAMES the record is one counted line of a single last section: its label,\nhow many rows name this record (a COUNT, never a page of rows measured), and a\npress that opens the register owning them narrowed to this record. An entity\nthis app lists nowhere is a count with no door, and where every count is zero\nthe section is not drawn at all. The one exception is a PROFILE, whose history\nIS its body and stands open in the column.\n\n**Rows the record owns whose `amount` is `signed_by` a direction are a\nBOOK**, drawn as a statement \u2014 each line dated and signed, the balance under\nthem where there is more than one line to add up, labelled by the amount\'s own\nword \u2014 where the same rows on the party they\nwere transacted with stay that party\'s history, which is scanned for the line\nshort of its paperwork rather than struck to a balance. **Rows that carry a\n`when` read as RUNS**: a party\'s history under the year \u2014 and only where the rows\nin hand span more than one, since a subhead over every line of a book names the\nyear and separates nothing \u2014 and a job\'s own rows under the day they fall on,\nwhere some day holds more than one (a row per day keeps its date column), and\nwhich, where those rows also carry a `lifecycle`, is an ITINERARY rather than a\ngrouped table: the day heads the run, each row is one line (its `slot`, its name,\nits party, its stage, its `category` and `reference`, its amount), the figures end\non one edge and the run closes with their sum \u2014 unless the record\'s own BAND is a\nsum rollup over exactly these rows, which states it once already. A `category`\npaints the node the run is read down, in the option\'s own colour; a `reference`\ncloses the line with the code somebody quotes on the phone. **A `mark` LEADS the\nline with the stop\'s own picture** \u2014 a venue, a vehicle, a machine \u2014 and it is the one\nplace on a record where a child entity\'s mark is drawn at all, since no register\ncolumn is ever a picture; a line whose subject holds none is marked with its\n`category`\'s glyph instead, so the run keeps one left edge. All three are\nPROJECTED for the run whether or not the register\'s column budget would have\ndrawn them, and a mark is projected NOWHERE ELSE.\nA line\'s mark is most often the SUBJECT\'s rather than the line\'s own \u2014 the\nservice, the product, the asset it is a line of \u2014 which is a `lookup` through\nthat link onto the subject\'s own `files`, given the role on the line.\n**EACH DAY\'S HEAD CARRIES THE SECTION\'S OWN ADD** as well, handing the panel that\nday, so a line made from Tuesday opens with Tuesday answered; the heading keeps\nthe verb too, for the first line and for a day nothing is planned on yet. **THE\nKEY LEAVES THE COLUMNS where the head states the whole of it** \u2014 a day head does,\na year head states four digits of the date and the day is what the column is\nstill there to carry.\n**A run is READ FROM THE END THE READER WANTS**: a job\'s own rows and an itinerary\nascending, a book, a history and a log descending.\n**A REGISTER WHOSE `when` IS A DEADLINE IS READ FROM THE NEAR END** whatever its\nshape does \u2014 `due` (or an `until` that says where the countdown stops) makes the\ndate a promise, so the rows in breach of it lead and a row nobody dated falls\nlast. A plain `when` keeps the shape\'s own end. `scaffold check` prints the\npromise (`order: Theo d\xF5i ti\u1EBFp, overdue first`).\n\n**A DESK OVER AN ENTITY THAT CARRIES A `slot` IS ITSELF A DAY\'S RUN.** Its own\nregister is drawn under one subhead per day, sorted by that day and then by the\npart of it, and the date column goes \u2014 the subhead states it once for the whole\nrun, and a column repeating it down every line is the same value twice. Without\nit an itinerary was one flat list in whatever order the rows arrived.\nA document desk keeps its head either way \u2014 the entries it owes are its\ncontent, filed or not. The name and whatever figure is left to it are the header\'s\nalone \u2014 it states them in full, so a fact for either would be the same sentence\ntwice.\n\n**A FACT IS PRIMARY OR IT IS PROVENANCE.** An `autonumber`, a date the platform\nstamps (`derive_from`) and a date a formula works out that no role names are what\nthe SYSTEM wrote; they fold, with every optional field this record does not\nstate, behind the grid\'s ONE link. Everything a person types or picks is primary\nand is shown, empty or not, because absence is work somebody owes. **A screen\nthat named `facts.groups` has already said which:** a field in an open group is\nprimary, and one in none \u2014 or in a `folded` group \u2014 folds \u2014 grouping says what the reader decides with, and\nby saying so says the rest are not, which is why `check` refuses a plan whose\ngroups leave a stated field out: the fold is for provenance, never for a fact\nsomebody fills in. A `tier` on a `facts` entry exists only for the case that\nderivation gets provably wrong.\n\n**A `contact` field whose kind the\nmodel decides** \u2014 an email, a number, a place, a `link`-formatted text, or a\nMESSAGING APP its label names (WhatsApp, Zalo, Telegram, Viber, WeChat, Line,\nMessenger) \u2014 leaves the facts too, for the row of links under the name on a\nrecord that opens as a page; one whose kind nothing decides stays a labelled\nfact, because a scheme nobody stated is a link that opens nothing. A handle is\ndrawn under its app\'s name \u2014 the app is what identifies the person there, and a\nbare number beside an envelope says the wrong thing \u2014 and it dials only where its\nvalue IS a number.\n`check` prints the record under each screen\'s slots:\n\n```\n  Orders \u2014 lifecycle desk over Orders (12 rows) \xB7 page \xB7 tabs: Stage (New \u2192 Quoted \u2192 Confirmed \u2192 Shipped \u2192 Done)\n    stage Stage \xB7 identity Order no. \xB7 mark Photo \xB7 party Customer \xB7 amount Total \xB7 level (none \u2014 no field declares "measure") \xB7 when Due\n    record: header (Order no. \xB7 Customer) \xB7 band (Total \xB7 Shipped against Lines \xB7 Due counting down) \xB7 progress: Stage (5 stages) \xB7 facts (Ship to \xB7 \u2026 2 filed) \xB7 files: Photos \xB7 documents: Papers (Kind: 4 required) \xB7 itinerary: Order lines by Ship by at Window, read by Window \xB7 Handling / Line total, status Status (Product \xB7 Quantity \xB7 Line total) \xB7 related: Visits (count via Order)\n```\n\nThe ORDER of that line is the record\'s own, top to bottom, and it is the KIND\'s,\nand every entry of it is a section of the one column. `related:` is the counted\nline that closes it \u2014 a register the record never acts on, named and counted \u2014\nand `\u2026 N filed` is how many facts fold behind the grid\'s one link.\nA child register whose `amount` is `signed_by` a direction is a BOOK of movements\n\u2014 what the record came to rather than what it is made of \u2014 so it closes the\ncolumn rather than standing among the rows the job is made of.\n\n**A section over a child is named by the CHILD\'s own label**, because the reader\nalready knows which record they are on: "\u0110\u01A1n h\xE0ng", not "\u0110\u01A1n h\xE0ng \u2014 Kh\xE1ch h\xE0ng".\nWhere two links from one entity reach this record, that label names two sections\nand each takes its own link\'s label as a qualifier \u2014 `H\u1ED3 s\u01A1 (\u0110\u01A1n h\xE0ng)` and\n`H\u1ED3 s\u01A1 (\u0110\u01A1n g\u1ED1c)`.\n\nIn that line `documents:` is a `RecordExpectedSet`, and `lines:` a `RecordChildren` over the rows\nthis record owns \u2014 `history:` where they NAME it instead, as their `party` or their `identity`, capped at its latest 5\nwhere the record is a profile (`latest 5 of N by <day>`, the whole of them behind the foot); a required set\nwhose entries are a CHILD entity carrying files takes `kind="files"`, and the entity\'s own\nmulti-select takes `kind="items"`, since nothing attaches to an option.\n\n**A section that knows its size says so.** Where a `measure` on the record is a\n`count` rollup over the very link a rows section hangs on, the limit it is read\n`against` is how many rows that section is OWED: the printout adds `\u2014 expects\n<limit>` and the screen draws that many ghost rows until the first one lands,\ninstead of "nothing here" two bands under a count saying three are outstanding.\n\nA figure printed as `Total (USD)` is MONEY in the currency named \u2014 a `formula`\nstates it in `formula.currency`, and a `rollup` or a `lookup` inherits it from the\nfield it reads, so read those brackets: a rate that should be in dollars and is\nprinted bare will be drawn in the workspace\'s own money. Where the entity carries\na `currency` role, the ROW\'s code outranks the field\'s on every line that states\none, and a line stating none falls back to the field\'s.\n\n**A record surface can be OPERATED, and that is the default.** Every screen with\na record gets a workflow that writes its editable facts \u2014 every field a person\nstates \u2014 so the record\'s values are edited in place and its stage is advanced\nfrom the progress section. `"writes": false` makes one screen a reader: use it\nfor a screen over rows another desk owns, never as the default. A desk nobody\ncan act on is a viewer of state somebody must go and set somewhere else. A\nreader keeps the acts that only READ the row \u2014 its papers and its `export` \u2014\nand refuses every one that writes it: the quick column, the agent act, the\nhand-off on any surface, and the file an `import` would mint rows from.\n\n**`"writes": "children"` splits the record from the rows under it.** The record\nis drawn exactly as `false` draws it \u2014 the same refusals, and the register opens\nno row of its own \u2014 while every section listing the rows that record OWNS keeps\nits Add, its drawer and its own editor. Use it where one desk states the plan\nand another logs against it: the hours typed under a period the office set, the\nitems ticked under a job somebody else opened.\n\n**`"writes": "record"` is the mirror.** The record keeps every editor, its ladder,\nits files, its quick column and its acts, and the register opens rows of its\nown; every section listing the rows that record OWNS is drawn at rest \u2014 no Add,\nno drawer that saves, no composer. Use it on the desk that decides the plan and\nreads what other desks log under it. `lotics app check` refuses a child create\nor a child editor under it, and the app\'s `package.json#lotics.writes` is seeded\nwithout the child tables.\n\n**Which facts those are is the FIELD\'s answer.** Text, number, date, yes/no and\nselect are typed or picked. A `"cardinality": "one"` link is RE-POINTED, through\na picker over the target entity named by its `display_field_aliases` \u2014 else the\ntarget\'s `identity` \u2014 narrowed by what the reader types and carrying that\nentity\'s own `read_scope`, so a link the plan gives neither column is read\ninstead of offering an empty list. A files field is ATTACHED TO and DETACHED\nFROM, as the delta rather than the pile, so two readers filing at once each keep\ntheir file. A link naming SEVERAL rows is written the same way \u2014 the generated\neditor takes the rows added and the rows taken off, never the list \u2014 so two\nreaders adding at once each keep theirs. An `autonumber` and every computed\nfield are read: they are the platform\'s to write.\n\n**A one-link is that fact WHATEVER its sync.** `sync_both_ways` is one relation\nwith a field on each side, and the sides are not the same surface: the record\nthat names ONE row states it as a fact, and the MANY side is the register on the\nother entity\'s record. Declaring both directions does not give this record a\nregister of the single row its own fact already names.\n\n**The write is the record SURFACE\'s.** Its inputs are the fields that surface\noffers to save \u2014 the facts with an editor, the lifecycle its ladder advances, a\nfiles section over a stated field, and what the BAND states rather than\nreads: its countdown\'s date, and the limit under a meter where that limit is a\ncolumn a person types \u2014 never every field a person could in principle type. What\nthe header states, a limit a level folds into a meter among the FACTS, a required\nset with a section of its own and the pile a page\'s mark draws are read there, so\nno input is declared for them. A second screen over the same entity draws no\nsurface of its own and adds nothing.\n\nWhere two operable screens of one plan reach the same entity, `scaffold check`\nnames them and the apps they belong to: two desks writing one record is a\ndecision, and the split is stated on the FIELD in each app\'s\n`package.json#lotics.writes` rather than left to whoever edits second.\n\nThat workflow lands in the app as source, like every other: its body in\n`src/workflows/update_<entity>.ts` and its declaration in\n`package.json#lotics.workflows`. The two together are the binding \u2014 `lotics app\ndeploy` pushes whatever differs from what it last saw live \u2014 so the write is\nversion-controlled and travels with the app rather than being bound by hand\nafterwards.\n\nA `custom` screen declares its slots under `roles` (slot \u2192 role) and they bind\nthe same way:\n\n```jsonc\n{ "alias": "readings", "label": "Readings", "shape": "custom", "entity": "reading",\n  "roles": { "subject": "identity", "reading": "measure" } }\n```\n\n## Applying packages\n\n`apply` copies published packages into the workspace AFTER the model\'s own\ntables exist \u2014 apps over the tables you just described, and any tables of their\nown they still need. Ordered, and run by `lotics setup` and `lotics scaffold\napply` alike.\n\n```jsonc\n"apply": [\n  {\n    "package": "apg_k3nf82ldpq",\n    "bind": {                              // optional \u2014 which of YOUR tables each entity is\n      "company": { "label": "Customers", "fields": { "name": "Company name" } }\n    },\n    "no_sample_data": true                 // optional\n  }\n]\n```\n\n`bind` is keyed by the package\'s entity alias and holds the LABELS this\nworkspace uses: scaffold adopts by label, so binding points the package at the\ntables the model created instead of a second set beside them. Only naming\nmoves \u2014 a bound field must be the TYPE the package declares, or the copy is\nrefused. `lotics library list` is the shelf, and `lotics library show <apg_id>`\nlists the aliases to bind.\n\nEntries run in the order they are written, because a later one may bind onto a\ntable an earlier one created. **A refused entry stops the run and the entries\nbefore it stay** \u2014 they are separate copies, committed as they land, so the\nrefusal names them rather than leaving a caller to re-run the file and copy them\ntwice.\n\n### What a run remembers\n\nThe WORKSPACE remembers what each entity, field, select option, role and\ntemplate alias became here, plus which record each first row landed on and the\nfile each document path was uploaded as. The model file itself holds no live id\n\u2014 it is the portable half, and the same file applies to a demo workspace and to\na customer\'s \u2014 so the join lives where the things it names live, and one model\napplied to two workspaces holds two bindings that know nothing of each other.\n\nIt is the workspace\'s and not the file\'s because a model file is never\ncommitted: memory kept beside it is one author\'s disk, absent for a teammate, on\na second machine or after a delete \u2014 and every one of those goes quietly back to\nbinding by label, which is what grows the second table.\n\nEvery later verb binds through it: `apply`, `diff`, `app create --from`,\n`app regenerate --from` and `workspace build` take the remembered id first and\nfall back to a label only for an alias nothing has bound \u2014 a field you have just\nadded, or a workspace nothing has applied this model to. That is what makes a\nrelabel on EITHER side a rename rather than one thing the workspace lacks and\none the model lacks: `diff` prints one line under the alias\n(`order.state: label: model "Stage" \xB7 workspace "Giai \u0111o\u1EA1n"`), and `apply` binds\nthe thing it has always meant, reports the move and names the command that makes\nthe two agree \u2014 which side is right is yours to decide, not a reason to refuse\nthe run.\n\nA bound target the workspace no longer holds IS a refusal, by name: re-binding\nto whatever carries that label today is how the model comes to point at\nsomebody else\'s table. `lotics run restore_table` puts a deleted table back, and\n`lotics scaffold unbind <kind> <alias>` forgets the binding \u2014 after which the\nnext apply creates a new one and nothing joins it to what was there.\n\n## Presets\n\nA preset is a trade\'s model, published to be READ. An assistant reads it, asks\nat most two questions, picks a variant and writes a `model.json` from it \u2014\nnothing is copied, and a preset is a file rather than anything a workspace\ninstalls.\n\n```jsonc\n"preset": {\n  "name": "Field service",\n  "description": "Jobs, the crew that runs them, and what each one billed.",\n  "questions": ["Do you dispatch crews, or one person per job?"],  // at most 2\n  "variants": {\n    "crews": {\n      "when": "work is dispatched to crews rather than to one person",\n      "entities": [ /* tables this branch ADDS */ ],\n      "fields": { "job": [ /* fields this branch ADDS to `job` */ ] }\n    }\n  }\n}\n```\n\nVariants are **additive only**: a branch adds entities and fields and never\nremoves them, so the base is a model in its own right rather than a draft.\n`lotics scaffold check` proves the base AND every variant merged onto it, so a\npreset ships with every branch already proven \u2014 the branch nobody took is the\none that fails in the workspace of whoever takes it.\n\n`preset` is not scaffolded. `lotics setup` and `lotics scaffold apply` ignore\nit and create the base model\'s tables.\n\n`lotics scaffold export` prints a workspace that already works as one of these\nfiles \u2014 the starting point for a preset or for another business\'s model, never a\nsource of truth: it carries one business\'s words and stops describing that\nworkspace the moment either changes.\n\n## Starting from a preset\n\n`lotics library list` is the shelf of them and `lotics library show <slug>`\nprints one whole: its questions, every table as `alias \xB7 label` with each field\nas `alias:type`, and each variant as `slug \xB7 when` followed by the tables and\nfields that branch adds. When one of them is the trade in front of you, do not\ntranscribe it \u2014 name it:\n\n```jsonc\n{\n  "from": "field_service",\n  "variants": ["crews"],\n  "rename": { "job": { "label": "\u0110\u01A1n h\xE0ng", "fields": { "code": "M\xE3 \u0111\u01A1n" } } },\n  "entities": [ /* a table this business has that the preset does not */ ],\n  "rows": { "job": [ { "ref": "j1", "fields": { "code": "J-1" } } ] },\n  "field_roles": { "job": { "code": "identity" } },\n  "write_rules": { "customer": { "natural_key": ["email"] } },\n  "apps": [ /* the screens this business\'s apps will have */ ]\n}\n```\n\n- **`from`** is the preset\'s SLUG \u2014 its own file name, a lowercase slug. Naming\n  it is what makes `entities` optional; every other rule on this page is\n  unchanged, because the file is resolved into the full form and then checked and\n  applied exactly as one. A slug nothing serves is refused with the ones there\n  are, never resolved against something else.\n- **`variants`** names the branches to merge onto the base, in order. Pick the\n  one whose `when` describes what the person said; a slug the preset does not\n  declare is refused rather than ignored.\n- **`rename`** is keyed by the preset\'s entity alias and holds the labels this\n  business uses \u2014 the same shape `apply[].bind` takes, and the same rule: only\n  naming moves. An alias the preset does not declare, and a label that is\n  already another table\'s, are both refused.\n- **`entities`** are added after the rename, already in this business\'s own\n  words.\n- **`rows`**, **`field_roles`**, **`write_rules`**, **`apps`** and **`apply`**\n  mean exactly what they mean in the full form \u2014 `"rows"` are this business\'s\n  real first records,\n  `"field_roles"` may name the preset\'s fields as well as its own (a role the\n  preset declares itself is kept unless this file names the same field, or\n  clears it with `null`), `"write_rules"` the create-time clauses on either\n  (an entity this file names replaces the preset\'s whole entry for it),\n  `"apps"` the screens it will have (a preset carries none), `"apply"` the\n  packages copied in once its tables exist.\n\nThis is the ONE thing on this page that needs the network: `check` reads the\npreset it names, once. Everything after that read is the same offline check.\n\nWrite the full form when no preset is the trade.\n\n## A complete model\n\n```json\n{\n  "entities": [\n    {\n      "alias": "customer",\n      "label": "Customers",\n      "singular": "Customer",\n      "fields": [\n        { "alias": "name", "label": "Name", "type": "text", "required": true },\n        {\n          "alias": "tier",\n          "label": "Tier",\n          "type": "select",\n          "options": [\n            { "alias": "standard", "label": "Standard", "color": "slate" },\n            { "alias": "gold", "label": "Gold", "color": "amber" }\n          ],\n          "default": ["standard"]\n        },\n        {\n          "alias": "orders",\n          "label": "Orders",\n          "type": "select_record_link",\n          "target_entity": "order",\n          "cardinality": "many",\n          "sync_both_ways": true,\n          "paired_field_alias": "customer",\n          "display_field_aliases": ["code"]\n        },\n        {\n          "alias": "total_ordered",\n          "label": "Total ordered",\n          "type": "rollup",\n          "source_field_alias": "orders",\n          "aggregate_option": { "operation": "sum", "field_key": "amount" }\n        }\n      ],\n      "views": [\n        {\n          "alias": "gold",\n          "label": "Gold customers",\n          "filters": {\n            "node_type": "condition",\n            "type": "select",\n            "field_key": "tier",\n            "operator": "has_any_of",\n            "value": ["gold"]\n          },\n          "sort": [{ "field_key": "name", "order": "asc" }]\n        }\n      ]\n    },\n    {\n      "alias": "order",\n      "label": "Orders",\n      "singular": "Order",\n      "fields": [\n        { "alias": "code", "label": "Order no.", "type": "text", "unique": true },\n        { "alias": "placed_on", "label": "Placed on", "type": "date", "format": "date" },\n        {\n          "alias": "amount",\n          "label": "Amount",\n          "type": "number",\n          "format": "currency",\n          "currency": "VND"\n        },\n        {\n          "alias": "total",\n          "label": "Total with VAT",\n          "type": "formula",\n          "formula": { "expression": "{amount} * 1.1", "format": "currency", "currency": "VND" }\n        },\n        {\n          "alias": "customer",\n          "label": "Customer",\n          "type": "select_record_link",\n          "target_entity": "customer",\n          "cardinality": "one",\n          "sync_both_ways": true,\n          "paired_field_alias": "orders",\n          "display_field_aliases": ["name"]\n        }\n      ]\n    }\n  ],\n  "roles": [{ "alias": "sales", "label": "Sales" }],\n  "field_roles": {\n    "customer": { "name": "identity" },\n    "order": { "code": "identity", "placed_on": "when", "amount": "amount", "customer": "party" }\n  },\n  "apps": [\n    {\n      "alias": "customers",\n      "name": "Customers",\n      "screen": { "alias": "customers", "label": "Customers", "shape": "party_register", "entity": "customer" }\n    },\n    {\n      "alias": "orders",\n      "name": "Orders",\n      "screen": { "alias": "orders", "label": "Orders", "shape": "transaction_ledger", "entity": "order" }\n    }\n  ],\n  "rows": {\n    "customer": [\n      { "ref": "acme", "fields": { "name": "Acme Trading", "tier": "gold" } },\n      { "ref": "bluebird", "fields": { "name": "Bluebird Foods", "tier": "standard" } }\n    ],\n    "order": [\n      {\n        "ref": "so_1001",\n        "fields": {\n          "code": "SO-1001",\n          "placed_on": "@month-start+2",\n          "amount": 4200000,\n          "customer": "customer:acme"\n        }\n      },\n      {\n        "ref": "so_1002",\n        "fields": {\n          "code": "SO-1002",\n          "placed_on": "@today-3",\n          "amount": 1150000,\n          "customer": "customer:bluebird"\n        }\n      }\n    ]\n  }\n}\n```\n\n`lotics scaffold check` on this file reports\n`2 tables, 9 fields, 2 links, 1 view, 1 role, 4 rows, 2 apps`, then\nthe plan:\n\n```\nCustomers\n  Customers \u2014 party register over Customers (2 rows) \xB7 page (default) \xB7 tabs: none (default)\n    identity Name \xB7 mark (none \u2014 no field declares "mark") \xB7 contact (none \u2014 no field declares "contact") \xB7 worth (none \u2014 no field declares "measure") \xB7 risk (none \u2014 no field declares "verdict")\n    presentation: leads with nothing (default), roomy (default) \xB7 above: rows (default)\n    record: header (Name) \xB7 history: Orders (latest 5 (default) of N by Placed on) (Order no. \xB7 Placed on \xB7 Amount (VND)) \xB7 facts (Tier \xB7 Total ordered (VND))\nOrders\n  Orders \u2014 transaction ledger over Orders (2 rows) \xB7 drawer (default) \xB7 tabs: none (default)\n    when Placed on \xB7 amount Amount (VND) \xB7 reference Order no. \xB7 party Customer \xB7 classification (none \u2014 no field declares "lifecycle") \xB7 document (none \u2014 no field declares "expected_set" or "verdict")\n    order: Placed on, newest first (default) \xB7 presentation: leads with the figure (default), roomy (default) \xB7 above: Amount (VND) (default)\n    record: header (Order no. \xB7 Placed on \xB7 Amount (VND)) \xB7 facts (Placed on \xB7 Total with VAT (VND) \xB7 Customer)\n    party: Customers \u2014 opens from Customer (profile: header (Name) \xB7 history: Orders (latest 5 (default) of N by Placed on) (Order no. \xB7 Placed on \xB7 Amount (VND)) \u2014 foot: the whole register, narrowed to this record \xB7 facts (Tier \xB7 Total ordered (VND)))\nWho writes what:\n  Customers (customer, one: Customer): Customers \xB7 written from the rows of Orders: facts\n    Name: required\n  Orders (order, one: Order): Orders\n```\n\nA `party:` line is the record a NAME on a row opens. A party is not a job, so it\ngets no app of its own \u2014 but a clerk reading the orders book presses the\ncustomer and corrects the phone number there, so the app whose rows name a party\ncarries that party\'s own record beside its register\'s. It is printed in the same\ngrammar the `record:` line is, because it is the same kind of surface: a profile,\non a page, its histories capped. Which cells are the door is what `opens from`\nsays \u2014 `the name` where the register\'s subject IS the party.\n\nThe last block is the WRITERS matrix \u2014 one line per record surface the plan\nleaves operable, the word one of its rows is called, and the app whose register\nopens it. Part of the verdict rather than a diagnostic beside it: which desk\nchanges a table is answerable from the plan, and two apps on one line is the\nsplit to state in each of their `package.json#lotics.writes`. A\n`written from the rows of \u2026` clause is the other reach: the party that register\nnames, and what the app can change on it \u2014 counted apart, because several\nregisters naming one account is the model working as designed rather than a\nsplit to declare. A publish desk\'s rows get a clause of their own, because the\npress that withdraws one DELETES it \u2014 the app declares that table in\n`package.json#lotics.deletes`, and `lotics app check` refuses a body that deletes\nfrom a table it does not name. Indented under each entity are the clauses only a\ncreate meets: the cells a row cannot stand without, and what `write_rules` state.\n\nEvery `(none)` is a slot no field fills, and it says WHY: no field declares the\nrole, or several could and the plan named none of them (`(none \u2014 a, b; name\none)`). Read it as the screen a person will see. `above: \u2026 (default)` is the band\nnobody stated \u2014 the shape sums the amount its slot draws, and a plan naming its\nown figures loses the word. Neither\nentity carries a stage, a required set or files, so the rest is facts \u2014 except\nthe sections neither entity declares: the customer\'s `history:` is the orders\nthat name it as their party, and the order\'s `via Orders:` is the customers whose\n`Orders` link names it. **A link is a section, not a fact**, on the side it\npoints AT and on the side that holds it: `Customers.Orders` therefore leaves the\ncustomer\'s facts, because the section below already lists the same relation and\na link fact can only ever show the first of them. Both records state their name\nin the header and nowhere else \u2014 a ledger\'s columns are the date and the figure,\nso `Order no.` is on no column of that list and is still what the drawer behind\na line is called. `Total ordered (VND)` is the rollup inheriting the currency of\nthe column it sums: money is read off the model, never off the field\'s own line.\n';
 
 // src/scaffold_commands.ts
 function printModelReference() {
@@ -79491,6 +79583,15 @@ function resolvePlan(model) {
     return resolved.screen;
   });
 }
+function describePlacement(model, child, placed) {
+  const name = (field) => fieldName(model, child, field);
+  const lines = placed.lines.length === 0 ? "" : `, read by ${placed.lines.map((line) => line.map(name).join(" \xB7 ")).join(" / ")}`;
+  const badge = placed.badge === void 0 ? "" : `, status ${name(placed.badge)}`;
+  const figure = placed.figure === void 0 ? "" : `, figure ${name(placed.figure)}`;
+  const shows = placed.evidence.length === 0 ? "" : `, shows ${placed.evidence.map(name).join(" \xB7 ")}`;
+  const folds = placed.detail.length === 0 ? "" : `, folds ${placed.detail.map(name).join(" \xB7 ")}`;
+  return `${lines}${badge}${figure}${shows}${folds}`;
+}
 function fieldName(model, entity, field) {
   const unit = moneyOf(field, entity, model.contract.entities, model.field_roles);
   if (unit === void 0) return field.label;
@@ -79723,19 +79824,17 @@ function describeRecord2(model, resolved, register = resolved.entity.alias) {
         const run = recordItinerary(archetype, recipeSlot, section.child, model.field_roles, resolved.screen.sections);
         if (run !== void 0) {
           const at2 = run.slot === void 0 ? "" : ` at ${fieldName(model, section.child, run.slot)}`;
-          const kind = run.kind === void 0 ? "" : `, kind ${fieldName(model, section.child, run.kind)}`;
-          const face = run.providerMark === void 0 ? "" : " with their own mark";
-          const by = run.provider === void 0 ? "" : `, by ${fieldName(model, section.child, run.provider)}${face}`;
-          const lasting = run.duration === void 0 ? "" : `, lasting ${fieldName(model, section.child, run.duration)} hours`;
           const marked = run.mark === void 0 ? "" : `, marked ${fieldName(model, section.child, run.mark)}`;
-          const quoted = run.reference === void 0 ? "" : `, ref ${fieldName(model, section.child, run.reference)}`;
+          const face = run.provider === void 0 || run.providerMark === void 0 ? "" : `, ${fieldName(model, section.child, run.provider)} with their own mark`;
           const over = run.span === void 0 ? "" : `, over ${fieldName(model, section.child, run.span)} days`;
-          const read2 = run.line === void 0 ? "" : `, read by ${run.line.join(" \xB7 ")}`;
-          return `itinerary: ${rows(section.child, section.link)}${headed(drawnAs)} by ${fieldName(model, section.child, run.when)}${at2}${kind}${marked}${by}${lasting}${quoted}${over}${read2} (${labels(section.child, section.fields)})`;
+          return `itinerary: ${rows(section.child, section.link)} by ${fieldName(model, section.child, run.when)}${at2}${marked}${face}${over}${describePlacement(model, section.child, run)} (${labels(section.child, section.fields)})`;
         }
-        const heading2 = section.via === "named" ? "history" : section.via === "link" ? `via ${section.link.label}` : "lines";
+        const book = recipeSlot === "ledger" && section.via === "parent" || resolved.screen.sections?.[section.child.alias]?.draw === "ledger";
+        const readAgainst = book ? bookAgainst(resolved.entity, section.child, section.link.alias, model.field_roles) : void 0;
+        const against = readAgainst === void 0 ? "" : ` \u2014 against ${fieldName(model, resolved.entity, readAgainst)}`;
+        const heading2 = book ? "book" : section.via === "named" ? "history" : section.via === "link" ? `via ${section.link.label}` : "lines";
         const owed = section.expected === void 0 ? "" : ` \u2014 expects ${typeof section.expected === "number" ? section.expected : fieldName(model, resolved.entity, section.expected)}`;
-        return `${heading2}: ${rows(section.child, section.link)}${headed(drawnAs)} (${section.fields.length === 0 ? "none" : labels(section.child, section.fields)})${owed}`;
+        return `${heading2}: ${rows(section.child, section.link)} (${section.fields.length === 0 ? "none" : labels(section.child, section.fields)})${against}${owed}`;
       }
       // WHERE THE RECORD IS AGAINST WHERE IT SHOULD BE — the promise per rung
       // and the day it was kept, named, because a reader approving the plan
@@ -79743,33 +79842,36 @@ function describeRecord2(model, resolved, register = resolved.entity.alias) {
       case "schedule":
         return `schedule: ${rows(section.child, section.link)}${renamed(section)} \u2014 ${fieldName(model, section.child, section.planned)} against ${fieldName(model, section.child, section.actual)}`;
       // A LOG — the entry, the day it is filed under and which end it is read
-      // from, who kept it, and the line under it. The day is named because the
-      // entries are read BY it, and a reader approving the plan cannot
-      // otherwise tell which of a row's dates the log is stacked on. The
-      // parties are named as who it was WITH, because read as a column they
-      // would say whose move it is; the address and the pile close the same
-      // line, the recording plays on the entry and the verbatim sits behind
-      // its words, and none is a column either. What is left is the facts, so
-      // nothing is stated twice.
+      // from, who kept it, and where each of its parts is drawn. The day is
+      // named because the entries are read BY it, and a reader approving the
+      // plan cannot otherwise tell which of a row's dates the log is stacked
+      // on. The placement is printed because the record line reads the entry
+      // by its roles and cannot otherwise say which rung the plan moved. What
+      // is left is the facts, so nothing is stated twice.
       case "log": {
         const from = section.order === "oldest" ? ", oldest first" : ", newest first under days";
         const answers = section.answer === void 0 ? "" : `, ${fieldName(model, section.child, section.answer.official)} answers`;
         const by = section.author === void 0 ? "" : ` by ${fieldName(model, section.child, section.author)}`;
-        const met = section.with.length === 0 ? "" : `, with ${labels(section.child, section.with)}`;
-        const at2 = section.address === void 0 ? "" : `, at ${fieldName(model, section.child, section.address)}`;
-        const attached = (section.files === void 0 ? "" : `, files ${fieldName(model, section.child, section.files)}`) + (section.recording === void 0 ? "" : `, recording ${fieldName(model, section.child, section.recording)}`) + (section.verbatim === void 0 ? "" : `, verbatim ${fieldName(model, section.child, section.verbatim)}`);
+        const attached = section.files === void 0 ? "" : `, files ${fieldName(model, section.child, section.files)}`;
         const said = new Set(
-          [section.when, section.author, section.answer?.official, ...section.with, section.address, section.files].flatMap(
-            (field) => field === void 0 ? [] : [field.alias]
-          )
+          [
+            section.when,
+            section.author,
+            section.answer?.official,
+            section.files,
+            section.name,
+            section.badge,
+            section.figure,
+            ...section.lines.flat(),
+            ...section.evidence,
+            ...section.detail
+          ].flatMap((field) => field === void 0 ? [] : [field.alias])
         );
         const read2 = [...section.fields, ...section.facts].filter(
-          (field, at3, all) => !said.has(field.alias) && all.findIndex((one) => one.alias === field.alias) === at3
+          (field, at2, all) => !said.has(field.alias) && all.findIndex((one) => one.alias === field.alias) === at2
         );
         const facts = labels(section.child, read2);
-        const beside = section.line.filter((field) => field.type === "select_record_link" && !said.has(field.alias));
-        const names = beside.length === 0 ? "" : `, naming ${labels(section.child, beside)}`;
-        return `log: ${rows(section.child, section.link)}${renamed(section)} \u2014 ${fieldName(model, section.child, section.body)} on ${fieldName(model, section.child, section.when)}${from}${answers}${by}${met}${at2}${names}${attached}${facts === "" ? "" : ` (${facts})`}`;
+        return `log: ${rows(section.child, section.link)}${renamed(section)} \u2014 ${fieldName(model, section.child, section.body)} on ${fieldName(model, section.child, section.when)}${from}${answers}${by}${describePlacement(model, section.child, section)}${attached}${facts === "" ? "" : ` (${facts})`}`;
       }
       case "prose":
         return `body: ${fieldName(model, resolved.entity, section.field)}`;
@@ -79788,9 +79890,14 @@ function describeRecord2(model, resolved, register = resolved.entity.alias) {
     resolved.record,
     resolved.screen
   );
-  const once = entries2.map((entry) => describe5(entry, false));
+  const framed = (entry, named3) => {
+    const line = describe5(entry, named3);
+    const head = entry.section.kind === "children" ? entry.section.head : void 0;
+    return head === void 0 ? line : `${line} \u2014 headed by the record's ${head.map((field) => fieldName(model, resolved.entity, field)).join(", ")}`;
+  };
+  const once = entries2.map((entry) => framed(entry, false));
   const twice = new Set(once.filter((line, at2) => once.indexOf(line) !== at2));
-  const sections = entries2.map((entry, at2) => twice.has(once[at2]) ? describe5(entry, true) : once[at2]);
+  const sections = entries2.map((entry, at2) => twice.has(once[at2]) ? framed(entry, true) : once[at2]);
   const band = recordBand(resolved.screen.shape, resolved.entity, model.contract.entities, model.field_roles, resolved.record, header.levels);
   const drawn = band === void 0 ? [] : [
     band.kind === "comparison" ? `band (${fieldName(model, resolved.entity, band.value)} against ${fieldName(model, resolved.entity, band.reference)})` : `band (${band.cells.map((cell) => {
@@ -80031,38 +80138,13 @@ function describeCarried(model, resolved) {
     // alias resolved to is the half the author cannot see in their own file.
     ...sectionActLines(model, resolved, act),
     // A SHEET IS THE ONE SECTION THAT WRITES, so the plan says which register it
-    // prices and which of the child's figures is the base and which the answer —
-    // and a BOOK says what the record it is against comes to, which is the line
-    // its reader sees before the first row exists.
-    // A PUBLISH DESK states everything it is in the record line itself — the
-    // destinations, the bodies and the press — so a second clause here would be
-    // the same sentence a line apart; and a RUN'S LINE, a CLAIM and a TREE are
-    // printed by the section that draws them, beside the columns they are read off.
-    // A LOG'S PLACEMENT is printed here, rung by rung, because the record line
-    // reads the entry by its roles and cannot say which rung the plan moved.
-    ...Object.entries(resolved.screen.sections ?? {}).flatMap(([alias, drawn2]) => {
-      if (drawn2.draw === void 0 || drawn2.draw === "publish" || drawn2.draw === "itinerary" || drawn2.draw === "claim" || drawn2.draw === "tree" || drawn2.draw === "gantt" || drawn2.draw === "curve" || drawn2.draw === "acts") {
-        return [];
-      }
-      if (drawn2.draw === "log") {
-        const rungs = [
-          ["name", drawn2.name === void 0 ? [] : [drawn2.name]],
-          ["words", drawn2.words === void 0 ? [] : [drawn2.words]],
-          ["evidence", drawn2.evidence ?? []],
-          ["detail", drawn2.detail ?? []],
-          ["line", drawn2.line ?? []],
-          ["trailing", drawn2.trailing === void 0 ? [] : [drawn2.trailing]]
-        ];
-        const placed = rungs.flatMap(([rung, aliases]) => aliases.length === 0 ? [] : [`${rung} ${aliases.join(" \xB7 ")}`]);
-        return [`placed on ${alias}: ${placed.join(", ")}`];
-      }
-      return [
-        drawn2.draw === "ledger" ? `book on ${alias}: headed ${drawn2.summary.map((field) => {
-          const carried = resolved.entity.fields.find((one) => one.alias === field);
-          return carried === void 0 ? field : fieldName(model, resolved.entity, carried);
-        }).join(" \xB7 ")}` : `sheet on ${alias}: ${drawn2.cost ?? "(no cost)"} \u2192 ${drawn2.sell ?? "(no sell)"}`
-      ];
-    }),
+    // prices and which of the child's figures is the base and which the answer.
+    // Every other clause is printed by the section that draws it — a run's and
+    // a log's placement, a desk, a claim, a tree, a book — beside the columns it
+    // is read off, so a second clause here would be the same sentence a line apart.
+    ...Object.entries(resolved.screen.sections ?? {}).flatMap(
+      ([alias, drawn2]) => drawn2.draw === "worksheet" ? [`sheet on ${alias}: ${drawn2.cost ?? "(no cost)"} \u2192 ${drawn2.sell ?? "(no sell)"}`] : []
+    ),
     // WHAT THE READER OF THIS SCREEN MAY CHANGE, where it is not everything:
     // nothing at all, the rows its record owns and not the record, or the reverse.
     ...resolved.screen.writes === void 0 || resolved.screen.writes === true ? [] : [`operable: ${resolved.screen.writes === false ? "no" : resolved.screen.writes}`]