@jam-overture/loom 0.2.0 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (194) hide show
  1. package/dist/audience/compose.d.ts +112 -0
  2. package/dist/audience/compose.js +134 -0
  3. package/dist/audience/memory.d.ts +14 -0
  4. package/dist/audience/memory.js +71 -0
  5. package/dist/audience/overlay-store.d.ts +343 -0
  6. package/dist/audience/overlay-store.js +217 -0
  7. package/dist/audience/rule.d.ts +121 -0
  8. package/dist/audience/rule.js +78 -0
  9. package/dist/cli/index.d.ts +3 -4
  10. package/dist/cli/index.js +3 -4
  11. package/dist/data/adapter.d.ts +9 -1
  12. package/dist/data/adapter.js +2 -0
  13. package/dist/data/resolve.d.ts +1 -1
  14. package/dist/interpretation/anthropic.d.ts +1 -1
  15. package/dist/interpretation/anthropic.js +2 -22
  16. package/dist/interpretation/client.d.ts +1 -1
  17. package/dist/interpretation/materialize.js +67 -22
  18. package/dist/interpretation/openai-compatible.d.ts +36 -0
  19. package/dist/interpretation/openai-compatible.js +79 -0
  20. package/dist/interpretation/status.d.ts +19 -0
  21. package/dist/interpretation/status.js +26 -0
  22. package/dist/live/index.d.ts +73 -0
  23. package/dist/live/index.js +73 -0
  24. package/dist/live/pages.d.ts +187 -0
  25. package/dist/live/pages.js +161 -0
  26. package/dist/live/pull.d.ts +147 -0
  27. package/dist/live/pull.js +398 -0
  28. package/dist/live/pulling.d.ts +79 -0
  29. package/dist/live/pulling.js +117 -0
  30. package/dist/live/window.d.ts +129 -0
  31. package/dist/live/window.js +132 -0
  32. package/dist/render/addressed.d.ts +35 -0
  33. package/dist/render/addressed.js +79 -0
  34. package/dist/render/document-theme.d.ts +70 -0
  35. package/dist/render/document-theme.js +139 -0
  36. package/dist/render/editable.d.ts +15 -1
  37. package/dist/render/editable.js +13 -1
  38. package/dist/render/expected.d.ts +98 -0
  39. package/dist/render/expected.js +88 -0
  40. package/dist/render/index.d.ts +2 -0
  41. package/dist/render/index.js +2 -0
  42. package/dist/render/render.d.ts +11 -0
  43. package/dist/render/render.js +192 -46
  44. package/dist/render/request.d.ts +8 -1
  45. package/dist/render/request.js +1 -0
  46. package/dist/runtime/auto-apply-ceiling.d.ts +54 -0
  47. package/dist/runtime/auto-apply-ceiling.js +66 -0
  48. package/dist/runtime/gate.js +69 -10
  49. package/dist/runtime/index.d.ts +1 -0
  50. package/dist/runtime/index.js +1 -0
  51. package/dist/runtime/nesting.d.ts +13 -1
  52. package/dist/runtime/nesting.js +41 -24
  53. package/dist/runtime/policy-change.js +8 -2
  54. package/dist/runtime/policy-log.d.ts +5 -5
  55. package/dist/runtime/policy.d.ts +8 -6
  56. package/dist/runtime/policy.js +5 -2
  57. package/dist/runtime/repointing.js +0 -0
  58. package/dist/sdk/definition.d.ts +65 -6
  59. package/dist/sdk/definition.js +44 -0
  60. package/dist/sdk/registry.d.ts +17 -1
  61. package/dist/sdk/registry.js +39 -0
  62. package/dist/signals/acted.contract.d.ts +21 -0
  63. package/dist/signals/acted.contract.js +236 -0
  64. package/dist/signals/acted.d.ts +359 -0
  65. package/dist/signals/acted.js +135 -0
  66. package/dist/signals/agenda.d.ts +585 -0
  67. package/dist/signals/agenda.js +295 -0
  68. package/dist/signals/arrivals.contract.d.ts +21 -0
  69. package/dist/signals/arrivals.contract.js +180 -0
  70. package/dist/signals/arrivals.d.ts +375 -0
  71. package/dist/signals/arrivals.js +254 -0
  72. package/dist/signals/broadcast.d.ts +25 -15
  73. package/dist/signals/broadcast.js +209 -36
  74. package/dist/signals/collect.d.ts +137 -43
  75. package/dist/signals/collect.js +103 -36
  76. package/dist/signals/conversion.d.ts +348 -0
  77. package/dist/signals/conversion.js +235 -0
  78. package/dist/signals/correlated.contract.d.ts +24 -0
  79. package/dist/signals/correlated.contract.js +94 -0
  80. package/dist/signals/counters.d.ts +51 -0
  81. package/dist/signals/counters.js +58 -0
  82. package/dist/signals/deployment-change.d.ts +28 -4
  83. package/dist/signals/deployment-change.js +57 -16
  84. package/dist/signals/deployment.d.ts +18 -5
  85. package/dist/signals/deployment.js +37 -11
  86. package/dist/signals/door.d.ts +34 -12
  87. package/dist/signals/door.js +37 -13
  88. package/dist/signals/expire.d.ts +192 -0
  89. package/dist/signals/expire.js +213 -0
  90. package/dist/signals/frontier.d.ts +268 -0
  91. package/dist/signals/frontier.js +145 -0
  92. package/dist/signals/funnel-hours.contract.d.ts +21 -0
  93. package/dist/signals/funnel-hours.contract.js +221 -0
  94. package/dist/signals/funnel-hours.d.ts +293 -0
  95. package/dist/signals/funnel-hours.js +99 -0
  96. package/dist/signals/funnel.d.ts +60 -0
  97. package/dist/signals/funnel.js +35 -20
  98. package/dist/signals/health.d.ts +201 -4
  99. package/dist/signals/health.js +214 -2
  100. package/dist/signals/index.d.ts +19 -0
  101. package/dist/signals/index.js +19 -0
  102. package/dist/signals/inside.d.ts +190 -0
  103. package/dist/signals/inside.js +263 -0
  104. package/dist/signals/join.d.ts +56 -0
  105. package/dist/signals/join.js +60 -0
  106. package/dist/signals/journal.d.ts +112 -9
  107. package/dist/signals/kept.contract.d.ts +22 -0
  108. package/dist/signals/kept.contract.js +111 -0
  109. package/dist/signals/library-agenda-change.d.ts +324 -0
  110. package/dist/signals/library-agenda-change.js +199 -0
  111. package/dist/signals/library-agenda.d.ts +258 -0
  112. package/dist/signals/library-agenda.js +167 -0
  113. package/dist/signals/library-reach-change.d.ts +10 -0
  114. package/dist/signals/library-reach-change.js +11 -3
  115. package/dist/signals/library-senders-change.d.ts +457 -0
  116. package/dist/signals/library-senders-change.js +367 -0
  117. package/dist/signals/library-senders-reach-change.d.ts +486 -0
  118. package/dist/signals/library-senders-reach-change.js +538 -0
  119. package/dist/signals/library-senders-reach.d.ts +340 -0
  120. package/dist/signals/library-senders-reach.js +252 -0
  121. package/dist/signals/library-senders.d.ts +271 -0
  122. package/dist/signals/library-senders.js +180 -0
  123. package/dist/signals/library-word-reach-change.js +2 -6
  124. package/dist/signals/memory.js +142 -1
  125. package/dist/signals/migrate.d.ts +6 -5
  126. package/dist/signals/migrate.js +150 -6
  127. package/dist/signals/notice.d.ts +88 -33
  128. package/dist/signals/notice.js +38 -16
  129. package/dist/signals/part-pace.d.ts +378 -0
  130. package/dist/signals/part-pace.js +333 -0
  131. package/dist/signals/parts.d.ts +25 -15
  132. package/dist/signals/parts.js +32 -73
  133. package/dist/signals/postgres.js +400 -26
  134. package/dist/signals/region.d.ts +1 -1
  135. package/dist/signals/retention.d.ts +43 -21
  136. package/dist/signals/retention.js +25 -8
  137. package/dist/signals/rhythm.d.ts +302 -0
  138. package/dist/signals/rhythm.js +262 -0
  139. package/dist/signals/rollup.d.ts +127 -1
  140. package/dist/signals/rollup.js +211 -24
  141. package/dist/signals/schema.d.ts +640 -3
  142. package/dist/signals/schema.js +239 -3
  143. package/dist/signals/silences.d.ts +310 -11
  144. package/dist/signals/silences.js +243 -0
  145. package/dist/signals/subtrees.d.ts +123 -0
  146. package/dist/signals/subtrees.js +102 -0
  147. package/dist/signals/tally.d.ts +125 -4
  148. package/dist/signals/unread.d.ts +292 -0
  149. package/dist/signals/unread.js +137 -0
  150. package/dist/signals/window-agenda.d.ts +276 -0
  151. package/dist/signals/window-agenda.js +83 -0
  152. package/dist/signals/window-funnels.d.ts +88 -0
  153. package/dist/signals/window-funnels.js +47 -0
  154. package/dist/store/cache.d.ts +101 -0
  155. package/dist/store/cache.js +149 -0
  156. package/dist/store/history.d.ts +82 -0
  157. package/dist/store/history.js +36 -0
  158. package/dist/store/index.d.ts +11 -0
  159. package/dist/store/index.js +11 -0
  160. package/dist/store/migrate.d.ts +26 -0
  161. package/dist/store/migrate.js +64 -0
  162. package/dist/store/postgres-audience.d.ts +14 -0
  163. package/dist/store/postgres-audience.js +272 -0
  164. package/dist/store/postgres.d.ts +1 -0
  165. package/dist/store/postgres.js +1 -0
  166. package/dist/store/schema.d.ts +312 -0
  167. package/dist/store/schema.js +77 -0
  168. package/dist/store/source.d.ts +57 -1
  169. package/dist/store/source.js +65 -1
  170. package/dist/submit/resolve.d.ts +1 -1
  171. package/dist/telemetry/index.d.ts +1 -0
  172. package/dist/telemetry/index.js +1 -0
  173. package/dist/telemetry/journal.d.ts +32 -0
  174. package/dist/telemetry/memory.js +10 -1
  175. package/dist/telemetry/postgres.js +18 -2
  176. package/dist/telemetry/window.d.ts +135 -0
  177. package/dist/telemetry/window.js +101 -0
  178. package/dist/testing/audience-overlay-contract.d.ts +31 -0
  179. package/dist/testing/audience-overlay-contract.js +354 -0
  180. package/dist/testing/contracts.d.ts +1 -0
  181. package/dist/testing/contracts.js +1 -0
  182. package/dist/testing/journal-contract.js +158 -5
  183. package/dist/theme/contrast.d.ts +19 -14
  184. package/dist/theme/contrast.js +181 -17
  185. package/dist/tree/apply.js +13 -0
  186. package/dist/tree/mutation.d.ts +18 -0
  187. package/dist/tree/mutation.js +24 -12
  188. package/dist/tree/navigation.d.ts +5 -0
  189. package/dist/tree/navigation.js +32 -10
  190. package/dist/tree/outline.d.ts +7 -0
  191. package/dist/tree/outline.js +9 -5
  192. package/package.json +39 -96
  193. package/dist/runtime/inverse-interpreter.d.ts +0 -90
  194. package/dist/runtime/inverse-interpreter.js +0 -56
