@niscorp/moss 0.9.2 → 0.10.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/CHANGELOG.md +122 -0
- package/DESIGN.md +58 -55
- package/DOCS.md +280 -170
- package/README.md +5 -5
- package/dist/{chunk-PVZMCEBX.cjs → chunk-3CKBKTXA.cjs} +2 -2
- package/dist/chunk-3CKBKTXA.cjs.map +1 -0
- package/dist/{chunk-FUJRIO4N.js → chunk-3PL4AH4I.js} +4 -4
- package/dist/{chunk-FUJRIO4N.js.map → chunk-3PL4AH4I.js.map} +1 -1
- package/dist/{chunk-QAHDSRPK.js → chunk-4URQHVYG.js} +2 -2
- package/dist/chunk-4URQHVYG.js.map +1 -0
- package/dist/{chunk-6ZWMC2OV.cjs → chunk-6ACVHHFK.cjs} +33 -30
- package/dist/chunk-6ACVHHFK.cjs.map +1 -0
- package/dist/{chunk-IUJ2TRNB.cjs → chunk-7MOEKAVC.cjs} +6 -6
- package/dist/{chunk-IUJ2TRNB.cjs.map → chunk-7MOEKAVC.cjs.map} +1 -1
- package/dist/{chunk-NCQBGK3E.cjs → chunk-BFA76AKR.cjs} +4 -4
- package/dist/chunk-BFA76AKR.cjs.map +1 -0
- package/dist/{chunk-T5BRTFKP.js → chunk-DSVRFAGX.js} +3 -3
- package/dist/{chunk-T5BRTFKP.js.map → chunk-DSVRFAGX.js.map} +1 -1
- package/dist/{chunk-IW3A2YIC.js → chunk-EYWD733E.js} +3 -3
- package/dist/{chunk-IW3A2YIC.js.map → chunk-EYWD733E.js.map} +1 -1
- package/dist/{chunk-IY5BOFLK.cjs → chunk-G4P3XEVM.cjs} +19 -19
- package/dist/chunk-G4P3XEVM.cjs.map +1 -0
- package/dist/{chunk-6QPTMKRE.cjs → chunk-HUP7CZ7X.cjs} +6 -6
- package/dist/{chunk-6QPTMKRE.cjs.map → chunk-HUP7CZ7X.cjs.map} +1 -1
- package/dist/{chunk-VKQPOZDJ.cjs → chunk-LTS4AM6T.cjs} +4 -4
- package/dist/chunk-LTS4AM6T.cjs.map +1 -0
- package/dist/{chunk-UTFOMFCH.js → chunk-MEHCZECW.js} +5 -5
- package/dist/chunk-MEHCZECW.js.map +1 -0
- package/dist/{chunk-WMIJU6ZZ.js → chunk-MYPK5YZR.js} +297 -206
- package/dist/chunk-MYPK5YZR.js.map +1 -0
- package/dist/{chunk-TKXYPO2Y.js → chunk-NUX5MH4I.js} +4 -4
- package/dist/chunk-NUX5MH4I.js.map +1 -0
- package/dist/{chunk-KVXP6OTW.cjs → chunk-UVY5ZPWW.cjs} +373 -282
- package/dist/chunk-UVY5ZPWW.cjs.map +1 -0
- package/dist/{chunk-5ZB7FZ2J.js → chunk-VYYDLGQ2.js} +29 -26
- package/dist/chunk-VYYDLGQ2.js.map +1 -0
- package/dist/{chunk-NRZ3Z2FF.js → chunk-WKZWSWOJ.js} +4 -4
- package/dist/chunk-WKZWSWOJ.js.map +1 -0
- package/dist/{chunk-KMZT6NVL.cjs → chunk-XH6TSWG4.cjs} +7 -7
- package/dist/{chunk-KMZT6NVL.cjs.map → chunk-XH6TSWG4.cjs.map} +1 -1
- package/dist/client.cjs +5 -5
- package/dist/client.js +2 -2
- package/dist/{document-deAs7Dre.d.cts → document-DvhT_HaJ.d.cts} +3 -2
- package/dist/{document-C3aS9uiW.d.ts → document-iKaRinZE.d.ts} +3 -2
- package/dist/{index-CSEo7Tys.d.ts → index-DWj3_0Zg.d.cts} +3 -0
- package/dist/{index-CSEo7Tys.d.cts → index-DWj3_0Zg.d.ts} +3 -0
- package/dist/index.cjs +16 -16
- package/dist/index.d.cts +4 -4
- package/dist/index.d.ts +4 -4
- package/dist/index.js +4 -4
- package/dist/integrations.cjs +27 -18
- package/dist/integrations.cjs.map +1 -1
- package/dist/integrations.d.cts +1 -1
- package/dist/integrations.d.ts +1 -1
- package/dist/integrations.js +25 -16
- package/dist/integrations.js.map +1 -1
- package/dist/node.cjs +9 -9
- package/dist/node.d.cts +2 -2
- package/dist/node.d.ts +2 -2
- package/dist/node.js +5 -5
- package/dist/protocol.cjs +5 -5
- package/dist/protocol.js +1 -1
- package/dist/terminal/dom/index.cjs +3 -3
- package/dist/terminal/dom/index.js +1 -1
- package/dist/terminal/dom/server.cjs +2 -2
- package/dist/terminal/dom/server.js +1 -1
- package/dist/terminal/index.cjs +3 -3
- package/dist/terminal/index.js +2 -2
- package/dist/terminal/ink/index.js.map +1 -1
- package/dist/terminal/react/index.cjs +9 -9
- package/dist/terminal/react/index.cjs.map +1 -1
- package/dist/terminal/react/index.js +4 -4
- package/dist/terminal/react/index.js.map +1 -1
- package/dist/terminal/react/server.cjs +4 -4
- package/dist/terminal/react/server.js +2 -2
- package/dist/terminal/tty/index.cjs +12 -12
- package/dist/terminal/tty/index.cjs.map +1 -1
- package/dist/terminal/tty/index.js +6 -6
- package/dist/terminal/tty/index.js.map +1 -1
- package/dist/terminal/vue/index.cjs +9 -9
- package/dist/terminal/vue/index.cjs.map +1 -1
- package/dist/terminal/vue/index.js +4 -4
- package/dist/terminal/vue/index.js.map +1 -1
- package/dist/terminal/vue/server.cjs +4 -4
- package/dist/terminal/vue/server.js +2 -2
- package/dist/tide.d.cts +1 -1
- package/dist/tide.d.ts +1 -1
- package/dist/unverified.cjs +4 -4
- package/dist/unverified.js +3 -3
- package/dist/vite.cjs +36 -10
- package/dist/vite.cjs.map +1 -1
- package/dist/vite.d.cts +2 -2
- package/dist/vite.d.ts +2 -2
- package/dist/vite.js +31 -5
- package/dist/vite.js.map +1 -1
- package/package.json +13 -13
- package/dist/chunk-5ZB7FZ2J.js.map +0 -1
- package/dist/chunk-6ZWMC2OV.cjs.map +0 -1
- package/dist/chunk-IY5BOFLK.cjs.map +0 -1
- package/dist/chunk-KVXP6OTW.cjs.map +0 -1
- package/dist/chunk-NCQBGK3E.cjs.map +0 -1
- package/dist/chunk-NRZ3Z2FF.js.map +0 -1
- package/dist/chunk-PVZMCEBX.cjs.map +0 -1
- package/dist/chunk-QAHDSRPK.js.map +0 -1
- package/dist/chunk-TKXYPO2Y.js.map +0 -1
- package/dist/chunk-UTFOMFCH.js.map +0 -1
- package/dist/chunk-VKQPOZDJ.cjs.map +0 -1
- package/dist/chunk-WMIJU6ZZ.js.map +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,127 @@
|
|
|
1
1
|
# @niscorp/moss
|
|
2
2
|
|
|
3
|
+
## 0.10.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- d3fadac: BREAKING — approved by moccadroid (owner), 2026-11-22: an app whose update hands a row over by writing a column its caller's update rule pins sets `runtime.checkMovedRows: false` to keep today's behaviour.
|
|
8
|
+
|
|
9
|
+
moss's `/api/vex` and `executeAs` now refuse an update that would move a row out of the caller's own update rule (400 `scope_denied`, nothing written), as vex does by default. An app that hands rows over that way keeps today's behaviour with `runtime.checkMovedRows: false`.
|
|
10
|
+
|
|
11
|
+
- 29e51ec: BREAKING — approved by moccadroid (owner), 2026-11-22: nothing unless the app's `session` verifier relied on being called one connection at a time, or on the lower rate of calls a pass that ran over its interval used to give it.
|
|
12
|
+
|
|
13
|
+
A revoked session's socket now closes within one `sessionRevalidateMs` plus the time the verifier takes to answer, however many connections are open: each revalidation pass asks the verifier once for each token, every token at the same moment, instead of one connection after another (200 connections with a 20 ms verifier and `sessionRevalidateMs: 500` closed a revoked socket after about 6.7 seconds; now after about 520 ms). Connections that present one token share one call. The most the verifier is now called is once for each distinct token every interval, and the calls of a pass arrive together at its start. Where a pass used to take longer than the interval, that is more calls than before: in the same example about 28 calls a second, one at a time, become about 350 a second, up to 200 at once. With `session: 'sessions'` the calls are queries on the app's pool, every 60 seconds by default. A pass that comes due while the previous one is still waiting for answers starts as soon as that one ends, instead of an interval later. The log line for a verifier that could not be asked still counts connections. The log line for an answer that fails after its pass went on now reads "could not be asked about a token after its pass went on. Its connections stay open and are asked again", since it is written once for each token.
|
|
14
|
+
|
|
15
|
+
- 1e228d3: BREAKING — approved by moccadroid (owner), 2026-11-22: an integration that read the visitor's `cookie`, `proxy-authorization` or `x-operator-key` at its hook, or a vendor page served through the webhook or proxy that used the app's session or browser storage, carries what it needs in the request itself.
|
|
16
|
+
|
|
17
|
+
The webhook door no longer passes the visitor's `cookie`, `proxy-authorization` or `x-operator-key` on to the integration, and what an integration answers through the webhook or the proxy is served with `x-content-type-options: nosniff` and a `content-security-policy` sandbox: a vendor's page still runs its script, submits its forms and navigates, but never as the app's own page. A vendor that read the app's cookie at its hook, or a landing page that used the app's browser storage, no longer can.
|
|
18
|
+
|
|
19
|
+
- b1e314e: BREAKING — approved by moccadroid (owner), 2026-11-22: nothing unless an app relied on `session.answerIntent` replaying an entry that declares a `reach` with more rows than `/api/vex` answers the same person; such a replay now answers fewer rows or `scope_denied`.
|
|
20
|
+
|
|
21
|
+
`engine.execute` can serve a replayed entry at the `reach` it declares: pass `policyForReach`, as the handler takes it. Without it the run is as before, with one warning per entry. moss's `session.answerIntent` passes it, so a replay of an entry that declares a reach answers what `/api/vex` answers the same person: fewer rows, or `scope_denied` for roles with no such reach.
|
|
22
|
+
|
|
23
|
+
### Patch Changes
|
|
24
|
+
|
|
25
|
+
- be6cc14: The docs now say plainly that time the app is down counts as unused for `runtime.artifactsUnusedMs`, so a long downtime lets the boot sweep delete what nobody used since. `runtime.artifactsUnusedSinceStart: true` counts that time only since the server started; the default is unchanged.
|
|
26
|
+
- adba9b1: A HEAD request through the integration proxy reaches the integration instead of answering 502. A session verifier that never answers for one socket no longer stops the re-check of every other live socket, and an answer that comes late is still acted on. The integration contract names an audience granted by a string where a list belongs. The aging sweep's timer no longer keeps the process alive. Boot prints a charter key the charter does not read (a misspelt `denny`) and a string where a list belongs.
|
|
27
|
+
- 23c4613: A webhook sent chunked (`Transfer-Encoding`), or with `Expect` or `Keep-Alive`, or with an `Upgrade` header but no `Connection: upgrade`, reaches the integration's service instead of answering `502`: the door leaves those four headers behind. A request with `Connection: upgrade` and `Upgrade` is a socket upgrade and never reaches the door; one with `Connection: upgrade` alone is answered `502`, since Node's fetch refuses that header.
|
|
28
|
+
|
|
29
|
+
A dev sign-in (`/dev/as/<who>`) that a proxy on this machine, such as a tunnel, carried for an address elsewhere, or for no address (`for=unknown`), writes a line in the dev log. The sign-in is answered: nothing is refused.
|
|
30
|
+
|
|
31
|
+
A `Host` that writes out the scheme's own port (`app.example.com:443` for a page on `https://app.example.com`) no longer turns off cookie sign-in on the socket.
|
|
32
|
+
|
|
33
|
+
A server shell's endpoint that declares its own lower-case `authorization` header is now called as the session, as one spelt `Authorization` already was, instead of carrying both tokens and answering `401`.
|
|
34
|
+
|
|
35
|
+
`Authorization: bearer <token>` is read in any case of the scheme, as HTTP defines it, instead of being refused with `401`.
|
|
36
|
+
|
|
37
|
+
A principal called `toString`, `constructor`, `__proto__` or `valueOf` is no longer answered `500` on every request: the assignments are read by their own keys, so such a principal is `public` unless they name it. A socket event for a canvas called `constructor` or `toString` is dropped, as one for any canvas the shell does not have, instead of reaching every action.
|
|
38
|
+
|
|
39
|
+
In `nisc dev` (`mossDev`), what the charter does not read as written (a misspelt `denny`: the `shape` warnings of `server.charterReport()`) is shown over the page on vite's error overlay each time a browser connects. The app runs under it. While the overlay is open it covers the page, and vite turns the next live update into a full reload.
|
|
40
|
+
|
|
41
|
+
DOCS says that a channel is not a trusted lane: the person's own terminal can publish any channel with any payload into their own shell, as `deliver` does.
|
|
42
|
+
|
|
43
|
+
DOCS shows a read saved with `body: undefined`, as `SessionArtifacts.save`'s type asks, and gives the limit `runtime.artifactsUnusedMs` refuses at boot: anything under two hours or not a whole number of milliseconds.
|
|
44
|
+
|
|
45
|
+
The word "held" and its relatives leave moss's internal names, comments, test titles and DOCS/DESIGN/README. Nothing public changes: `WireTokenStore.held`, the `<session>.held` cookie and every message moss prints or throws keep their wording.
|
|
46
|
+
|
|
47
|
+
- b18f9d3: `AGENTS.md` reads as short numbered points instead of long paragraphs, its worked example now obeys every rule it states, and the commands it names are the ones an app actually has. The part for whoever changes a package is now `CHANGING_A_PACKAGE.md`, beside it (moss's `DESIGN.md` points there).
|
|
48
|
+
- 8b4d6cd: A write can now be told to answer only the rows the caller's read rules show: `mutations: { …, answerReadableRows: true }` on the handler and on the Hono and Express adapters, and `answerReadableRows: true` in moss's runtime for its `/api/vex` surfaces. It is off by default, and with it off a write runs and answers exactly as before.
|
|
49
|
+
- Updated dependencies [092b5f1]
|
|
50
|
+
- Updated dependencies [c9158e2]
|
|
51
|
+
- Updated dependencies [74a9a7a]
|
|
52
|
+
- Updated dependencies [4b7d4a4]
|
|
53
|
+
- Updated dependencies [bf72478]
|
|
54
|
+
- Updated dependencies [e1db181]
|
|
55
|
+
- Updated dependencies [241bd4d]
|
|
56
|
+
- Updated dependencies [9f8e4b5]
|
|
57
|
+
- Updated dependencies [1b615d6]
|
|
58
|
+
- Updated dependencies [e7edd95]
|
|
59
|
+
- Updated dependencies [0a46ff6]
|
|
60
|
+
- Updated dependencies [59f314a]
|
|
61
|
+
- Updated dependencies [281108e]
|
|
62
|
+
- Updated dependencies [b233463]
|
|
63
|
+
- Updated dependencies [e2b9595]
|
|
64
|
+
- Updated dependencies [7aef6a7]
|
|
65
|
+
- Updated dependencies [79cf65c]
|
|
66
|
+
- Updated dependencies [e828562]
|
|
67
|
+
- Updated dependencies [6b01a50]
|
|
68
|
+
- Updated dependencies [6eef458]
|
|
69
|
+
- Updated dependencies [a41edf9]
|
|
70
|
+
- Updated dependencies [eb4ffb9]
|
|
71
|
+
- Updated dependencies [ae647e8]
|
|
72
|
+
- Updated dependencies [2effb54]
|
|
73
|
+
- Updated dependencies [bd996ea]
|
|
74
|
+
- Updated dependencies [180787b]
|
|
75
|
+
- Updated dependencies [d53910e]
|
|
76
|
+
- Updated dependencies [276f457]
|
|
77
|
+
- Updated dependencies [413afbd]
|
|
78
|
+
- Updated dependencies [1f6d37d]
|
|
79
|
+
- Updated dependencies [d77baf9]
|
|
80
|
+
- Updated dependencies [3f92c52]
|
|
81
|
+
- Updated dependencies [841c010]
|
|
82
|
+
- Updated dependencies [d93170b]
|
|
83
|
+
- Updated dependencies [61b15e4]
|
|
84
|
+
- Updated dependencies [7e8f6d4]
|
|
85
|
+
- Updated dependencies [5c52ef5]
|
|
86
|
+
- Updated dependencies [66eb934]
|
|
87
|
+
- Updated dependencies [909ae6b]
|
|
88
|
+
- Updated dependencies [5eb6e6c]
|
|
89
|
+
- Updated dependencies [1c2b7ce]
|
|
90
|
+
- Updated dependencies [069efde]
|
|
91
|
+
- Updated dependencies [85f1536]
|
|
92
|
+
- Updated dependencies [d7f10ac]
|
|
93
|
+
- Updated dependencies [8bf0c30]
|
|
94
|
+
- Updated dependencies [9e5c5e3]
|
|
95
|
+
- Updated dependencies [8b4d6cd]
|
|
96
|
+
- Updated dependencies [4c6300e]
|
|
97
|
+
- Updated dependencies [be6e7af]
|
|
98
|
+
- Updated dependencies [b1e314e]
|
|
99
|
+
- Updated dependencies [d8dc7d9]
|
|
100
|
+
- Updated dependencies [b2b2d8d]
|
|
101
|
+
- Updated dependencies [f995714]
|
|
102
|
+
- Updated dependencies [df44b8e]
|
|
103
|
+
- Updated dependencies [a002748]
|
|
104
|
+
- Updated dependencies [2233113]
|
|
105
|
+
- Updated dependencies [04f5821]
|
|
106
|
+
- @niscorp/charter@0.2.0
|
|
107
|
+
- @niscorp/nova@0.6.0
|
|
108
|
+
- @niscorp/prism@0.4.0
|
|
109
|
+
- @niscorp/strata@0.2.0
|
|
110
|
+
- @niscorp/tide@0.2.0
|
|
111
|
+
- @niscorp/vex@0.5.0
|
|
112
|
+
|
|
113
|
+
## 0.9.3
|
|
114
|
+
|
|
115
|
+
### Patch Changes
|
|
116
|
+
|
|
117
|
+
- 637d412: **A vex read returns stamped JSON columns upgraded.** A JSON column whose values carry the grammar stamp they were written at in another JSON column of the row can now be named once on the engine, with a strata upgrader beside it: `createQueryEngine({ upgrader: await createUpgrader(grammars, { transform: evaluate }), upgradedColumns: { answers: { plan: { stamp: 'grammar', kind: 'acme.answers/plan' } } } })`. A kind can also be read from the row: `kind: { grammar: 'acme.notes', column: 'kind' }`. Every read that returns the column (a replay, a generated read, a reactive read's every answer, `engine.test`) hands its mapping and its caller the value upgraded, with the stamp set to the stamp the upgrade gives back. A read returns the column only as one of its own fields, with its stamp (and kind) column beside it; vex refuses any other read of it when the read is compiled. A row that does not upgrade refuses the read, or, where the column says `unreadable: 'omit'` or `'null'`, is left out or has that value set to null, with a line in `meta.warnings`. New exports: `UpgradedColumnsSchema`, `UNREADABLE_MODES`, and the types `UpgradedColumn`, `UpgradedColumns`, `ColumnUpgrader`.
|
|
118
|
+
|
|
119
|
+
**Moss takes them on the manifest.** `defineApp({ upgradedColumns })` hands them to the app's engine and to the one that answers intents, with the upgrader moss builds from nova's, Prism's and vex's grammars and the app's `grammars`. Only the app's own tables can be named. The boot is refused where a table named is a feature's, the artifactory's or the generation pointer's (their owners read them as stored), where a kind is in none of those grammars, where a column or its stamp is not a json column of the database, or where a seeded read does not compile: an app that names `upgradedColumns` has every seeded read compiled at boot and on a refresh, so a read of an upgraded column that vex refuses stops the boot rather than its first replay.
|
|
120
|
+
|
|
121
|
+
**The rulebook** says so under "Using Vex" and in rule 19.
|
|
122
|
+
|
|
123
|
+
**What to change:** nothing. An app or engine that names no `upgradedColumns` reads every column as stored, as before. No grammar, table, entry or cache format changes.
|
|
124
|
+
|
|
3
125
|
## 0.9.2
|
|
4
126
|
|
|
5
127
|
### Patch Changes
|
package/DESIGN.md
CHANGED
|
@@ -58,7 +58,7 @@ runs, each through one door: a set of actions is handed over
|
|
|
58
58
|
each is verified before it is taken. The artifact library
|
|
59
59
|
that makes publish a runtime write for every artifact is specified and unbuilt
|
|
60
60
|
(see below). The mechanism is already the function it needs to be: what a set
|
|
61
|
-
of roles
|
|
61
|
+
of roles is granted, and the policy it reads and writes under, are derived from what
|
|
62
62
|
is in force and dropped when that changes, so there is no invalidation
|
|
63
63
|
protocol; a pointer in the database tells every other process that it did.
|
|
64
64
|
The pointer tells them *that*, not *what*: another process reads again the
|
|
@@ -71,20 +71,20 @@ somebody authored (its actions, its frame and layout store, its fragments, the
|
|
|
71
71
|
entries its reads replay) is answered by the running manifest in one function,
|
|
72
72
|
for a shell and a principal with their roles (`artifactsFor`, `src/artifactory/running.ts`). A shell is built
|
|
73
73
|
from that answer and adopts it: an adopt puts in place the actions that are
|
|
74
|
-
|
|
74
|
+
granted now, and each `{ ref }` of the layout store and each fragment that the
|
|
75
75
|
answer says differently from the last time. Every layout the shell draws is
|
|
76
|
-
one of those refs, under the name of what draws it: the answer
|
|
76
|
+
one of those refs, under the name of what draws it: the answer keeps an
|
|
77
77
|
action's in the layout store under `action/<id>`, and the definition names
|
|
78
78
|
it; the shell's own is under `frame` and a canvas's under `canvas/<id>`
|
|
79
79
|
(`shellWithStoredLayouts`, `src/artifactory/artifacts.ts`). So a layout is changed by setting
|
|
80
80
|
a ref, which a screen that is open follows with its data kept, and not by
|
|
81
81
|
registering the action again, which only a screen opened afterwards sees. It
|
|
82
82
|
is also how a saved layout reaches a screen: under an action's ref the answer
|
|
83
|
-
|
|
84
|
-
variant their roles
|
|
83
|
+
carries the principal's own layout that is marked in use, else the layout
|
|
84
|
+
variant their roles are granted, else the one published for everybody, else the
|
|
85
85
|
build's. The first two tables of the
|
|
86
86
|
library are built for that: a row for each save and a row for each version it
|
|
87
|
-
|
|
87
|
+
has, never changed (`src/artifactory/saves.ts`). A row is its principal's,
|
|
88
88
|
and vex keeps it so. What is published for everybody is the rows of one
|
|
89
89
|
principal no caller is, under that same rule: publishing is the save a person
|
|
90
90
|
makes, made by the app's own server code as that principal
|
|
@@ -98,7 +98,7 @@ it declares. (The
|
|
|
98
98
|
canvases a manifest declares are what a shell starts with: an adopt does not
|
|
99
99
|
take them again, a reset does. Nova gives a shell a canvas when something is
|
|
100
100
|
first pushed onto it; an adopt takes out one the manifest does not declare
|
|
101
|
-
once no layout in force
|
|
101
|
+
once no layout in force has a slot for it, where one did: `slottedCanvases`,
|
|
102
102
|
`src/artifactory/artifacts.ts`.) The
|
|
103
103
|
entries vex replays it asks the running manifest for as well, before its own
|
|
104
104
|
cache table; nothing else in moss reads one of the four off what the app
|
|
@@ -161,7 +161,7 @@ The organizing principle: an app hands over **artifacts** and an
|
|
|
161
161
|
one verification (`src/manifest/verify.ts`): every action is one nova reads,
|
|
162
162
|
the charter verifies (`verifyCharter`, with nova's closure audit over the
|
|
163
163
|
definitions in force), every entry's `reach` names a profile the behaviors
|
|
164
|
-
declare, and nobody
|
|
164
|
+
declare, and nobody is granted two layout variants of one action. It is asked at
|
|
165
165
|
boot, at every change (`refresh`, `replaceActions`), and of a manifest that
|
|
166
166
|
is not served (`verifyApp`); a boot or a change that fails it throws. The closure audit's findings are not errors: they are
|
|
167
167
|
filed under each role's `issues` in the report, and boot neither refuses on
|
|
@@ -186,11 +186,11 @@ open.)
|
|
|
186
186
|
Per-principal UI difference is existence (ring 1) or a served variant (ring 2),
|
|
187
187
|
never a runtime capability flag in a layout. A layout variant (`NiscApp.layouts`)
|
|
188
188
|
is `{ action, layout }` under a minted id; the charter's `layouts` section
|
|
189
|
-
selects who
|
|
189
|
+
selects who is granted which. At shell build, moss puts the granted variant's
|
|
190
190
|
layout where that action's layout is kept *before* the shell exists, so every downstream render
|
|
191
191
|
and serialize is already per-principal and the terminal renders what it is served
|
|
192
192
|
— nothing on the wire says why a button is absent. The base layout is the floor
|
|
193
|
-
(the least-privileged
|
|
193
|
+
(the least-privileged principal's shape); variants enrich upward as grants, so
|
|
194
194
|
`extends` composes them and a forgotten grant fails closed. This is the charter's
|
|
195
195
|
extensibility paying off: one `Section` value, moss hands the universe in and
|
|
196
196
|
compiles it.
|
|
@@ -208,12 +208,12 @@ entry.
|
|
|
208
208
|
verifier, moss's stored credential, the browser's cookie and its seal), and
|
|
209
209
|
a principal is a record (roles, scope values, what is installed for them).
|
|
210
210
|
2. **What exists for them?** `artifactory`: what the app consists of right
|
|
211
|
-
now, with one writer, and what a set of roles
|
|
211
|
+
now, with one writer, and what a set of roles is granted of it. Every artifact a
|
|
212
212
|
shell is handed is asked of it: the actions, the frame and the layout
|
|
213
213
|
store, the fragments and the entries, in one answer for a shell and a
|
|
214
214
|
principal, and read off the app by nothing else. It keeps what somebody
|
|
215
215
|
saved while the app runs (a layout, today) and answers it in the same
|
|
216
|
-
place. It
|
|
216
|
+
place. It alone keeps the
|
|
217
217
|
entries too: the ones the app shipped and each set handed over, compiled as
|
|
218
218
|
vex replays them. It stands on `manifest`,
|
|
219
219
|
the app as it was handed over: the types an app is written in, the schema
|
|
@@ -224,7 +224,7 @@ entry.
|
|
|
224
224
|
role, and the tables with their migration. The engine's cache asks the
|
|
225
225
|
artifactory for a fingerprint first, through two functions the server
|
|
226
226
|
hands it, and its own table (`vex_cache`) for what the artifactory does not
|
|
227
|
-
|
|
227
|
+
have: a query written for an intent while the app runs. Nothing is copied
|
|
228
228
|
into that table, and a copy an earlier release left in it is not replayed.
|
|
229
229
|
So what a fingerprint resolves to is decided in `artifactory`, as what an
|
|
230
230
|
action, a layout or a fragment resolves to is.
|
|
@@ -254,7 +254,7 @@ cannot write one. **The seams are made for the feature they are handed
|
|
|
254
254
|
to, and what they reach is that feature's**: its own tables, which it names on
|
|
255
255
|
itself before it runs (`Feature.tables.names`); its own set of actions, kept
|
|
256
256
|
under its name, which it alone writes; the documents in its own rows. The core reads and
|
|
257
|
-
writes no row of a feature, reads no header of one, and
|
|
257
|
+
writes no row of a feature, reads no header of one, and keeps no setting of
|
|
258
258
|
one (the key the integrations feature signs with is that feature's own).
|
|
259
259
|
`feature` is the module that says what a feature and
|
|
260
260
|
its seams are: types, and no code. There are two features: `integrations`
|
|
@@ -292,7 +292,7 @@ this is a copy of it:
|
|
|
292
292
|
|
|
293
293
|
The table has no cycle, and what it leaves out is as deliberate as what it
|
|
294
294
|
names. `shells` does not import `identity`: who somebody is, it is told.
|
|
295
|
-
`socket` does not import `artifactory`: what somebody
|
|
295
|
+
`socket` does not import `artifactory`: what somebody is granted is a function it
|
|
296
296
|
is handed. `artifactory` and `data` do not import each other: the generation
|
|
297
297
|
pointer's row is `data`'s, when it moves is the artifactory's, the entries
|
|
298
298
|
over the artifactory's two tables are written by the artifactory and replayed
|
|
@@ -310,7 +310,7 @@ whole runtime: those two are handed to `createServer`, and the wiring hands on
|
|
|
310
310
|
the parts. Each table and each long-lived piece of state has one owner, and
|
|
311
311
|
nobody else authors what is written to it. What crosses a boundary (a
|
|
312
312
|
manifest, a socket message, a route's body, a row, a token) is parsed by a
|
|
313
|
-
schema in the module where it enters, and no module
|
|
313
|
+
schema in the module where it enters, and no module contains a type assertion.
|
|
314
314
|
And a function is at most 300 lines (200 is fine; 300 is the ceiling), a file
|
|
315
315
|
at most 400 lines of code, a line at most 200 wide.
|
|
316
316
|
|
|
@@ -322,27 +322,28 @@ that made the table:
|
|
|
322
322
|
|---|---|---|---|
|
|
323
323
|
| `sessions` | `identity` | `identity/sessions.ts`: five statements straight to the pool, before anybody is signed in | Its table is made in `data`'s one migration run (`migrateTables`, or boot under `migrations: 'apply'`; otherwise boot only checks it), from a sequence `identity` declares |
|
|
324
324
|
| `moss_generation` | `data` | `data/own-entries.ts`: two entries, one that reads and one that moves | `artifactory` decides when it moves (`artifactory/generation.ts`), through a function `data` hands over |
|
|
325
|
-
| `artifact_saves`, `artifacts` | `artifactory` | `artifactory/saves.ts`:
|
|
326
|
-
| `integrations`, `integration_actions` | the `integrations` feature | `integrations/entries.ts`: vex entries, replayed through the seam the feature is handed | The two tables are made by the core's own sequence (`data/tables.ts`, `nisc.moss`): that is the history every database has run, and it is not edited. The documents stored in `integration_actions` are brought to the current grammars by `data`, which
|
|
325
|
+
| `artifact_saves`, `artifacts` | `artifactory` | `artifactory/saves.ts`: four vex entries (what is in force, the history, a save, and the stamp that one was used) and the row rule they run under, replayed through a function `data` hands over (`Data.artifactEntries`) | The two tables are made by the core's sequence (`data/tables.ts`, `nisc.moss/5`). Their rows are somebody's, unlike the pointer's: the entries are replayed with the caller's scope, and vex keeps every read and write to the rows whose `principal` is the caller's `userId`. What is published for everybody is the rows of the principal `*`, replayed with that as the `userId` by the server's own code and by no caller. The one update is `last_used_at`, stamped when a shell is built for the owner. A stored body is not rewritten when a grammar moves: it is brought to the current grammars where it is read. The sweep that deletes what a person generated and nobody used (`runtime.artifactsUnusedMs`) is `data/aging.ts`: two statements straight to the pool, because vex keeps every statement to one principal's rows and the sweep crosses them all |
|
|
326
|
+
| `integrations`, `integration_actions` | the `integrations` feature | `integrations/entries.ts`: vex entries, replayed through the seam the feature is handed | The two tables are made by the core's own sequence (`data/tables.ts`, `nisc.moss`): that is the history every database has run, and it is not edited. The documents stored in `integration_actions` are brought to the current grammars by `data`, which keeps the pool, when the feature asks through its seam |
|
|
327
327
|
|
|
328
|
-
`data`
|
|
328
|
+
`data` has the engine and the one ledgered migration run, so every owner's
|
|
329
329
|
entries and every owner's migrations run through it. It authors no statement
|
|
330
|
-
on a table that is not its own
|
|
330
|
+
on a table that is not its own, but for the aging sweep's two on the
|
|
331
|
+
artifactory's. The app's own tables, and tide's when the app
|
|
331
332
|
keeps them, are migrated in the same run (`runtime.tables`) and are the app's
|
|
332
333
|
and tide's.
|
|
333
334
|
|
|
334
|
-
What
|
|
335
|
+
What enforces the rules is a build that fails, not this page: `pnpm
|
|
335
336
|
check:modules` (the table above, the doors, nothing flat, no cycle, and no
|
|
336
337
|
feature in the core), `pnpm check:api` (an exported name is a line in
|
|
337
338
|
`api.txt`, and a line there is an exported name), `pnpm check:raw-sql` (a
|
|
338
339
|
statement outside vex is counted, with its reason) and `pnpm lint` (no type
|
|
339
340
|
assertion, no `any` that becomes a typed value, no written type predicate, the
|
|
340
341
|
two sizes and the width).
|
|
341
|
-
**Narrow inputs and one owner are
|
|
342
|
+
**Narrow inputs and one owner are enforced by none of the four**: they are read
|
|
342
343
|
for in review, and the table above is what a review found, not what a build
|
|
343
|
-
checks. What each gate
|
|
344
|
-
as somebody changing a package follows them are in
|
|
345
|
-
|
|
344
|
+
checks. What each gate enforces is said at the top of its script. The rules
|
|
345
|
+
as somebody changing a package follows them are in
|
|
346
|
+
`packages/nisc/CHANGING_A_PACKAGE.md`.
|
|
346
347
|
|
|
347
348
|
---
|
|
348
349
|
|
|
@@ -377,9 +378,9 @@ Operational shape, all falling out of "the message is state, not history":
|
|
|
377
378
|
- **Delivery.** Events are fire-and-forget; the tree is the confirmation. No
|
|
378
379
|
acks, no replay after reconnect — a replayed intention against a changed screen
|
|
379
380
|
is worse than a lost one, so reconnect simply re-sends the current trees. The
|
|
380
|
-
same rule
|
|
381
|
-
not open and nothing is
|
|
382
|
-
screen before its socket, so a press in that moment is dropped.
|
|
381
|
+
same rule applies before the first connect: nothing is sent on a socket that
|
|
382
|
+
is not open and nothing is kept back for when it is. A server-drawn page
|
|
383
|
+
(below) is on screen before its socket, so a press in that moment is dropped.
|
|
383
384
|
- **Durability.** The database is the durable thing; a shell is a warm cache,
|
|
384
385
|
rebuilt on the next connection from definitions and whatever the app reads
|
|
385
386
|
from rows as it builds. Evicting an idle shell, restarting the process and
|
|
@@ -401,10 +402,10 @@ Operational shape, all falling out of "the message is state, not history":
|
|
|
401
402
|
nova's shell keeps a journal of the positions its navigations displaced, and
|
|
402
403
|
`back` restores the newest one it can. So the browser's back button, a TUI's
|
|
403
404
|
Escape and an app's own control are one message, an app authors nothing to
|
|
404
|
-
receive it, and the terminal
|
|
405
|
+
receive it, and the terminal keeps no location that could drift out of step
|
|
405
406
|
with the server's. It is also the answer to a real failure: with no history
|
|
406
407
|
integration at all, a browser's back button unloaded the application.
|
|
407
|
-
- **A connection that drops.** The trees a terminal
|
|
408
|
+
- **A connection that drops.** The trees a terminal has stay on screen
|
|
408
409
|
while it reconnects: the current ones are re-sent when it does, and blanking
|
|
409
410
|
in between would show a working app as an empty one. The price is that a
|
|
410
411
|
screen left up by a dead socket looks exactly like a live one, so the
|
|
@@ -413,7 +414,7 @@ Operational shape, all falling out of "the message is state, not history":
|
|
|
413
414
|
them. What is drawn for it is not moss's: the two console targets print a
|
|
414
415
|
line, and the three that draw into an element say it on that element
|
|
415
416
|
(`data-wire-status`) and leave what it looks like to the app's stylesheet.
|
|
416
|
-
The terminal
|
|
417
|
+
The terminal has one socket at a time — it lets go of the one it had
|
|
417
418
|
before it makes another — so one connection writes the screen, whatever a
|
|
418
419
|
person pressed while the last was still connecting.
|
|
419
420
|
- **Emptiness.** A canvas whose layout renders no visible content is served as
|
|
@@ -424,7 +425,7 @@ Operational shape, all falling out of "the message is state, not history":
|
|
|
424
425
|
|
|
425
426
|
### Where a browser keeps its session
|
|
426
427
|
|
|
427
|
-
A terminal served by the app it talks to does not
|
|
428
|
+
A terminal served by the app it talks to does not keep its session. Its browser
|
|
428
429
|
does, in a cookie no script can read, and sends it by itself with the two
|
|
429
430
|
requests that need to know who is asking: the page, and the upgrade that opens
|
|
430
431
|
the socket. A token in the page — in storage, in a cookie script can read — is
|
|
@@ -437,7 +438,7 @@ cannot be taken from it.
|
|
|
437
438
|
request is answered, and the answer carries the cookie.
|
|
438
439
|
- **A sign-in over the socket reaches it sealed.** `session.grant` happens on a
|
|
439
440
|
socket, which cannot write a cookie; the token has to travel through the
|
|
440
|
-
page to the next upgrade. It travels encrypted with a key the browser
|
|
441
|
+
page to the next upgrade. It travels encrypted with a key the browser keeps
|
|
441
442
|
in a second cookie no script can read or set — the *seal*, given by the
|
|
442
443
|
answer to the browser's first upgrade under a name (`__Http-`) a browser
|
|
443
444
|
lets only an HTTP answer set. The page can hand a sealed sign-in back and
|
|
@@ -463,13 +464,13 @@ cannot be taken from it.
|
|
|
463
464
|
would sign each other out. Over https it is `__Host-` prefixed and `Secure`,
|
|
464
465
|
which a browser lets nothing but this host set.
|
|
465
466
|
- **What the page sees is a flag** (`<name>.held=1`), with no secret in it: how
|
|
466
|
-
a terminal knows to let go of a token it was
|
|
467
|
+
a terminal knows to let go of a token it was keeping, and that a page drawn
|
|
467
468
|
for somebody was drawn for it.
|
|
468
469
|
- **Signing out says so.** moss revokes its own credential, and a cookie that
|
|
469
470
|
no longer resolves is taken back on the next upgrade. An app's own provider's
|
|
470
471
|
token may go on resolving, so a terminal that was signed out says it is
|
|
471
|
-
leaving, and the cookie is taken back whatever it
|
|
472
|
-
- **Any other terminal
|
|
472
|
+
leaving, and the cookie is taken back whatever it carries.
|
|
473
|
+
- **Any other terminal keeps its own token** — a process, a page served from
|
|
473
474
|
somewhere else, a browser that refuses cookies — offers it, and is handed a
|
|
474
475
|
sign-in as its token, as before. A token such a page of the app's own offers
|
|
475
476
|
(one an earlier build left in storage) is moved into the cookie and let go of.
|
|
@@ -493,7 +494,7 @@ Two reductions are available, and they are deliberately separate things:
|
|
|
493
494
|
hundred thousand, which is the only reason it is a knob rather than a
|
|
494
495
|
constant.
|
|
495
496
|
- **Frame deltas** (`shellFrameDelta`, **off** by default) describe a changed
|
|
496
|
-
canvas against the frame the connection already
|
|
497
|
+
canvas against the frame the connection already has, as copy runs plus
|
|
497
498
|
literal inserts (`src/protocol/delta.ts` — an encoder and a decoder, both readable in
|
|
498
499
|
full, no dependency). Measured on Lyra: an in-place change (a keystroke
|
|
499
500
|
filtering a list, one row's badge flipping) falls to **1–4%** of the frame; a
|
|
@@ -569,9 +570,9 @@ mechanism). Anonymous connections get a throwaway shell, disposed on detach,
|
|
|
569
570
|
and so does every connection of a page.
|
|
570
571
|
|
|
571
572
|
**Every living shell follows a change.** When what the app consists of
|
|
572
|
-
changes, each shell that lives is brought level with what its principal
|
|
573
|
+
changes, each shell that lives is brought level with what its principal is granted
|
|
573
574
|
now, in place: the kept ones, a visitor's, and a page's, in every host. A
|
|
574
|
-
host
|
|
575
|
+
host keeps every shell it built from when its build lands until it ends, and
|
|
575
576
|
lets it go where it ends, so the walk is over the shells that live and no
|
|
576
577
|
other. A role change (`invalidateIdentity`) rebuilds every living shell of
|
|
577
578
|
that principal the same way: the kept one, and each one a page built for them.
|
|
@@ -595,12 +596,12 @@ the screen boot would serve that principal now — which is also the whole cost:
|
|
|
595
596
|
a reset is not a repair that preserves what someone was doing.
|
|
596
597
|
|
|
597
598
|
**One canvas cannot take the session down.** Rendering is guarded per canvas.
|
|
598
|
-
A tree that throws
|
|
599
|
+
A tree that throws keeps its last good frame and its neighbours keep rendering,
|
|
599
600
|
rather than killing the flush pass, escaping a microtask uncaught, and wedging
|
|
600
601
|
the shell for the life of the process.
|
|
601
602
|
|
|
602
603
|
The shell is built from the manifest: canvases and fragments are data; a canvas's
|
|
603
|
-
`initial` may be a candidate list, and the first action the principal
|
|
604
|
+
`initial` may be a candidate list, and the first action the principal is granted
|
|
604
605
|
mounts — so login is the anonymous principal's application (the charter's
|
|
605
606
|
`public` grant) by derivation, not a special case. The role name is fixed and
|
|
606
607
|
the charter has to define it, as `public: []` if it grants nothing: boot does
|
|
@@ -609,7 +610,9 @@ fails. `inputs(session)` and
|
|
|
609
610
|
`seeds(session)` are the app's per-principal boot hooks — boot data and boot
|
|
610
611
|
instances. Endpoint calls ride the server's own HTTP surfaces
|
|
611
612
|
with the session's token — the server shell is just another principal-bound
|
|
612
|
-
client, enforcement included.
|
|
613
|
+
client, enforcement included. The token replaces an `Authorization` the
|
|
614
|
+
endpoint declares, in whatever case it is spelt; a shell for nobody sends
|
|
615
|
+
what the endpoint declares.
|
|
613
616
|
|
|
614
617
|
---
|
|
615
618
|
|
|
@@ -633,7 +636,7 @@ The follow ends when the call's signal aborts (nova aborts it on unmount),
|
|
|
633
636
|
when the last subscriber leaves (nova unsubscribes when a newer call to the
|
|
634
637
|
same endpoint lands), or at once when nobody takes the response up — a server
|
|
635
638
|
function reading through the same wire follows nothing. An answer that changed
|
|
636
|
-
in the gap between the response and nova's subscription is
|
|
639
|
+
in the gap between the response and nova's subscription is kept back and handed
|
|
637
640
|
over on subscribe.
|
|
638
641
|
|
|
639
642
|
This retires most of "writers announce, viewers react" for data: a screen whose
|
|
@@ -664,7 +667,7 @@ page carries its screen twice (markup and snapshot), 3–5 KB compressed.
|
|
|
664
667
|
|
|
665
668
|
**The head of the page is part of the screen.** A title, a description and a
|
|
666
669
|
preview card are facts about what the screen shows, so the page's `<head>` is a
|
|
667
|
-
node in a layout (nova's `nova:head`,
|
|
670
|
+
node in a layout (nova's `nova:head`, carrying the elements a head contains) and
|
|
668
671
|
rides in the same trees as everything else: `renderDocument` reads the
|
|
669
672
|
elements off the snapshot and writes them into the template's `<head>`, and the
|
|
670
673
|
terminal reads them off the wire to keep the page's head. Nothing was added to
|
|
@@ -714,7 +717,7 @@ are terminals like the others — handed a screen, they draw it — and the same
|
|
|
714
717
|
shape as lyceum's SSH door, which has drawn served trees inside a server
|
|
715
718
|
process since before this existed.
|
|
716
719
|
|
|
717
|
-
One thing a kit must
|
|
720
|
+
One thing a kit must take care of: its first pass in the browser has to
|
|
718
721
|
draw what the server drew. Anything that differs between the two — the window's
|
|
719
722
|
width, a portal target, storage — may not decide a component's first render.
|
|
720
723
|
Lyra's kit answered "is the window wide" from `window.matchMedia` in a state
|
|
@@ -722,12 +725,12 @@ initialiser, behind a `typeof window` guard; the guard is the bug, because it
|
|
|
722
725
|
makes the two sides disagree about the same render, and on a wide screen React
|
|
723
726
|
threw the page's elements away. What a component writes onto `<html>` from an
|
|
724
727
|
effect (a palette) is not in the page until the script runs, so the app reads it
|
|
725
|
-
off the snapshot and hands it to the document. Each app
|
|
728
|
+
off the snapshot and hands it to the document. Each app guards both with a check.
|
|
726
729
|
|
|
727
730
|
## Pages
|
|
728
731
|
|
|
729
732
|
`shell` is the app: one durable shell per person, the thing that rearranges
|
|
730
|
-
itself around whoever
|
|
733
|
+
itself around whoever has it. Not everything at a path is that. A welcome, the
|
|
731
734
|
docs, a published talk are read, not worked in, and a person who is signed in is
|
|
732
735
|
still the same person when they open one.
|
|
733
736
|
|
|
@@ -751,7 +754,7 @@ still happen. Every reason a drawn screen is not finished is a declared part of
|
|
|
751
754
|
an action — a `ui:` trigger, a two-way binding, a channel it waits on, a read
|
|
752
755
|
that keeps answering — so the question is decidable from the definitions
|
|
753
756
|
actually mounted, without running anything. Nova reports those facts
|
|
754
|
-
(`livenessOf`); moss, which
|
|
757
|
+
(`livenessOf`); moss, which keeps the entries behind each fingerprint, composes
|
|
755
758
|
the verdict (`src/shells/snapshot.ts`) and puts it on the snapshot as `live`. A page that
|
|
756
759
|
is not live is served as markup and its terminal opens no socket at all. A page
|
|
757
760
|
that is live gets a shell for as long as its connection lasts — per connection,
|
|
@@ -781,8 +784,8 @@ the application guide puts it — shell state is the truth.
|
|
|
781
784
|
The `fn:` escape hatch runs server-side, in-process, next to the durable shell.
|
|
782
785
|
The manifest's `functions(session)` builds handlers once per session, closing
|
|
783
786
|
over the living shell, who is calling (the principal, their roles, what they
|
|
784
|
-
|
|
785
|
-
A session says who is calling and
|
|
787
|
+
are granted), the server's own surfaces as that session (`wire`), and `grant`/`revoke`.
|
|
788
|
+
A session says who is calling and has no key: it carries no database pool, no
|
|
786
789
|
operator key and no policy object, and what app code needs of those has a call
|
|
787
790
|
(DOCS.md, `FunctionSession`). Agents live here (their reads run under the
|
|
788
791
|
caller's policy — they see what the caller sees); keys are `.env`. This is deliberately the *side-
|
|
@@ -865,7 +868,7 @@ nothing.
|
|
|
865
868
|
| An auth provider | BYO identity. Who somebody is, the app decides at its own door (magic link is the default strategy); the server only asks who a token is. Moss does keep a credential an app may use for that: `mintSession` stores a token by its hash once the app has decided, and `'dev-open'` trusts an unsigned one for a harness. Neither decides anything. |
|
|
866
869
|
| A framework | An assembly point. The intelligence lives in the artifacts; the server resolves, serves, pushes, enforces. Its core is eleven modules, each one question or the wiring, and a twelfth that runs it on Node (*How the code is laid out*). |
|
|
867
870
|
| A place where policy hides | Every opinion it enforces is a readable artifact: charter, scope policy, assertion. No annotations, no interceptor magic. |
|
|
868
|
-
| A second way to do anything | Reads are vex, writes are vex, compute is functions, UI is actions, permissions are the charter. Moss's core adds no vocabulary of its own, and
|
|
871
|
+
| A second way to do anything | Reads are vex, writes are vex, compute is functions, UI is actions, permissions are the charter. Moss's core adds no vocabulary of its own, and is bound by the same: the rows it keeps it reads and writes through vex entries, and the statements left outside vex are counted, each with its reason (`pnpm check:raw-sql`). |
|
|
869
872
|
| A web framework | A page is a shell manifest at a path; a drawn document is a first frame delivered early. No file-system routes, no layouts-of-layouts, no loaders, and no chain of middleware for an app to configure (one gate may be laid over the operator prefix, `runtime.operatorGate`). A page's `<head>` is not managed either: it is a node in a layout, written into the document like the rest of the screen. The template, the route and the kit are the app's. |
|
|
870
873
|
|
|
871
874
|
## Deliberately unbuilt
|
|
@@ -880,15 +883,15 @@ On the record, so nothing reads as finished that isn't:
|
|
|
880
883
|
dropping their data). Verify-at-boot becomes verify-at-publish, same gates.
|
|
881
884
|
- **The `/fns` host** — named, side-effect-free, independently deployable
|
|
882
885
|
functions under `/fns`, gated by catalog closure.
|
|
883
|
-
- **The projection model** — per-identity state
|
|
884
|
-
pushed, seeded on login with no AI call,
|
|
886
|
+
- **The projection model** — per-identity state kept in the DB, written-and-
|
|
887
|
+
pushed, seeded on login with no AI call, kept while the principal is offline.
|
|
885
888
|
- **The working set (level streaming).** For large apps and AI context budgets,
|
|
886
889
|
the catalog itself streams: serve the graph neighborhood of a principal's
|
|
887
890
|
active actions now, fault the rest in on demand. Level streaming for humans is
|
|
888
891
|
context management for models — one mechanism, two products.
|
|
889
892
|
- **Scale-out** beyond sticky sessions pinned by session id. What crosses
|
|
890
893
|
processes today is invalidation only: `refresh` moves a generation pointer
|
|
891
|
-
every process polls (`src/artifactory/generation.ts`
|
|
894
|
+
every process polls (`src/artifactory/generation.ts` keeps the clock; the row is
|
|
892
895
|
read and moved through vex, `src/data/own-entries.ts`), and an optional fabric
|
|
893
896
|
(`runtime.fabric`, `src/server/signals.ts`) carries identity invalidations, nudges, and the word to adopt for one principal.
|
|
894
897
|
A set of actions does not cross: a process that follows the pointer reads
|
|
@@ -908,7 +911,7 @@ On the record, so nothing reads as finished that isn't:
|
|
|
908
911
|
parameters: the app's shell is durable and shared across a person's
|
|
909
912
|
terminals, so an opener has to be idempotent against whatever is already
|
|
910
913
|
mounted, and decide what a reload means after they have moved on.
|
|
911
|
-
- **Letting a page's connection go.** A terminal that
|
|
914
|
+
- **Letting a page's connection go.** A terminal that has a token on a page
|
|
912
915
|
drawn for nobody (a file, on a static host) connects, and is served a page
|
|
913
916
|
shell for as long as it stays — even when that page turns out not to be live
|
|
914
917
|
for them either. Closing such a connection once its frames are sent is unbuilt.
|