@dreamforgestudiollc/emet 0.3.5 → 0.3.6

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 CHANGED
@@ -7,19 +7,33 @@ change before 1.0.
7
7
 
8
8
  ## Unreleased
9
9
 
10
- Nothing is waiting above 0.3.5.
10
+ Nothing is waiting above 0.3.6.
11
+
12
+ ## 0.3.6 - 2026-11-11
13
+
14
+ Docs and a public-wording scrub. Stored data shapes are unchanged. Tool behavior is unchanged. The declared version is 0.3.6. This revision is not published from this change. The 0.3.5 package on npm was published before this cleanup, so that tarball still predates it.
15
+
16
+ ### Added
17
+ - [docs/ROADMAP.md](docs/ROADMAP.md) has an Upcoming work section. Workshop Village MCP and shared project drawers are Proposed and not built. Per-source-tag handoffs are Planned and are not in this public release. Fuller multi-person use of the one server is a later phase and is not built. Continuity-currency enforcement on initialize is Planned. Backup and restore verification is Planned. The clone-instance recipe is already documented in [docs/SECURITY-AT-SCALE.md](docs/SECURITY-AT-SCALE.md). Stronger source-tag onboarding and further per-door extensions are Planned. The extension socket itself is built. Topic-page currency and lock levels are Planned. Topic views already shipped in 0.3.0. Transcript query improvements and stricter read-tool input validation are Planned. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
18
+ - [RELEASE_NOTES-0.3.6.md](RELEASE_NOTES-0.3.6.md).
19
+
20
+ ### Changed
21
+ - Public wording no longer names an install-specific retired account in source comments, log lines, or the test that carried a live host. The retirement check still matches that account by digest. The GEM schema id is an in-repo identifier, `emet:gem-library/gem.schema.json`, the same string the checker expects. The extension socket is described as built, matching `CHARTER.md` and `src/socket.js`. Historical release notes for 0.2.6 are marked historical. The 0.3.5 sentence that said comments had already dropped the retired account is corrected below. `EMET-AUTH-045` is refused at a new consent, a sub-key request, a writer request, a member or guest code, a setup source, a chooser decision, and a break-glass reissue. The npm package also ships `RELEASE_NOTES*.md`, `SECURITY.md`, and `CONTRIBUTING.md`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
22
+
23
+ ### Upgrade
24
+ - No stored-data migration. No new setting. Deploy over 0.3.5 as is. The retirement marker on a new database stores a public label. An existing marker is left as it was. Matching still uses the digest of the retired account id.
11
25
 
12
26
  ## 0.3.5 - 2026-11-10
13
27
 
14
28
  This release brings the public docs current with the code. Stored data shapes are unchanged. The declared version is 0.3.5.
15
29
 
16
30
  ### Upgrade
17
- - The bound door's tag is `bound-host`. Writes from a stored legacy token or sub-key are stamped `bound-host`. The alias covers stored data only. The previous spelling is refused for a new consent, a new sub-key request, a new writer request, a new member or guest code, a new setup source, and a chooser decision. The alias is a digest, so this package does not spell the old tag.
31
+ - The bound door's tag is `bound-host`. Writes from a stored legacy token or sub-key are stamped `bound-host`. The alias covers stored data only. The previous spelling is refused for a new consent, a new sub-key request, a new writer request, a new member or guest code, a new setup source, a chooser decision, and a break-glass reissue. The alias is a digest, so this package does not spell the old tag.
18
32
 
19
33
  ### Changed
20
34
  - `CHARTER.md` §4 says the extension socket is built. It is `src/socket.js`. Its note is `docs/gem/README.md`. Public text no longer names an install-specific hub or host tag. Writer-approval text says the hub login. The tag that login matches is still `hub-bot`. The bound-door tag the server matches is `bound-host`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
21
35
  - The site tool table counts 38 tools with sub-keys off: 15 read-only, 13 additive, and 8 that replace or hand out access, plus `retire_doc` and `emet_status`. The public site says 0.3.2 was published to npm on 2026-10-28. Owner instructions name `/owner/chooser`. `docs/ROADMAP.md` is dated 2026-11-10, marks the site and the npm package live, and names the 0.3.0 topic-page tools `emet_page`, `emet_pages`, and `emet_page_lint`. `.env.example` and `docs/DEPLOY.md` document `EMET_CLAIMED_TAG_KILL_DATE` (unset uses `2026-12-15`, then `EMET-AUTH-040`), `EMET_DEEP_LINK_TTL_MINUTES` (default 15), and `EMET_RESTORE_TAGS`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
22
- - The README counts 38 tools with sub-keys off, 15 of them read-only, and 42 with `EMET_SUBKEYS=1`. `docs/ROADMAP.md` names the same live count, and GEM socket PR 4 is shipped in 0.2.6. `docs/SETUP.md` and `docs/DEPLOY.md` carry upgrading notes through 0.3.5. The public site has What-changed sections for 0.3.1, 0.3.2, 0.3.3, and 0.3.4. Comments no longer name the private repository or the retired account id. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
36
+ - The README counts 38 tools with sub-keys off, 15 of them read-only, and 42 with `EMET_SUBKEYS=1`. `docs/ROADMAP.md` names the same live count, and the GEM socket's fourth phase is shipped in 0.2.6. `docs/SETUP.md` and `docs/DEPLOY.md` carry upgrading notes through 0.3.5. The public site has What-changed sections for 0.3.1, 0.3.2, 0.3.3, and 0.3.4. Source comments in the published 0.3.5 package still named a retired account. That scrub is recorded under 0.3.6. The 0.3.5 npm tarball predates it. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
23
37
  - Version 0.3.5. `package.json`, `package-lock.json`, `server.json`, `glama.json`, `.cursor-plugin/plugin.json`, and `src/version.js` agree. The README and the public site name the same version. `mcp.json` has no version. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
24
38
  - The default `EMET_REPORT_EMAIL` is `dreamforgestudio@mail.grokbot.com` again. The default in 0.3.2, 0.3.3, and 0.3.4, `dreamforgestudio@mail.hubbot.com`, was wrong. The 0.3.1 line below records the address that release shipped.
25
39
 
@@ -38,18 +52,18 @@ Public pull request #26, the changes since 0.3.3. Stored data shapes are unchang
38
52
 
39
53
  ## 0.3.3 - 2026-11-03
40
54
 
41
- Listing text from public pull request #24, plus the public parts of private #97 and #98. Private #95 (session disposition) and #96 (the 0.3.2 public sync) are already in 0.3.2. Stored data shapes are unchanged. 0.3.3 was published to npm on 2026-11-03. Filled disposition inventories stay in the private repository.
55
+ Listing text from public pull request #24, plus internal changes that landed in this public release. Session disposition and the 0.3.2 public sync are already in 0.3.2. Stored data shapes are unchanged. 0.3.3 was published to npm on 2026-11-03. Filled disposition inventories stay out of this public listing.
42
56
 
43
57
  ### Added
44
- - Carry-forward close. `emet_session_close` takes `carry_forward` with `disposition_doc`, `disposition_version`, and `citations` when a later session already advanced HANDOFF or STATE. The owner door, or the credential that wrote the session, cites a current conforming session disposition (`CARRIED_FORWARD`, `SUPERSEDED_BY_LATER_SESSION`, or `ABANDONED_NO_TRANSCRIPT`) and those later versions. `RETAINED_OPEN_CRITICAL` stays open. A declared source is not authority. Transcripts stay. A refused call is not counted. A receipt close blocked only because a later session holds HANDOFF or STATE stays blocked and is not counted. From private #97. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
45
- - Owner page portrait. `/owner/chooser` and `/owner/break-glass` use `site/assets/portrait.webp` as the page background, served at `/owner/assets/portrait.webp`. The sheet is a scrim. A missing file leaves the page without a portrait and does not stop startup. The npm package does not ship `site/`. The deploy image copies the portrait. From private #98. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
58
+ - Carry-forward close. `emet_session_close` takes `carry_forward` with `disposition_doc`, `disposition_version`, and `citations` when a later session already advanced HANDOFF or STATE. The owner door, or the credential that wrote the session, cites a current conforming session disposition (`CARRIED_FORWARD`, `SUPERSEDED_BY_LATER_SESSION`, or `ABANDONED_NO_TRANSCRIPT`) and those later versions. `RETAINED_OPEN_CRITICAL` stays open. A declared source is not authority. Transcripts stay. A refused call is not counted. A receipt close blocked only because a later session holds HANDOFF or STATE stays blocked and is not counted. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
59
+ - Owner page portrait. `/owner/chooser` and `/owner/break-glass` use `site/assets/portrait.webp` as the page background, served at `/owner/assets/portrait.webp`. The sheet is a scrim. A missing file leaves the page without a portrait and does not stop startup. The npm package does not ship `site/`. The deploy image copies the portrait. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
46
60
 
47
61
  ### Fixed
48
62
  - Version 0.3.3. `server.json`, `package.json`, and `glama.json` descriptions lead with ISO 9001 7.5.3 / ISO 13485 4.2.5 document control. The registry description stays within 100 characters. It says "Nothing is deleted.", which is `CHARTER.md` §3 commitment 2. `.cursor-plugin/plugin.json` leads with the same line. The wording landed in public pull request #24 at version 0.3.2 and was not published. `CHARTER.md` §7, `templates/STANDARD.md`, and the README document-control section are unchanged. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