@@ -1,7 +1,7 @@
1
1
  import { sql } from "drizzle-orm";
2
2
  import { bigint, bigserial, index, integer, jsonb, pgTable, primaryKey, text, timestamp, } from "drizzle-orm/pg-core";
3
3
  /**
4
- * Five tables: the buffer batches wait in, and the four counters that outlive
4
+ * Six tables: the buffer batches wait in, and the five counters that outlive
5
5
  * them.
6
6
  *
7
7
  * The split is 0146's — raw signals are short-lived and aggregates are durable
@@ -9,11 +9,11 @@ import { bigint, bigserial, index, integer, jsonb, pgTable, primaryKey, text, ti
9
9
  * would make the retention rule a `DELETE` somebody has to remember to write
10
10
  * correctly forever.
11
11
  *
12
- * All five carry `application_id` (0269), led by it in every key and every
12
+ * All six carry `application_id` (0269), led by it in every key and every
13
13
  * index, on the same terms as the store's four: a reader is filed against the
14
14
  * application whose page they read, and no reading here spans two.
15
15
  *
16
- * All five then carry `audience_id` immediately after it
16
+ * All six then carry `audience_id` immediately after it
17
17
  * ([0284](../../decisions/0284-a-signal-names-the-audience-it-was-collected-under-and-the-predicate-stays-in-the-control-plane.md)),
18
18
  * which is the second of the two migrations
19
19
  * [0273](../../decisions/0273-the-reader-tables-take-the-application-now-and-the-audience-when-it-is-ratified.md)
@@ -72,6 +72,21 @@ export const loomReaderSignals = pgTable("loom_reader_signals", {
72
72
  receivedAt: timestamp("received_at", { withTimezone: true })
73
73
  .notNull()
74
74
  .default(sql `now()`),
75
+ /**
76
+ * When a fold counted this delivery into the counters (0351).
77
+ *
78
+ * Nullable and undefaulted, and null is a state rather than a gap: *not yet
79
+ * counted*. It is the only column on this table a second statement ever
80
+ * writes, and the only writer is the collection run — which is why the
81
+ * `UPDATE` that sets it carries `folded_at IS NULL`, so a repeat of that
82
+ * statement cannot move an instant a reading has been taken against.
83
+ *
84
+ * A row written before the column existed reads as uncounted, which is
85
+ * conservative in the one direction that matters: retention will not delete
86
+ * what nothing says was counted, so the first fold after the migration
87
+ * stamps it and the second sweep takes it.
88
+ */
89
+ foldedAt: timestamp("folded_at", { withTimezone: true }),
75
90
  }, (table) => [
76
91
  /**
77
92
  * Unchanged by the audience dimension, which is not the shape the
@@ -85,6 +100,18 @@ export const loomReaderSignals = pgTable("loom_reader_signals", {
85
100
  * serve a filter no caller expresses.
86
101
  */
87
102
  index("loom_reader_signals_tree_seq_idx").on(table.applicationId, table.treeId, table.seq),
103
+ /**
104
+ * The oldest end of the whole application, which both sweeps start from
105
+ * (0351).
106
+ *
107
+ * It did not exist while the table held an hour of deliveries, because a
108
+ * scan of an hour is cheap however it is served. The kept window makes it
109
+ * thirty days by default and invites a deployment to lengthen it, so the
110
+ * two reads that run from the oldest end across every tree — the fold's
111
+ * scan and retention's — are the two reads whose cost would have grown with
112
+ * the setting.
113
+ */
114
+ index("loom_reader_signals_seq_idx").on(table.applicationId, table.seq),
88
115
  ]);
