@dreamforgestudiollc/emet 0.2.6 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (56) hide show
  1. package/.env.example +10 -0
  2. package/CHANGELOG.md +18 -1
  3. package/README.md +31 -7
  4. package/areas/emet.md +18 -0
  5. package/areas/garden.md +18 -0
  6. package/areas/health.md +18 -0
  7. package/areas/home.md +18 -0
  8. package/areas/learning.md +18 -0
  9. package/areas/state.md +18 -0
  10. package/docs/DEPLOY.md +32 -1
  11. package/docs/ERROR-CODES-SPEC.md +43 -0
  12. package/docs/ERROR-CODES.md +332 -0
  13. package/docs/GUIDED-SETUP.md +16 -0
  14. package/docs/PERMISSIONS.md +8 -5
  15. package/docs/ROADMAP.md +10 -10
  16. package/docs/SETUP.md +115 -12
  17. package/package.json +3 -2
  18. package/server.json +7 -3
  19. package/src/aleph.js +16 -10
  20. package/src/annotations.js +8 -3
  21. package/src/atlas-role.js +8 -3
  22. package/src/attribution.js +12 -12
  23. package/src/conformance.js +6 -4
  24. package/src/database.js +28 -12
  25. package/src/dispatch.js +33 -16
  26. package/src/error-codes.js +394 -0
  27. package/src/error-log.js +273 -0
  28. package/src/error-report.js +245 -0
  29. package/src/floor.js +6 -4
  30. package/src/gaps.js +2 -2
  31. package/src/gem-check.js +27 -26
  32. package/src/http-remote.js +2 -1
  33. package/src/index.js +1 -0
  34. package/src/invites.js +6 -5
  35. package/src/layers.js +8 -7
  36. package/src/mongo-connect.js +5 -0
  37. package/src/oauth-provider.js +28 -27
  38. package/src/pages.js +806 -0
  39. package/src/persons.js +2 -1
  40. package/src/provenance.js +10 -10
  41. package/src/rune-dispatch.js +10 -10
  42. package/src/session-graph.js +16 -15
  43. package/src/session.js +1 -1
  44. package/src/setup.js +21 -17
  45. package/src/startup-pages.js +3 -2
  46. package/src/startup-payload.js +3 -2
  47. package/src/subkey-store.js +3 -2
  48. package/src/tools.js +254 -177
  49. package/src/validation.js +61 -52
  50. package/src/version.js +1 -1
  51. package/templates/AREA.md +35 -0
  52. package/templates/INDEX.md +7 -6
  53. package/templates/PROCEDURE.md +1 -1
  54. package/templates/SEED.md +2 -2
  55. package/templates/STAGING.md +1 -1
  56. package/templates/THREAD.md +1 -1
