From 3b6dd3970d5290844b20d69a143763d841594159 Mon Sep 17 00:00:00 2001 From: Omar Sobh Date: Mon, 21 Sep 2026 14:10:02 -0500 Subject: [PATCH] =?UTF-8?q?docs:=20addendum=205=20=E2=80=94=20door=20gover?= =?UTF-8?q?nor,=20memory=20rerank,=20paper=20triage?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5 --- docs/NEXT-SESSION.md | 33 ++++++++++++++++++++++++++++----- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/docs/NEXT-SESSION.md b/docs/NEXT-SESSION.md index 0ddefb6..5adcdcc 100644 --- a/docs/NEXT-SESSION.md +++ b/docs/NEXT-SESSION.md @@ -411,8 +411,31 @@ and the test's write gets EPIPE on Linux); tolerated as the no-node path working. Key lives in prod `.env` + compose passthrough and the local override; never in git, never in a mission container. -**Next for this tier, in order:** (1) accumulate agreement rows from real -missions before any promotion from shadow to selection; (2) the door -governor on Jev with the human middle band — stops the GLM spend per door -action and gives the door a third path; (3) memory rerank; (4) paper -triage in continuous research. +**The door governor, on the same tier** (`2656d73`). Three Nouls per +outbound action — data leaving the organisation, a credential in the +content, unsolicited/abusive — the max is the deny probability. On 24 +hand-labelled door actions (`eval/door-actions.json`): **AUROC 1.000, +no false denies, no misses**, 4 of 24 in the review band (db dump 0.71, +delegate-exfil 0.74, a threat 0.77, and the one borderline allow: the +repo's name to a contractor, 0.56). 168 ms, ~600 tokens, off the z.ai +quota. `PolicyOutcome::Hold`: ≥ 0.8 refused, < 0.2 executed, between +them a pending approval (session_key `door:`) the agent is told not +to retry; the approvals route executes a held door action on approve — +the grant decide mints, the tool consumes. The chat-model governor stays +as the fallback without a key. Live, `door` scenario **7/7**: internal +summary executed; credentials outbound refused at 99%; onboarding mail +held with a pending approval and no outbox row; approve executed it then. + +**Two smaller uses** (`33560c7`): `mission_memory::recall` reranks BM25's +top 8 with one Noul per candidate and drops < 0.3 (keyword overlap made +every task that names a file recall the MICROVM.md verdict). The +continuous-research manifest's `topic_tags`, empty since the manifest +existed, is filled per paper by a Choice over the mission's topics, plus +a four-level `relevance` Score the ranking phase can start from; PORTICO's +abstract scored 3.0 at 1.0. + +**Next for this tier:** accumulate skill-triage agreement rows from real +missions before any promotion from shadow to selection; a local backend +only if the vendor dependency bites (logit read-out over the 9B fleet +model, not a cross-encoder — measured); Slack/A2A intent routing when +inbound volume justifies it.