89
116
  /**
90
117
  * One node at one revision, summed.
@@ -243,4 +270,213 @@ export const loomReaderPageViews = pgTable("loom_reader_page_views", {
243
270
  columns: [table.applicationId, table.audienceId, table.treeId, table.revision],
244
271
  }),
245
272
  ]);
273
+ /**
274
+ * Page views that began, by the hour they began in.
275
+ *
276
+ * **The sixth table, and the first in this subsystem with a clock in its
277
+ * key** — the seventh, what readers did by hour, is the other. Everything else
278
+ * here is either timeless — a tally, a funnel answer, a
279
+ * region bucket and a page-view total say *so far* and nothing about when — or
280
+ * short-lived, which is the buffer. `docs/portal-wireframes.md` asks for a
281
+ * range picker and a chart of page views by hour, and neither is answerable
282
+ * from a counter with no time in it or from a capped scan of the deliveries
283
+ * (`arrivals.ts`, which says why at length).
284
+ *
285
+ * It is written by the door, in the same transaction as the page-view total it
286
+ * slices, from the same openings — so the hours of a revision sum to its
287
+ * `opened` for every arrival counted after this table existed, and the two can
288
+ * never disagree about how many readers arrived.
289
+ *
290
+ * Keyed like every other counter — the application, the audience, the tree and
291
+ * the revision — with the hour last, so a reading for one page is a prefix scan
292
+ * and a reading for the deployment is the second index below.
293
+ */
294
+ export const loomReaderArrivals = pgTable("loom_reader_arrivals", {
295
+ /** See `loomReaderSignals.applicationId`. */
296
+ applicationId: text("application_id").notNull().default("app_default"),
297
+ /** See `loomReaderSignals.audienceId`. In the key here, as it is on the other counters. */
298
+ audienceId: text("audience_id").notNull().default("aud_everyone"),
299
+ treeId: text("tree_id").notNull(),
300
+ revision: integer("revision").notNull(),
301
+ /**
302
+ * The hour, as the instant it began, in UTC.
303
+ *
304
+ * A `timestamptz` rather than a number of hours since an epoch, so that a
305
+ * range is a `BETWEEN` an operator can read and a bucket is an instant
306
+ * every other column in this schema is comparable with. The truncation is
307
+ * the writer's, not the column's: nothing here constrains it to the hour,
308
+ * and `arrivals.ts` is the one place the unit is decided.
309
+ */
310
+ hour: timestamp("hour", { withTimezone: true }).notNull(),
311
+ /** Page views that began in this hour. Counted once, at the door, never recounted. */
312
+ views: bigint("views", { mode: "number" }).notNull(),
313
+ updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(),
314
+ }, (table) => [
315
+ primaryKey({
316
+ columns: [table.applicationId, table.audienceId, table.treeId, table.revision, table.hour],
317
+ }),
318
+ /**
319
+ * Every tree of one application, by hour, which is the deployment-wide
320
+ * chart and the only read here whose cost grows with the range.
321
+ *
322
+ * The primary key serves a reading of one page, because that read names the
323
+ * tree and the revision; a reading over the whole deployment names neither,
324
+ * and without this it would scan every row of every page to find a month.
325
+ */
326
+ index("loom_reader_arrivals_hour_idx").on(table.applicationId, table.hour),
327
+ ]);
328
+ /**
329
+ * What readers did to a part, by the hour they did it in.
330
+ *
331
+ * **The seventh table, and the second with a clock in its key.** Page views by
332
+ * hour (0356) let the portal draw a range picker and one chart; every other
333
+ * question on that screen — a goal's figure for the range, each goal's trend,
334
+ * the `By page` drawer's bars for what readers did — needs the *parts* counted
335
+ * by hour, and a tally keeps no time (`acted.ts`, which says why at length).
336
+ *
337
+ * **It holds the three delegated kinds and no others**, which is the whole of
338
+ * what keeps it affordable: `activations`, `opens`, `closes` and `completions`
339
+ * are things a reader aimed at something to cause (0167), so a row exists only
340
+ * where a reader did something. The distinct counters are not here because
341
+ * distinctness does not add across hours and the honest hourly denominator is
342
+ * the door's own arrivals; `dwell_ms` is not here because a `dwelled` signal is
343
+ * observed for every part that comes into view, so slicing it by hour would be
344
+ * thousands of rows an hour on one large page, for ever, in a table nothing
345
+ * sweeps.
346
+ *
347
+ * It is written by the fold, in the same transaction as the tallies it slices
348
+ * and from the same pass over the window — so a part's hours sum to the part's
349
+ * own counters for every window folded since this table existed.
350
+ *
351
+ * Keyed like the tallies with the hour last, so a reading of one part over a
352
+ * range is a prefix scan.
353
+ */
354
+ export const loomReaderActedHours = pgTable("loom_reader_acted_hours", {
355
+ /** See `loomReaderSignals.applicationId`. */
356
+ applicationId: text("application_id").notNull().default("app_default"),
357
+ /** See `loomReaderSignals.audienceId`. In the key here, as it is on the other counters. */
358
+ audienceId: text("audience_id").notNull().default("aud_everyone"),
359
+ treeId: text("tree_id").notNull(),
360
+ revision: integer("revision").notNull(),
361
+ nodeId: text("node_id").notNull(),
362
+ /**
363
+ * The hour, as the instant it began, in UTC — a `timestamptz` for the
364
+ * reasons `loomReaderArrivals.hour` gives, and truncated by the writer
365
+ * rather than by the column, because `arrivals.ts` is the one place the
366
+ * unit is decided.
367
+ */
368
+ hour: timestamp("hour", { withTimezone: true }).notNull(),
369
+ /** What the part is, as the latest signal about it said. Not in the key, as on a tally. */
370
+ type: text("type").notNull(),
371
+ activations: bigint("activations", { mode: "number" }).notNull().default(0),
372
+ opens: bigint("opens", { mode: "number" }).notNull().default(0),
373
+ closes: bigint("closes", { mode: "number" }).notNull().default(0),
374
+ completions: bigint("completions", { mode: "number" }).notNull().default(0),
375
+ updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(),
376
+ }, (table) => [
377
+ primaryKey({
378
+ columns: [
379
+ table.applicationId,
380
+ table.audienceId,
381
+ table.treeId,
382
+ table.revision,
383
+ table.nodeId,
384
+ table.hour,
385
+ ],
386
+ }),
387
+ /**
388
+ * **One part of one page over a range**, which is a goal's series and the
389
+ * commonest read here.
390
+ *
391
+ * The primary key cannot serve it: a goal sums every revision a part has
392
+ * had and reads every audience unless it is comparing two, so a read naming
393
+ * the tree and the part names neither of the two columns that sit between
394
+ * them in the key.
395
+ */
396
+ index("loom_reader_acted_part_idx").on(table.applicationId, table.treeId, table.nodeId, table.hour),
397
+ /**
398
+ * **Every part of one application, by hour**, which is the deployment-wide
399
+ * reading and the only one here whose cost grows with the range.
400
+ */
401
+ index("loom_reader_acted_hour_idx").on(table.applicationId, table.hour),
402
+ ]);
403
+ /**
404
+ * A funnel pair's answer, by the hour the readers in it entered the funnel.
405
+ *
406
+ * **The eighth table and the third with a clock in its key.** The funnel row
407
+ * beside it is a revision and two ends summed over every window that revision
408
+ * was folded in, which answers *the share since this step was set* (0418) and
409
+ * cannot answer *the share over these fourteen days* — the two sides a change
410
+ * is scored over (0402 clause 6), which is what `Page history` needs and had to
411
+ * read off the kept deliveries instead.
412
+ *
413
+ * The two ends are four columns rather than a reference to a configured pair,
414
+ * for the reason the funnel table's are: a deployment that stops asking a
415
+ * question keeps the answers it already has.
416
+ *
417
+ * **Both counters are distinct counts of page views, which is a thing an
418
+ * hourly table may hold exactly once**: a view is filed under the single hour
419
+ * it first reached the pair's first end in, so the hours of a window partition
420
+ * that window's answer instead of being filed once per delivery
421
+ * (`funnel-hours.ts`, which says why at length). It is written by the fold, in
422
+ * the same transaction as the answers it slices and from the same pass over the
423
+ * window, so a pair's hours sum to the pair's own row.
424
+ *
425
+ * Keyed like the funnel table with the hour last, so a reading of one pair over
426
+ * a range is a prefix scan.
427
+ */
428
+ export const loomReaderFunnelHours = pgTable("loom_reader_funnel_hours", {
429
+ /** See `loomReaderSignals.applicationId`. */
430
+ applicationId: text("application_id").notNull().default("app_default"),
431
+ /** See `loomReaderSignals.audienceId`. In the key here, as it is on the other counters. */
432
+ audienceId: text("audience_id").notNull().default("aud_everyone"),
433
+ treeId: text("tree_id").notNull(),
434
+ revision: integer("revision").notNull(),
435
+ fromNodeId: text("from_node_id").notNull(),
436
+ fromKind: text("from_kind").notNull(),
437
+ toNodeId: text("to_node_id").notNull(),
438
+ toKind: text("to_kind").notNull(),
439
+ /**
440
+ * The hour the readers in this row entered the funnel, as the instant it
441
+ * began, in UTC — a `timestamptz` for the reasons
442
+ * `loomReaderArrivals.hour` gives, and truncated by the writer rather than
443
+ * by the column.
444
+ */
445
+ hour: timestamp("hour", { withTimezone: true }).notNull(),
446
+ /** Views that satisfied the first end in this hour. */
447
+ reached: bigint("reached", { mode: "number" }).notNull(),
448
+ /** Of those, the ones that satisfied the second — whenever they did it. */
449
+ converted: bigint("converted", { mode: "number" }).notNull(),
450
+ updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(),
451
+ }, (table) => [
452
+ primaryKey({
453
+ columns: [
454
+ table.applicationId,
455
+ table.audienceId,
456
+ table.treeId,
457
+ table.revision,
458
+ table.fromNodeId,
459
+ table.fromKind,
460
+ table.toNodeId,
461
+ table.toKind,
462
+ table.hour,
463
+ ],
464
+ }),
465
+ /**
466
+ * **One pair of one page over a range**, which is a step's two sides and
467
+ * the commonest read here.
468
+ *
469
+ * The primary key cannot serve it: a step sums every revision the pair has
470
+ * been asked of — which is the whole point of comparing two fortnights
471
+ * across a change — and reads every audience unless it is comparing two,
472
+ * so a read naming the tree and the two ends names neither of the columns
473
+ * that sit between them in the key.
474
+ */
475
+ index("loom_reader_funnel_hours_pair_idx").on(table.applicationId, table.treeId, table.fromNodeId, table.toNodeId, table.hour),
476
+ /**
477
+ * **Every pair of one application, by hour**, which is the deployment-wide
478
+ * reading and the only one here whose cost grows with the range.
479
+ */
480
+ index("loom_reader_funnel_hours_hour_idx").on(table.applicationId, table.hour),
481
+ ]);
246
482
  //# sourceMappingURL=schema.js.map
