@dreamforgestudiollc/emet 0.3.1 → 0.3.3
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 +40 -0
- package/README.md +29 -6
- package/docs/BOOTSTRAP.md +2 -0
- package/docs/BOTS.md +8 -7
- package/docs/DEPLOY.md +6 -0
- package/docs/ERROR-CODES-SPEC.md +2 -2
- package/docs/ERROR-CODES.md +29 -0
- package/docs/GUIDED-SETUP.md +1 -1
- package/docs/PERMISSIONS.md +5 -5
- package/docs/SETUP.md +10 -4
- package/docs/SUBKEYS.md +4 -4
- package/package.json +2 -2
- package/server.json +8 -4
- package/src/aleph.js +34 -13
- package/src/annotations.js +6 -2
- package/src/approve-throttle.js +3 -0
- package/src/atlas-role.js +1 -1
- package/src/attribution.js +76 -28
- package/src/bound-door.js +170 -0
- package/src/break-glass.js +531 -0
- package/src/carry-forward-close.js +386 -0
- package/src/checkpoint.js +241 -0
- package/src/chooser.js +543 -0
- package/src/claimed-tag.js +140 -0
- package/src/conformance.js +269 -5
- package/src/deep-links.js +267 -0
- package/src/dispatch.js +112 -18
- package/src/error-codes.js +29 -0
- package/src/error-log.js +138 -26
- package/src/error-report.js +17 -5
- package/src/gaps.js +1 -1
- package/src/grants.js +230 -0
- package/src/http-remote.js +80 -26
- package/src/index.js +18 -2
- package/src/invites.js +47 -1
- package/src/layers.js +1 -1
- package/src/lessons-to-checks.js +1 -1
- package/src/logger.js +3 -1
- package/src/oauth-provider.js +89 -5
- package/src/owl.js +232 -0
- package/src/owner-approvals.js +24 -267
- package/src/owner-session.js +235 -0
- package/src/pages.js +1 -1
- package/src/persons.js +39 -6
- package/src/proof-run.js +70 -0
- package/src/redact.js +4 -0
- package/src/request-log.js +2 -2
- package/src/rotate.js +554 -0
- package/src/rune-dispatch.js +1 -1
- package/src/session-graph.js +44 -25
- package/src/session.js +52 -9
- package/src/setup.js +21 -12
- package/src/staged-write.js +522 -0
- package/src/startup-pages.js +2 -2
- package/src/startup-payload.js +3 -3
- package/src/subkeys.js +61 -0
- package/src/tools.js +290 -79
- package/src/transcript-session.js +23 -4
- package/src/validation.js +1 -1
- package/src/version.js +1 -1
- package/src/writer-approval.js +394 -0
- package/templates/AREA.md +1 -1
- package/templates/BOTHANDOFF.md +2 -2
- package/templates/GRANT.md +48 -0
- package/templates/INDEX.md +9 -7
- package/templates/PROCEDURE.md +1 -1
- package/templates/ROSTER.md +2 -2
- package/templates/SEED.md +2 -2
- package/templates/SESSIONDISPOSITION.md +59 -0
- package/templates/STAGING.md +1 -1
- package/templates/STANDARD.md +1 -1
- package/templates/THREAD.md +1 -1
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
# TEMPLATE — SESSION DISPOSITION
|
|
2
|
+
|
|
3
|
+
**Template control:** id `templates/SESSIONDISPOSITION.md` · revision: the store's version governs · status: IN FORCE · approved: user · 2026-10-28 · session-disposition brief · owner: EMET (base) · built to `templates/STANDARD.md` · supersedes: none
|
|
4
|
+
**Fills:** `records/<name>.md` — one session, or a batch of sessions, noted under document control. **Every `records/*` document is validated against this template by its id** (`templates/STANDARD.md` §9 map). Leaving out the control block does not exempt it (§9a L4).
|
|
5
|
+
**Failure it prevents:** `emet_session_close` compares receipts with the store as it stands that day, so a close attempted days later blocks, and a third blocked close escalates. A fabricated receipt is not a close. Reference case, 2026-10-28: an early `save_transcript` for `2026-10-28_mb-main-chat-backfill-2026-10-26`, inserted_id `6ae1df09c4da08b2cadc1fb4`, eight exchanges, first assistant line opening `grok-bot-vm-453484571 Wed Oct 28 07:38:40 EDT 2026`. That row is a duplicate of `2026-10-28_mb-main-chat-backfill-2026-10-26_verbatim_part1`, written by `emet_transcript_append`, machine line `no local shell MCP`. The duplicate is marked SUPERSEDED and retained. It is not deleted, and it is not a close.
|
|
6
|
+
**Completion rules:** `templates/STANDARD.md` §5, unmodified.
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## HOW TO FILL — rules specific to this template
|
|
11
|
+
|
|
12
|
+
1. **One record may list one session or many.** A batch is one record. Each row is one subject: a session, or one transcript row named by `inserted_id`.
|
|
13
|
+
2. **Disposition is one of** `CARRIED_FORWARD` · `ABANDONED_NO_TRANSCRIPT` · `SUPERSEDED_BY_LATER_SESSION` · `CLOSED_NORMAL` · `RETAINED_OPEN_CRITICAL`. **Reason** is at least 10 characters. **Evidence** names a record, a revision, an inserted id, or dated words. A blank is not evidence.
|
|
14
|
+
3. **A row does not close the session and does not write a receipt.** `emet_session_close` stays receipt-strict. `CLOSED_NORMAL` is rare. Use it only when a real close's receipts still match the store. The row is not those receipts.
|
|
15
|
+
4. **`inserted_id` set** means the row dispositions that transcript document. Use `SUPERSEDED_BY_LATER_SESSION`. The transcript stays in the store. Nothing is deleted. That row does not by itself resolve the session. A session-level row for the same `session_id` uses `inserted_id` `None — <what was checked>`.
|
|
16
|
+
5. **`CARRIED_FORWARD` and `SUPERSEDED_BY_LATER_SESSION` name `carried_forward_to`.** The others may say `None — <what was checked>`.
|
|
17
|
+
6. **`RETAINED_OPEN_CRITICAL` keeps the session open.** Use it when a formal close is still owed, or when the work stays on the ladder. Do not invent the close. Checkpoint overdue listing treats the session-level row as the disposition of record. The session row stays until a real `emet_session_close`.
|
|
18
|
+
7. **`ABANDONED_NO_TRANSCRIPT` is for no live transcript save.** Say that `last_saved_at` is null. Do not use it when a live save exists.
|
|
19
|
+
8. **A subject leaves the next revision of this record only through §3**, with evidence. The prior revision stays in `documents_history`. Nothing is deleted.
|
|
20
|
+
9. **Rows in §0 match the table.** A count that does not match the rows is a nonconformance.
|
|
21
|
+
|
|
22
|
+
### Example — superseded duplicate, and a backfill that still needs a real close
|
|
23
|
+
|
|
24
|
+
Late Oct 25 PM and Oct 27 after about 8:40 had no owner main-chat turns (hidden wakes only). The filtered 31-exchange append path is the complete substance backfill for Oct 25 through Oct 27. These open sessions still need a formal `emet_session_close`. Do not invent closes: `2026-10-28_mb-main-chat-backfill-2026-10-25_verbatim_part1` and `_verbatim_part2`, `2026-10-28_mb-main-chat-backfill-2026-10-26_verbatim_part1`, `2026-10-28_mb-main-chat-backfill-2026-10-27_verbatim_part1` and `_verbatim_part2`.
|
|
25
|
+
|
|
26
|
+
The early `save_transcript` stays SUPERSEDED. It is a duplicate of the Oct 26 verbatim append path. It is not deleted.
|
|
27
|
+
|
|
28
|
+
| session_id | opened_at | last_saved_at | disposition | reason | evidence | carried_forward_to | inserted_id |
|
|
29
|
+
|---|---|---|---|---|---|---|---|
|
|
30
|
+
| 2026-10-28_mb-main-chat-backfill-2026-10-26 | None — this row dispositions the early save_transcript, not the session open. | None — the live Oct 26 backfill is the verbatim part, not this inserted id. | SUPERSEDED_BY_LATER_SESSION | Early save_transcript is a SUPERSEDED duplicate of the verbatim_part1 append path. The transcript row is retained and is not deleted. | inserted_id 6ae1df09c4da08b2cadc1fb4 has 8 exchanges. The first assistant message opens with grok-bot-vm-453484571 Wed Oct 28 07:38:40 EDT 2026. The correct Oct 26 backfill is 2026-10-28_mb-main-chat-backfill-2026-10-26_verbatim_part1 via emet_transcript_append, machine line no local shell MCP. | 2026-10-28_mb-main-chat-backfill-2026-10-26_verbatim_part1 | 6ae1df09c4da08b2cadc1fb4 |
|
|
31
|
+
| 2026-10-28_mb-main-chat-backfill-2026-10-26_verbatim_part1 | None — not an overdue-inventory timestamp. This row records the open append path. | None — this row does not invent a save time. The append path holds the substance. | RETAINED_OPEN_CRITICAL | This open backfill still needs a formal emet_session_close. The filtered 31-exchange append path is the complete substance for Oct 25 through Oct 27. Do not invent a close or a receipt. | Coverage note 2026-10-28. Late Oct 25 PM and Oct 27 after about 8:40 had no owner main-chat turns (hidden wakes only). | None — formal close is still owed on this session. | None — this row dispositions the session, not one transcript document. |
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## §0 RECORD CONTROL
|
|
36
|
+
- Template: `templates/SESSIONDISPOSITION.md` rev __ · Record revision: the store's version governs
|
|
37
|
+
- Session id: __ · Source tag: __ · Written (local): __
|
|
38
|
+
- Scope: __
|
|
39
|
+
- Rows: __
|
|
40
|
+
|
|
41
|
+
## §1 DISPOSITION
|
|
42
|
+
| session_id | opened_at | last_saved_at | disposition | reason | evidence | carried_forward_to | inserted_id |
|
|
43
|
+
|---|---|---|---|---|---|---|---|
|
|
44
|
+
|
|
45
|
+
Or: *None — no session in this record. Checked against: __.*
|
|
46
|
+
|
|
47
|
+
## §2 LIMITS
|
|
48
|
+
What this record does not do. It does not write an `emet_session_close` receipt, it does not mark a session closed, and it does not delete a transcript. A superseded `inserted_id` stays in the store.
|
|
49
|
+
|
|
50
|
+
Say what was checked, including a coverage note when the batch is a backfill. Or: *None — checked against: __.*
|
|
51
|
+
|
|
52
|
+
## §3 SUPERSESSION
|
|
53
|
+
- Supersedes: __ — or *None — first disposition record.*
|
|
54
|
+
|
|
55
|
+
| session_id | inserted_id | why it left | evidence |
|
|
56
|
+
|---|---|---|---|
|
|
57
|
+
|
|
58
|
+
A subject leaves §1 only by a row here. Name the later record that holds it. The prior revision stays in the archive.
|
|
59
|
+
Or: *None — no subject left this revision.*
|
package/templates/STAGING.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# TEMPLATE — STAGING
|
|
2
2
|
|
|
3
|
-
**Template control:** id `templates/STAGING.md` · revision: the store's version governs · status: IN FORCE · approved: user · 2026-09-11 · procedural ref 311 (board
|
|
3
|
+
**Template control:** id `templates/STAGING.md` · revision: the store's version governs · status: IN FORCE · approved: user · 2026-09-11 · procedural ref 311 (board 011) · owner: EMET (base) · built to `templates/STANDARD.md` · supersedes: none
|
|
4
4
|
**Fills:** `staging/<name>-<yyyy-mm>.md` — work lists, proposals, pricings, research notes: anything that is worked on before it is decided.
|
|
5
5
|
**Failure it prevents:** an instance-authored proposal read later as a decision — a delete tool was specified from a staging note nobody had approved, and the note contradicted itself (reference install, procedural ref 296); drafts with no visible status, so a reader could not tell a priced option from an adopted one.
|
|
6
6
|
**Completion rules:** `templates/STANDARD.md` §5, unmodified.
|
package/templates/STANDARD.md
CHANGED
|
@@ -70,7 +70,7 @@ template id and revision used · record revision · session id · source tag ·
|
|
|
70
70
|
|
|
71
71
|
**Every record from a templated document type is validated against its template. No caller can skip it.**
|
|
72
72
|
|
|
73
|
-
**Design — priced 2026-09-10; v1 scope APPROVED by the user 2026-09-11; not yet built. Build detail and limits: `staging
|
|
73
|
+
**Design — priced 2026-09-10; v1 scope APPROVED by the user 2026-09-11; not yet built. Build detail and limits: `the staging note`.**
|
|
74
74
|
- **Where it cannot be skipped:** the write path. Every document write already passes one door (redaction, digests, read-back, receipt). Validation runs there on every write to a templated type.
|
|
75
75
|
- **Which documents are templated:** by the record control block's template id, **and** by a document-id map (`HANDOFF.md` → HANDOFF, `STATE.md` → BOARD, `seeds/*` → SEED, `threads/*` → THREAD, `staging/*` → STAGING, `procedures/*` → PROCEDURE …). The map means leaving out the control block cannot evade validation.
|
|
76
76
|
- **Where it is also visible:** the write receipt carries the verdict; reads carry it per document (as integrity is carried today); session start counts nonconforming documents (as record gaps are counted today).
|
package/templates/THREAD.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# TEMPLATE — THREAD
|
|
2
2
|
|
|
3
|
-
**Template control:** id `templates/THREAD.md` · revision: the store's version governs · status: IN FORCE · approved: user · 2026-09-11 · procedural ref 311 (board
|
|
3
|
+
**Template control:** id `templates/THREAD.md` · revision: the store's version governs · status: IN FORCE · approved: user · 2026-09-11 · procedural ref 311 (board 011) · owner: EMET (base) · built to `templates/STANDARD.md` · supersedes: none
|
|
4
4
|
**Fills:** `threads/<name>.md` — the working document for one project or line of work: its current position, its decisions and their reasons, and a dated log.
|
|
5
5
|
**Failure it prevents:** threads grown by appended sections until the current state sat under hundreds of kilobytes of history (reference install: two threads at 147 KB and 328 KB). A phone session did not read one — the mobile startup skips threads by rule — so the board marked its career rows `NOT COMPLETED` (2026-09-10); whether a phone session could read a thread that size was never tested. When it was read, its priority list still told the user to submit an application that had been submitted two weeks earlier — the current state was never rewritten, only appended to.
|
|
6
6
|
**Completion rules:** `templates/STANDARD.md` §5, unmodified.
|