From 95f380c46eb83da11f38000a1811be54ee00c912 Mon Sep 17 00:00:00 2001 From: Aaron Trowbridge Date: Fri, 25 Sep 2026 04:42:13 -0400 Subject: [PATCH] feat(modes): encode meta-improvement + the per-loop visual record into the research and develop gate packs (#1554) --- packages/extension/modes/develop/pack.toml | 6 ++++++ packages/extension/modes/research/card.md | 6 +++++- packages/extension/modes/research/pack.toml | 6 ++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/packages/extension/modes/develop/pack.toml b/packages/extension/modes/develop/pack.toml index c5fd65fcd..72b88ea2b 100644 --- a/packages/extension/modes/develop/pack.toml +++ b/packages/extension/modes/develop/pack.toml @@ -44,6 +44,12 @@ name = "integrate" owner = "human" procedure = "A unit finishing under human-in-the-loop review has its ready PR approved by a reviewer who is never the implementer, and no merge happens before that approval." + [[phases.gates]] + name = "meta-improvement-delta" + kind = "derived" + owner = "director" + procedure = "Each dev walk records its own meta-delta alongside the landed code: skill friction encountered during implementation filed as findings, doctrine and docs updated in the same PR where the code moved, and the hypothesis seed for research handed over at close. Improvement is part of the walk's record, never deferred maintenance." + [[handoffs]] kind = "hypothesis_seed" target = "research" diff --git a/packages/extension/modes/research/card.md b/packages/extension/modes/research/card.md index d2e1b45a3..755a0b2df 100644 --- a/packages/extension/modes/research/card.md +++ b/packages/extension/modes/research/card.md @@ -80,7 +80,11 @@ commit the ledger update → repeat. The analyzer cast carries the skill-friction check — instructions-vs-reality mismatches become findings, repeated un-skilled idioms become skill proposals — and the record boundary carries the same skill-delta row (findings filed, skills touched, proposals -pending). +pending) PLUS the loop's visual record: pulse/data plot artifacts beside the +run outputs and the campaign dashboard widget refresh where one exists, and +vault knowledge cards for measured laws. Recording, refining, and curating +skills and vault knowledge is a first-class loop output — meta-improvement +rides the loop, never trails it (the `record-boundary-curation` gate). **The boundary** — read-only ops and bounded side-effect-free one-liners are probes; the moment work writes a durable file, launches a solve, or runs a diff --git a/packages/extension/modes/research/pack.toml b/packages/extension/modes/research/pack.toml index da10c4b38..eb860fff4 100644 --- a/packages/extension/modes/research/pack.toml +++ b/packages/extension/modes/research/pack.toml @@ -65,6 +65,12 @@ roles = ["analyzer"] owner = "director" procedure = "Commit the ledger update at the loop boundary as sole writer — hypothesis-verdict row, loop-log row, in-flight state, and next queue — so the ledger never lies about what is in the air." + [[phases.gates]] + name = "record-boundary-curation" + kind = "derived" + owner = "director" + procedure = "At every record boundary emit the loop's visual record (pulse/data plot artifacts beside the run outputs, plus the campaign dashboard widget refresh where one exists) and commit the curation delta as a first-class loop output: skill findings filed with provenance, vault knowledge cards written for measured laws, and pending proposals' status. Meta-improvement rides the loop, never trails it." + [[phases.gates]] name = "catalog-promotion" kind = "human"