@@ -0,0 +1,332 @@
1
+ # EMET error codes
2
+
3
+ Every error EMET returns carries a stable code in `error.emet_code`. The existing `error.code` field is unchanged. The same meaning keeps the same code. A code is not reused and its meaning is not changed. A retired number stays reserved in the list below and is not issued again.
4
+
5
+ Internal codes are raised inside a check that catches them before a caller sees them. If one ever reaches a caller it is still that code, not a new one.
6
+
7
+ | Code | Summary | Status |
8
+ |---|---|---|
9
+ | EMET-AUTH-001 | Could not allocate a person id | active |
10
+ | EMET-AUTH-002 | CIMD document is not a JSON object | active, internal |
11
+ | EMET-AUTH-003 | CIMD client_id does not match its URL | active, internal |
12
+ | EMET-AUTH-004 | CIMD redirect_uris are missing | active, internal |
13
+ | EMET-AUTH-005 | CIMD client is not public | active, internal |
14
+ | EMET-AUTH-006 | CIMD host is not a public address | active, internal |
15
+ | EMET-AUTH-007 | CIMD host did not resolve | active, internal |
16
+ | EMET-AUTH-008 | CIMD host resolves to a blocked address | active, internal |
17
+ | EMET-AUTH-009 | CIMD fetch rate limit | active, internal |
18
+ | EMET-AUTH-010 | CIMD fetch returned an HTTP error | active, internal |
19
+ | EMET-AUTH-011 | CIMD document exceeds the size cap | active, internal |
20
+ | EMET-AUTH-012 | CIMD document is not valid JSON | active, internal |
21
+ | EMET-AUTH-013 | Authorization code is not recognised | active |
22
+ | EMET-AUTH-014 | Authorization code has expired | active |
23
+ | EMET-AUTH-015 | Redirect URI does not match the code | active |
24
+ | EMET-AUTH-016 | Authorization code has already been used | active |
25
+ | EMET-AUTH-017 | Refresh token is not recognised | active |
26
+ | EMET-AUTH-018 | Refresh token has expired | active |
27
+ | EMET-AUTH-019 | Login has no source tag bound | active |
28
+ | EMET-AUTH-020 | Refresh token has already been replaced | active |
29
+ | EMET-AUTH-021 | Member access login can no longer be refreshed | active |
30
+ | EMET-AUTH-022 | Invite login can no longer be refreshed | active |
31
+ | EMET-AUTH-023 | A refresh cannot widen scope | active |
32
+ | EMET-AUTH-024 | Access token is not recognised | active |
33
+ | EMET-AUTH-025 | Access token has expired | active |
34
+ | EMET-AUTH-026 | Sub-key open lost a race | active |
35
+ | EMET-AUTH-027 | Sub-key store conflict | active |
36
+ | EMET-AUTH-028 | Sub-key refusal | active |
37
+ | EMET-AUTH-029 | Guest display name is required | active |
38
+ | EMET-AUTH-030 | Guest access is off on this install | active |
39
+ | EMET-AUTH-031 | A guest invite accepts only read access | active |
40
+ | EMET-AUTH-032 | Guest invite source is not a registered tag | active |
41
+ | EMET-AUTH-033 | Member display name is required | active |
42
+ | EMET-AUTH-034 | Member access is off on this install | active |
43
+ | EMET-AUTH-035 | Member code source is not a registered tag | active |
44
+ | EMET-AUTH-036 | Only the owner can create invites | active |
45
+ | EMET-AUTH-037 | Only the owner can create member access | active |
46
+ | EMET-AUTH-038 | The error report is owner-only | active |
47
+ | EMET-AUTH-039 | HTTP attribution preflight was refused | active |
48
+ | EMET-CFG-001 | Database name must be a plain name | active, internal |
49
+ | EMET-CFG-002 | Collection prefix must be a plain name | active, internal |
50
+ | EMET-CFG-004 | Hosted setup cannot turn sub-keys on from here | active |
51
+ | EMET-CFG-005 | Could not read .env | active |
52
+ | EMET-CFG-006 | Could not write .env | active |
53
+ | EMET-CFG-007 | Startup page is not a whole number | active |
54
+ | EMET-CFG-008 | Startup page does not exist | active |
55
+ | EMET-CFG-009 | First-time setup was given a bot tag | active |
56
+ | EMET-CFG-010 | Setup is missing required answers | active |
57
+ | EMET-CFG-011 | Sub-key answer must be yes or no | active |
58
+ | EMET-CFG-012 | Backup answer must be yes or no | active |
59
+ | EMET-CFG-013 | Setup requires the owner | active |
60
+ | EMET-CFG-014 | Store is already set up | active |
61
+ | EMET-DB-001 | MONGODB_URI is not set | active |
62
+ | EMET-DB-002 | Failed to connect to MongoDB | active |
63
+ | EMET-DB-003 | Query failed on a memory layer | active |
64
+ | EMET-DB-004 | Count failed on a memory layer | active |
65
+ | EMET-DB-005 | Unknown layer field | active |
66
+ | EMET-DB-006 | Failed to write to primary storage | active |
67
+ | EMET-DB-007 | Invalid memory layer | active |
68
+ | EMET-DB-008 | Failed to initialize a layer schema | active |
69
+ | EMET-DB-010 | Unknown layer in a gap query | active |
70
+ | EMET-DB-013 | Failed to save memory | active |
71
+ | EMET-DB-014 | Failed to revise memory | active |
72
+ | EMET-DB-015 | Failed to recall memories | active |
73
+ | EMET-DB-016 | Failed to query a layer | active |
74
+ | EMET-DB-017 | Failed to get system status | active |
75
+ | EMET-DB-018 | Failed to query transcripts | active |
76
+ | EMET-DB-019 | Failed to save a session transcript | active |
77
+ | EMET-DB-020 | Session open could not load unhandled drops | active |
78
+ | EMET-DB-021 | Session open could not check a closed session | active |
79
+ | EMET-DB-022 | Failed to revise a transcript | active |
80
+ | EMET-DB-023 | Failed to read a document | active |
81
+ | EMET-DB-024 | Failed to read document history | active |
82
+ | EMET-DB-025 | Failed to write a document | active |
83
+ | EMET-DB-026 | Failed to list documents | active |
84
+ | EMET-DB-027 | Retirement mark did not persist | active |
85
+ | EMET-DB-028 | Retiring altered the document | active |
86
+ | EMET-DB-029 | Failed to retire a document | active |
87
+ | EMET-DB-030 | Failed to rename a document | active |
88
+ | EMET-DB-031 | Failed to validate a document | active |
89
+ | EMET-DB-032 | Acceptance did not persist | active |
90
+ | EMET-DB-033 | Failed to accept a nonconformance | active |
91
+ | EMET-DB-034 | Failed to patch a document | active |
92
+ | EMET-DB-035 | Failed semantic recall | active |
93
+ | EMET-DB-036 | Failed corpus recall | active |
94
+ | EMET-DOC-001 | doc_id must be a non-empty string | active |
95
+ | EMET-DOC-002 | Document not found | active |
96
+ | EMET-DOC-003 | No retained revision | active |
97
+ | EMET-DOC-004 | expected_version is not a whole number | active |
98
+ | EMET-DOC-005 | Document changed while paging | active |
99
+ | EMET-DOC-006 | Version must be a positive integer | active |
100
+ | EMET-DOC-007 | A record is superseded, not amended | active |
101
+ | EMET-DOC-008 | Doc id is not stored as given | active |
102
+ | EMET-DOC-009 | Client approvals are kept by the server | active |
103
+ | EMET-DOC-010 | A declared tag wrote outside its own folder | active |
104
+ | EMET-DOC-011 | A bot may write only its own records | active |
105
+ | EMET-DOC-012 | Bot records require a registered tag | active |
106
+ | EMET-DOC-013 | A bot tag cannot write a main record | active |
107
+ | EMET-DOC-014 | Main records require a registered tag | active |
108
+ | EMET-DOC-015 | Content must be a non-empty string | active |
109
+ | EMET-DOC-016 | Content exceeds the 2MB limit | active |
110
+ | EMET-DOC-017 | A record revision must name what it supersedes | active |
111
+ | EMET-DOC-018 | supersedes does not name the revision in force | active |
112
+ | EMET-DOC-019 | A record revision needs a reason | active |
113
+ | EMET-DOC-020 | Unregistered source may write a new drop only | active |
114
+ | EMET-DOC-021 | Drop cap for the day is reached | active |
115
+ | EMET-DOC-022 | An existing working document is edited, not rewritten | active |
116
+ | EMET-DOC-023 | A drop id already exists | active |
117
+ | EMET-DOC-024 | A shipped copy is not replaced | active |
118
+ | EMET-DOC-025 | A write would condense a document below half | active |
119
+ | EMET-DOC-026 | A write would fall below half of the daily peak | active |
120
+ | EMET-DOC-027 | The board is never retired | active |
121
+ | EMET-DOC-028 | Working documents are edited, not retired | active |
122
+ | EMET-DOC-029 | retire_doc needs a reason | active |
123
+ | EMET-DOC-030 | old_id must be a non-empty string | active |
124
+ | EMET-DOC-031 | new_id must be a non-empty string | active |
125
+ | EMET-DOC-032 | old_id and new_id name the same document | active |
126
+ | EMET-DOC-033 | rename_doc needs a reason | active |
127
+ | EMET-DOC-034 | The board is never renamed | active |
128
+ | EMET-DOC-035 | A drop is write-once | active |
129
+ | EMET-DOC-036 | Rename destination already exists | active |
130
+ | EMET-DOC-037 | restore_doc needs a reason | active |
131
+ | EMET-DOC-038 | restore_doc needs a source | active |
132
+ | EMET-DOC-039 | A drop is never restored | active |
133
+ | EMET-DOC-040 | A record is not restored | active |
134
+ | EMET-DOC-041 | A shipped copy is not restored | active |
135
+ | EMET-DOC-042 | Restore source is not in EMET_RESTORE_TAGS | active |
136
+ | EMET-DOC-043 | Retained revision does not match its digest | active |
137
+ | EMET-DOC-044 | Templated revision has no conformance verdict | active |
138
+ | EMET-DOC-045 | Retained revision was not conforming | active |
139
+ | EMET-DOC-046 | validate_doc needs a document or content | active |
140
+ | EMET-DOC-047 | Template does not ship with this release | active |
141
+ | EMET-DOC-048 | An acceptance needs a written reason | active |
142
+ | EMET-DOC-049 | An acceptance reason is too short | active |
143
+ | EMET-DOC-050 | Document has no nonconformance to accept | active |
144
+ | EMET-DOC-051 | A required name is empty | active |
145
+ | EMET-DOC-052 | Document version conflict | active |
146
+ | EMET-DOC-053 | Patch target text was not found | active |
147
+ | EMET-DOC-054 | Patch target text matched more than once | active |
148
+ | EMET-DOC-055 | patch_doc needs a reason | active |
149
+ | EMET-DOC-056 | patch_doc cannot edit a drop | active |
150
+ | EMET-DOC-057 | old_str must be a non-empty string | active |
151
+ | EMET-DOC-058 | new_str must be a string | active |
152
+ | EMET-DOC-059 | Patch edits overlap | active |
153
+ | EMET-GEM-001 | Read-back found no document | active |
154
+ | EMET-GEM-002 | Read-back content digest differs | active |
155
+ | EMET-GEM-003 | Read-back version differs | active |
156
+ | EMET-GEM-004 | Read-back found no layer entry | active |
157
+ | EMET-GEM-005 | Layer sha256 column does not match content | active |
158
+ | EMET-GEM-006 | Read-back content differs | active |
159
+ | EMET-GEM-007 | Metadata digest column does not match | active |
160
+ | EMET-GEM-008 | Read-back metadata differs | active |
161
+ | EMET-GEM-009 | Unknown floor section | active |
162
+ | EMET-GEM-010 | Unknown GEM | active |
163
+ | EMET-GEM-011 | GEM is not loadable | active |
164
+ | EMET-GEM-012 | GEM has no floor | active |
165
+ | EMET-GEM-013 | GEM manifest schema id | active, internal |
166
+ | EMET-GEM-014 | Unexpected end of JSON | active, internal |
167
+ | EMET-GEM-015 | Unexpected character in JSON | active, internal |
168
+ | EMET-GEM-016 | Unexpected token in JSON | active, internal |
169
+ | EMET-GEM-017 | Bad number in JSON | active, internal |
170
+ | EMET-GEM-018 | Bad escape in JSON | active, internal |
171
+ | EMET-GEM-019 | Raw control character in a JSON string | active, internal |
172
+ | EMET-GEM-020 | Unterminated JSON string | active, internal |
173
+ | EMET-GEM-021 | Trailing comma in JSON | active, internal |
174
+ | EMET-GEM-022 | Expected a comma in JSON | active, internal |
175
+ | EMET-GEM-023 | Unterminated JSON array | active, internal |
176
+ | EMET-GEM-024 | Expected a JSON key | active, internal |
177
+ | EMET-GEM-025 | Duplicate JSON key | active, internal |
178
+ | EMET-GEM-026 | Forbidden JSON key | active, internal |
179
+ | EMET-GEM-027 | Expected a colon in JSON | active, internal |
180
+ | EMET-GEM-028 | Unterminated JSON object | active, internal |
181
+ | EMET-GEM-029 | JSON starts with a BOM | active, internal |
182
+ | EMET-GEM-030 | Trailing data after JSON | active, internal |
183
+ | EMET-GEM-031 | JSON number is not a safe integer | active, internal |
184
+ | EMET-GEM-032 | Unsupported JSON value | active, internal |
185
+ | EMET-GEM-033 | Attestation is immutable | active |
186
+ | EMET-GEM-034 | metadata.gem must name the active directive | active |
187
+ | EMET-GEM-035 | Served artifact has no hash pin | active |
188
+ | EMET-GEM-036 | No authenticated principal | active |
189
+ | EMET-GEM-037 | Serve log could not be written | active |
190
+ | EMET-GEM-038 | No serve event | active |
191
+ | EMET-GEM-039 | Client-reported sha256 is not accepted here | active |
192
+ | EMET-GEM-040 | Input hash or reference is required | active |
193
+ | EMET-GEM-041 | Served rune has no hash pin | active |
194
+ | EMET-GEM-042 | GEM socket failed closed | active |
195
+ | EMET-INT-001 | Unclassified internal error | active |
196
+ | EMET-MEM-001 | Unknown memory layer | active |
197
+ | EMET-MEM-002 | Unknown importance bucket | active |
198
+ | EMET-MEM-003 | Unknown importance bucket name | active |
199
+ | EMET-MEM-004 | Unknown importance degree | active |
200
+ | EMET-MEM-005 | Lesson metadata was refused | active |
201
+ | EMET-MEM-006 | session_id must come from emet_session_open | active |
202
+ | EMET-MEM-007 | Transcript positions cannot be read | active |
203
+ | EMET-MEM-008 | An entry must carry its source | active |
204
+ | EMET-MEM-009 | A correction names a missing entry | active |
205
+ | EMET-MEM-010 | Episodic revision is prohibited | active |
206
+ | EMET-MEM-011 | target_id must be a positive integer | active |
207
+ | EMET-MEM-012 | No entry with that id in the layer | active |
208
+ | EMET-MEM-013 | Entry is already superseded | active |
209
+ | EMET-MEM-014 | order must be latest | active |
210
+ | EMET-MEM-015 | Search term exceeds the maximum length | active |
211
+ | EMET-MEM-016 | Session slug was refused | active |
212
+ | EMET-MEM-017 | session_id is required | active |
213
+ | EMET-MEM-018 | Machine check refused the append | active |
214
+ | EMET-MEM-019 | A bot tag cannot retire documents | active |
215
+ | EMET-MEM-020 | A bot tag cannot rename documents | active |
216
+ | EMET-MEM-021 | The board already exists | active |
217
+ | EMET-MEM-022 | The board is never written with write_doc | active |
218
+ | EMET-MEM-023 | The board is provisioned by setup | active |
219
+ | EMET-MEM-024 | A board edit needs a session id | active |
220
+ | EMET-MEM-025 | Board edit blocked: drop list unknown | active |
221
+ | EMET-MEM-026 | Unhandled drops block a board restore | active |
222
+ | EMET-MEM-027 | Unhandled drops block a board edit | active |
223
+ | EMET-MEM-028 | An added board row needs origin | active |
224
+ | EMET-MEM-029 | The board edit is nonconforming | active |
225
+ | EMET-MEM-030 | Query must be a non-empty string | active |
226
+ | EMET-MEM-032 | Corpus name is not recognised | active |
227
+ | EMET-MEM-034 | Only a ready payload can be abridged | active |
228
+ | EMET-PAGE-001 | as_of must be an ISO date or unix seconds | active |
229
+ | EMET-PAGE-002 | Only the owner can create or edit an area document | active |
230
+ | EMET-PAGE-003 | Only the owner can read topic pages | active |
231
+ | EMET-PAGE-004 | Area must be a slug | active |
232
+ | EMET-PAGE-005 | No current area document | active |
233
+ | EMET-PAGE-006 | Lint found no current area document | active |
234
+ | EMET-PAGE-007 | Startup pages could not fit the budget | active |
235
+ | EMET-PROV-001 | derived_from must be an object | active |
236
+ | EMET-PROV-002 | derived_from has two origins | active |
237
+ | EMET-PROV-003 | derived_from needs a span or entries | active |
238
+ | EMET-PROV-004 | derived_from.entries must be a non-empty array | active |
239
+ | EMET-PROV-005 | Entry ids must be positive integers | active |
240
+ | EMET-PROV-006 | derived_from.session_id must be a non-empty string | active |
241
+ | EMET-PROV-007 | exchange_start must be a positive integer | active |
242
+ | EMET-PROV-008 | exchange_end is before exchange_start | active |
243
+ | EMET-PROV-009 | exchange_end must be a positive integer | active |
244
+ | EMET-PROV-010 | Provenance entry is required | active |
245
+ | EMET-RATE-001 | Rate limit exceeded | active |
246
+ | EMET-SESS-001 | The transcript position is not available | active |
247
+ | EMET-SESS-002 | Transcript timestamps must be numbers | active |
248
+ | EMET-SESS-003 | timestamp_start must be before timestamp_end | active |
249
+ | EMET-SESS-004 | session_id must be a string | active |
250
+ | EMET-SESS-005 | Session graph is unavailable | active |
251
+ | EMET-TOOL-001 | A tool has no annotation entry | active, internal |
252
+ | EMET-TOOL-002 | A source tag is required | active |
253
+ | EMET-TOOL-003 | A source tag is required and none are registered | active |
254
+ | EMET-TOOL-004 | Source tag is not registered | active |
255
+ | EMET-TOOL-005 | The call is outside the token scope | active |
256
+ | EMET-TOOL-006 | Exchange index was refused | active |
257
+ | EMET-TOOL-007 | Client approval was refused | active |
258
+ | EMET-TOOL-008 | Unknown tool | active |
259
+ | EMET-TOOL-009 | since must be an ISO date | active |
260
+ | EMET-TOOL-010 | since is older than 90 days | active |
261
+ | EMET-TOOL-011 | codes must be a list of EMET codes | active |
262
+ | EMET-TOOL-012 | limit must be a whole number from 1 to 200 | active |
263
+ | EMET-TOOL-013 | correlation_id must be 16 hex characters | active |
264
+ | EMET-TRN-001 | An exchange field exceeds the length cap | active |
265
+ | EMET-TRN-002 | Transcript request exceeds the length cap | active |
266
+ | EMET-TRN-003 | session_id must be a non-empty string | active |
267
+ | EMET-TRN-004 | session_start must be a Unix timestamp | active |
268
+ | EMET-TRN-005 | exchanges must be a non-empty array | active |
269
+ | EMET-TRN-006 | Exchange messages must be strings | active |
270
+ | EMET-TRN-007 | A transcript revision replaces the whole part | active |
271
+ | EMET-TRN-008 | A transcript correction needs a reason | active |
272
+ | EMET-TRN-009 | No transcript found under that session id | active |
273
+ | EMET-TRN-010 | exchange_index must be a whole number | active |
274
+ | EMET-VAL-001 | Content is required | active |
275
+ | EMET-VAL-002 | Content must be a string | active |
276
+ | EMET-VAL-003 | Content is shorter than the minimum | active |
277
+ | EMET-VAL-004 | Content exceeds the maximum length | active |
278
+ | EMET-VAL-005 | Query is required | active |
279
+ | EMET-VAL-006 | Query must be a string | active |
280
+ | EMET-VAL-007 | Query cannot be empty | active |
281
+ | EMET-VAL-008 | Query exceeds the maximum length | active |
282
+ | EMET-VAL-010 | Context must be a string | active |
283
+ | EMET-VAL-011 | Context exceeds the maximum length | active |
284
+ | EMET-VAL-012 | Layer is required | active |
285
+ | EMET-VAL-013 | Layer must be a string | active |
286
+ | EMET-VAL-014 | Invalid layer | active |
287
+ | EMET-VAL-015 | Value is required | active |
288
+ | EMET-VAL-016 | Value must be a number | active |
289
+ | EMET-VAL-017 | Value is outside the allowed range | active |
290
+ | EMET-VAL-018 | Metadata must be an object | active |
291
+ | EMET-VAL-019 | Metadata exceeds the maximum size | active |
292
+ | EMET-VAL-020 | metadata.session_id is not accepted | active |
293
+ | EMET-VAL-021 | expires_at disagrees with valid_until | active |
294
+ | EMET-VAL-022 | valid_until disagrees with expires_at | active |
295
+ | EMET-VAL-023 | Routing must be a plain object | active |
296
+ | EMET-VAL-024 | Value must be a boolean | active |
297
+ | EMET-VAL-025 | Invalid assertion_origin | active |
298
+ | EMET-VAL-026 | Value must be a string | active |
299
+ | EMET-VAL-027 | Custom metadata object is too large | active |
300
+ | EMET-VAL-028 | valid_from is after valid_until | active |
301
+ | EMET-VAL-029 | Value must be a positive integer | active |
302
+ | EMET-VAL-030 | Tags must be an array | active |
303
+ | EMET-VAL-031 | Too many tags | active |
304
+ | EMET-VAL-032 | Each tag must be a string | active |
305
+ | EMET-VAL-033 | Tag exceeds the maximum length | active |
306
+ | EMET-VAL-034 | Related ids must be an array | active |
307
+ | EMET-VAL-035 | Too many related ids | active |
308
+ | EMET-VAL-036 | Value exceeds the maximum length | active |
309
+ | EMET-VAL-037 | Filters must be an object | active |
310
+ | EMET-VAL-038 | Unknown importance bucket filter | active |
311
+ | EMET-VAL-039 | Content search term exceeds the maximum length | active |
312
+ | EMET-VAL-040 | Context search term exceeds the maximum length | active |
313
+ | EMET-VAL-041 | importance_min is greater than importance_max | active |
314
+ | EMET-VAL-042 | emotional_intensity_min is greater than the max | active |
315
+ | EMET-VAL-043 | timestamp_after is after timestamp_before | active |
316
+ | EMET-VAL-044 | Options must be an object | active |
317
+ | EMET-VAL-045 | order_by must be a string | active |
318
+ | EMET-VAL-046 | Arguments must be an object | active |
319
+
320
+ ## Retired numbers
321
+
322
+ These numbers were removed from the registry. They stay reserved. A later removal is added here. The registry and the lock file do not list them.
323
+
324
+ | Code | Summary | Status |
325
+ |---|---|---|
326
+ | EMET-CFG-003 | MONGODB_URI is not set for setup | retired |
327
+ | EMET-DB-009 | MONGODB_URI is not set; cannot assess gaps | retired |
328
+ | EMET-DB-011 | MONGODB_URI is not set; cannot read topic pages | retired |
329
+ | EMET-DB-012 | MONGODB_URI is not set; cannot verify session artifacts | retired |
330
+ | EMET-MEM-031 | Query exceeds the maximum length | retired |
331
+ | EMET-MEM-033 | Startup pages could not fit the budget | retired |
332
+ | EMET-VAL-009 | Query exceeds the maximum length | retired |
@@ -179,6 +179,22 @@ EMET_SOURCE_TAG=<this computer's name, e.g. laptop>
179
179
 