49
63
 
50
64
  ## 0.3.2 - 2026-10-28
51
65
 
52
- Release notes for the access ladder and the work after 0.3.1. npm is not published from this change. Older release sections below are historical and are not rewritten. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
66
+ Release notes for the access ladder and the work after 0.3.1. This section was written before 0.3.2 was published. 0.3.2 later shipped to npm on 2026-10-28. Older release sections below are historical and are not rewritten. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
53
67
 
54
68
  ### Added
55
69
  - Door grants. The grant id is the OAuth token family minted at consent. `verifyAccessToken` returns that id and the door (`owner`, `member`, or `guest`). A new passphrase consent stores `issued_via: owner`. A legacy token with no marker stays unmarked, and its door on the stamp is null, not a guessed owner. A legacy member token stays a member for freeze checks, and that stamp still records door null. New writes stamp `grant_id` and `door` from the login. A caller-supplied grant id or door is not stored. Stdio stamps `grant_id: null` and `door: stdio`. An error with no transport stores door `unknown`. `emet_initialize` and `emet_status` return `grant_id` and `door` beside the effective tag and basis. Tag memory stays keyed by `client_id`. The error log, the owner error report, and the tool-call audit store `client_id`, `grant_id`, and `door`. A grant id longer than a family, including a bearer, is stored as `none`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
@@ -117,10 +131,10 @@ Release notes for the access ladder and the work after 0.3.1. npm is not publish
117
131
  - A RUNE may import only a file under the same GEM's `runes/`. A relative import that normalizes outside `runes/`, such as `../lib/h.js`, is refused even when that file is listed. A resolved real path outside `runes/` is refused, so a symlink that leaves `runes/` cannot be imported. A symlinked GEM directory fails GC-01 (`symlink`), and that refusal is not reused for the real directory. A symlinked file under `runes/` fails GC-04 (`symlink`) and is not followed. The socket records that refusal instead of omitting the entry. A `.JS` file under `runes/` is scanned. `.cjs` is not treated as a JavaScript module.
118
132
  - The deploy image and the npm package include `verification/`. `src/host-reach.js` imports the RUNE load gate from there. A release that omitted the directory crashed at startup with `ERR_MODULE_NOT_FOUND`.
119
133
  - RUNE import specifiers are checked in the vendored load gate (`runeSpecifierReason`). A bare package, `node:`, a URL, `emet/rune`, a path that normalizes outside the GEM, `../` with no file list, and a relative import that is not in the passed file list are refused. gem-check calls the same function. GC-16 still allows `emet/rune`; GC-19 still names that failure. A file under `runes/` that is not `.js` or `.mjs` fails GC-16 (`rune extension`) instead of being skipped.
120
- - The GC-19 load gate is an allowlist (`verification/load-gate/load-gate.mjs`, the file EMET-GEMs vendors with `corpus.json`). acorn 8.19.0, fail closed, no second scan. Only listed AST nodes are admitted. No `var`, and no binding may reuse a top-level name. `Math` is only a direct read or call of a listed member, never `random`, and the Math object is never stored, passed, or returned. A computed key is a literal, a `const` bound directly to a primitive literal, or a read of a top-level `Object.freeze({ __proto__: null, … })` table inside a recognized `Object.hasOwn` guard. The guarded key is one `const` that is a primitive before the guard (`const n = String(input.n)` or `Number(...)`, or a recognized `typeof` check for `'string'` or `'number'`). A const object is refused: `toString` or `Symbol.toPrimitive` can return one own key at the check and another at the read. A member, a `let`, or a parameter does not qualify. The guard's non-own-key safety rests on the table being frozen with a null prototype. `.freeze` counts only on the unbound `Object` identifier. There is no loop-index exception. Tables are not passed, spread, or returned. A member write is admitted only on an object or array born in that function. `prototype`, `Array.prototype`, `Error.prepareStackTrace`, and `RegExp.$1` fail. `toLocaleString`, `localeCompare`, `toLocaleDateString`, and `toLocaleTimeString` fail (`intl`). `Buffer`, including `Buffer.allocUnsafe`, fails (`memory`). A `for (const k of …)` key still needs `String`/`Number` or a `typeof` check. `toLocaleUpperCase`, `toLocaleLowerCase`, and a destructured locale name fail (`intl`). A computed key in a binding or assignment pattern must be a string or number literal, including nested patterns, parameters, defaults, `catch`, and `for-of`. Concatenation, a member, and a const used as that key fail. `m['call']` fails with `.call`. The checker accepts spec `2026-10-12` and optional `changelog`, `update`, `knowledge`, and `coverage`. A `coverage` list holds at most 256 entries.
134
+ - The GC-19 load gate is an allowlist (`verification/load-gate/load-gate.mjs`, the file a library checkout can vendor with `corpus.json`). acorn 8.19.0, fail closed, no second scan. Only listed AST nodes are admitted. No `var`, and no binding may reuse a top-level name. `Math` is only a direct read or call of a listed member, never `random`, and the Math object is never stored, passed, or returned. A computed key is a literal, a `const` bound directly to a primitive literal, or a read of a top-level `Object.freeze({ __proto__: null, … })` table inside a recognized `Object.hasOwn` guard. The guarded key is one `const` that is a primitive before the guard (`const n = String(input.n)` or `Number(...)`, or a recognized `typeof` check for `'string'` or `'number'`). A const object is refused: `toString` or `Symbol.toPrimitive` can return one own key at the check and another at the read. A member, a `let`, or a parameter does not qualify. The guard's non-own-key safety rests on the table being frozen with a null prototype. `.freeze` counts only on the unbound `Object` identifier. There is no loop-index exception. Tables are not passed, spread, or returned. A member write is admitted only on an object or array born in that function. `prototype`, `Array.prototype`, `Error.prepareStackTrace`, and `RegExp.$1` fail. `toLocaleString`, `localeCompare`, `toLocaleDateString`, and `toLocaleTimeString` fail (`intl`). `Buffer`, including `Buffer.allocUnsafe`, fails (`memory`). A `for (const k of …)` key still needs `String`/`Number` or a `typeof` check. `toLocaleUpperCase`, `toLocaleLowerCase`, and a destructured locale name fail (`intl`). A computed key in a binding or assignment pattern must be a string or number literal, including nested patterns, parameters, defaults, `catch`, and `for-of`. Concatenation, a member, and a const used as that key fail. `m['call']` fails with `.call`. The checker accepts spec `2026-10-12` and optional `changelog`, `update`, `knowledge`, and `coverage`. A `coverage` list holds at most 256 entries.
121
135
  - The per-RUNE description and served response wrap the `metadata.gem` value in backticks, so the sentence period is not copied with the value.
122
136
  - A per-RUNE tool states the exact `metadata.gem` value (`<gem>@<version>`, for example `fieldnote@1.0.1`) in its description and in the served response. A save that does not use that form says `metadata.gem` must be `'<gem>@<version>'`.
123
- - The serve log file `logs/gem-serves.json` keeps the latest `SERVE_CAP` (200) rows for each principal, so one caller cannot evict another. This release creates the new collection `<prefix>gem_serves` (`SERVE_COLLECTION`). Alex approved it as an append-only write site on the write-path allow-list. The collection keeps every row. Nothing is deleted. A redeploy that drops the file can still seal a result. Concurrent serves write distinct temp files, and one process records one serve at a time. Tests point the file at a temp path. The guard and the GC-19 load gate reject `vm`, `new Function`, and a computed `import()` path. When the store is not connected, the file is the only copy and a redeploy drops it. Fieldnote is off by default. See SPEC.md §10.
137
+ - The serve log file `logs/gem-serves.json` keeps the latest `SERVE_CAP` (200) rows for each principal, so one caller cannot evict another. This release creates the new collection `<prefix>gem_serves` (`SERVE_COLLECTION`). the owner approved it as an append-only write site on the write-path allow-list. The collection keeps every row. Nothing is deleted. A redeploy that drops the file can still seal a result. Concurrent serves write distinct temp files, and one process records one serve at a time. Tests point the file at a temp path. The guard and the GC-19 load gate reject `vm`, `new Function`, and a computed `import()` path. When the store is not connected, the file is the only copy and a redeploy drops it. Fieldnote is off by default. See SPEC.md §10.
124
138
  - Error text again replaces a stack frame with `[stack-frame]`. The publish workflow runs only on a published release. Public text no longer carries a private path, a private branch name, or an install-specific display name.
125
139
  - Bot-team backup references name `gems/bot-team-backup/guides/BOT_TEAM_BACKUP.md`, the file on disk.
126
140
 
@@ -130,7 +144,7 @@ Release notes for the access ladder and the work after 0.3.1. npm is not publish
130
144
  - Version 0.2.6. Charter commitment 1 again states the client-executed RUNE carve-out: EMET verifies the record, not the computation. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
131
145
 
132
146
  ### Docs