@@ -1,5 +1,6 @@
1
1
  import type { ActionChangeSilence } from "./action-change.js";
2
2
  import type { ChangeSilence } from "./change.js";
3
+ import type { ConversionSilence } from "./conversion.js";
3
4
  import type { CopyChangeSilence } from "./copy-change.js";
4
5
  import type { CopySilence } from "./copy.js";
5
6
  import type { FormActionSilence } from "./form-action.js";
@@ -14,20 +15,34 @@ import type { KindCopyChangeSilence } from "./library-copy-change.js";
14
15
  import type { KindPaceSilence } from "./library-pace.js";
15
16
  import type { KindReachChangeSilence } from "./library-reach-change.js";
16
17
  import type { KindReachSilence } from "./library-reach.js";
18
+ import type { SenderFixSilence } from "./library-senders-change.js";
19
+ import type { SenderReachChangeSilence } from "./library-senders-reach-change.js";
20
+ import type { SenderReachSilence } from "./library-senders-reach.js";
21
+ import type { SenderSilence } from "./library-senders.js";
17
22
  import type { KindWordReachChangeSilence } from "./library-word-reach-change.js";
18
23
  import type { KindSilence } from "./library.js";
19
24
  import type { PaceChangeSilence } from "./pace-change.js";
20
25
  import type { PaceSilence } from "./pace.js";
