From 50129b710565a0f4794cf3dcc01178773d154637 Mon Sep 17 00:00:00 2001 From: Daniel Parapunov Date: Tue, 7 Jul 2026 12:07:02 +0200 Subject: [PATCH 1/4] docs(osc): add portfolio follow-up for active-open-questions-e9b7cdc8b3 --- .../178-active-open-questions-e9b7cdc8b3.md | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 .osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md diff --git a/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md new file mode 100644 index 00000000..974c1f16 --- /dev/null +++ b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md @@ -0,0 +1,57 @@ +# Plan: .osc portfolio gap active-open-questions-e9b7cdc8b3 + + + +## Status + +backlog + +## Context + +john-lomein's `.osc` portfolio steward detected a `active_open_questions` gap. + +Active plan `.osc/plans/active/163-proof-harness-v2.md` still has unresolved open questions that can block roadmap/backlog alignment. + +Source evidence: + +- Active plan: `.osc/plans/active/163-proof-harness-v2.md` +- Open question: Judge model choice and whether two judge models are needed for agreement checks. +- Open question: Whether the naked arm gets a minimal-checklist variant as a second control (the June 3 reset doc suggests it should). +- Open question: Which adapter(s) constitute the proof arms first: codex only, or codex plus claude. + +GitHub intake: #252 + +## Goal + +Resolve the detected roadmap/backlog/active-plan gap with a small, source-grounded follow-up that keeps the public roadmap and `.osc` work record coherent. + +## Constraints / Out of scope + +- Do not merge, publish, release, dispatch workflows, change repository settings, or touch secrets from this plan alone. +- Keep public wording owner-neutral and avoid local/private machine context. +- Do not overclaim proof, compliance, or runtime authority. +- If the gap is a false positive, close this plan with evidence rather than forcing implementation. + +## Files to touch + +- `ROADMAP.md` or relevant docs only if the gap requires wording/priority clarification. +- `.osc/plans/active/*` or `.osc/plans/backlog/*` only through normal plan/amendment flow. +- Source/test files only if a later accepted issue narrows implementation scope. + +## Acceptance criteria + +- [ ] The gap is confirmed against current `ROADMAP.md` and `.osc/plans` source truth. +- [ ] The chosen outcome is one of: create/update a real follow-up plan, mark the older backlog entry superseded/done with evidence, amend the active plan, or reject the steward finding as a false positive. +- [ ] Any public issue/PR comments use compact Status / Evidence / Next wording. +- [ ] Verification commands appropriate to touched files pass before closeout. + +## Verification steps + +1. Re-run the portfolio steward dry-run and confirm this gap no longer appears, or document why it remains intentionally open. +2. Run the repository's configured verification for any touched code/docs. +3. Run `git diff --check`. + +## Open questions + +- Should this gap become implementation work, roadmap clarification, backlog cleanup, or a rejected false-positive record? +- If implementation is needed, which existing active/backlog plan should own it? From f1fb831c08ad72ee4a90b3d561d39b2a285adedc Mon Sep 17 00:00:00 2001 From: Daniel Parapunov Date: Tue, 7 Jul 2026 12:15:52 +0200 Subject: [PATCH 2/4] test: update corpus hash for portfolio gap 178 --- tests/section-parser.test.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/section-parser.test.ts b/tests/section-parser.test.ts index 6df92beb..359a3b62 100644 --- a/tests/section-parser.test.ts +++ b/tests/section-parser.test.ts @@ -255,7 +255,8 @@ This sample must not count as the real section. // 174 release closeout: added evidence-battery package-sync plan to done. // 175 release prep: added ambient capture trust package-sync plan. // 176 release prep: added 0.35.0 package release-sync plan. - expect(hash(planIssueSnapshot)).toBe('d8d8777986758ddf5d505cfd732dcfbe62ef93b326358c375b3e551ac7bb5c9c'); + // 178 portfolio follow-up: added active-open-questions-e9b7cdc8b3 backlog gap plan. + expect(hash(planIssueSnapshot)).toBe('3affef87e5b44e36c1c14a212ce5ba8078cfe86d88beaa8f81a67fbbec3f803b'); expect(scaffold.failures).toEqual([]); // 168: evidence note 2026-06-12-168-dollar-verb-retirement.md added to .osc/releases. // 170 review hardening: evidence note refreshed with PR URL, final test count, and Codex-reported total_tokens. From 05a5d1df3cb620068b50148d5364838dca08b72f Mon Sep 17 00:00:00 2001 From: Daniel Parapunov Date: Tue, 7 Jul 2026 12:55:20 +0200 Subject: [PATCH 3/4] docs: keep portfolio gap steward wording neutral --- .osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md index 974c1f16..7d6c9e0e 100644 --- a/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md +++ b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md @@ -1,6 +1,6 @@ # Plan: .osc portfolio gap active-open-questions-e9b7cdc8b3 - + ## Status @@ -8,7 +8,7 @@ backlog ## Context -john-lomein's `.osc` portfolio steward detected a `active_open_questions` gap. +The `.osc` portfolio steward detected an `active_open_questions` gap. Active plan `.osc/plans/active/163-proof-harness-v2.md` still has unresolved open questions that can block roadmap/backlog alignment. From 0d307bb25dc1a6b2fc51b54ec82a94ef9d876560 Mon Sep 17 00:00:00 2001 From: Daniel Parapunov Date: Tue, 7 Jul 2026 13:13:42 +0200 Subject: [PATCH 4/4] docs(osc): narrow proof harness portfolio gap --- .../178-active-open-questions-e9b7cdc8b3.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md index 7d6c9e0e..8e95f7d7 100644 --- a/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md +++ b/.osc/plans/backlog/178-active-open-questions-e9b7cdc8b3.md @@ -8,22 +8,23 @@ backlog ## Context -The `.osc` portfolio steward detected an `active_open_questions` gap. +The `.osc` portfolio steward detected an `active_open_questions` gap against the parent active plan text. -Active plan `.osc/plans/active/163-proof-harness-v2.md` still has unresolved open questions that can block roadmap/backlog alignment. +Current source truth is narrower than the parent plan's original open-question list: amendment 1 already adds the minimal-checklist control arm, chooses the Claude-first execution lane, and defers the judge-model choice to preregistration review. This follow-up should reconcile that parent-plan/amendment drift or reject the steward finding as a stale-text false positive, not reopen all original questions as unresolved work. Source evidence: -- Active plan: `.osc/plans/active/163-proof-harness-v2.md` -- Open question: Judge model choice and whether two judge models are needed for agreement checks. -- Open question: Whether the naked arm gets a minimal-checklist variant as a second control (the June 3 reset doc suggests it should). -- Open question: Which adapter(s) constitute the proof arms first: codex only, or codex plus claude. +- Parent active plan: `.osc/plans/active/163-proof-harness-v2.md` +- Amendment source truth: `.osc/plans/active/163-proof-harness-v2-amendment-1.md` +- Resolved by amendment: minimal-checklist control arm is in; execution lane is Claude-first. +- Deferred by amendment: Codex/OMX lane is not the first proof arm; judge-model choice is a preregistration-review decision before any scored run. +- Narrowed gap: reconcile the parent plan's stale `## Open questions` text with amendment 1, or record that the steward gap is a false positive against current source truth. GitHub intake: #252 ## Goal -Resolve the detected roadmap/backlog/active-plan gap with a small, source-grounded follow-up that keeps the public roadmap and `.osc` work record coherent. +Resolve the narrowed parent-plan/amendment drift with a small, source-grounded follow-up that keeps the public roadmap and `.osc` work record coherent. ## Constraints / Out of scope