180
180
  **Verify:** `node -e "import('mongodb').then(async ({MongoClient}) => { const c = new MongoClient(process.env.MONGODB_URI); await c.connect(); console.log('ok', (await c.db('emet').command({ping:1})).ok); await c.close(); })"` — run with the `.env` loaded (`node --env-file=.env -e "..."` on Node 20.6+). Expect `ok 1`. If it times out, the access list has not propagated yet; wait a minute and retry once.
181
181
 
182
+ **Give `emet_app` EMET's role before the server writes.** `atlas setup` leaves a built-in role that can delete. Replace it with `emetRecordKeeper`, defined in `src/atlas-role.js`. The privilege list includes `REMOVE@<db>.error_log` (`<db>` is `emet`) so error-log rotation can delete from `error_log` only (10,000 entries or 90 days, daily summaries kept). Do not grant `REMOVE` on the database. Do not grant `REMOVE` on any other collection.
183
+
184
+ ```
185
+ atlas projects list
186
+ node scripts/atlas-role.mjs --project <projectId> --db emet --user emet_app --prefix <prefix>
187
+ node scripts/atlas-role.mjs --project <projectId> --db emet --user emet_app --prefix <prefix> --apply
188
+ ```
189
+
190
+ The dry run prints the create `scripts/atlas-role.mjs` will run.
191
+ The dry run calls the read-only `atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json`. It needs Atlas auth and changes nothing.
192
+ The `--privilege` value is the full list from `src/atlas-role.js`, including `REMOVE@<db>.error_log`.
193
+ `--apply` runs that command. `--prefix <prefix>` is `EMET_COLLECTION_PREFIX` (default `emet_`). Pass it for a prefixed install. `--prefix` overrides `EMET_COLLECTION_PREFIX`. The effective prefix is `--prefix`, or else the env. Re-applying replaces prefixed privilege names if the effective prefix doesn't match the install.
194
+ Do not pass `--privilege` to `customDbRoles update` on its own. That replaces the whole role and drops find, insert, and update.
195
+
196
+ **Atlas UI, if you are not using the script.** Database Access → Custom Roles → Add New Custom Role, name `emetRecordKeeper`. On collection `error_log`, enable `REMOVE` only (`REMOVE@<db>.error_log`). Add the other actions from [SETUP.md](SETUP.md) stage 1 step 2. Leave `REMOVE` off the database-wide row and off every other collection. Edit `emet_app` and set its role to `emetRecordKeeper`.
197
+
182
198
  **Skip the vector index for now.** `semantic_recall` is optional; keyword recall works without