21
26
  import type { ReachSilence } from "./reach.js";
27
+ import type { DayShapeSilence } from "./rhythm.js";
22
28
  /**
23
29
  * What two readings mean when they both say nothing, and whether they mean the
24
30
  * same thing.
25
31
  *
26
32
  * Every reading in this subsystem publishes a closed set of reasons a figure is
27
- * absent, and there are twenty of them. Each set's names are right in its own
28
- * sentence, and across them they overlap in two ways that a surface drawing
29
- * two readings on one card has to resolve and nothing until now would resolve
30
- * for it.
33
+ * absent. Each set's names are right in its own sentence, and across them they
34
+ * overlap in two ways that a surface drawing two readings on one card has to
35
+ * resolve and nothing until now would resolve for it.
36
+ *
37
+ * **Every set is mapped here, and that is a sweep rather than a claim.** This
38
+ * table is hand-written, so for three days it was missing two sets that had
39
+ * landed beside it — a reading of a deployment's day and a census of its silent
40
+ * senders — and nothing went red, because nothing looked for a set the table had
41
+ * never heard of. [`silence-sweep.test.ts`](silence-sweep.test.ts) reads this
42
+ * directory's source, finds every published silence set in it, and fails on one
43
+ * this module does not map (0397). A count in this prose would be the same kind
44
+ * of remembered figure, so there is none: the sweep is where the arithmetic
45
+ * lives.
31
46
  *
32
47
  * **Two names for one reason.** A window that held no page views is
33
48
  * `nothing-measured` to a before-and-after reading and `unmeasured` to a copy
@@ -110,7 +125,22 @@ export type SilenceSubject =
110
125
  * can be silent because there is none of it, which no reading whose rows come
111
126
  * from the data could ever report.
112
127
  */
113
- | "kind";
128
+ | "kind"
129
+ /**
130
+ * The run of hours a series holds, at whatever scope its counters were read.
131
+ *
132
+ * The fifth subject, and the first that is about **time** rather than about
133
+ * anything a page is made of. A fold of an hourly series is silent because the
134
+ * series holds no hour at all or because it holds no finished one, and neither
135
+ * sentence is about a page, a part, a pair or a kind — a deployment every
136
+ * reader in the world had read is in the second of them for the fifty-nine
137
+ * minutes after it starts counting.
138
+ *
139
+ * It is the series and not the range, because the two silences are facts about
140
+ * what was handed in: a range is a pair of instants and says nothing about
141
+ * whether a row was ever written under it.
142
+ */
143
+ | "series";
114
144
  export declare const SILENCE_SUBJECTS: readonly SilenceSubject[];
115
145
  /** One line per subject, for a surface naming what a reason is about. */
116
146
  export declare const describeSilenceSubject: (subject: SilenceSubject) => string;
@@ -122,7 +152,7 @@ export declare const describeSilenceSubject: (subject: SilenceSubject) => string
122
152
  * denominator are states of the deployment and not of the question asked, so
123
153
  * there is one vocabulary and not two.
124
154
  */
125
- export type SilenceVocabulary = "action-change" | "change" | "copy" | "copy-change" | "deployment" | "deployment-change" | "form-action" | "form-copy" | "forms" | "funnel-change" | "library" | "library-action" | "library-change" | "library-copy-change" | "library-pace" | "library-reach" | "library-reach-change" | "library-word-reach-change" | "pace" | "pace-change" | "reach";
155
+ export type SilenceVocabulary = "action-change" | "change" | "conversion" | "copy" | "copy-change" | "deployment" | "deployment-change" | "form-action" | "form-copy" | "forms" | "funnel-change" | "library" | "library-action" | "library-change" | "library-copy-change" | "library-pace" | "library-reach" | "library-reach-change" | "library-senders" | "library-senders-change" | "library-senders-reach" | "library-senders-reach-change" | "library-word-reach-change" | "pace" | "pace-change" | "reach" | "rhythm";
126
156
  export declare const SILENCE_VOCABULARIES: readonly SilenceVocabulary[];