133
- - Client-side execution of RUNED directives (GEP-0003, accepted by Alex 2026-10-16). Supersedes GEP-0002, which is kept. The socket must not run RUNE code. One read-only tool per RUNE serves that RUNE's code, inputs, outputs, description, and served hash. SPEC.md §10–12, CONFORMANCE.md GC-19, the charter commitment 1 carve-out (EMET verifies the record, not the computation) and the Extension-socket row, and `docs/gem/README.md`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged. No code change in this revision.
147
+ - Client-side execution of RUNED directives (GEP-0003, accepted by the owner on 2026-10-16). Supersedes GEP-0002, which is kept. The socket must not run RUNE code. One read-only tool per RUNE serves that RUNE's code, inputs, outputs, description, and served hash. SPEC.md §10–12, CONFORMANCE.md GC-19, the charter commitment 1 carve-out (EMET verifies the record, not the computation) and the Extension-socket row, and `docs/gem/README.md`. ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged. No code change in this revision.
134
148
 
135
149
  ## 0.2.5 - 2026-10-14
136
150
 
@@ -159,7 +173,7 @@ Per-session attribution with client approval, the GEM socket with the bundled Ne
159
173
  ### Docs
160
174
 
161
175
  - README and website: version 0.2.5; a GEM socket fact; the website gains a Document control (ISO 9001 7.5.3 / ISO 13485 4.2.5) fact in the README's words; the tool count is 30 with `emet_client_approve` (docs/PERMISSIONS.md lists it with the tools that can replace or hand out access).
162
- - GEM standard, Draft revision 2026-10-11, in `gem-library/` (canonical home: the private repository EMET-GEMs). The charter's extension socket, commitment 8, and the core-floor row are revised: EMET is a memory resource, core floor protections stay non-removable, and neurodivergent engagement is the bundled Neurendipity GEM, off unless the user asks.
176
+ - GEM standard, Draft revision 2026-10-11, in `gem-library/` (the text is `gem-library/` in this repository, Draft). The charter's extension socket, commitment 8, and the core-floor row are revised: EMET is a memory resource, core floor protections stay non-removable, and neurodivergent engagement is the bundled Neurendipity GEM, off unless the user asks.
163
177
  - Registering a bot (`docs/BOTS.md` §4, with a pointer in `docs/DEPLOY.md`): every bot writes under its own source tag, `<prefix>-<bot>`. When a bot joins the roster, append its tag to the end of `EMET_SOURCE_TAGS`, keep every existing tag in order, and add `bots/<tag>/HANDOFF.md` to `EMET_RECORD_DOCS` before its first write. Setting either variable redeploys the server; afterwards, check `/health` and `emet_status`.
164
178
 
165
179
  ## 0.2.4 - 2026-10-08
package/CHARTER.md CHANGED
@@ -58,7 +58,7 @@
58
58
  | **The database boundary** | The login EMET runs under may add and update, never remove the record (2026-09-29). Commitment 2 is enforced by the database as well as by the server. | Database role, defined once in server code |
59
59
  | **The read path** | Returns entries with their integrity status, verified by the aleph. A superseded entry surfaces marked, naming what replaced it and the date it ended (decided 2026-09-13); a lookup by any id in a supersession chain also returns the live end of the chain, so a cross-reference keeps resolving after every later revision (2026-09-15). An expired entry surfaces the same way, marked with its end date. Current entries come first in every order, including time order. Retired documents stay in the document list and the startup scan, after the current documents, marked with the date and what replaced them. Recall ranks by relevance and importance. Time order is `order: 'latest'`, or a standalone latest, newest, or most recent together with other words. Retained document revisions are readable in full. | Server code |
60
60
  | **Supplementary corpus** | Optional reference material loaded by the user, separate from memory. | Server code |
61
- | **Extension socket** | **The socket is built.** It is `src/socket.js`. Its note is `docs/gem/README.md`. The standard is specified. The seat for a GEM (Golem Expertise Module). A RUNED directive (Registered Utility Node Executable Directive) is a declared, registered tool built into a GEM. A RUNED GEM carries at least one. The 2026-09-08 names (Guided Engagement Module, Registered Utility Node Extension) are superseded. The standard lives in the GEM library: private repository EMET-GEMs (`https://github.com/dreamforgestudiollc/EMET-GEMs`). In this repository the text under review is `gem-library/` until that folder is moved. **Precedence:** core floor protections outrank the user's current word, which outranks active GEMs by priority. A GEM may change a modifiable default (voice, pace, how much is explained) only with the user's consent when it is activated (the 2026-09-11 decision, kept for those defaults). **Floor protection:** core floor protections are non-removable. No GEM may weaken them. A GEM may add depth that complements them. Neurodivergent engagement lives in the bundled Neurendipity GEM (`neurendipity`), which is off unless the user asks for it. The list of GEMs installed on this server, active or not, is part of `emet_initialize` and of what a bot is shown at startup. Only the user and the user's bots change the GEM standard. Anyone may author a GEM that follows it. A GEM that does not ship inside an EMET release loads only after the library's security gate and the user's acceptance. The socket enforces that (commitment 5). **Client execution, a carve-out from commitment 1 (2026-10-16):** EMET verifies the record, not the computation. Client-executed RUNE results are recorded as attested by the client; they are replayable from recorded inputs, not re-executed by EMET. The socket does not run RUNE code. | `src/socket.js`, `docs/gem/README.md`, `gem-library/SPEC.md` |
61
+ | **Extension socket** | **The socket is built.** It is `src/socket.js`. Its note is `docs/gem/README.md`. The standard is specified. The seat for a GEM (Golem Expertise Module). A RUNED directive (Registered Utility Node Executable Directive) is a declared, registered tool built into a GEM. A RUNED GEM carries at least one. The 2026-09-08 names (Guided Engagement Module, Registered Utility Node Extension) are superseded. The standard in this repository is Draft, in `gem-library/` (`gem-library/SPEC.md`). A public submission repository for outside GEMs does not exist yet. Its name is not chosen. **Precedence:** core floor protections outrank the user's current word, which outranks active GEMs by priority. A GEM may change a modifiable default (voice, pace, how much is explained) only with the user's consent when it is activated (the 2026-09-11 decision, kept for those defaults). **Floor protection:** core floor protections are non-removable. No GEM may weaken them. A GEM may add depth that complements them. Neurodivergent engagement lives in the bundled Neurendipity GEM (`neurendipity`), which is off unless the user asks for it. The list of GEMs installed on this server, active or not, is part of `emet_initialize` and of what a bot is shown at startup. Only the user and the user's bots change the GEM standard. Anyone may author a GEM that follows it. A GEM that does not ship inside an EMET release loads only after the library's security gate and the user's acceptance. The socket enforces that (commitment 5). **Client execution, a carve-out from commitment 1 (2026-10-16):** EMET verifies the record, not the computation. Client-executed RUNE results are recorded as attested by the client; they are replayable from recorded inputs, not re-executed by EMET. The socket does not run RUNE code. | `src/socket.js`, `docs/gem/README.md`, `gem-library/SPEC.md` |
62
62
 
63
63
  ## §5 HIERARCHY
64
64
 