183
199
  it, and Atlas Automated Embedding is not available on every tier. It is a later step, in
184
200
  [SETUP.md](SETUP.md) stage 1, item 7, once everything else works.
@@ -14,8 +14,11 @@ There are three places, and it is worth being clear about which is which:
14
14
  archiving before replacing, checking the order of a session's writes (the monorail) - all here.
15
15
  - **The database** decides *what the server's own login may do*. EMET's login runs under the
16
16
  least-privilege role `emetRecordKeeper` ([SETUP.md](SETUP.md), `src/atlas-role.js`): it can
17
- insert and update, and it has no permission to remove anything from the record. So "nothing is
18
- deleted" holds even against a bug in the server, not only against a model's choice.
17
+ insert and update, and it has no permission to remove anything from the record. Error-log
18
+ rotation may delete from `error_log` only, so the role includes `REMOVE@<db>.error_log`
19
+ (10,000 entries or 90 days, daily summaries kept). That action is not granted on a memory,
20
+ a controlled document, or a transcript. So "nothing is deleted" holds for the record even
21
+ against a bug in the server, not only against a model's choice.
19
22
 
20
23
  No layer can widen another. In particular, **a server cannot grant itself permission**. Nothing in
21
24
  this repository can stop your host from asking you to approve every call, and nothing in it should