127
157
  /**
128
158
  * What each reading's reasons are about.
@@ -136,10 +166,12 @@ export declare const SUBJECT_OF_VOCABULARY: Readonly<Record<SilenceVocabulary, S
136
166
  /**
137
167
  * The state of the world a silence reports, named once for the whole subsystem.
138
168
  *
139
- * Eighteen of them against a hundred and eighteen members across the
140
- * twenty-one sets, which is the overlap this module exists to state. None of them replaces a set's own name:
141
- * a reading still reports its own vocabulary, and this is what that vocabulary
142
- * means.
169
+ * Fewer of them than there are members across the sets, which is the overlap
170
+ * this module exists to state — and the figures are left to
171
+ * [`silence-sweep.test.ts`](silence-sweep.test.ts) rather than written here,
172
+ * because the two that used to be in this sentence had both gone false. None of
173
+ * them replaces a set's own name: a reading still reports its own vocabulary,
174
+ * and this is what that vocabulary means.
143
175
  *
144
176
  * **Neither the sixth set nor the seventh needed a tenth condition**
145
177
  * ([0244](../../decisions/0244-a-pace-moved-because-the-words-moved-or-the-readers-did-and-a-counterfactual-says-which.md),
@@ -333,6 +365,52 @@ export declare const SUBJECT_OF_VOCABULARY: Readonly<Record<SilenceVocabulary, S
333
365
  * reading handed both with neither asked for has nothing to hold against
334
366
  * anything. A deployment given either in place of the other goes to the wrong
335
367
  * remedy.
368
+ *
369
+ * **Three arrived together with the two sets this table had never been told
370
+ * about**
371
+ * ([0397](../../decisions/0397-every-silence-set-in-the-subsystem-is-mapped-and-a-sweep-is-what-makes-that-true.md)),
372
+ * and the reason they could not be reused is the same reason the pairs above
373
+ * are pairs.
374
+ *
375
+ * `no-reach-below` is a census of silent senders finding that **nothing under a
376
+ * part reported being reached**, so nothing it holds could witness whether it
377
+ * reports itself. Its sibling is `no-reach-reported`, which is the subject's own
378
+ * counters reporting no reach — and the two send a deployment to different
379
+ * places: that one to its senders, this one back in a week with readers. A
380
+ * reading that could not tell them apart would publish *this component is
381
+ * silent* about a component nobody has stood under.
382
+ *
383
+ * `no-hour-counted` and `no-hour-settled` are the first conditions about a
384
+ * **clock**, and they arrived with the first reading whose subject is a run of
385
+ * hours. One is a series holding no hour at all; the other is a series holding
386
+ * hours not one of which is over, which is a deployment fifty-nine minutes into
387
+ * counting and is the one state here that **fixes itself** if nothing is done.
388
+ * `no-window-folded` was the near neighbour and could not serve: it asserts that
389
+ * readers arrived, and a series can be empty because nobody came.
390
+ * **A comparison of two windows' senders brought two, and both are about a
391
+ * population rather than about a reader, a row or a word**
392
+ * ([0400](../../decisions/0400-a-comparison-of-two-windows-senders-reports-two-conditions-of-its-own-and-both-are-a-population-with-nowhere-to-stand.md)).
393
+ * A reading that holds two windows against each other at the scale of a place
394
+ * can run out of places to compare at in two ways, and the two send a
395
+ * deployment somewhere different.
396
+ *
397
+ * `nothing-checkable` is every place the subject holds still across the two
398
+ * readings being one the question could not be asked at in both of them, **with
399
+ * at least one of them holding something inside it on both sides** — so the
400
+ * remedy is readers under those places, and waiting is the thing that answers
401
+ * it. The structural half went to `nothing-inside` when the comparison split its
402
+ * member in two
403
+ * ([0414](../../decisions/0414-the-two-reasons-a-comparison-has-no-place-to-check-are-two-silences-and-the-structural-one-is-reserved.md));
404
+ * until then this condition carried both, and carrying both is what stopped it
405
+ * saying which remedy applied.
406
+ *
407
+ * `nothing-claimed` is the places being checkable in both and every one of them
408
+ * unclaimed on a side: something stood there, something was under it, and what
409
+ * it reported was neither the thing asked about nor its absence
410
+ * ([0282](../../decisions/0282-a-word-nothing-can-be-said-about-is-in-no-mass-and-a-page-that-reports-no-reach-has-no-mean.md)).
411
+ * Its remedy is neither more readers nor a rewrite, which is why it is not the
412
+ * condition above: the places are counted and published, and it is the
413
+ * comparison that is withheld.
336
414
  */
337
415
  export type SilenceCondition =
338
416
  /** The two readings are of different trees, so nothing in either is comparable. */
@@ -513,7 +591,98 @@ export type SilenceCondition =
513
591
  * is a window from before there was anything to split by, and there is nothing
514
592
  * a caller can do to it.
515
593
  */
