@jam-overture/loom 0.1.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.
- package/README.md +3 -1
- package/dist/application/application.d.ts +109 -0
- package/dist/application/application.js +97 -0
- package/dist/application/memory.d.ts +20 -0
- package/dist/application/memory.js +79 -0
- package/dist/application/store.d.ts +101 -0
- package/dist/application/store.js +25 -0
- package/dist/audience/audience.d.ts +36 -0
- package/dist/audience/audience.js +41 -0
- package/dist/audience/compose.d.ts +112 -0
- package/dist/audience/compose.js +134 -0
- package/dist/audience/memory.d.ts +14 -0
- package/dist/audience/memory.js +71 -0
- package/dist/audience/overlay-store.d.ts +343 -0
- package/dist/audience/overlay-store.js +217 -0
- package/dist/audience/rule.d.ts +121 -0
- package/dist/audience/rule.js +78 -0
- package/dist/cli/index.d.ts +3 -4
- package/dist/cli/index.js +3 -4
- package/dist/cli/templates.js +19 -0
- package/dist/data/adapter.d.ts +9 -1
- package/dist/data/adapter.js +2 -0
- package/dist/data/plan.js +0 -0
- package/dist/data/resolution.d.ts +23 -1
- package/dist/data/resolve.d.ts +31 -4
- package/dist/data/resolve.js +11 -3
- package/dist/ids.d.ts +10 -0
- package/dist/ids.js +11 -1
- package/dist/index.d.ts +1 -0
- package/dist/index.js +1 -0
- package/dist/interpretation/anthropic.d.ts +1 -1
- package/dist/interpretation/anthropic.js +2 -22
- package/dist/interpretation/client.d.ts +1 -1
- package/dist/interpretation/materialize.js +67 -22
- package/dist/interpretation/openai-compatible.d.ts +36 -0
- package/dist/interpretation/openai-compatible.js +79 -0
- package/dist/interpretation/status.d.ts +19 -0
- package/dist/interpretation/status.js +26 -0
- package/dist/live/index.d.ts +73 -0
- package/dist/live/index.js +73 -0
- package/dist/live/pages.d.ts +187 -0
- package/dist/live/pages.js +161 -0
- package/dist/live/pull.d.ts +147 -0
- package/dist/live/pull.js +398 -0
- package/dist/live/pulling.d.ts +79 -0
- package/dist/live/pulling.js +117 -0
- package/dist/live/window.d.ts +129 -0
- package/dist/live/window.js +132 -0
- package/dist/patch.d.ts +54 -0
- package/dist/patch.js +44 -0
- package/dist/project/closing.d.ts +51 -0
- package/dist/project/closing.js +53 -0
- package/dist/project/memory.d.ts +20 -0
- package/dist/project/memory.js +97 -0
- package/dist/project/project.d.ts +90 -0
- package/dist/project/project.js +91 -0
- package/dist/project/store.d.ts +135 -0
- package/dist/project/store.js +41 -0
- package/dist/registered.d.ts +64 -0
- package/dist/registered.js +118 -0
- package/dist/render/addressed.d.ts +35 -0
- package/dist/render/addressed.js +79 -0
- package/dist/render/behaviour-adjust.d.ts +11 -19
- package/dist/render/behaviour-adjust.js +75 -21
- package/dist/render/behaviour-present.d.ts +8 -0
- package/dist/render/behaviour-present.js +57 -6
- package/dist/render/behaviour.d.ts +98 -17
- package/dist/render/behaviour.js +91 -26
- package/dist/render/control-name.d.ts +68 -0
- package/dist/render/control-name.js +37 -0
- package/dist/render/diagnostics.d.ts +72 -0
- package/dist/render/diagnostics.js +7 -0
- package/dist/render/document-theme.d.ts +70 -0
- package/dist/render/document-theme.js +139 -0
- package/dist/render/editable.d.ts +15 -1
- package/dist/render/editable.js +13 -1
- package/dist/render/expected.d.ts +98 -0
- package/dist/render/expected.js +88 -0
- package/dist/render/index.d.ts +4 -0
- package/dist/render/index.js +4 -0
- package/dist/render/reads.d.ts +11 -0
- package/dist/render/reads.js +12 -1
- package/dist/render/render.d.ts +11 -0
- package/dist/render/render.js +294 -53
- package/dist/render/request.d.ts +8 -1
- package/dist/render/request.js +1 -0
- package/dist/render/slots.d.ts +52 -0
- package/dist/render/slots.js +24 -0
- package/dist/render/theme.d.ts +54 -1
- package/dist/render/theme.js +23 -1
- package/dist/render/unshown.d.ts +152 -0
- package/dist/render/unshown.js +80 -0
- package/dist/runtime/analysis.d.ts +94 -9
- package/dist/runtime/analysis.js +54 -9
- package/dist/runtime/assessment.d.ts +36 -2
- package/dist/runtime/assessment.js +27 -2
- package/dist/runtime/auto-apply-ceiling.d.ts +54 -0
- package/dist/runtime/auto-apply-ceiling.js +66 -0
- package/dist/runtime/checks.d.ts +148 -0
- package/dist/runtime/checks.js +112 -0
- package/dist/runtime/disposition.d.ts +96 -0
- package/dist/runtime/disposition.js +46 -0
- package/dist/runtime/gate.js +91 -10
- package/dist/runtime/index.d.ts +4 -0
- package/dist/runtime/index.js +4 -0
- package/dist/runtime/irreversibility.d.ts +64 -0
- package/dist/runtime/irreversibility.js +45 -0
- package/dist/runtime/nesting.d.ts +13 -1
- package/dist/runtime/nesting.js +41 -24
- package/dist/runtime/pipeline.d.ts +43 -0
- package/dist/runtime/pipeline.js +10 -2
- package/dist/runtime/policy-change.d.ts +93 -0
- package/dist/runtime/policy-change.js +305 -0
- package/dist/runtime/policy-log.d.ts +406 -0
- package/dist/runtime/policy-log.js +285 -0
- package/dist/runtime/policy.d.ts +8 -6
- package/dist/runtime/policy.js +5 -2
- package/dist/runtime/repointing.js +0 -0
- package/dist/runtime/reversibility.d.ts +11 -9
- package/dist/runtime/stakes.d.ts +129 -1
- package/dist/runtime/stakes.js +240 -26
- package/dist/runtime/vocabulary.d.ts +164 -7
- package/dist/runtime/vocabulary.js +181 -8
- package/dist/sdk/audit.d.ts +174 -3
- package/dist/sdk/audit.js +176 -17
- package/dist/sdk/catalogue.d.ts +9 -1
- package/dist/sdk/conformance.d.ts +37 -3
- package/dist/sdk/conformance.js +25 -4
- package/dist/sdk/definition.d.ts +129 -5
- package/dist/sdk/definition.js +66 -0
- package/dist/sdk/registry.d.ts +45 -2
- package/dist/sdk/registry.js +102 -1
- package/dist/signals/acted.contract.d.ts +21 -0
- package/dist/signals/acted.contract.js +236 -0
- package/dist/signals/acted.d.ts +359 -0
- package/dist/signals/acted.js +135 -0
- package/dist/signals/action-change.d.ts +507 -0
- package/dist/signals/action-change.js +265 -0
- package/dist/signals/action.d.ts +331 -0
- package/dist/signals/action.js +182 -0
- package/dist/signals/agenda.d.ts +585 -0
- package/dist/signals/agenda.js +295 -0
- package/dist/signals/applied-window.contract.d.ts +23 -0
- package/dist/signals/applied-window.contract.js +160 -0
- package/dist/signals/arrivals.contract.d.ts +21 -0
- package/dist/signals/arrivals.contract.js +180 -0
- package/dist/signals/arrivals.d.ts +375 -0
- package/dist/signals/arrivals.js +254 -0
- package/dist/signals/arriving.d.ts +210 -0
- package/dist/signals/arriving.js +133 -0
- package/dist/signals/audiences.d.ts +528 -0
- package/dist/signals/audiences.js +255 -0
- package/dist/signals/broadcast.d.ts +33 -17
- package/dist/signals/broadcast.js +255 -32
- package/dist/signals/change.d.ts +378 -0
- package/dist/signals/change.js +327 -0
- package/dist/signals/collect.d.ts +169 -34
- package/dist/signals/collect.js +186 -38
- package/dist/signals/conversion.d.ts +348 -0
- package/dist/signals/conversion.js +235 -0
- package/dist/signals/copy-change.d.ts +553 -0
- package/dist/signals/copy-change.js +377 -0
- package/dist/signals/copy.d.ts +337 -0
- package/dist/signals/copy.js +211 -0
- package/dist/signals/correlated.contract.d.ts +24 -0
- package/dist/signals/correlated.contract.js +94 -0
- package/dist/signals/counters.d.ts +97 -0
- package/dist/signals/counters.js +160 -0
- package/dist/signals/deliver.d.ts +23 -4
- package/dist/signals/deliver.js +34 -6
- package/dist/signals/deployment-change.d.ts +395 -0
- package/dist/signals/deployment-change.js +309 -0
- package/dist/signals/deployment.d.ts +278 -0
- package/dist/signals/deployment.js +178 -0
- package/dist/signals/door.d.ts +114 -0
- package/dist/signals/door.js +77 -0
- package/dist/signals/expire.d.ts +192 -0
- package/dist/signals/expire.js +213 -0
- package/dist/signals/fold.d.ts +10 -0
- package/dist/signals/fold.js +5 -1
- package/dist/signals/form-action.d.ts +302 -0
- package/dist/signals/form-action.js +169 -0
- package/dist/signals/form-copy.d.ts +523 -0
- package/dist/signals/form-copy.js +346 -0
- package/dist/signals/forms.d.ts +247 -0
- package/dist/signals/forms.js +147 -0
- package/dist/signals/frontier.d.ts +268 -0
- package/dist/signals/frontier.js +145 -0
- package/dist/signals/funnel-change.d.ts +548 -0
- package/dist/signals/funnel-change.js +361 -0
- package/dist/signals/funnel-hours.contract.d.ts +21 -0
- package/dist/signals/funnel-hours.contract.js +221 -0
- package/dist/signals/funnel-hours.d.ts +293 -0
- package/dist/signals/funnel-hours.js +99 -0
- package/dist/signals/funnel.d.ts +592 -0
- package/dist/signals/funnel.js +231 -0
- package/dist/signals/health.d.ts +694 -0
- package/dist/signals/health.js +573 -0
- package/dist/signals/index.d.ts +60 -0
- package/dist/signals/index.js +60 -0
- package/dist/signals/ingest.d.ts +56 -1
- package/dist/signals/ingest.js +91 -1
- package/dist/signals/inside.d.ts +190 -0
- package/dist/signals/inside.js +263 -0
- package/dist/signals/join.d.ts +56 -0
- package/dist/signals/join.js +60 -0
- package/dist/signals/journal.d.ts +123 -9
- package/dist/signals/kept.contract.d.ts +22 -0
- package/dist/signals/kept.contract.js +111 -0
- package/dist/signals/kinds.d.ts +8 -6
- package/dist/signals/kinds.js +14 -6
- package/dist/signals/library-action.d.ts +430 -0
- package/dist/signals/library-action.js +336 -0
- package/dist/signals/library-agenda-change.d.ts +324 -0
- package/dist/signals/library-agenda-change.js +199 -0
- package/dist/signals/library-agenda.d.ts +258 -0
- package/dist/signals/library-agenda.js +167 -0
- package/dist/signals/library-change.d.ts +477 -0
- package/dist/signals/library-change.js +335 -0
- package/dist/signals/library-copy-change.d.ts +498 -0
- package/dist/signals/library-copy-change.js +476 -0
- package/dist/signals/library-pace.d.ts +319 -0
- package/dist/signals/library-pace.js +305 -0
- package/dist/signals/library-reach-change.d.ts +646 -0
- package/dist/signals/library-reach-change.js +542 -0
- package/dist/signals/library-reach.d.ts +377 -0
- package/dist/signals/library-reach.js +227 -0
- package/dist/signals/library-senders-change.d.ts +457 -0
- package/dist/signals/library-senders-change.js +367 -0
- package/dist/signals/library-senders-reach-change.d.ts +486 -0
- package/dist/signals/library-senders-reach-change.js +538 -0
- package/dist/signals/library-senders-reach.d.ts +340 -0
- package/dist/signals/library-senders-reach.js +252 -0
- package/dist/signals/library-senders.d.ts +271 -0
- package/dist/signals/library-senders.js +180 -0
- package/dist/signals/library-word-reach-change.d.ts +567 -0
- package/dist/signals/library-word-reach-change.js +564 -0
- package/dist/signals/library.d.ts +306 -0
- package/dist/signals/library.js +178 -0
- package/dist/signals/memory.d.ts +9 -0
- package/dist/signals/memory.js +246 -14
- package/dist/signals/migrate.d.ts +20 -4
- package/dist/signals/migrate.js +269 -8
- package/dist/signals/notice.d.ts +389 -0
- package/dist/signals/notice.js +250 -0
- package/dist/signals/pace-change.d.ts +501 -0
- package/dist/signals/pace-change.js +310 -0
- package/dist/signals/pace.d.ts +296 -0
- package/dist/signals/pace.js +291 -0
- package/dist/signals/page-views.d.ts +365 -0
- package/dist/signals/page-views.js +218 -0
- package/dist/signals/part-pace.d.ts +378 -0
- package/dist/signals/part-pace.js +333 -0
- package/dist/signals/parts.d.ts +354 -0
- package/dist/signals/parts.js +232 -0
- package/dist/signals/postgres.d.ts +16 -2
- package/dist/signals/postgres.js +753 -76
- package/dist/signals/progress.d.ts +212 -0
- package/dist/signals/progress.js +150 -0
- package/dist/signals/ratios.d.ts +108 -0
- package/dist/signals/ratios.js +40 -0
- package/dist/signals/reach.d.ts +309 -0
- package/dist/signals/reach.js +93 -0
- package/dist/signals/readable.d.ts +34 -0
- package/dist/signals/readable.js +34 -0
- package/dist/signals/readership.d.ts +381 -0
- package/dist/signals/readership.js +308 -0
- package/dist/signals/region-pages.d.ts +173 -0
- package/dist/signals/region-pages.js +62 -0
- package/dist/signals/region.d.ts +287 -0
- package/dist/signals/region.js +198 -0
- package/dist/signals/retention.d.ts +163 -0
- package/dist/signals/retention.js +75 -0
- package/dist/signals/rhythm.d.ts +302 -0
- package/dist/signals/rhythm.js +262 -0
- package/dist/signals/rollup.d.ts +194 -4
- package/dist/signals/rollup.js +0 -0
- package/dist/signals/schema.d.ts +1069 -1
- package/dist/signals/schema.js +393 -3
- package/dist/signals/signal.d.ts +237 -11
- package/dist/signals/signal.js +70 -10
- package/dist/signals/silence-census.d.ts +205 -0
- package/dist/signals/silence-census.js +87 -0
- package/dist/signals/silences.d.ts +1147 -0
- package/dist/signals/silences.js +996 -0
- package/dist/signals/subtrees.d.ts +123 -0
- package/dist/signals/subtrees.js +102 -0
- package/dist/signals/tally.d.ts +262 -12
- package/dist/signals/unread.d.ts +292 -0
- package/dist/signals/unread.js +137 -0
- package/dist/signals/window-agenda.d.ts +276 -0
- package/dist/signals/window-agenda.js +83 -0
- package/dist/signals/window-figures.d.ts +148 -0
- package/dist/signals/window-figures.js +42 -0
- package/dist/signals/window-funnels.d.ts +88 -0
- package/dist/signals/window-funnels.js +47 -0
- package/dist/signals/window.d.ts +866 -0
- package/dist/signals/window.js +693 -0
- package/dist/signals/words.d.ts +24 -0
- package/dist/signals/words.js +24 -0
- package/dist/store/cache.d.ts +101 -0
- package/dist/store/cache.js +149 -0
- package/dist/store/history.d.ts +82 -0
- package/dist/store/history.js +36 -0
- package/dist/store/index.d.ts +30 -0
- package/dist/store/index.js +30 -0
- package/dist/store/memory.d.ts +2 -1
- package/dist/store/memory.js +48 -12
- package/dist/store/migrate.d.ts +106 -0
- package/dist/store/migrate.js +323 -7
- package/dist/store/postgres-applications.d.ts +4 -0
- package/dist/store/postgres-applications.js +197 -0
- package/dist/store/postgres-audience.d.ts +14 -0
- package/dist/store/postgres-audience.js +272 -0
- package/dist/store/postgres-holds.d.ts +10 -1
- package/dist/store/postgres-holds.js +116 -101
- package/dist/store/postgres-policy-log.d.ts +14 -0
- package/dist/store/postgres-policy-log.js +240 -0
- package/dist/store/postgres-projects.d.ts +4 -0
- package/dist/store/postgres-projects.js +217 -0
- package/dist/store/postgres.d.ts +17 -1
- package/dist/store/postgres.js +60 -9
- package/dist/store/replay.d.ts +102 -1
- package/dist/store/replay.js +190 -19
- package/dist/store/reseed.d.ts +238 -0
- package/dist/store/reseed.js +308 -0
- package/dist/store/schema.d.ts +762 -2
- package/dist/store/schema.js +218 -5
- package/dist/store/source.d.ts +57 -1
- package/dist/store/source.js +65 -1
- package/dist/store/store.d.ts +29 -6
- package/dist/submit/resolve.d.ts +1 -1
- package/dist/submit/resolve.js +2 -1
- package/dist/telemetry/calibration.d.ts +25 -0
- package/dist/telemetry/calibration.js +27 -1
- package/dist/telemetry/event.d.ts +391 -33
- package/dist/telemetry/event.js +84 -20
- package/dist/telemetry/index.d.ts +2 -0
- package/dist/telemetry/index.js +2 -0
- package/dist/telemetry/journal.d.ts +104 -3
- package/dist/telemetry/journal.js +9 -0
- package/dist/telemetry/lookup.d.ts +27 -0
- package/dist/telemetry/lookup.js +18 -0
- package/dist/telemetry/memory.js +33 -1
- package/dist/telemetry/migrate.js +22 -1
- package/dist/telemetry/postgres.d.ts +10 -1
- package/dist/telemetry/postgres.js +188 -90
- package/dist/telemetry/remeasure.d.ts +78 -0
- package/dist/telemetry/remeasure.js +83 -0
- package/dist/telemetry/retention.d.ts +2 -2
- package/dist/telemetry/schema.d.ts +17 -0
- package/dist/telemetry/schema.js +27 -1
- package/dist/telemetry/sink.d.ts +2 -2
- package/dist/telemetry/window.d.ts +135 -0
- package/dist/telemetry/window.js +101 -0
- package/dist/testing/application-contract.d.ts +14 -0
- package/dist/testing/application-contract.js +270 -0
- package/dist/testing/audience-overlay-contract.d.ts +31 -0
- package/dist/testing/audience-overlay-contract.js +354 -0
- package/dist/testing/contracts.d.ts +13 -7
- package/dist/testing/contracts.js +13 -7
- package/dist/testing/definitions.d.ts +78 -0
- package/dist/testing/definitions.js +134 -9
- package/dist/testing/doubles.d.ts +103 -0
- package/dist/testing/doubles.js +143 -0
- package/dist/testing/index.d.ts +2 -2
- package/dist/testing/index.js +2 -2
- package/dist/testing/journal-contract.js +297 -6
- package/dist/testing/model-contract.d.ts +110 -0
- package/dist/testing/model-contract.js +150 -0
- package/dist/testing/policy-log-contract.d.ts +26 -0
- package/dist/testing/policy-log-contract.js +344 -0
- package/dist/testing/project-contract.d.ts +14 -0
- package/dist/testing/project-contract.js +266 -0
- package/dist/testing/reader-signal-contract.d.ts +27 -2
- package/dist/testing/reader-signal-contract.js +475 -5
- package/dist/testing/store-contract.d.ts +7 -1
- package/dist/testing/store-contract.js +84 -3
- package/dist/theme/apply.d.ts +20 -1
- package/dist/theme/apply.js +5 -3
- package/dist/theme/contrast.d.ts +19 -14
- package/dist/theme/contrast.js +181 -17
- package/dist/theme/derive.d.ts +22 -0
- package/dist/theme/derive.js +54 -1
- package/dist/theme/library.js +1 -1
- package/dist/theme/measure.d.ts +34 -0
- package/dist/theme/measure.js +30 -1
- package/dist/theme/palettes.js +7 -7
- package/dist/theme/ramp.d.ts +64 -0
- package/dist/theme/ramp.js +114 -0
- package/dist/theme/registry.d.ts +9 -0
- package/dist/theme/registry.js +11 -1
- package/dist/theme/separation.d.ts +97 -3
- package/dist/theme/separation.js +75 -0
- package/dist/tree/apply.js +13 -0
- package/dist/tree/compare.d.ts +9 -0
- package/dist/tree/compare.js +18 -0
- package/dist/tree/mutation.d.ts +18 -0
- package/dist/tree/mutation.js +24 -12
- package/dist/tree/navigation.d.ts +5 -0
- package/dist/tree/navigation.js +32 -10
- package/dist/tree/outline.d.ts +7 -0
- package/dist/tree/outline.js +9 -5
- package/dist/write/computed.d.ts +60 -0
- package/dist/write/computed.js +61 -0
- package/dist/write/held.d.ts +59 -0
- package/dist/write/index.d.ts +5 -2
- package/dist/write/index.js +5 -2
- package/dist/write/reseed.d.ts +151 -0
- package/dist/write/reseed.js +184 -0
- package/dist/write/revert.js +2 -16
- package/package.json +25 -3
- package/dist/runtime/inverse-interpreter.d.ts +0 -90
- package/dist/runtime/inverse-interpreter.js +0 -56
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
import { z } from "zod";
|
|
2
|
+
import { everyMemberOf } from "../closed-set.js";
|
|
3
|
+
import { STAKE_ORDER, stakeLevelSchema } from "./stake-level.js";
|
|
4
|
+
/**
|
|
5
|
+
* How much a policy lets an origin apply unattended, including none of it.
|
|
6
|
+
*
|
|
7
|
+
* A ceiling used to be a stake level, which made the strictest thing a
|
|
8
|
+
* deployment could say about an origin *low-stakes changes go live*. There is
|
|
9
|
+
* no level beneath `low`, so *nothing goes live, every change waits for a
|
|
10
|
+
* person* was not expressible at all — not by a lower ceiling, which does not
|
|
11
|
+
* exist, and not by `refusalFloor`, which throws the change away instead of
|
|
12
|
+
* holding it for somebody to look at.
|
|
13
|
+
*
|
|
14
|
+
* So the ceiling is its own scale: the four stake levels with one more rung
|
|
15
|
+
* below them. It lives beside the levels rather than among them because
|
|
16
|
+
* `nothing` is not a measure of damage — nothing is ever assessed at `nothing`
|
|
17
|
+
* stakes — and putting it in `STAKE_ORDER` would offer it to every reader of a
|
|
18
|
+
* level, `refusalFloor` and a role's acceptance ceiling included (0285).
|
|
19
|
+
*/
|
|
20
|
+
/**
|
|
21
|
+
* The rung below `low`: this origin applies nothing on its own.
|
|
22
|
+
*
|
|
23
|
+
* Spelled as a word rather than as an absent entry, because an absent entry
|
|
24
|
+
* already means something — `ceilingFor` reads it as `low` — and a policy
|
|
25
|
+
* cannot say *I thought about this origin and decided none of it* by leaving it
|
|
26
|
+
* out.
|
|
27
|
+
*/
|
|
28
|
+
export const NOTHING_AUTO_APPLIES = "nothing";
|
|
29
|
+
export const autoApplyCeilingSchema = z.union([z.literal(NOTHING_AUTO_APPLIES), stakeLevelSchema]);
|
|
30
|
+
/**
|
|
31
|
+
* The ceiling scale in order, which like `STAKE_ORDER` is the order and not
|
|
32
|
+
* merely the set.
|
|
33
|
+
*
|
|
34
|
+
* Built from the stake order rather than written out again, so a level added to
|
|
35
|
+
* the scale the Gate weighs on arrives here in the same edit and cannot be
|
|
36
|
+
* ranked by accident.
|
|
37
|
+
*/
|
|
38
|
+
export const CEILING_ORDER = everyMemberOf()([
|
|
39
|
+
NOTHING_AUTO_APPLIES,
|
|
40
|
+
...STAKE_ORDER,
|
|
41
|
+
]);
|
|
42
|
+
/**
|
|
43
|
+
* Where a ceiling sits on that scale.
|
|
44
|
+
*
|
|
45
|
+
* `indexOf` answers `-1` for a value this list does not name, which ranks it
|
|
46
|
+
* beneath `nothing` and so waves the change through — the same reassuring
|
|
47
|
+
* failure `rankOf` in `stake-level.ts` documents, reached the same way and
|
|
48
|
+
* filed in the same entry. The list is complete at compile time, so the route
|
|
49
|
+
* left is a value that never passed through the types.
|
|
50
|
+
*/
|
|
51
|
+
const rankOf = (ceiling) => CEILING_ORDER.indexOf(ceiling);
|
|
52
|
+
/**
|
|
53
|
+
* Two ceilings compared. Only the sign is meaningful: negative is stricter,
|
|
54
|
+
* positive is looser, zero is the same latitude.
|
|
55
|
+
*/
|
|
56
|
+
export const compareCeilings = (left, right) => rankOf(left) - rankOf(right);
|
|
57
|
+
/**
|
|
58
|
+
* Whether a change assessed at this level is above what the origin may apply
|
|
59
|
+
* unattended — which, at `nothing`, every change is.
|
|
60
|
+
*
|
|
61
|
+
* A stake level is a ceiling, so this is one comparison on one scale rather
|
|
62
|
+
* than a branch on the sentinel. `low` stakes against a `low` ceiling is *at*
|
|
63
|
+
* it and applies; `low` stakes against `nothing` is above it and waits.
|
|
64
|
+
*/
|
|
65
|
+
export const isAboveCeiling = (level, ceiling) => compareCeilings(level, ceiling) > 0;
|
|
66
|
+
//# sourceMappingURL=auto-apply-ceiling.js.map
|
|
@@ -0,0 +1,148 @@
|
|
|
1
|
+
import { z } from "zod";
|
|
2
|
+
import type { BindingReader } from "../render/reads.js";
|
|
3
|
+
import type { SlotPlacer } from "../render/slots.js";
|
|
4
|
+
import type { PropsVocabulary } from "./vocabulary.js";
|
|
5
|
+
/**
|
|
6
|
+
* Which of the write path's optional checks a runtime was actually holding when
|
|
7
|
+
* it judged a change.
|
|
8
|
+
*
|
|
9
|
+
* `policyFingerprintOf` proves that two judgments consulted the same rules, and
|
|
10
|
+
* a reader is entitled to hear that as *the same thing judged both*. It is not
|
|
11
|
+
* quite that. 0179 keeps a props vocabulary off the policy on purpose — it is a
|
|
12
|
+
* function, and a policy is a Zod-parsed serialisable value — so a deployment
|
|
13
|
+
* that wires one on Tuesday produces dispositions on Wednesday whose fingerprint
|
|
14
|
+
* is byte-identical to Monday's. The policy did not change. What decided did.
|
|
15
|
+
*
|
|
16
|
+
* That gap was filed on 21 September as a stated limit, and the thing that made
|
|
17
|
+
* it worth closing arrived afterwards: 0208 wired a second seam the same way, so
|
|
18
|
+
* there were two inputs that could turn an `accepted` into a `rejected` and
|
|
19
|
+
* leave no trace of having been consulted — three since 0252. A refusal rate
|
|
20
|
+
* that moved in the week somebody wired a registry into the write path is
|
|
21
|
+
* either explained by that wiring or is a fault, and nothing in this repository
|
|
22
|
+
* could tell those apart.
|
|
23
|
+
*
|
|
24
|
+
* **These are named rather than digested, and that is the design.** A policy has
|
|
25
|
+
* fourteen knobs of host data, so what it contains can only be compared as a
|
|
26
|
+
* hash; the seams are three, their names are Loom's own, and a list of them is
|
|
27
|
+
* something a person can read against their own composition root. The
|
|
28
|
+
* fingerprint's own doc comment makes the argument for the other side of this
|
|
29
|
+
* trade — *a digest is not something a person can look up in their own
|
|
30
|
+
* configuration* — and here there is nothing to look up, because the record says
|
|
31
|
+
* `props` or it does not.
|
|
32
|
+
*
|
|
33
|
+
* Naming also means this needs no shape half. A fingerprint carries one because
|
|
34
|
+
* adding a knob to the policy would otherwise change every digest in the corpus
|
|
35
|
+
* and make every host look as though it had edited a policy it never touched.
|
|
36
|
+
* Adding a *check* changes no existing list: a judgment from a version that had
|
|
37
|
+
* two checks and wired both says `props, bindings`, and so does a judgment from a
|
|
38
|
+
* version that has three and wired the same two. They compare equal, which is
|
|
39
|
+
* correct — a check that was not wired and a check that did not yet exist were
|
|
40
|
+
* applied exactly as much as each other.
|
|
41
|
+
*
|
|
42
|
+
* What this does not reach: whether a wired seam's *answers* changed. A props
|
|
43
|
+
* vocabulary is `propsVocabularyFor(registry)`, so tightening one primitive's
|
|
44
|
+
* schema changes what it refuses while this record stays identical. The runtime
|
|
45
|
+
* cannot read a function, and a record that implied otherwise would be worse than
|
|
46
|
+
* one with a single clear meaning — so this says which checks were in place and
|
|
47
|
+
* nothing about what they concluded.
|
|
48
|
+
*/
|
|
49
|
+
export declare const writeCheckSchema: z.ZodEnum<["props", "bindings", "regions"]>;
|
|
50
|
+
/**
|
|
51
|
+
* One check the write path performs only when a composition root hands it the
|
|
52
|
+
* seam to perform it with.
|
|
53
|
+
*
|
|
54
|
+
* - `props` — the node's own primitive accepts the props it would carry (0179).
|
|
55
|
+
* - `bindings` — something will read the answer a bound node asks for (0208).
|
|
56
|
+
* - `regions` — the primitive places the named region a node fills (0252).
|
|
57
|
+
*
|
|
58
|
+
* The type-name vocabulary is deliberately not here. *Which primitives exist at
|
|
59
|
+
* all* is `registeredPrimitiveTypes`, a policy field, so it is already inside the
|
|
60
|
+
* fingerprint and an empty list already reads as a host that has not spoken
|
|
61
|
+
* (0173). Listing it again would record one input twice and leave a reader
|
|
62
|
+
* unable to tell which of the two records to believe.
|
|
63
|
+
*/
|
|
64
|
+
export type WriteCheck = z.infer<typeof writeCheckSchema>;
|
|
65
|
+
/**
|
|
66
|
+
* Every check this version of Loom has a seam for, in the order a composition
|
|
67
|
+
* root meets them — which is also the order `assessChange` takes them, and the
|
|
68
|
+
* canonical order `wiredChecksOf` writes a list in, so that two runtimes holding
|
|
69
|
+
* the same checks produce the same list rather than two spellings of it.
|
|
70
|
+
*/
|
|
71
|
+
export declare const WRITE_CHECKS: readonly WriteCheck[];
|
|
72
|
+
/**
|
|
73
|
+
* The seams, as much of them as reading the record needs.
|
|
74
|
+
*
|
|
75
|
+
* A structural subset of `CompositionRuntime` rather than that type's
|
|
76
|
+
* declaration: the composition root is where a host writes what it is wiring,
|
|
77
|
+
* with the doc comments explaining each seam, and splitting it to win a guard
|
|
78
|
+
* rail here would have cost a reading surface — lesson 5 prints the runtime
|
|
79
|
+
* whole, and a type assembled from two files cannot be printed whole.
|
|
80
|
+
*
|
|
81
|
+
* So the correspondence is held from the test side instead, where
|
|
82
|
+
* `checks.test.ts` enumerates `CompositionRuntime`'s optional fields and makes a
|
|
83
|
+
* seam added there a compile error until somebody decides whether it is a check.
|
|
84
|
+
*
|
|
85
|
+
* `| undefined` on each field rather than the runtime's stricter optionality,
|
|
86
|
+
* because *absent* and *present and `undefined`* are two different things on the
|
|
87
|
+
* record a host declares — rightly, since a host that writes a key means to say
|
|
88
|
+
* something — and one answer here: this call was handed no seam. A caller holding
|
|
89
|
+
* an `X | undefined` is the ordinary case at an optional seam, and making it
|
|
90
|
+
* rebuild the object to say so would put the presence test in two places.
|
|
91
|
+
*/
|
|
92
|
+
export type WriteCheckSeams = {
|
|
93
|
+
readonly propsVocabulary?: PropsVocabulary | undefined;
|
|
94
|
+
readonly bindingReader?: BindingReader | undefined;
|
|
95
|
+
readonly slotPlacer?: SlotPlacer | undefined;
|
|
96
|
+
};
|
|
97
|
+
/**
|
|
98
|
+
* Which checks a composition root wired, in canonical order.
|
|
99
|
+
*
|
|
100
|
+
* Presence and never behaviour: a host that hands `EVERY_TYPE_UNDECLARED` across
|
|
101
|
+
* the props seam is recorded as having wired a props check, because it did. The
|
|
102
|
+
* alternative was to recognise that one sentinel and quietly believe every other
|
|
103
|
+
* no-op a host might write, which would make the record mean *this seam does
|
|
104
|
+
* something* in some cases and *this seam was handed over* in the rest. One clear
|
|
105
|
+
* meaning is worth more than a special case, and the sentinels exist as defaults
|
|
106
|
+
* rather than as something a composition root reaches for.
|
|
107
|
+
*/
|
|
108
|
+
export declare const wiredChecksOf: (seams: WriteCheckSeams) => readonly WriteCheck[];
|
|
109
|
+
/**
|
|
110
|
+
* The same checks, in canonical order and without repetition.
|
|
111
|
+
*
|
|
112
|
+
* Which checks were in place is a membership test, so neither the order a caller
|
|
113
|
+
* holds them in nor a repeat may change what two lists say about each other.
|
|
114
|
+
* `wiredChecksOf` already answers in this form; this is for a list that arrived
|
|
115
|
+
* from a record, a wire or a host's own hand.
|
|
116
|
+
*/
|
|
117
|
+
export declare const canonicalChecksOf: (checks: readonly WriteCheck[]) => readonly WriteCheck[];
|
|
118
|
+
/**
|
|
119
|
+
* What a set of recorded check lists says about a run of judgments.
|
|
120
|
+
*
|
|
121
|
+
* - `unrecorded` — nothing carried the field. Every one of those judgments
|
|
122
|
+
* predates it, and no amount of reading will recover what was wired.
|
|
123
|
+
* - `single` — one set of checks judged all of them. The apparatus held.
|
|
124
|
+
* - `changed` — two judgments were made with different checks in place, so a
|
|
125
|
+
* reader comparing their outcomes is comparing two write paths.
|
|
126
|
+
*
|
|
127
|
+
* There is no `incomparable` here, which is the one way this differs from
|
|
128
|
+
* `rulesetContinuityOf`, and the reason is the argument at the top of this
|
|
129
|
+
* module: a check list is made of Loom's own names, so lists from either side of
|
|
130
|
+
* an upgrade compare directly and an honest "cannot tell" is never needed.
|
|
131
|
+
*
|
|
132
|
+
* `single` is a statement about the lists present and nothing else. A run that
|
|
133
|
+
* also holds judgments carrying no list is not thereby shown constant, which is
|
|
134
|
+
* why the count of those belongs beside this rather than folded into it — the
|
|
135
|
+
* bargain `rulesetContinuityOf` strikes with `unfingerprinted`, for its reason.
|
|
136
|
+
*/
|
|
137
|
+
export type ChecksContinuity = "unrecorded" | "single" | "changed";
|
|
138
|
+
export declare const checksContinuityOf: (wired: readonly (readonly WriteCheck[])[]) => ChecksContinuity;
|
|
139
|
+
/**
|
|
140
|
+
* A check list for a reader, with a word for the empty one.
|
|
141
|
+
*
|
|
142
|
+
* An empty list is a real and common state — a deployment that has wired neither
|
|
143
|
+
* seam — and a row rendering it as blank space reads as missing data rather than
|
|
144
|
+
* as the answer. "none" is a word rather than a name, which is why it is written
|
|
145
|
+
* here and not spelled into `WriteCheck`.
|
|
146
|
+
*/
|
|
147
|
+
export declare const describeWiredChecks: (checks: readonly WriteCheck[]) => string;
|
|
148
|
+
//# sourceMappingURL=checks.d.ts.map
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
import { z } from "zod";
|
|
2
|
+
/**
|
|
3
|
+
* Which of the write path's optional checks a runtime was actually holding when
|
|
4
|
+
* it judged a change.
|
|
5
|
+
*
|
|
6
|
+
* `policyFingerprintOf` proves that two judgments consulted the same rules, and
|
|
7
|
+
* a reader is entitled to hear that as *the same thing judged both*. It is not
|
|
8
|
+
* quite that. 0179 keeps a props vocabulary off the policy on purpose — it is a
|
|
9
|
+
* function, and a policy is a Zod-parsed serialisable value — so a deployment
|
|
10
|
+
* that wires one on Tuesday produces dispositions on Wednesday whose fingerprint
|
|
11
|
+
* is byte-identical to Monday's. The policy did not change. What decided did.
|
|
12
|
+
*
|
|
13
|
+
* That gap was filed on 21 September as a stated limit, and the thing that made
|
|
14
|
+
* it worth closing arrived afterwards: 0208 wired a second seam the same way, so
|
|
15
|
+
* there were two inputs that could turn an `accepted` into a `rejected` and
|
|
16
|
+
* leave no trace of having been consulted — three since 0252. A refusal rate
|
|
17
|
+
* that moved in the week somebody wired a registry into the write path is
|
|
18
|
+
* either explained by that wiring or is a fault, and nothing in this repository
|
|
19
|
+
* could tell those apart.
|
|
20
|
+
*
|
|
21
|
+
* **These are named rather than digested, and that is the design.** A policy has
|
|
22
|
+
* fourteen knobs of host data, so what it contains can only be compared as a
|
|
23
|
+
* hash; the seams are three, their names are Loom's own, and a list of them is
|
|
24
|
+
* something a person can read against their own composition root. The
|
|
25
|
+
* fingerprint's own doc comment makes the argument for the other side of this
|
|
26
|
+
* trade — *a digest is not something a person can look up in their own
|
|
27
|
+
* configuration* — and here there is nothing to look up, because the record says
|
|
28
|
+
* `props` or it does not.
|
|
29
|
+
*
|
|
30
|
+
* Naming also means this needs no shape half. A fingerprint carries one because
|
|
31
|
+
* adding a knob to the policy would otherwise change every digest in the corpus
|
|
32
|
+
* and make every host look as though it had edited a policy it never touched.
|
|
33
|
+
* Adding a *check* changes no existing list: a judgment from a version that had
|
|
34
|
+
* two checks and wired both says `props, bindings`, and so does a judgment from a
|
|
35
|
+
* version that has three and wired the same two. They compare equal, which is
|
|
36
|
+
* correct — a check that was not wired and a check that did not yet exist were
|
|
37
|
+
* applied exactly as much as each other.
|
|
38
|
+
*
|
|
39
|
+
* What this does not reach: whether a wired seam's *answers* changed. A props
|
|
40
|
+
* vocabulary is `propsVocabularyFor(registry)`, so tightening one primitive's
|
|
41
|
+
* schema changes what it refuses while this record stays identical. The runtime
|
|
42
|
+
* cannot read a function, and a record that implied otherwise would be worse than
|
|
43
|
+
* one with a single clear meaning — so this says which checks were in place and
|
|
44
|
+
* nothing about what they concluded.
|
|
45
|
+
*/
|
|
46
|
+
export const writeCheckSchema = z.enum(["props", "bindings", "regions"]);
|
|
47
|
+
/**
|
|
48
|
+
* Every check this version of Loom has a seam for, in the order a composition
|
|
49
|
+
* root meets them — which is also the order `assessChange` takes them, and the
|
|
50
|
+
* canonical order `wiredChecksOf` writes a list in, so that two runtimes holding
|
|
51
|
+
* the same checks produce the same list rather than two spellings of it.
|
|
52
|
+
*/
|
|
53
|
+
export const WRITE_CHECKS = writeCheckSchema.options;
|
|
54
|
+
/**
|
|
55
|
+
* Where each check's seam is found, so the record is read off the declaration
|
|
56
|
+
* rather than kept beside it.
|
|
57
|
+
*
|
|
58
|
+
* The mapped type is the guard rail: a member added to `writeCheckSchema` is a
|
|
59
|
+
* compile error here until somebody says which seam supplies it. The other
|
|
60
|
+
* direction — a seam a composition root can hand over that no check reads — is a
|
|
61
|
+
* compile error in `checks.test.ts`, which enumerates the runtime's own optional
|
|
62
|
+
* fields rather than this type's.
|
|
63
|
+
*
|
|
64
|
+
* `unknown` rather than the seam's own type, because presence is the whole of
|
|
65
|
+
* what is asked. Nothing here calls a seam, and a reader of this record that
|
|
66
|
+
* believed it had been called would be believing more than it says.
|
|
67
|
+
*/
|
|
68
|
+
const SEAM_OF = {
|
|
69
|
+
props: (seams) => seams.propsVocabulary,
|
|
70
|
+
bindings: (seams) => seams.bindingReader,
|
|
71
|
+
regions: (seams) => seams.slotPlacer,
|
|
72
|
+
};
|
|
73
|
+
/**
|
|
74
|
+
* Which checks a composition root wired, in canonical order.
|
|
75
|
+
*
|
|
76
|
+
* Presence and never behaviour: a host that hands `EVERY_TYPE_UNDECLARED` across
|
|
77
|
+
* the props seam is recorded as having wired a props check, because it did. The
|
|
78
|
+
* alternative was to recognise that one sentinel and quietly believe every other
|
|
79
|
+
* no-op a host might write, which would make the record mean *this seam does
|
|
80
|
+
* something* in some cases and *this seam was handed over* in the rest. One clear
|
|
81
|
+
* meaning is worth more than a special case, and the sentinels exist as defaults
|
|
82
|
+
* rather than as something a composition root reaches for.
|
|
83
|
+
*/
|
|
84
|
+
export const wiredChecksOf = (seams) => WRITE_CHECKS.filter((check) => SEAM_OF[check](seams) !== undefined);
|
|
85
|
+
/**
|
|
86
|
+
* The same checks, in canonical order and without repetition.
|
|
87
|
+
*
|
|
88
|
+
* Which checks were in place is a membership test, so neither the order a caller
|
|
89
|
+
* holds them in nor a repeat may change what two lists say about each other.
|
|
90
|
+
* `wiredChecksOf` already answers in this form; this is for a list that arrived
|
|
91
|
+
* from a record, a wire or a host's own hand.
|
|
92
|
+
*/
|
|
93
|
+
export const canonicalChecksOf = (checks) => WRITE_CHECKS.filter((check) => checks.includes(check));
|
|
94
|
+
export const checksContinuityOf = (wired) => {
|
|
95
|
+
const distinct = new Set(wired.map((checks) => canonicalChecksOf(checks).join(",")));
|
|
96
|
+
if (distinct.size === 0)
|
|
97
|
+
return "unrecorded";
|
|
98
|
+
return distinct.size === 1 ? "single" : "changed";
|
|
99
|
+
};
|
|
100
|
+
/**
|
|
101
|
+
* A check list for a reader, with a word for the empty one.
|
|
102
|
+
*
|
|
103
|
+
* An empty list is a real and common state — a deployment that has wired neither
|
|
104
|
+
* seam — and a row rendering it as blank space reads as missing data rather than
|
|
105
|
+
* as the answer. "none" is a word rather than a name, which is why it is written
|
|
106
|
+
* here and not spelled into `WriteCheck`.
|
|
107
|
+
*/
|
|
108
|
+
export const describeWiredChecks = (checks) => {
|
|
109
|
+
const canonical = canonicalChecksOf(checks);
|
|
110
|
+
return canonical.length === 0 ? "none" : canonical.join(", ");
|
|
111
|
+
};
|
|
112
|
+
//# sourceMappingURL=checks.js.map
|
|
@@ -1,4 +1,6 @@
|
|
|
1
1
|
import { z } from "zod";
|
|
2
|
+
import { type WriteCheck } from "./checks.js";
|
|
3
|
+
import { type IrreversibilityReason } from "./irreversibility.js";
|
|
2
4
|
import { type StakeLevel } from "./stake-level.js";
|
|
3
5
|
/**
|
|
4
6
|
* What the Gate decided, and why. The rationale is structured rather than
|
|
@@ -66,6 +68,71 @@ export declare const dispositionSchema: z.ZodObject<{
|
|
|
66
68
|
* to check.
|
|
67
69
|
*/
|
|
68
70
|
policyFingerprint: z.ZodOptional<z.ZodString>;
|
|
71
|
+
/**
|
|
72
|
+
* And which of the write path's optional checks were in place, beside what the
|
|
73
|
+
* rules were.
|
|
74
|
+
*
|
|
75
|
+
* A fingerprint proves the rules held; it says nothing about the two seams a
|
|
76
|
+
* composition root hands over separately, either of which can turn an
|
|
77
|
+
* `accepted` into a `rejected` (0179, 0208). Without this, a deployment that
|
|
78
|
+
* wired a registry into the write path on Tuesday produced Wednesday's
|
|
79
|
+
* judgments under a byte-identical fingerprint, and a reader comparing the two
|
|
80
|
+
* weeks was told nothing had changed.
|
|
81
|
+
*
|
|
82
|
+
* **The empty list is written rather than omitted**, which is the opposite of
|
|
83
|
+
* `irreversibilityReasons` below, and the difference is that nothing else here
|
|
84
|
+
* disambiguates the absence. `reversible` says whether any reason could have
|
|
85
|
+
* fired; no field says whether this runtime was asked about its seams. So an
|
|
86
|
+
* empty array is *asked, and none were wired*, and the field being absent is
|
|
87
|
+
* *judged before the Gate recorded this* — the same two states `policyId` and
|
|
88
|
+
* `policyFingerprint` keep apart, by the same means.
|
|
89
|
+
*/
|
|
90
|
+
wiredChecks: z.ZodOptional<z.ZodArray<z.ZodEnum<["props", "bindings", "regions"]>, "many">>;
|
|
91
|
+
/**
|
|
92
|
+
* Why it cannot be taken back, for the one screen that has to ask somebody.
|
|
93
|
+
*
|
|
94
|
+
* `reversible` above says *whether*, and `reason.detail` says why in a
|
|
95
|
+
* sentence — and a sentence is the wrong thing to read, because the two
|
|
96
|
+
* reasons ask opposite things of the person holding the decision. One sends
|
|
97
|
+
* them to go and look at a payment flow; the other asks whether some content
|
|
98
|
+
* is worth keeping. The detail line is prose written for a reader and
|
|
99
|
+
* documented as such, so a consumer recovering the codes out of it would be
|
|
100
|
+
* parsing somebody else's wording, and would break silently the first time
|
|
101
|
+
* anybody improved it.
|
|
102
|
+
*
|
|
103
|
+
* Absent and never defaulted (0045), and omitted rather than empty when
|
|
104
|
+
* nothing fired. `reversible` is what disambiguates the absence, which leaves
|
|
105
|
+
* three states readable and the fourth impossible:
|
|
106
|
+
*
|
|
107
|
+
* | `reversible` | this field | what it means |
|
|
108
|
+
* | --- | --- | --- |
|
|
109
|
+
* | `true` | absent | nothing fired, which is what `true` already said |
|
|
110
|
+
* | `false` | present | these are the reasons |
|
|
111
|
+
* | `false` | absent | judged before this field existed |
|
|
112
|
+
* | `true` | present | never written; asserted in `gate.test.ts` |
|
|
113
|
+
*/
|
|
114
|
+
irreversibilityReasons: z.ZodOptional<z.ZodArray<z.ZodDiscriminatedUnion<"code", [z.ZodObject<{
|
|
115
|
+
code: z.ZodLiteral<"out-of-tree-effect">;
|
|
116
|
+
primitiveTypes: z.ZodArray<z.ZodBranded<z.ZodString, "PrimitiveType">, "many">;
|
|
117
|
+
}, "strip", z.ZodTypeAny, {
|
|
118
|
+
code: "out-of-tree-effect";
|
|
119
|
+
primitiveTypes: (string & z.BRAND<"PrimitiveType">)[];
|
|
120
|
+
}, {
|
|
121
|
+
code: "out-of-tree-effect";
|
|
122
|
+
primitiveTypes: string[];
|
|
123
|
+
}>, z.ZodObject<{
|
|
124
|
+
code: z.ZodLiteral<"retention-budget-exceeded">;
|
|
125
|
+
retainedNodeCount: z.ZodNumber;
|
|
126
|
+
budget: z.ZodNumber;
|
|
127
|
+
}, "strip", z.ZodTypeAny, {
|
|
128
|
+
code: "retention-budget-exceeded";
|
|
129
|
+
retainedNodeCount: number;
|
|
130
|
+
budget: number;
|
|
131
|
+
}, {
|
|
132
|
+
code: "retention-budget-exceeded";
|
|
133
|
+
retainedNodeCount: number;
|
|
134
|
+
budget: number;
|
|
135
|
+
}>]>, "many">>;
|
|
69
136
|
}, "strip", z.ZodTypeAny, {
|
|
70
137
|
kind: "rejected" | "accepted" | "requires-confirmation";
|
|
71
138
|
confidence: number;
|
|
@@ -77,6 +144,15 @@ export declare const dispositionSchema: z.ZodObject<{
|
|
|
77
144
|
stakes: "low" | "medium" | "high" | "critical";
|
|
78
145
|
reversible: boolean;
|
|
79
146
|
policyFingerprint?: string | undefined;
|
|
147
|
+
wiredChecks?: ("props" | "bindings" | "regions")[] | undefined;
|
|
148
|
+
irreversibilityReasons?: ({
|
|
149
|
+
code: "out-of-tree-effect";
|
|
150
|
+
primitiveTypes: (string & z.BRAND<"PrimitiveType">)[];
|
|
151
|
+
} | {
|
|
152
|
+
code: "retention-budget-exceeded";
|
|
153
|
+
retainedNodeCount: number;
|
|
154
|
+
budget: number;
|
|
155
|
+
})[] | undefined;
|
|
80
156
|
}, {
|
|
81
157
|
kind: "rejected" | "accepted" | "requires-confirmation";
|
|
82
158
|
confidence: number;
|
|
@@ -88,6 +164,15 @@ export declare const dispositionSchema: z.ZodObject<{
|
|
|
88
164
|
reversible: boolean;
|
|
89
165
|
policyId?: string | undefined;
|
|
90
166
|
policyFingerprint?: string | undefined;
|
|
167
|
+
wiredChecks?: ("props" | "bindings" | "regions")[] | undefined;
|
|
168
|
+
irreversibilityReasons?: ({
|
|
169
|
+
code: "out-of-tree-effect";
|
|
170
|
+
primitiveTypes: string[];
|
|
171
|
+
} | {
|
|
172
|
+
code: "retention-budget-exceeded";
|
|
173
|
+
retainedNodeCount: number;
|
|
174
|
+
budget: number;
|
|
175
|
+
})[] | undefined;
|
|
91
176
|
}>;
|
|
92
177
|
export type Disposition = {
|
|
93
178
|
readonly kind: DispositionKind;
|
|
@@ -98,5 +183,16 @@ export type Disposition = {
|
|
|
98
183
|
readonly policyId: string;
|
|
99
184
|
/** Absent on a judgment recorded before the Gate fingerprinted policies. */
|
|
100
185
|
readonly policyFingerprint?: string;
|
|
186
|
+
/**
|
|
187
|
+
* Absent on a judgment recorded before the Gate wrote down which checks were
|
|
188
|
+
* wired. Empty means it was asked and none were; the schema above says why the
|
|
189
|
+
* two are kept apart here and folded together elsewhere.
|
|
190
|
+
*/
|
|
191
|
+
readonly wiredChecks?: readonly WriteCheck[];
|
|
192
|
+
/**
|
|
193
|
+
* Absent when nothing fired, and on a judgment recorded before the field
|
|
194
|
+
* existed. The schema above says which absence is which.
|
|
195
|
+
*/
|
|
196
|
+
readonly irreversibilityReasons?: readonly IrreversibilityReason[];
|
|
101
197
|
};
|
|
102
198
|
//# sourceMappingURL=disposition.d.ts.map
|
|
@@ -1,4 +1,6 @@
|
|
|
1
1
|
import { z } from "zod";
|
|
2
|
+
import { writeCheckSchema } from "./checks.js";
|
|
3
|
+
import { irreversibilityReasonSchema } from "./irreversibility.js";
|
|
2
4
|
import { stakeLevelSchema } from "./stake-level.js";
|
|
3
5
|
/**
|
|
4
6
|
* What the Gate decided, and why. The rationale is structured rather than
|
|
@@ -55,5 +57,49 @@ export const dispositionSchema = z.object({
|
|
|
55
57
|
* to check.
|
|
56
58
|
*/
|
|
57
59
|
policyFingerprint: z.string().min(1).optional(),
|
|
60
|
+
/**
|
|
61
|
+
* And which of the write path's optional checks were in place, beside what the
|
|
62
|
+
* rules were.
|
|
63
|
+
*
|
|
64
|
+
* A fingerprint proves the rules held; it says nothing about the two seams a
|
|
65
|
+
* composition root hands over separately, either of which can turn an
|
|
66
|
+
* `accepted` into a `rejected` (0179, 0208). Without this, a deployment that
|
|
67
|
+
* wired a registry into the write path on Tuesday produced Wednesday's
|
|
68
|
+
* judgments under a byte-identical fingerprint, and a reader comparing the two
|
|
69
|
+
* weeks was told nothing had changed.
|
|
70
|
+
*
|
|
71
|
+
* **The empty list is written rather than omitted**, which is the opposite of
|
|
72
|
+
* `irreversibilityReasons` below, and the difference is that nothing else here
|
|
73
|
+
* disambiguates the absence. `reversible` says whether any reason could have
|
|
74
|
+
* fired; no field says whether this runtime was asked about its seams. So an
|
|
75
|
+
* empty array is *asked, and none were wired*, and the field being absent is
|
|
76
|
+
* *judged before the Gate recorded this* — the same two states `policyId` and
|
|
77
|
+
* `policyFingerprint` keep apart, by the same means.
|
|
78
|
+
*/
|
|
79
|
+
wiredChecks: z.array(writeCheckSchema).optional(),
|
|
80
|
+
/**
|
|
81
|
+
* Why it cannot be taken back, for the one screen that has to ask somebody.
|
|
82
|
+
*
|
|
83
|
+
* `reversible` above says *whether*, and `reason.detail` says why in a
|
|
84
|
+
* sentence — and a sentence is the wrong thing to read, because the two
|
|
85
|
+
* reasons ask opposite things of the person holding the decision. One sends
|
|
86
|
+
* them to go and look at a payment flow; the other asks whether some content
|
|
87
|
+
* is worth keeping. The detail line is prose written for a reader and
|
|
88
|
+
* documented as such, so a consumer recovering the codes out of it would be
|
|
89
|
+
* parsing somebody else's wording, and would break silently the first time
|
|
90
|
+
* anybody improved it.
|
|
91
|
+
*
|
|
92
|
+
* Absent and never defaulted (0045), and omitted rather than empty when
|
|
93
|
+
* nothing fired. `reversible` is what disambiguates the absence, which leaves
|
|
94
|
+
* three states readable and the fourth impossible:
|
|
95
|
+
*
|
|
96
|
+
* | `reversible` | this field | what it means |
|
|
97
|
+
* | --- | --- | --- |
|
|
98
|
+
* | `true` | absent | nothing fired, which is what `true` already said |
|
|
99
|
+
* | `false` | present | these are the reasons |
|
|
100
|
+
* | `false` | absent | judged before this field existed |
|
|
101
|
+
* | `true` | present | never written; asserted in `gate.test.ts` |
|
|
102
|
+
*/
|
|
103
|
+
irreversibilityReasons: z.array(irreversibilityReasonSchema).optional(),
|
|
58
104
|
});
|
|
59
105
|
//# sourceMappingURL=disposition.js.map
|