@@ -37,11 +40,11 @@ Every tool carries MCP annotations, declared in one table in `src/annotations.js
37
40
  | `idempotentHint` | Calling it again with the same arguments changes nothing further. |
38
41
  | `openWorldHint` | It reaches systems outside this server's own store. |
39
42
 
40
- Of the 30 tools (`EMET_SUBKEYS=1` adds the four sub-key tools below; with the flag off they are not registered):
43
+ Of the 34 tools (`EMET_SUBKEYS=1` adds the four sub-key tools below; with the flag off they are not registered):
41
44
 
42
- - **11 are read-only.** `emet_gaps`, `emet_floor`, `recall`, `semantic_recall`,
45
+ - **15 are read-only.** `emet_gaps`, `emet_page`, `emet_pages`, `emet_page_lint`, `emet_error_report`, `emet_floor`, `recall`, `semantic_recall`,
43
46
  `corpus_recall`, `query_layer`, `query_transcripts`, `read_doc`, `read_doc_history`, `list_docs`,
44
- `validate_doc`. These cannot change the store under any arguments.
47
+ `validate_doc`. These cannot change the store under any arguments. `emet_page`, `emet_pages`, and `emet_page_lint` are owner-only views: they compute a topic page and never write it back. `emet_error_report` is owner-only and reads the operational error log. It sends nothing.
45
48
  - **10 are additive writes.** `emet_initialize` (it provisions a missing board), `save_to_layer`, `revise_memory`, `save_transcript`,
46
49
  `revise_transcript`, `emet_session_open`, `emet_transcript_append`, `emet_session_close` (it
47
50
  records blocked attempts), `rename_doc`, `accept_nonconformance`. They add; they do not remove or replace.
package/docs/ROADMAP.md CHANGED
@@ -4,7 +4,7 @@ Status as of 2026-10-11 (last full report: [status/2026-09-29-state-of-the-syste
4
4
 
5
5
  ## Where things stand
6
6
 
7
- - **Live:** 30 tools (11 read-only); `EMET_SUBKEYS=1` adds four sub-key tools. 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.
7
+ - **Live:** 34 tools (15 read-only); `EMET_SUBKEYS=1` adds four sub-key tools. 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
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
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
10
  - **The database** login runs under the least-privilege role `emetRecordKeeper`: it can insert and update, never remove the record.
@@ -22,22 +22,22 @@ Status as of 2026-10-11 (last full report: [status/2026-09-29-state-of-the-syste
22
22
 
23
23
  ## Done since the last revision (2026-09-28)
24
24
 
25
- - SQL translator stage 2: read path native to MongoDB; the translator and the `event` mirror column removed (commit-017c7f3).
26
- - Test-tree pass: one shared harness; dated suites named by subject (commit-7980e20).
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
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 (6491586), then the chain walk moved into `emet_gaps` so no host needs the repo or a shell (commit-43a5ef6).
29
- - Security audit, first pass: two findings fixed; nothing open (commit-c2aa70d).
30
- - Least-privilege Atlas role, scripted and documented for new users (commit-26134e7).
31
- - Provenance stamped from the transcript; semantic and procedural writes with no source refused (commit-4f6aba8).
32
- - Guardrails & Monorails and lab results (commit-e7b4ebe through commit-20c39d3).
33
- - Charter revised 2026-09-29 (the aleph, the monorail, the database boundary, the per-exchange transcript; commit-d98356e) and again 2026-09-30 (the admission test in commitment 6; procedural ref 404).
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
34
 
35
35
  ## Proposed features and functions
36
36
 
37
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
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
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 (proposed): 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.
40
+ - PR 4 (proposed, EMET-private branch `gem-socket/pr4-status-cost`): 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
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
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
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.)
package/docs/SETUP.md CHANGED
@@ -36,29 +36,52 @@ when you want a second device to reach the same memory.
36
36
 
37
37
  | On | Allowed |
38
38
  |---|---|
39
- | your whole EMET database | find, insert, update, create collection, create index, list collections, list indexes, list search indexes, collection and database stats |
39
+ | your whole EMET database | find, insert, update, create collection, create index, list collections, list indexes, list search indexes, collection and database stats. Not `REMOVE`. |
40
40
  | `<prefix>oauth_tokens` | remove — revoking a sign-in token |
41
41
  | `_emet_verify` | remove — the status check deletes its probe document and does not drop the collection |
42
+ | `error_log` | `REMOVE` — rotation deletes old rows (10,000 entries or 90 days) after a daily summary is kept in `error_log_summary`. The name is not prefixed. It is not the record. |
42
43
 
43
- Nothing else may be removed or dropped. `tests/atlas-role.test.js` fails if the code ever
44
- starts deleting from a collection this role does not allow.
44
+ `REMOVE` on `error_log` is the rotation privilege. Do not grant `REMOVE` on the database.
45
+ Do not grant `REMOVE` on any other collection. `error_log_summary` is insert and update only.
46
+ A document-controlled collection cannot be deleted. Nothing else may be removed or
47
+ dropped. `tests/atlas-role.test.js` fails if the code ever starts deleting from a
48
+ collection this role does not allow.
45
49
 
46
50
  **The quick way (Atlas CLI).** Install it (`winget install MongoDB.MongoDBAtlasCLI`, or
47
51
  see mongodb.com/docs/atlas/cli), sign in with `atlas auth login` in your own terminal —
48
52
  it asks you to pick options, so it needs a real keyboard — then from the EMET folder:
49
53
 
50
54
  ```