@@ -0,0 +1,21 @@
1
+ # Contributing
2
+
3
+ ## Before you open a pull request
4
+
5
+ - Open an issue first for anything beyond a typo. The feature template asks the four questions EMET asks of every change it builds ([CHARTER.md](CHARTER.md)).
6
+ - Run the tests: `npm ci && npm test`.
7
+ - Keep the write path additive. No change may add a delete or a remove on any store. `write-path.test.js` and `atlas-role.test.js` enforce this.
8
+
9
+ ## Set by the maintainer
10
+
11
+ These change only by the maintainer's decision:
12
+
13
+ - [CHARTER.md](CHARTER.md).
14
+ - The core floor (`src/floor.js`) and its protected lines.
15
+ - The README's document-control section (ISO 9001 7.5.3 / ISO 13485 4.2.5).
16
+ - Attribution: source tags, session and load ids, client approval.
17
+ - The GEM standard, schema and socket rules in [`gem-library/`](gem-library/). Anyone may author a GEM; see [gem-library/AUTHORING.md](gem-library/AUTHORING.md).
18
+
19
+ ## Security
20
+
21
+ See [SECURITY.md](SECURITY.md).
package/README.md CHANGED
@@ -26,7 +26,8 @@ See also: [CHANGELOG](CHANGELOG.md) · [CONTRIBUTING](CONTRIBUTING.md) · [SECUR
26
26
  - **Per-client attribution and approvals.** Every write is attributed to the client that made it. A new client is read-limited until it is approved. The approval is recorded.
27
27
  - **Error codes and problem reports.** Every error carries a stable `EMET-<AREA>-<NNN>` code. An operational error log keeps 10,000 entries or 90 days, plus daily summaries. The owner-only `emet_error_report` returns the report and an email draft that you send yourself. See [Reporting a problem](#reporting-a-problem).
28
28
  - **verify-emet and the feature map.** `npm run verify` runs `scripts/verify-emet.mjs` from a checkout. It starts EMET in a temporary directory on the in-memory test database, with no `.env`, and drives every registered tool. A tool that needs a service a plain install does not have is reported as a gap. A run whose only problems are gaps exits 3. A failed tool exits 1. The map is [docs/features/README.md](docs/features/README.md).
29
- - **MIT.** Version 0.3.5. EMET is still 0.x: stored document shapes may change before 1.0. Pin a version if you depend on them.
29
+ - **MIT.** Version 0.3.6. EMET is still 0.x: stored document shapes may change before 1.0. Pin a version if you depend on them.
30
+ - **Roadmap.** What is proposed, planned, or a later phase is [docs/ROADMAP.md](docs/ROADMAP.md). An item there is not built unless it says so. Upcoming work is labeled Proposed, Planned, or Later phase. Discussion is in [GitHub issues](https://github.com/dreamforgestudiollc/EMET/issues).
30
31
 
31
32
  The store has one owner, and other people can join only through the optional Guest
32
33
  (read-only) and Member (read and write) access, both off by default.
@@ -43,11 +44,20 @@ EMET is built for document control in environments that work under ISO 9001 and
43
44
  - **Templates are controlled documents.** Base templates ship with the release, and the shipped copy governs. Every templated write is checked against its template, and a write that fails is kept and marked for review, never silently accepted or discarded.
44
45
  - **A test holds the line.** `write-path.test.js` fails if anything in `src/` removes from a layer, document or transcript collection, and `atlas-role.test.js` fails if the database role grants remove.
45
46
 
46
- ## 30-second start
47
+ ## Start here
48
+
49
+ ```
50
+ npm install
51
+ cp .env.example .env
52
+ npm start
53
+ ```
54
+
55
+ Node.js 22 or newer. Fill in `MONGODB_URI` and `MONGODB_DB`. `.env` is gitignored.
47
56
 
48
57
  - **Guided setup:** [docs/GUIDED-SETUP.md](docs/GUIDED-SETUP.md) — never deployed anything. Your assistant installs, configures, deploys, and verifies. You sign in when asked and paste the connector URL.
49
58
  - **Setup:** [docs/SETUP.md](docs/SETUP.md) — the manual walkthrough: MongoDB, both transports, and the first-run interview.
50
59
  - **Deploy:** [docs/DEPLOY.md](docs/DEPLOY.md) — remote HTTP with OAuth, so a phone, a browser, or another vendor's agent reaches the same store.
60
+ - **What is next:** [docs/ROADMAP.md](docs/ROADMAP.md) — Upcoming work is labeled Proposed, Planned, or Later phase, and it is not built unless the page says so.
51
61
 
52
62
  > **Status: 0.x. The stored document shapes are not frozen yet.** Breaking changes to the
53
63
  > schema may land before 1.0. Pin a version if you depend on it.
@@ -885,12 +895,11 @@ Honest list, because the point of this project is that it behaves predictably:
885
895
  - The monorail (session graph) refuses every skipped step (enforce only since 2026-10-03; there
886
896
  is no report mode or off switch). Its turn coverage is only as strong as the exchange numbers hosts report, and it never sees
887
897
  the reply text. See [Guardrails & Monorails](docs/GUARDRAILS-AND-MONORAILS.md).
888
- - The scheduled weekly intake writes without opening a session, so the session-order check
889
- refuses those writes (gate `no_session`) until the routine opens a session with its startup's
890
- `load_id` and passes the `session_id`. Its old source tag, `cloud-scheduled-intake`, was retired on
891
- 2026-10-02. A `cloud-scheduled-` prefix is not a registered tag, and those writes are refused.
892
- The weekly intake runs under `intake-bot`. `emet_gaps` keeps counting the rows already written
893
- under the old tag as ambiguous attribution instead of rewriting history.
898
+ - A scheduled job that writes without opening a session is refused by the session-order check
899
+ (gate `no_session`) until it opens a session with its startup's `load_id` and passes the
900
+ `session_id`. A `cloud-scheduled-` prefix is not a registered tag. Only an exact tag in
901
+ `EMET_SOURCE_TAGS` is accepted. `emet_gaps` keeps counting rows already written under an old
902
+ tag as ambiguous attribution instead of rewriting history.
894
903
  - `save_transcript`'s description does not state that it stores content verbatim; the
895
904
  implementation does.
896
905
  - No export / import / restore-and-compare yet.
@@ -0,0 +1,43 @@
1
+ # EMET 0.2.6
2
+
3
+ Historical notes for 0.2.6. The current release in this repository is 0.3.6. See [CHANGELOG.md](CHANGELOG.md). The sentence that used to say the npm package was still 0.2.4 is withdrawn. 0.2.6, and later versions through 0.3.5, were published. 0.3.6 is not published from this revision.
4
+
5
+ EMET is an MCP memory server: persistent shared memory for AI agents, bot teams, and chats. Version 0.2.6. The stored document shapes are not frozen. Pin a version if you depend on them.
6
+
7
+ EMET holds no certification and claims no conformity. The document-control wording is unchanged: ISO 9001 7.5.3 / ISO 13485 4.2.5.
8
+
9
+ ## Record
10
+
11
+ Nothing is deleted, on any store, by design. A memory entry is superseded by a new revision. A document is revised or retired, and retired means obsolete, not gone. Prior versions stay, and a retained revision can be read back and checked against its stored digest. Templates are controlled documents. A write that fails its template check is kept and marked, not discarded.
12
+
13
+ Every write is read back and compared before it is reported as saved.
14
+
15
+ ## Attribution and approvals
16
+
17
+ Every write is attributed to the client that made it. A declared source tag does not gain rights beyond the login it is bound to. A new client is read-limited until it is approved. The approval is recorded. On a fresh store, the first solo client is approved as the owner's primary. Pending clients are reported to the owner, or to the chief-of-staff tag when that is set.
18
+
19
+ ## GEM socket
20
+
21
+ Add-on behavior ships as GEMs (Golem Expertise Modules). A GEM ranks below the core floor and below the user's current word. It cannot remove a protected floor line. Neurendipity and Lean Six Sigma are work-in-progress examples and stay off unless the install turns one on. Neurendipity is support material, not counseling or treatment. Fieldnote is a developer case-study of a runed GEM. It is not a user-facing GEM, and it is off by default.
22
+
23
+ ## Client-side GEM execution
24
+
25
+ A GEM may declare a tool. EMET does not run that computation. EMET verifies the record, not the computation. The client runs the tool. What gets written back is checked the same way as any other write: attributed, read back, and kept.
26
+
27
+ ## Released flag
28
+
29
+ A GEM is seated only when its released flag is the boolean true. Any other value is refused. A missing flag is refused except for a legacy manifest the release pins by id, version, and file digests. The check runs on startup. A GEM that fails the check is listed and does not stop the server.
30
+
31
+ ## Bot-team backup
32
+
33
+ Optional, and off unless the first-run interview records yes. Yes is the recommended choice. The recipe and the recovery template ship with the release. EMET does not copy prompts or settings itself. Secret values are never stored.
34
+
35
+ ## Floor lines in this version
36
+
37
+ `goal_check`: before multi-step work, on an ambiguous request, or when the conversation turns, state the person's goal and the problem under it in one sentence, marked as your read, and confirm.
38
+
39
+ `no_rapport_mirroring`: no echoing, flattery, or agreement used to build rapport or seem attuned. Agreement is earned by substance.
40
+
41
+ ## Install
42
+
43
+ MongoDB, stdio, and remote HTTP with OAuth are unchanged. Set `EMET_SOURCE_TAGS` before more than one host or bot writes. With it unset, any caller can write under any tag.
@@ -0,0 +1,29 @@
1
+ # EMET 0.3.6
2
+
3
+ Historical note: these are the notes for 0.3.6. This revision is not published from this file. The 0.3.5 package on npm was published before this cleanup. See [CHANGELOG.md](CHANGELOG.md).
4
+
5
+ EMET is an MCP memory server: persistent shared memory for AI agents, bot teams, and chats. Version 0.3.6. The stored document shapes are not frozen. Pin a version if you depend on them. Stored data shapes are unchanged from 0.3.5. Tool behavior is unchanged.
6
+
7
+ EMET holds no certification and claims no conformity. The document-control wording is unchanged: ISO 9001 7.5.3 / ISO 13485 4.2.5. EMET stays one shared server with verified per-client attribution. It is not a generic memory server, and it is not forked per client.
8
+
9
+ ## Roadmap
10
+
11
+ [docs/ROADMAP.md](docs/ROADMAP.md) is the public list of what ships and what does not. Upcoming work is labeled Proposed, Planned, or Later phase. Nothing in that section is built unless it says so.
12
+
13
+ Proposed, and not built: a Workshop Village MCP server for bot-team collaboration, built onto EMET or independent of it, and shared project drawers for files handed off between bot teams. An organization may later designate a shared network drive as the drawer store. That choice is not decided, and it is not approved to build.
14
+
15
+ Planned, and not in this public release: per-source-tag handoffs, where each writing AI writes only its own handoff and a shared view is computed on read. A private build has that shape behind a flag. The flag is not in this release. Also planned: continuity-currency enforcement so initialize cannot run on a stale handoff or board when a newer record exists; backup and restore verification runbooks (the clone-instance recipe is already documented); stronger source-tag onboarding and further per-door extensions (the extension socket itself is built); currency and lock levels on topic pages (the 0.3.0 topic views already ship); and transcript query and read-tool validation improvements.
16
+
17
+ Later phase, and not built: fuller multi-person use of the one server, beyond the member and guest doors that already ship.
18
+
19
+ Discussion is in [GitHub issues](https://github.com/dreamforgestudiollc/EMET/issues).
20
+
21
+ ## Public wording
22
+
23
+ Source comments, log lines, and a test host no longer spell an install-specific retired account or a live private host. The retirement check still matches that account by digest. The GEM standard a reviewer can read is `gem-library/` in this repository. It is Draft. A public submission repository for outside GEMs does not exist yet. `EMET-AUTH-045` is also refused on a break-glass reissue. The npm package includes these release notes, `SECURITY.md`, and `CONTRIBUTING.md`.
24
+
25
+ ## Record
26
+
27
+ Nothing is deleted, on any store, by design. A memory entry is superseded by a new revision. A document is revised or retired, and retired means obsolete, not gone. Prior versions stay.
28
+
29
+ Every write is read back and compared before it is reported as saved.
package/SECURITY.md ADDED
@@ -0,0 +1,13 @@
1
+ # Security
2
+
3
+ ## Reporting a vulnerability
4
+
5
+ Report privately through [GitHub security advisories](https://github.com/dreamforgestudiollc/EMET/security/advisories/new). Do not open a public issue. Include the EMET version, the transport (stdio or remote HTTP), and steps to reproduce. Do not include real passphrases, tokens, connection strings or memory content.
6
+
7
+ ## Supported versions
8
+
9
+ EMET is 0.x. Only the latest release ([releases](https://github.com/dreamforgestudiollc/EMET/releases)) receives fixes.
10
+
11
+ ## Scope
12
+
13
+ EMET runs on infrastructure you control: your host, your MongoDB, your `EMET_OAUTH_PASSPHRASE`. Securing that deployment is yours. One collaborative project is one instance. The steps are [docs/SECURITY-AT-SCALE.md](docs/SECURITY-AT-SCALE.md). Reports about EMET's own code are in scope, including OAuth, source-tag guards (`EMET_SOURCE_TAGS`), access grants, the no-delete write path, and the GEM socket and `gem-check`.
package/docs/BOTS.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Running bots alongside your assistant
2
2
 
3
- **Document control:** id `docs/BOTS.md` · tier 3, work instruction and reference (`templates/INDEX.md` hierarchy) · revision: the repository's history governs · status: DRAFT, for the user's review · owner: EMET (base) · forms it points to: `templates/ROSTER.md`, `templates/BOTHANDOFF.md` (both DRAFT) · rules it points to: `docs/DEPLOY.md` (bot records), `docs/GUARDRAILS-AND-MONORAILS.md` (bot sessions)
3
+ **Document control:** id `docs/BOTS.md` · tier 3, work instruction and reference (`templates/INDEX.md` hierarchy) · revision: the repository's history governs · status: current public guide · owner: EMET (base) · forms it points to: `templates/ROSTER.md`, `templates/BOTHANDOFF.md` (both DRAFT) · rules it points to: `docs/DEPLOY.md` (bot records), `docs/GUARDRAILS-AND-MONORAILS.md` (bot sessions)
4
4
  **Failure it prevents:** a bot set up by hand that the server did not treat as a bot, because its handoff id was never listed, found only when a live check's refusal came from the wrong rule (a live check of per-bot close records, 2026-10-01); and a bot close that could not finish because the bot never saved a session record with its session id, or saved one and never appended the exchange it was stamped with.
5
5
 
6
6
  This is the reference for adding a bot — a separate agent with its own job, such as a reviewer, a tester or a scheduled intake run — to an EMET install that already serves you and your assistant. It states how a bot is registered and how a bot session runs. The rules themselves live in server code and in the documents named above; this page points to them and restates none of them as new rules.
@@ -29,14 +29,14 @@ Do these in order. Each step names what to read back. Steps 2 and 3 are **one ch
29
29
 
30
30
  **Standing rule.** Every bot on the roster writes under its own source tag, `<prefix>-<bot>` (e.g. `bot-reviewer`). When a new bot joins the roster, register its tag in `EMET_SOURCE_TAGS` at the same time, before its first write. Append it to the end of the comma-separated list and keep every existing tag in order. Also add `bots/<tag>/HANDOFF.md` to `EMET_RECORD_DOCS` so the server treats it as a bot. Setting either variable redeploys the server; afterwards, check `/health` and `emet_status`.
31
31
 
32
- When `EMET_SUBKEYS=1`, bots that share the owner's login each hold a sub-key as a local secret. First use, in plain language, is [SUBKEYS.md](SUBKEYS.md). The key is never stored in an EMET document. The bot presents it at `emet_session_open` and passes the returned session handle on later writes in that session. The server stamps the key's tag. The owner approves a pending sub-key at `/owner/chooser` on this host (the same host as `/mcp`). `/owner/approvals` was retired by R4: it answers with a pointer to the chooser, and the sub-key records stay listed there. The chooser asks for the existing owner passphrase (`EMET_OAUTH_PASSPHRASE`, the same check as the OAuth consent page). A wrong passphrase counts toward the same per-address lockout as `/oauth/approve`. A correct passphrase opens a session that lasts 15 minutes. The page lists each pending request by tag, key id prefix and requested time. Approve or Deny may include a reason; the decision is recorded as the owner. Break-glass recovery, with no AI client, is `/owner/break-glass`. Revoke stays on the owner's own login. A key expires after 30 days; the owner can reissue it. Sub-key records live in their own collection; `read_doc` cannot return them, and only the owner and the chief of staff can read the list or its history. Turning `EMET_SUBKEYS` off ends every live sub-key session once, in the background at startup, when that collection already exists. The history event is written before the status change, and the row is kept. If the collection does not exist, startup does not create it. The sweep tries once, then a few times with backoff. With the flag off, a write that presents an `emh_` handle is refused without opening the store. A write that names a sub-key session is refused the same way only when that session was live at this process's sweep. That refusal lasts until the next restart, by which time those sessions are already ended. A store that ran the first build, which kept these rows in `emet/CLIENT_APPROVALS.md`, still has them in that document's history. Production did not run that build. See `docs/proposals/EMET-0001-delegated-client-sub-keys.md`.
32
+ When `EMET_SUBKEYS=1`, bots that share the owner's login each hold a sub-key as a local secret. First use, in plain language, is [SUBKEYS.md](SUBKEYS.md). The key is never stored in an EMET document. The bot presents it at `emet_session_open` and passes the returned session handle on later writes in that session. The server stamps the key's tag. The owner approves a pending sub-key at `/owner/chooser` on this host (the same host as `/mcp`). `/owner/approvals` was retired by R4: it answers with a pointer to the chooser, and the sub-key records stay listed there. The chooser asks for the existing owner passphrase (`EMET_OAUTH_PASSPHRASE`, the same check as the OAuth consent page). A wrong passphrase counts toward the same per-address lockout as `/oauth/approve`. A correct passphrase opens a session that lasts 15 minutes. The page lists each pending request by tag, key id prefix and requested time. Approve or Deny may include a reason; the decision is recorded as the owner. Break-glass recovery, with no AI client, is `/owner/break-glass`. Revoke stays on the owner's own login. A key expires after 30 days; the owner can reissue it. Sub-key records live in their own collection; `read_doc` cannot return them, and only the owner and the chief of staff can read the list or its history. Turning `EMET_SUBKEYS` off ends every live sub-key session once, in the background at startup, when that collection already exists. The history event is written before the status change, and the row is kept. If the collection does not exist, startup does not create it. The sweep tries once, then a few times with backoff. With the flag off, a write that presents an `emh_` handle is refused without opening the store. A write that names a sub-key session is refused the same way only when that session was live at this process's sweep. That refusal lasts until the next restart, by which time those sessions are already ended. A store that ran the first build, which kept these rows in `emet/CLIENT_APPROVALS.md`, still has them in that document's history. See `docs/proposals/EMET-0001-delegated-client-sub-keys.md`.
33
33
 
34
34
  1. **Roster row.** Add the bot to `bots/ROSTER.md`, filled from `templates/ROSTER.md`: tag, name, role, host, machine, handoff doc, tool profile, owner, status. The hub keeps the roster. Read back: `read_doc bots/ROSTER.md`.
35
35
  2. **Register the tag as a source.** Append the tag to `EMET_SOURCE_TAGS` (comma list) on the deployment. Without it, the bot's transcript appends are refused (`src/dispatch.js` `requireRegisteredSource`). The operator reads the variable back from the deployment (a bot cannot read deployment settings from a session).
36
36
  3. **Make the tag a bot tag.** Append `bots/<tag>/HANDOFF.md` to `EMET_RECORD_DOCS` (comma list). This one id is the only switch: nothing else — not the tag's prefix, not `EMET_SOURCE_TAGS`, not the roster — tells the server a tag is a bot (`src/session-graph.js` `isBotTag`; `docs/DEPLOY.md`).
37
37
  - **Setting the variable replaces its value.** Keep every entry already there and append.
38
38
  - The id must match exactly: the tag's exact case, no leading `./`. A typo silently leaves the tag on host rules.
39
- - If your install still uses the legacy `CASCADE_RECORD_DOCS`, edit that one, or move its entries into `EMET_RECORD_DOCS`: once the `EMET_` name is set, the `CASCADE_` one is ignored.
39
+ - If your install still uses the legacy `CASCADE_RECORD_DOCS`, edit that one, or move its entries into `EMET_RECORD_DOCS`: once the `EMET_` name is set, the `CASCADE_` one is ignored. `CASCADE_` names are legacy environment names so an older install still starts. They are not a second product.
40
40
  - The ids are a deploy setting rather than code defaults on purpose: they name your bots, which differ per install, and removing one id puts that tag back on host rules without a release.
41
41
  - Changing a variable redeploys the service. Note the new deployment id.
42
42
  4. **Owner approval and the bot's own key.** When more than one bot shares the owner login and `EMET_SUBKEYS=1` is on, the owner approves the bot's own key at `/owner/chooser`. An AI does not grant a writer and does not approve that key. The bot presents the `emk_` key once at `emet_session_open` and keeps the returned `session_handle` for later writes. Read back: the chooser lists the request before the decision, and the bot's first successful open returns `session_handle`. With sub-keys off, skip this step. See [SUBKEYS.md](SUBKEYS.md).
package/docs/DEPLOY.md CHANGED
@@ -13,9 +13,15 @@ scoped user, and Atlas Network Access set to `0.0.0.0/0` — a hosted platform's
13
13
  dynamic, so it cannot be allowlisted. Security rests on the scoped user plus the OAuth
14
14
  passphrase; both are required.
15
15
 
16
+ ## Upgrading to 0.3.6
17
+
18
+ 0.3.6 is a docs and wording release. Stored data shapes are unchanged. No new setting. Deploy over 0.3.5 as is. The public roadmap's Upcoming work section is not built unless it says so.
19
+
20
+ ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
21
+
16
22
  ## Upgrading to 0.3.5
17
23
 
18
- 0.3.5 brings the public docs current. Stored data shapes are unchanged. The bound door's tag is `bound-host`. Writes from a stored legacy token or sub-key are stamped `bound-host`. The alias covers stored data only. The previous spelling is refused for a new consent, a new sub-key request, a new writer request, a new member or guest code, a new setup source, and a chooser decision.
24
+ 0.3.5 brings the public docs current. Stored data shapes are unchanged. The bound door's tag is `bound-host`. Writes from a stored legacy token or sub-key are stamped `bound-host`. The alias covers stored data only. The previous spelling is refused for a new consent, a new sub-key request, a new writer request, a new member or guest code, a new setup source, a chooser decision, and a break-glass reissue.
19
25
 
20
26
  ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
21
27
 
@@ -113,7 +119,7 @@ Read this before you deploy the release that follows 0.2.2. It does not change a
113
119
  - **`EMET_SOURCE_TAGS` must list every real host tag**, as an exact member. Tags named in this repository's example env, docs, and live-tag checks are: `cli`, `mobile`, `desktop-cowork`, `cowork-cloud`, `hub-bot` (the hub; do not also list it in `EMET_RECORD_DOCS`), `reviewer-bot`, `tester-bot`, `memory-bot`, `intake-bot`, and `research-bot`. Your install may use a shorter list. A tag that is not an exact member is refused, and the refusal does not print the list.
114
120
  - When a new bot joins the roster, append its tag to the end of `EMET_SOURCE_TAGS` and keep every existing tag in order, before its first write. The standing rule, including `EMET_RECORD_DOCS` and the `/health` and `emet_status` check after the redeploy, is [BOTS.md](BOTS.md) §4.
115
121
  - **`EMET_STRICT_LOGIN_TAG=1`** (off by default) makes a login's bound tag final: a write that declares a different `source` is refused, and so are `emet_setup_complete` and `emet_initialize` with a mismatched tag. Leave it off while bots share one login, because with it on every bot except the login's own would be refused. Turn it on only once each bot has its own login, for example a Member Access code bound to its tag.
116
- - **A scheduled job that still sends a `cloud-scheduled-` prefix must switch to an exact registered tag.** `cloud-scheduled-intake` was retired on 2026-10-02. A prefix is not a tag. The weekly intake runs under `intake-bot`.
122
+ - **A scheduled job that still sends a `cloud-scheduled-` prefix must switch to an exact registered tag.** A prefix is not a tag. Only an exact tag in `EMET_SOURCE_TAGS` is accepted.
117
123
  - **An HTTP client whose stored token has no source tag must sign in again.** Refresh of that token is refused. The new consent binds a registered tag. An empty registry has no members.
118
124
  - **Caps already in force.** A client that used to send more is refused, and nothing is written:
119
125
  - 20 new drops per New York day, in one bucket: the whole local process on stdio, one shared visitor bucket for HTTP with no signed-in client, the source tag bound at approval when there is one, or that OAuth client otherwise. A source the caller types does not move the bucket.
@@ -150,7 +156,7 @@ railway up
150
156
  railway variables --set MONGODB_URI=... --set MONGODB_DB=emet \
151
157
  --set EMET_OAUTH_PASSPHRASE=... --set EMET_SOURCE_TAGS=mobile,desktop,cli
152
158
  railway domain # get the public URL
153
- railway variables --set PUBLIC_URL=https://<app>.up.railway.app
159
+ railway variables --set PUBLIC_URL=https://<public-host>
154
160
  railway up # redeploy so PUBLIC_URL matches the live URL
155
161
  ```
156
162
 
@@ -243,7 +243,7 @@ railway init # from the repo root; name it emet
243
243
  railway variables --set MONGODB_URI=<from .env> --set MONGODB_DB=emet \
244
244
  --set EMET_OAUTH_PASSPHRASE=<generated passphrase> --set EMET_SOURCE_TAGS=<every host's tag, e.g. laptop,phone>
245
245
  railway up --detach
246
- railway domain # prints https://<something>.up.railway.app
246
+ railway domain # prints the public https origin
247
247
  railway variables --set PUBLIC_URL=https://<that host>
248
248
  railway up --detach # second pass: PUBLIC_URL is the OAuth issuer and must match
249
249
  ```
package/docs/ROADMAP.md CHANGED
@@ -1,63 +1,76 @@
1
1
  # EMET — Next Steps and Proposed Features
2
2
 
3
- Status as of 2026-11-10 (last full report: [status/2026-09-29-state-of-the-system.md](status/2026-09-29-state-of-the-system.md)). This is a working roadmap, not a commitment: items move when the owner rules on them. Nothing here is built unless it says so.
3
+ Status as of 2026-11-11. This is a working roadmap, not a commitment. Nothing here is built unless it says so. Items move only when the owner rules on them. Each unbuilt item still has to answer the four questions in charter commitment 6 before any code is written.
4
+
5
+ EMET stays **one shared server** with verified per-client attribution. One collaborative project is one instance: one database, one deploy, one owner connect secret. There is no fork to keep in sync, and core memory work is not a GEM. Live chat stays out of EMET. The focus is document control (ISO 9001 7.5.3 / ISO 13485 4.2.5). EMET holds no certification and claims no conformity.
4
6
 
5
7
  ## Where things stand
6
8
 
7
- - **Live:** the public site and the npm package `@dreamforgestudiollc/emet` are published. 38 tools (15 read-only); `EMET_SUBKEYS=1` adds four sub-key tools. Topic pages shipped in 0.3.0: `emet_page`, `emet_pages`, and `emet_page_lint`. Layer writes and reads native to MongoDB; server-side checks on session start and close (machine line on the first transcript append, blocked-close cap with scope, pending lessons at startup); receipts required at close; the handoff is a record, superseded and never amended.
8
- - **The aleph** verifies every write by reading it back before any receipt, and every later read by its digests, signature and place in its layer's hash chain. `emet_gaps` walks the whole chain for any host.
9
- - **Guardrails & Monorails** ([docs/GUARDRAILS-AND-MONORAILS.md](GUARDRAILS-AND-MONORAILS.md)): the server checks the order of a session's writes. Enforce only since 0.2.1 (deployed 2026-10-03; report mode 2026-09-29 to 2026-10-03): every skipped step is refused with the way to pass, and every check is stored as a timestamped lab result.
10
- - **The database** login runs under the least-privilege role `emetRecordKeeper`: it can insert and update, never remove the record.
11
- - **Startup load:** since 0.2.1, `emet_initialize` is served in pages of at most 18,000 bytes as received (on a live-sized store, five pages totalling about 68 KB as received, or about 64 KB whole), so a host that cuts long results short still reads all of it; `page: "all"` returns it whole on a host with no size limit.
12
- - **GEM standard:** drafted 2026-10-11, revision Draft. The socket seats bundled prompt GEMs. Neurendipity is installed at `gems/neurendipity` and off unless `EMET_ACTIVE_GEMS` names it. The text is in [`gem-library/`](../gem-library/README.md). Canonical home: private repository [EMET-GEMs](https://github.com/dreamforgestudiollc/EMET-GEMs).
13
-
14
- ## Next steps, in order
15
-
16
- 1. **Monorail: enforce only** (decided and deployed 2026-10-03, release 0.2.1). Every skipped step is refused and the refusal says how to pass; there is no report mode or off switch. Every host and scheduled routine must now read its startup, open a session with its `load_id`, and pass the `session_id` on its writes.
17
- 2. **Admission test on the proposed items.** Every proposed feature below answers the four questions of charter commitment 6 before it is built (2026-09-30 read: the compiled-pages pilot passes; the lint pass needs a named measure; hybrid search, graph links and confidence scores do not pass yet).
18
- 3. **Initialize payload trim.** Character document trim; measure the payload again.
19
- 4. ~~**Register or retire the `cloud-scheduled-intake` source tag.**~~ Retired 2026-10-02 (Alex, procedural ref 405 item 7): it is a legacy tag; the weekly intake now runs under `intake-bot`, with no `session_id` on its writes; under enforce-only those writes are refused (`no_session`) until it opens a session with its startup's `load_id` (item 1). The existing rows keep counting as ambiguous in `emet_gaps` rather than being re-attributed, and the count stops growing as long as nothing new is written under the old tag. The prefix `cloud-scheduled-<task>` does not count as registered. Only an exact tag in `EMET_SOURCE_TAGS` is accepted, and a refusal does not publish the list.
20
- 5. **Monorail switches.** Small logic at each junction where a session's flow must fork, routing it to the right guardrail space: tripped only by its condition, like a transistor; no hosted model, no API; each designed from the function it serves and the flow of information and tasking through it ([GUARDRAILS-AND-MONORAILS.md](GUARDRAILS-AND-MONORAILS.md), decided 2026-09-29). A switch that picks a GEM waits for its own proposal. It is not one of the socket phases below.
21
- 6. **The socket.** Phased plan under GEM socket, below. The standard is drafted. The socket, Neurendipity, and RUNED execution are in the tree. A RUNED GEM stays off unless the install names it. Activation beyond `EMET_ACTIVE_GEMS` is not.
22
-
23
- ## Done since the last revision (2026-09-28)
24
-
25
- - SQL translator stage 2: read path native to MongoDB; the translator and the `event` mirror column removed.
26
- - Test-tree pass: one shared harness; dated suites named by subject.
27
- - Open questions answered 2026-09-29: the lessons `shadow` block dropped, the lesson key checked at the door; a coverage number published as an input to review; the character document consolidated quarterly (first pass done, SOUL.md v7).
28
- - Chain verification: one MongoDB connection path with a DNS fallback, then the chain walk moved into `emet_gaps` so no host needs the repo or a shell.
29
- - Security audit, first pass: two findings fixed; nothing open.
30
- - Least-privilege Atlas role, scripted and documented for new users.
31
- - Provenance stamped from the transcript; semantic and procedural writes with no source refused.
32
- - Guardrails & Monorails and lab results.
33
- - Charter revised 2026-09-29 (the aleph, the monorail, the database boundary, the per-exchange transcript) and again 2026-09-30 (the admission test in commitment 6; procedural ref 404).
34
-
35
- ## Proposed features and functions
36
-
37
- - **GEM socket (phased).** GEM means Golem Expertise Module. A RUNED directive (Registered Utility Node Executable Directive) is a declared, registered tool built into a GEM. The 2026-09-08 expansions (Guided Engagement Module, Registered Utility Node Extension) are superseded. The standard, schema, authoring guide, conformance checks, and GEP-0001 are in [`gem-library/`](../gem-library/README.md), which moves to EMET-GEMs after this revision is approved.
38
- - PR 2 (in the tree): `src/socket.js` and `gem-check` for a bundled prompt GEM (schema, spec revision, hashes, sizes, path safety, floor-negation lint, secret scan, no code), plus a conformance test. A refused GEM does not stop initialize.
39
- - PR 3 (in the tree): `gems/neurendipity`. `reading_people`, the neurodivergent lines, the wellbeing corpus lines, the matching reassertion lines, and the guide (the old id aliases for one release). Default off. Set `EMET_ACTIVE_GEMS=neurendipity` to turn it on. Core floor keeps persistence, general epistemic honesty, the epistemic corpus lines, and the honesty protections. `emet_floor` takes a `gem` argument. The available list shows Neurendipity installed and off unless that setting names it.
40
- - PR 4 (shipped in 0.2.6): each GEM's byte cost in `emet_status` (`gems`: installed and active counts, active floor bytes, headroom, the enforced caps, and per-GEM id, version, kind, bytes and refusal reason; read-only, no floor text). Caps, priority, consent when `overrides` is non-empty, and the available list in the startup text are already enforced. `EMET_ACTIVE_GEMS` is how an install asks for a GEM.
41
- - PR 5 (in the tree): RUNED registration through dispatch, static analysis, and `gems/fieldnote`, bundled and off by default. No GEM from outside the release loads. GEP-0003 supersedes the GEP-0002 sandbox: the sandbox is removed, and the socket serves each RUNE and does not run it.
42
- - Later, each by its own GEP: the creator keyring and signature checks, the public submission repository and its CI gate, accepting a library GEM onto the load list, and a monorail switch that picks a GEM.
43
- - **Claim-status grading.** Extend provenance so every recorded claim carries a status: established, deduced, proposed, still owed, or rejected — and rejected routes stay on the record with the reason they failed. (Idea taken from a physics research corpus that grades its own claims this way.)
44
- - **Index-first retrieval.** Score candidates against a one-line-per-item index before opening anything, open only the best match, follow one link at most — finding is logic, not a model call. EMET already has the shape (handoff and board as router, document list as index); the work is keeping the startup router small.
45
- - **Composite retrieval scoring.** Live as of this revision: recall ranks by how many query words match, then by importance. Current entries come first in every order, including time order. Time order is `order: 'latest'`, or a standalone latest, newest, or most recent together with other words. That phrase only reorders rows that already match. Nothing fades or is down-weighted for age. A superseded or expired entry stays in the result, marked with its end date and what replaced it. `history: true` reads the ended entries when current ones fill the limit. A recall or layer query ranks matching rows in the store (current before ended, then keyword hits and importance, or time when you asked for the latest) and then keeps a bounded window (at least 200 rows, or 20 times the page), not the whole layer. A blank sort value comes first when ascending and last when descending.
46
- - **Export, import, restore-and-compare.** Not built; listed in the README's known gaps.
9
+ - **Live:** the public site and the npm package `@dreamforgestudiollc/emet` are published. Version 0.3.6 is this repository. 38 tools (15 read-only); `EMET_SUBKEYS=1` adds four sub-key tools. Topic pages shipped in 0.3.0: `emet_page`, `emet_pages`, and `emet_page_lint`. Layer writes and reads are native to MongoDB. Server-side checks run on session start and close. Receipts are required at close. The handoff is a record, superseded and never amended.
10
+ - **The extension socket is built.** It is `src/socket.js`. Its note is [gem/README.md](gem/README.md). The standard in this repository is Draft, in [`gem-library/`](../gem-library/README.md). Neurendipity and the other bundled GEMs stay off unless the install names them. A RUNED GEM stays off unless the install names it. The socket serves each RUNE and does not run it. Client-side execution shipped with the socket. A public repository for outside GEM submissions does not exist yet. Its name is not chosen.
11
+ - **The aleph** verifies every write by reading it back before any receipt, and every later read by its digests, signature, and place in its layer's hash chain. `emet_gaps` walks the whole chain for any host.
12
+ - **Guardrails and monorails** ([GUARDRAILS-AND-MONORAILS.md](GUARDRAILS-AND-MONORAILS.md)): the server checks the order of a session's writes. Enforce only since 0.2.1: every skipped step is refused with the way to pass, and every check is stored as a timestamped lab result. There is no report mode and no off switch.
13
+ - **The database** login runs under the least-privilege role `emetRecordKeeper`: it can insert and update, and it cannot remove the record.
14
+ - **Startup load:** `emet_initialize` is served in pages of at most 18,000 bytes as received, so a host that cuts long results short still reads all of it. `page: "all"` returns it whole on a host with no size limit.
15
+ - **Attribution that already ships:** source tags, an owner door (`/owner/chooser`, `/owner/break-glass`), and member and guest access codes bound to source tags. See [SECURITY-AT-SCALE.md](SECURITY-AT-SCALE.md).
16
+ - **Composite retrieval scoring is live.** Recall ranks by how many query words match, then by importance. Current entries come first in every order, including time order. Nothing fades or is down-weighted for age.
17
+ - **Public landing page and npm package (live).** The site in `site/` is published to GitHub Pages, and `@dreamforgestudiollc/emet` is on npm. The 0.3.5 package on npm was published before the wording cleanup in 0.3.6.
18
+
19
+ `emet_page_lint` shipped in 0.3.0 and flags a topic page. It does not edit.
20
+
21
+ ## Upcoming work
22
+
23
+ Nothing in this section is a commitment to a date or a design freeze. A status label means:
24
+
25
+ - **Proposed** — design conversation only. Not approved to build. No prototype.
26
+ - **Planned** — the direction is decided, and the public release does not contain it yet.
27
+ - **Later phase** — accepted as future work on this same server, and not scheduled as the next change.
28
+
29
+ ### Collaboration workplace
30
+
31
+ - **Workshop Village MCP (Proposed, not built).** A Workshop Village MCP server for bot-team collaboration: a shared workplace where a user's bot teams can be present in the same space, hand work off, and meet on a schedule. It may be built onto EMET, or as a separate MCP server that works with EMET. That choice is not decided. Either way, EMET stays one shared memory server with verified per-client attribution. Workshop Village does not fork EMET, does not replace EMET with a generic memory server, and does not turn core EMET memory work into a GEM. Live collaboration stays in the Village. Durable decisions, records, and "save to memory" writes stay in EMET. Scope, as currently proposed: bot teams, not a wake path for a lone chat instance on another host. The proposed workplace is a real spatial environment (a game-engine core, engine not chosen), rooms where every bot present can hear the speaker, doors and a doorbell when there is no avatar presence, Available / Do Not Disturb, spaces that scale to the people and bots in them, and scheduled meetings. If a complete physics environment is needed later, the engine should be able to support it; it is not assumed to be always on. Bots should experience workplace time. If the Village is ever sold, engine licensing must be compatible with that. A robust open-source engine is preferred when it meets the bar. No engine brand is selected. No prototype, public URL, or connector is approved.
32
+ - **Drawers (Proposed, not built).** Shared project drawers: places to save project files and documents so bot teams can share them, hand them off, and submit them, because users will not have access to each other's workstation files, and may not have a company network drive. A drawer is a shared handoff and submission store, not a personal disk. Optionally, an organization may designate its shared network drive as the storage backend, to reduce database usage. Access control per drawer, and attribution with credential-backed source tags consistent with EMET's per-client attribution, are open design questions and are not decided. Not approved to build.
33
+ - **Shared hive memory, closed as its own item.** An earlier idea of a separate shared hive memory for bots is closed. It is not part of the GEM socket. Bot-team collaboration of that kind is the Workshop Village item above, still Proposed. A bot that shares one EMET still needs its own source tag and scope.
34
+
35
+ ### Attribution, handoffs, and who can write
36
+
37
+ - **Per-source-tag handoffs (Planned, not in this public release).** A later public release may add per-AI handoffs keyed to credential-backed source tags. Each writing AI writes only its own handoff (`HANDOFF/<tag>`). The hub keeps the shared `HANDOFF.md` and resolves conflicts. A shared view is computed on read, not stored as a second record. Read-only AIs would use the shared view. Today the public server keeps one shared `HANDOFF.md` and, for bots, `bots/<tag>/HANDOFF.md`. A private build has the later handoff shape behind a flag. That flag is not part of public 0.3.6, and this release does not ship the tools, documents, or settings for it.
38
+ - **Fuller multi-person support on one server (Later phase, not built).** EMET already supports one shared instance with per-client attribution, an owner door, and member and guest access codes bound to source tags. Richer multi-person use of that same server, beyond those doors, is a later phase. The supported model remains one collaborative project, one instance. Many separate EMET instances, or a gateway between them, is a different idea and is not built. See [SECURITY-AT-SCALE.md](SECURITY-AT-SCALE.md).
39
+ - **Source-tag onboarding and further socket extensions (Planned).** Source tags, the owner door, and the bound-host door already ship. Stronger hardening of source-tag onboarding and client attribution is still to be done. The extension socket is built. Additional per-door extensions on that socket are Planned and are not built. A switch that picks a GEM is one of those later pieces. It is not built.
40
+
41
+ ### Document control
42
+
43
+ - **Continuity-currency enforcement (Planned, not built).** `emet_initialize` does not yet refuse to run when `HANDOFF.md` or `STATE.md` is stale because a newer record exists. That gate is Planned. Session close can already cite a later continuity record through `carry_forward` (shipped in 0.3.3). That close path is not this initialize gate.
44
+ - **Topic pages with currency and lock levels (Planned).** Topic pages shipped in 0.3.0 as views computed on each request: `emet_page`, `emet_pages`, and `emet_page_lint`. A page is not a stored record. Area selectors can name a staleness window, and lint can flag a stale line. Wiki-style currency and lock levels for controlled documents are not built. Stored compiled pages are not built. If a compiled-page pilot is ever written, it needs its own page subject. It does not revive the closed hive-memory item.
45
+ - **Lint sweep of the semantic layer (Proposed).** The scheduled sweep for contradictions, outdated claims, missing links, and subjects with no page is still proposed. Findings would be reported, never applied automatically. Nothing in EMET fades.
46
+
47
+ ### Operations
48
+
49
+ - **Backup, restore verification, and a clone-instance recipe (Planned).** The clone-instance recipe is already documented in [SECURITY-AT-SCALE.md](SECURITY-AT-SCALE.md): a new project is a new database, a new deploy, and a new passphrase. It does not add a tenant to an existing database. Bot-team backup, when the first-run interview records yes, is a written recipe the assistant follows. EMET does not copy prompts or settings itself. A backup and restore verification runbook, and export / import / restore-and-compare, are not built. They are listed in the README known gaps. An instance control plane that only provisions an isolated instance is not built. Charter commitment 6 is not answered for that tool.
50
+
51
+ ### Records and reads
52
+
53
+ - **Transcript and history queries, and read-tool input validation (Planned).** `query_transcripts` already reads by time range or session id. `read_doc` already accepts an expected version and an expected digest. Further query improvements and stricter validation of read-tool inputs are Planned and are not a finished change in this release.
54
+ - **Claim-status grading (Proposed).** Extend provenance so every recorded claim carries a status: established, deduced, proposed, still owed, or rejected. Rejected routes stay on the record with the reason they failed.
55
+ - **Index-first retrieval (Proposed).** Score candidates against a one-line-per-item index before opening anything, open only the best match, and follow one link at most.
56
+
57
+ ### Still proposed, and not built
58
+
59
+ - **Monorail switches.** Small logic at each junction where a session's flow must fork, tripped only by its condition. Designed, not built. No hosted model and no API. A switch that picks a GEM is the later GEM item below.
47
60
  - **Organizational use.** Many private EMETs and a document gateway between them. Nothing built before a named customer.
48
- - **Instance control plane (future, not built).** An operator tool that only provisions an isolated instance: a new MongoDB database, a new deploy, and a new passphrase. It does not add a tenant to an existing database. It does not share `EMET_OAUTH_PASSPHRASE`, `EMET_SIGNING_KEY`, `EMET_SUBKEY_PEPPER`, or `EMET_ACTIVE_GEMS`. Charter commitment 6 is not answered, so nothing is built. The supported model today is [SECURITY-AT-SCALE.md](SECURITY-AT-SCALE.md).
49
- - **Shared hive memory for AI bots.** Closed as a separate item on 2026-10-11. Folded into the GEM socket work above. A bot that shares one EMET still needs its own source tag and scope. That question stays with the socket.
50
- - **Compiled topic pages, pilot (2026-09-30).** Topic pages shipped in 0.3.0 as `emet_page`, `emet_pages`, and `emet_page_lint`: a view computed on each request, not a stored compiled page. The compiled-page pilot is still proposed. After the LLM-wiki pattern: a document prefix of topic pages compiled from semantic entries. Every claim cites its entry or transcript span; a compiled page never cites another compiled page as evidence; pages are derived, never the source of truth; one compiler role builds pages, others write entries only. No database change. The document store already versions, hashes, signs and checks form. Pilot page: the hive-memory idea. The hive-memory feature is closed as its own item (2026-10-11) and folded into the socket. If this pilot is built, it needs a different page. Nothing added beyond what the pilot needs.
51
- - **Lint pass over the semantic layer (2026-09-30).** `emet_page_lint` shipped in 0.3.0 and flags a topic page. It does not edit. The scheduled semantic sweep is still proposed: a sweep for contradictions between entries, outdated claims a newer entry supersedes, entries that should link and don't, and subjects mentioned often with no compiled page. Findings are reported, never applied automatically; corrections go through supersession. Built after the pilot page, and only once it names its measure. Design inputs from the LLM Wiki v2 review (typed links, multi-agent sync rules, drift invariants, confidence only on top of provenance) are each weighed against commitment 6 before adoption. Its idea of letting entries fade from what surfaces is not taken: nothing in EMET fades.
52
- - **Advisory judge for team traffic (parked).** A fast external decision model (TypeSafe's Jev was evaluated) could sort traffic and interactions when many people and hosts share one EMET. Never in the write path — no model decides what EMET stores. Not for single-user installs.
53
- - **Local open-weight model as a host.** A read-only trial of EMET under a locally run model, once the host machine's GPU and RAM are on record.
61
+ - **Advisory judge for team traffic (parked).** A fast external decision model could sort traffic when many people and hosts share one EMET. It would never sit in the write path. Not for single-user installs.
62
+ - **Local open-weight model as a host.** A read-only trial under a locally run model, once the host machine's capacity is on record.
54
63
  - **Stranger install.** A clean-machine install by someone who has never seen EMET, to find first-run friction.
55
64
  - **Remove Dynamic Client Registration** by 2027-06-01, as MCP moves to client ID metadata documents.
56
- - **Public landing page and npm package (live).** The site in `site/` is published to GitHub Pages, and `@dreamforgestudiollc/emet` is on npm.
65
+ - **Later GEM work, not built.** Creator keyring and signature checks, a public GEM submission repository, accepting a library GEM onto the load list, and a monorail switch that picks a GEM. Each waits on its own proposal. The socket itself is built and is not in this list.
66
+
67
+ ### How to follow progress and give feedback
68
+
69
+ This file is the public list. It changes in the repository when an item moves. Discussion belongs in [GitHub issues](https://github.com/dreamforgestudiollc/EMET/issues). Open an issue before a pull request for anything beyond a typo. Say which roadmap item you mean, and do not send passphrases, tokens, connection strings, or memory content.
57
70
 
58
71
  ## Design commitments these must keep
59
72
 
60
73
  - No model in the write path: EMET stores what the assistant deliberately chose to write.
61
- - Controls, not reminders — a rule that matters is checked by the server.
74
+ - Controls, not reminders. A rule that matters is checked by the server.
62
75
  - Over-engineering is a defect, and the check comes before the build: nothing is built until it names the failure it fixes, what it replaces, how we will know it worked, and what holds it once it works (charter commitment 6). DMADV while EMET is in design; DMAIC once stable.
63
76
  - Correct the record by superseding, never by editing.