516
- | "no-audience-named";
594
+ | "no-audience-named"
595
+ /**
596
+ * Every question it is asked names a part the page no longer has.
597
+ *
598
+ * A funnel question is written against two node ids and the page is then
599
+ * revised: the parts are removed, renamed or moved to another tree, and the
600
+ * counts against those ends cannot move again (0212). The noughts they report
601
+ * are indistinguishable from a funnel readers abandon, which is why the state
602
+ * has to be named rather than drawn.
603
+ *
604
+ * **The second condition here about the questions a deployment wrote rather
605
+ * than about the deployment, the window or the shape of the page** — the
606
+ * first being a page nothing asks anything of, which a comparison already
607
+ * reports as nothing carried. Only a reading keyed by what was asked can be
608
+ * in either, and the instruction this one carries is the opposite of a
609
+ * measurement to look at: the questions are what is out of date, and
610
+ * re-pointing them is the whole of the remedy.
611
+ */
612
+ | "questions-stale"
613
+ /**
614
+ * Nothing below it reported being reached, so nothing it holds can witness
615
+ * anything about it.
616
+ *
617
+ * The sibling of `no-reach-reported` and deliberately not a second spelling of
618
+ * it. That one is the subject's **own** counters reporting no reach; this one
619
+ * is about the parts **underneath** it — a placement that holds parts, none of
620
+ * which any view reported reaching. Only a reading that asks whether a part
621
+ * reports *itself* can be in it, because the witness such a reading needs is a
622
+ * reader demonstrably below the thing being checked (0382, 0393).
623
+ *
624
+ * The remedy is the opposite of its sibling's: that one is a sender to fix,
625
+ * this one is a window with nobody under the part yet, and a deployment handed
626
+ * the wrong one either rewrites a working primitive or waits for a defect that
627
+ * is already there.
628
+ */
629
+ | "no-reach-below"
630
+ /**
631
+ * No hour of it has ever been counted, so the run of hours is empty.
632
+ *
633
+ * Held apart from `no-window-folded`, which is the near neighbour and asserts
634
+ * something this does not: that readers arrived and the fold has not caught
635
+ * up. A series can be empty because nobody came, because counting began after
636
+ * the range ended, or because the range is older than what is kept — and the
637
+ * three are one state to a fold of it, which is why the condition says what is
638
+ * absent rather than why.
639
+ */
640
+ | "no-hour-counted"
641
+ /**
642
+ * It holds hours and not one of them is over.
643
+ *
644
+ * **The one condition here about a clock**, and the only one that resolves
645
+ * itself: a deployment read inside its own first hour, or over a range shorter
646
+ * than one, is in it for as long as it takes the hour to end. Every other
647
+ * condition is a state of the deployment, the window, the shape of the page or
648
+ * the questions it wrote, and none of them changes because time passed.
649
+ *
650
+ * It is not `no-hour-counted` and the distance between them is the whole
651
+ * remedy: counting is working, and the figure is one hour away from existing.
652
+ */
653
+ | "no-hour-settled"
654
+ /**
655
+ * No place it holds still across the two readings could be checked in both of
656
+ * them, and at least one of those places holds something inside it on both
657
+ * sides.
658
+ *
659
+ * The places are there, something stands inside one of them on both sides, and
660
+ * one of the two windows reported nothing under it. So the comparison has
661
+ * nowhere to stand **and readers would give it somewhere**, which is the whole
662
+ * of what this condition says and the reason it is not `nothing-inside`
663
+ * (0414): that one is the state no week of readers changes.
664
+ *
665
+ * Held apart from `nothing-carried`, which is the state where the places
666
+ * themselves did not survive the change. A state only a reading of two windows
667
+ * can be in, and what each window could speak for travels beside it so that a
668
+ * surface can say which of the two was the narrow one.
669
+ */
670
+ | "nothing-checkable"
671
+ /**
672
+ * Every place it could be compared at is unclaimed in one of the two
673
+ * readings.
674
+ *
675
+ * The population is not empty — the places were there and something was under
676
+ * them on both sides — and not one of them said anything a comparison can use:
677
+ * what each reported was neither the thing asked about nor its absence
678
+ * (0282). So nothing is claimed rather than claimed narrowly, which is the one
679
+ * thing a comparison cannot do that a reading of one window can.
680
+ *
681
+ * Its sibling is `nothing-checkable` and the instructions differ: that one is
682
+ * answered by readers on both sides, this one by a sender that reports what it
683
+ * did.
684
+ */
685
+ | "nothing-claimed";
517
686
  export declare const SILENCE_CONDITIONS: readonly SilenceCondition[];
518
687
  /**
519
688
  * One line per condition, written so that it reads after the subject it is
@@ -720,6 +889,37 @@ export declare const meaningOfKindCopyChangeSilence: (silence: KindCopyChangeSil
720
889
  * subjects (0240).
721
890
  */
722
891
  export declare const meaningOfKindPaceSilence: (silence: KindPaceSilence) => SilenceMeaning;
892
+ /**
893
+ * What a comparison of two windows' senders reports, of one kind (0394, 0414).
894
+ *
895
+ * **Two conditions of its own, and both are about running out of places rather
896
+ * than out of readers** (0400). Its first two members are the pair every
897
+ * comparison keyed by the vocabulary reports: `unplaced` is the census's
898
+ * `nothing-of-the-kind`, and `unpaired` is `nothing-carried` said of a place,
899
+ * exactly as a comparison of two windows of one library says it (0266).
900
+ *
901
+ * The next three are the population being empty, and they are three conditions
902
+ * rather than one because they are three instructions. `unwitnessable` is
903
+ * answered by nothing at all — it is a fact about the library. `uncheckable` is
904
+ * answered by readers under the places on both sides. `unclaimable` is answered
905
+ * by a sender that reports what it did. A surface handed one in place of another
906
+ * sends a deployment to rewrite pages that are fine, to wait for a week of
907
+ * readers it has already had, or to go and look at a primitive that is working.
908
+ *
909
+ * **`unwitnessable` is the census's word and `nothing-inside` said of an
910
+ * intersection, which is new and is the clause worth reading twice** (0414).
911
+ * 0400 refused the structural condition for the coarse member and was right to:
912
+ * *there is nothing inside it* is false of a library full of parts and short of
913
+ * readers. The split makes it true of what it is now said about — a kind no
914
+ * paired place of which holds anything on **both** sides. A place that held
915
+ * parts and was emptied by the release is in it, and that is deliberate: being a
916
+ * leaf on either side is a fact about a tree, so no reading of either window
917
+ * could ever have checked the place in both, and the remedy is the pages rather
918
+ * than the readers. That is what separates it from `no-reach-below`, which 0400
919
+ * also refused here and which stays refused — that one is a **measurement** of
920
+ * one window, and whether it holds depends on which window is read.
921
+ */
922
+ export declare const meaningOfSenderFixSilence: (silence: SenderFixSilence) => SilenceMeaning;
723
923
  /** What a pace reading's silence reports, of one part (0230). */
724
924
  export declare const meaningOfPaceSilence: (silence: PaceSilence) => SilenceMeaning;
725
925
  /**
@@ -803,6 +1003,105 @@ export declare const meaningOfFormActionSilence: (silence: FormActionSilence) =>
803
1003
  * that can be in a state nothing before it could reaches for a condition.
804
1004
  */