51
- node scripts/atlas-role.mjs --project <projectId> --db <database> --user emet_app
55
+ node scripts/atlas-role.mjs --project <projectId> --db <database> --user emet_app --prefix <prefix>
56
+ node scripts/atlas-role.mjs --project <projectId> --db <database> --user emet_app --prefix <prefix> --apply
52
57
  ```
53
58
 
54
- That is a dry run: it prints the commands. Add `--apply` to create the role and move the
55
- user onto it; `--rollback` puts the user back on `readWrite@<database>`. Find the project id
56
- with `atlas projects list`. A non-default `EMET_COLLECTION_PREFIX` is picked up, or pass
57
- `--prefix`.
58
-
59
- **The click way.** Database Access → Custom Roles → Add New Custom Role, name
60
- `emetRecordKeeper`, add the actions in the table above against your database and the two
61
- collections; then edit the user and set its role to `emetRecordKeeper`.
59
+ The first command is a dry run. `scripts/atlas-role.mjs` prints the create it will run.
60
+ The dry run calls the read-only `atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json`. It needs Atlas auth and changes nothing.
61
+ The `--privilege` value is the full list from `src/atlas-role.js`, which includes `REMOVE@<db>.error_log`.
62
+ It does not grant `REMOVE` on any other collection. The second command creates the role
63
+ and moves the user onto it. `--rollback` puts the user back on `readWrite@<database>`.
64
+ Find the project id with `atlas projects list`. `<db>` is the `MONGODB_DB` you pass as `--db`.
65
+ `--prefix <prefix>` is `EMET_COLLECTION_PREFIX` (default `emet_`). Pass it for a prefixed install.
66
+ `--prefix` overrides `EMET_COLLECTION_PREFIX`. The effective prefix is `--prefix`, or else the env. Re-applying replaces prefixed privilege names if the effective prefix doesn't match the install.
67
+ Do not pass `--privilege` to `customDbRoles update` on its own.
68
+ That replaces the whole role and drops find, insert, and update.
69
+
70
+ **Atlas UI.** Database Access → Custom Roles → Add New Custom Role, name
71
+ `emetRecordKeeper`. Add the actions in the table. For `error_log`, set the database to
72
+ `<db>`, the collection to `error_log` (not blank, not every collection), and enable the
73
+ action `REMOVE` only. That is `REMOVE@<db>.error_log`. Leave `REMOVE` off the
74
+ database-wide row. Leave `REMOVE` off every other collection. Then edit the user and
75
+ set its role to `emetRecordKeeper`.
76
+
77
+ **Local MongoDB.** `scripts/atlas-role.mjs` is Atlas only. On a server with users, in the
78
+ EMET database, `db.createRole` with the same rows. The shell action is lowercase. The
79
+ log privilege is the resource below, which is the Atlas privilege `REMOVE@<db>.error_log`.
80
+ Do not grant that action on any other collection.
81
+
82
+ ```javascript
83
+ { resource: { db: "<db>", collection: "error_log" }, actions: ["remove"] }
84
+ ```
62
85
 
63
86
  **Prove it.** From any EMET host, run `emet_status` with `probe: true`. It writes, reads
64
87
  back and removes a test document, so a role missing something fails there, loudly, instead
@@ -225,6 +248,81 @@ it should come back `ready` with your existing identity, not `setup_required`. I
225
248
  `setup_required`, one of the four variables above is wrong; **do not run the setup interview,
226
249
  which would write a new identity over your existing one.**
227
250
 
251
+ ## Upgrading to 0.3.0
252
+
253
+ 0.3.0 rotates `error_log`. The log is capped at 10,000 entries or 90 days, and the daily summaries are kept in `error_log_summary`. Rotation deletes from `error_log`, so an existing `emetRecordKeeper`
254
+ role — or whatever custom role you created at setup — needs the `REMOVE` action on
255
+ `<db>.error_log`. Without it, rotation fails. Add `REMOVE` on `error_log` only. Do not add
256
+ `REMOVE` on the database. Do not add `REMOVE` on any other collection. Memories, controlled
257
+ documents, and transcripts stay non-deletable.
258
+ ISO 9001 7.5.3 / ISO 13485 4.2.5 document-control wording is unchanged.
259
+
260
+ `<db>` is your `MONGODB_DB`. `<id>` is the project id from `atlas projects list`. If the role is
261
+ not named `emetRecordKeeper`, use the name you created.
262
+
263
+ **Save the role first.**
264
+
265
+ ```
266
+ atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json > role-before.json
267
+ ```
268
+
269
+ Keep `role-before.json`. It is the copy you can read if the next command is wrong.
270
+
271
+ **Atlas CLI.** This command adds `REMOVE` on `error_log` and leaves the rest of the role in place.
272
+ Passing `--privilege` to `customDbRoles update` on its own replaces the role's privileges, including find, insert, and update.
273
+
274
+ ```
275
+ atlas customDbRoles update emetRecordKeeper --privilege REMOVE@<db>.error_log --append --projectId <id>
276
+ ```
277
+
278
+ **Atlas UI.** Database Access → Custom Roles → edit `emetRecordKeeper` → add a privilege.
279
+ Database `<db>`, collection `error_log`, action `REMOVE`. Do not enable `REMOVE` on the
280
+ database-wide row. Do not enable `REMOVE` on any other collection. Save. Then confirm the
281
+ database user still has that custom role and no broader built-in role.
282
+
283
+ **Local MongoDB.** In the database where you created the role:
284
+
285
+ ```javascript
286
+ db.grantPrivilegesToRole("emetRecordKeeper", [
287
+ { resource: { db: "<db>", collection: "error_log" }, actions: ["remove"] }
288
+ ])
289
+ ```
290
+
291
+ That shell action is the Atlas privilege `REMOVE@<db>.error_log`.
292
+
293
+ ### Clear a stray DROP_COLLECTION
294
+
295
+ **Confirm `DROP_COLLECTION` is gone.** Describe the role again:
296
+
297
+ ```
298
+ atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json
299
+ ```
300
+
301
+ `DROP_COLLECTION` must not appear anywhere in that output. An older stray `DROP_COLLECTION` on `_emet_verify` is not cleared by that append command. That append command cannot remove a privilege. Remove it by re-applying the definition, which has no `DROP_COLLECTION`. Dry run first, then apply. The dry run calls the read-only `atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json`. It needs Atlas auth and changes nothing. `--prefix <prefix>` is `EMET_COLLECTION_PREFIX` (default `emet_`). `--prefix` overrides `EMET_COLLECTION_PREFIX`. The effective prefix is `--prefix`, or else the env. Re-applying replaces prefixed privilege names if the effective prefix doesn't match the install.
302
+
303
+ ```
304
+ node scripts/atlas-role.mjs --project <id> --db <db> --user <dbUsername> --prefix <prefix>
305
+ node scripts/atlas-role.mjs --project <id> --db <db> --user <dbUsername> --prefix <prefix> --apply
306
+ ```
307
+
308
+ Or in the Atlas UI: Database Access → Custom Roles → edit `emetRecordKeeper` and clear `DROP_COLLECTION` from `_emet_verify` and from every other resource. Then describe the role again and confirm `DROP_COLLECTION` is still absent.
309
+
310
+ **Verify `REMOVE`.** The same describe output is the check:
311
+
312
+ ```
313
+ atlas customDbRoles describe emetRecordKeeper --projectId <id> --output json
314
+ ```
315
+
316
+ Pass when all of these are true:
317
+
318
+ - An `actions` entry has `"action": "REMOVE"` and a resource with `"db"` equal to `<db>` and `"collection": "error_log"`.
319
+ - No `REMOVE` resource has an empty collection. An empty collection is the whole database.
320
+ - Every collection on a `REMOVE` action is either `error_log` or one of the two rows above it in the Stage 1 table. This upgrade adds `error_log` and no other collection.
321
+
322
+ From a machine that has the server's `MONGODB_URI`, `node scripts/db-privileges.mjs` prints
323
+ `<db>.error_log` with `remove`, and `<db>.*` does not include `remove`. Then, from any EMET
324
+ host, `emet_status` with `probe: true` still passes.
325
+
228
326
  ## Stage 4 — tell your assistant to use it
229
327
 
230
328
  Setup gives the store an identity. It does not tell your assistant to consult it. See
@@ -249,6 +347,10 @@ the thing is doing its job.
249
347
 
250
348
  ---
251
349
 
350
+ ## Error reports
351
+
352
+ `emet_error_report` is owner-only and read-only. It returns the report and a draft. EMET does not send mail. The draft address is `EMET_REPORT_EMAIL`. When that variable is unset, the address is `reports@example.com`. That address is a placeholder, not a mailbox. Configure `EMET_REPORT_EMAIL` to a real address, or the report is returned and goes nowhere. An empty string, or any value that is not one plain address, returns the report and no email.
353
+
252
354
  ## When it does not work
253
355
 
254
356
  | Symptom | Cause |
@@ -259,6 +361,7 @@ the thing is doing its job.
259
361
  | `semantic entries must carry their source` | Open a session with `emet_session_open` and pass its `session_id` on the save. |
260
362
  | `vector_index: not queryable on this deployment tier` | Normal on a local MongoDB or before the Atlas index exists; only `semantic_recall` needs it. |
261
363
  | Connect times out | Your IP is not in Atlas Network Access, or the cluster is paused. |
364
+ | Error-log rotation fails, unauthorized to remove | The role has no `REMOVE` on `error_log`. Follow [Upgrading to 0.3.0](#upgrading-to-030) and append `REMOVE@<db>.error_log`. |
262
365
  | Auth fails | The password in the URI needs percent-encoding if it contains `@ : / ?` etc. |
263
366
  | `semantic_recall` returns nothing, keyword search works | The vector index is missing or was dropped by a tier migration. |
264
367
  | Writes land but another device cannot see them | The two hosts point at different `MONGODB_DB` values. |
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@dreamforgestudiollc/emet",
3
- "version": "0.2.6",
4
- "description": "EMET 0.2.6 — Enduring Memory & Epistemic Tiers. An MCP memory server with persistent shared memory for AI agents, bot teams and chats: layered memory, verified writes, a verbatim transcript tier, per-client attribution and approvals, and client-side GEM execution. EMET verifies the record, not the computation. A GEM is seated only when its released flag is true.",
3
+ "version": "0.3.0",
4
+ "description": "EMET 0.3.0 — Enduring Memory & Epistemic Tiers. An MCP memory server with persistent shared memory for AI agents, bot teams and chats: layered memory, verified writes, a verbatim transcript tier, per-client attribution and approvals, and client-side GEM execution. EMET verifies the record, not the computation. A GEM is seated only when its released flag is true.",
5
5
  "keywords": [
6
6
  "agent-memory",
7
7
  "ai-agents",
@@ -42,6 +42,7 @@
42
42
  "src/",
43
43
  "verification/",
44
44
  "templates/",
45
+ "areas/",
45
46
  "guides/",
46
47
  "gems/",
47
48
  "docs/*.md",