Repository navigation
v1.30.0 #59
v1.30.0
#59
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Draft-atom lifecycle (#274) — the mk-side prerequisite for #268's session-end extract. Two halves: a recall/render visibility gate (Gap 1) and tiered promotion in
reflect(Gap 2).Added — auto-extracted drafts excluded from recall/render by default (#274 Gap 1)
Session-end extract (#268) lands
status: draftatoms taggedauto-extracted. Those are unvetted, but recall rankeddraftjust belowactive, so they entered live context (and #267's recall-inject) immediately. Recall, the SQLite index query, and fill-mode render now excludestatus: draftatoms that carry theauto-extractedtag by default.auto-extractedtag, not all drafts — hand-authored draft beliefs (the developmental-arc resting state, held in draft by Gap 2) still render. An explicitstatuses: ['draft']filter still surfaces them for inspection.mk recall --include-drafts,RecallQuery.include_drafts, and themk_recallMCP tool'sinclude_draftsparam (CLI / library / MCP parity).AUTO_EXTRACTED_TAGconstant (src/types.ts, also used by themk extractproducer andmk consolidate) + a sharedisUnvettedDraft()predicate:recall.tsfilterAtoms(file-scan path),index-db.tsqueryIndex(SQL path),render.tsfill-mode. Isolated recall inherits the exclusion (routes throughrecall()).test/recall-draft-visibility.test.ts). (PR #276)Changed — tiered draft promotion in
reflect(#274 Gap 2)Replaced the old
belief → fact @ confidence 0.9auto-promote (which converted the over-produced type — the opposite of the monoculture-fix intent) with type-tiered, status-only promotion (draft → active; type unchanged, no file rename):confidence ≥ 0.7and no contradiction with an existing active atom of the same type/scope (reuses thedetectConflictsheuristic).Promotion strips the
auto-extractedtag (matchingmk consolidate, so a reflect-promoted atom isn't left looking unvetted). The contradiction check shares a singleatomsConflict()predicate +CONFLICT_CONFIDENCE_GAPconstant withdetectConflicts(no drift between the promotion gate and the detector). Theatom_promotedevent now carries{ from_status, to_status, type }(was{ from_type, to_type }). +11 tests (test/reflect-tiered-promotion.test.ts); ~10 existing tests that asserted the old belief→fact rule updated to the new semantics. Closes #274; unblocks #268's fork-sideMK_EXTRACT_ON_END=1. (PR #277)This discussion was created from the release v1.30.0.
All reactions