805
1005
  export declare const meaningOfFormCopySilence: (silence: FormCopySilence) => SilenceMeaning;
1006
+ /**
1007
+ * What an order of a deployment's conversions reports (0333).
1008
+ *
1009
+ * **The twenty-second set, and the second whose subject is what a deployment
1010
+ * asked rather than what it measured.** Three members are the door's three
1011
+ * (0229) at the page subject, `unsplit` is the window fault the split of two
1012
+ * forms brought (0300), and `inconsistent` is the alarm every reading of
1013
+ * counters against page views raises.
1014
+ *
1015
+ * Two are worth reading twice. `unanswered` is `no-reach-reported` said of a
1016
+ * funnel end rather than of a part — a counter that is there and reports
1017
+ * nobody arriving at it — and `stale` is the one condition this set brings:
1018
+ * every question asked of a page that the page no longer has the parts for.
1019
+ *
1020
+ * **A page nothing asks anything of is not in this set at all.** It is a
1021
+ * standing and not a silence: no figure is withheld, because no question was
1022
+ * written, and the sentence is *there is nothing here to measure* rather than
1023
+ * *this could not be measured*.
1024
+ */
1025
+ export declare const meaningOfConversionSilence: (silence: ConversionSilence) => SilenceMeaning;
1026
+ /**
1027
+ * What a reader-weighted reading of a library's silent senders reports, of one
1028
+ * kind.
1029
+ *
1030
+ * **Six members and not one new state of the world**, which is the claim this
1031
+ * table exists to make. Three of them are the census of silent senders' own
1032
+ * values, reused rather than respelled because that census is already asked of a
1033
+ * kind; the other three are the door's, said at this subject exactly as a kind's
1034
+ * share of the readers who met it says them (0256). A reading that answers a
1035
+ * question no reading here could answer, and brings no condition with it, is
1036
+ * what a mapped vocabulary is supposed to look like.
1037
+ *
1038
+ * `unwitnessed` is `no-reach-below` for the reason the sibling condition exists
1039
+ * at all: the reach it is missing is not the subject's own, and a deployment
1040
+ * handed `no-reach-reported` instead would go and rewrite a primitive that works
1041
+ * because nobody has stood under it yet.
1042
+ *
1043
+ * **The door's three are kept apart from each other here, too.** A weighted
1044
+ * figure is withheld for the whole kind when any page bearing a checkable place
1045
+ * of it cannot be scaled, and which page that was is published with a page's own
1046
+ * reason on it — so the remedy stays legible: a missing row is retention, no
1047
+ * openings is a sender, and an unfolded window is a wait.
1048
+ */
1049
+ export declare const meaningOfSenderReachSilence: (silence: SenderReachSilence) => SilenceMeaning;
1050
+ /**
1051
+ * What a comparison of two windows of a library's silent senders, among the
1052
+ * readings that got inside them, reports of one kind.
1053
+ *
1054
+ * **Not one new state of the world**, which is what a reading built out of two
1055
+ * readings that are both already mapped ought to report. The comparison of
1056
+ * places' own values are reused rather than respelled, because that comparison
1057
+ * is already asked of a kind; the rest are the door's, said at this subject
1058
+ * exactly as the reader-weighted reading of one window says them. No count of
1059
+ * them is written here: the member list is the test's to count (0400 clause 8).
1060
+ *
1061
+ * The three worth reading twice are `unwitnessable`, `uncheckable` and
1062
+ * `unclaimable`, in that order. *Nothing stands inside its places to report
1063
+ * them*, *come back with readers on both sides*, and *the places are checkable
1064
+ * and one window would not say what they did* are three instructions with three
1065
+ * remedies — nothing, waiting, and a primitive to look at — and the subsystem's
1066
+ * conditions for them keep that difference where a surface can see it (0414).
1067
+ */
1068
+ export declare const meaningOfSenderReachChangeSilence: (silence: SenderReachChangeSilence) => SilenceMeaning;
1069
+ /**
1070
+ * What a fold of an hourly series into the hours of a day reports (0389).
1071
+ *
1072
+ * **The twenty-third set, and the first whose subject is a run of hours.** It
1073
+ * brought both of its conditions, which no set had done since the first five,
1074
+ * and the reason is that it is the first reading here that is a fold of a
1075
+ * **clock** rather than of a window: its silences are the two ways a series can
1076
+ * hold no finished hour, and nothing about a page, a part, a pair or a kind can
1077
+ * be in either.
1078
+ *
1079
+ * `unmeasured` is the one worth stating. It is not `no-window-folded`, which is
1080
+ * the state it reads most like — that condition asserts readers arrived and the
1081
+ * rollup has not caught up, and an empty series is equally what a deployment
1082
+ * nobody has read looks like. Collapsing the two would have put *your rollup is
1083
+ * behind* on a deployment with no readers.
1084
+ */
1085
+ export declare const meaningOfDayShapeSilence: (silence: DayShapeSilence) => SilenceMeaning;
1086
+ /**
1087
+ * What a census of a library's silent senders reports, of one kind (0393).
1088
+ *
1089
+ * **The twenty-fourth set, and it brought exactly one condition.** Two of its
1090
+ * three members are states already here at the same subject: `unplaced` is the
1091
+ * census's `nothing-of-the-kind`, and `unwitnessable` is `nothing-inside` — a
1092
+ * kind standing only in places with no element part under them, which is the
1093
+ * eleventh set's condition said of the one question a part's own report can be
1094
+ * checked by.
1095
+ *
1096
+ * `unwitnessed` is the new one, and it is `no-reach-below` rather than
1097
+ * `no-reach-reported` because the reach it is missing is not the subject's. A
1098
+ * placement of this kind holds parts and no view reported reaching any of them,
1099
+ * so the defect this reading is about — a part on a reader's screen that said
1100
+ * nothing — cannot be seen there at all. The sibling condition would have sent a
1101
+ * deployment to its senders for a window in which nobody had stood under the
1102
+ * component.
1103
+ */
1104
+ export declare const meaningOfSenderSilence: (silence: SenderSilence) => SilenceMeaning;
806
1105
  /** How two readings' reasons for saying nothing stand to each other. */
807
1106
  export type SilenceRelation =
808
1107
  /**