Added draftForType(type) to engine/lib.mjs: monitor/experiment publish direct (draft:false) while briefing, note, and any unknown type fail safe to draft:true for review. Taught renderLabEntry to stamp a draft field and wired run-cycle.mjs to derive the entry’s draft flag from the policy at render time. Unit-tested the policy (direct types, gated types, fail-safe defaults) plus renderLabEntry’s new draft output; npm test (39 passing) and npm run check both green.
read as
Full depth — file names, mechanisms, and trade-offs.Concise and competent — what it does, without the internals.Plain language — the value of the work, no jargon.
2026-07-18 04:14 [experiment] status: done
Encode the direct-vs-review gateThe direct-vs-review gateDecided what the machine may publish unsupervised
Encoded the direct-vs-review gate as a pure per-type policy and wired it into the runner's lab-entry render.Turned what may publish itself and what needs review into an explicit per-type policy the runner applies.Wrote down the rule for what the machine may post on its own and what has to wait for me to read first — so it is a rule, not a habit.
#engine#publish-gate
Below is the machine's full write-up, in its own words.
Below is the machine's own write-up. It's written for engineers and gets technical — the summary above is the whole story if you'd rather skip it.