From dba7811f902e3a2d6ba4573350744851b4903c3a Mon Sep 17 00:00:00 2001 From: REPPL <77722411+REPPL@users.noreply.github.com> Date: Sat, 31 Oct 2026 15:01:48 +0000 Subject: [PATCH 1/2] chore: record itd-39's scope conditions as none stated abcd build refused itd-39 at claim_sections because the record had no Scope Conditions section; its planning stated no conditions the context claim holds under, so the section records the nullity token the reader accepts. Also captures intent ready calling the record READY while the build refused it. Assisted-by: Claude:claude-opus-5-5 --- .../itd-39-scope-aware-memory-retrieval.md | 4 ++++ ...73953-abcd-intent-ready-itd-39-reported-the.md | 15 +++++++++++++++ 2 files changed, 19 insertions(+) create mode 100644 .abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md diff --git a/.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md b/.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md index f7157ed6ce..ca19fae8a6 100644 --- a/.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md +++ b/.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md @@ -61,6 +61,10 @@ The failure mode itd-3 guards against is *unbounded scaffolding outside the repo - **Given** a recall keyword that matches a page in both the workspace and user scope, **when** the hook resolves the match, **then** the workspace-scope page is injected and the user-scope page is suppressed (narrower scope wins). - **Given** any prompt, **when** the hook runs, **then** `~/.claude/.../memory/` is never read or written by the retrieval path. +## Scope Conditions + +None stated. + ## Open Questions _None open; the three questions first left here are settled under Decisions (2026-10-11), and the technical questions the plan leaves open are in the bundle's spec._ diff --git a/.abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md b/.abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md new file mode 100644 index 0000000000..4da9b4e022 --- /dev/null +++ b/.abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md @@ -0,0 +1,15 @@ +--- +schema_version: 1 +id: "iss-2610311501473953" +slug: "abcd-intent-ready-itd-39-reported-the" +severity: "minor" +category: "bug" +source: "agent-observation" +found_during: "starting the product thinker's selected builds" +origin: researcher-authored +production_mode: hand-written +found_at: "internal/core/intent/ready.go" +remedy: "Have intent ready append every record-only start check the build runs (claim_sections, hold, blocked, steps where gating) as gating rows, read from intent.StartChecksIn, so READY means the build's record checks pass." +--- + +abcd intent ready itd-39 reported the intent READY on 2026-10-31, listing scope_conditions as an advisory row ('no ## Scope Conditions section — the context claim is unrecorded'), and abcd build itd-39 then refused it at claim_sections for the same missing section. ReadyWithQuestions (internal/core/intent/ready.go) appends only the open-questions start check to the readiness verdict, so READY still does not mean the build will start, the defect iss-2610101610446956 fixed for open questions alone. From b21bd655a4a36aa88c3a456245aae83952274312 Mon Sep 17 00:00:00 2001 From: REPPL <77722411+REPPL@users.noreply.github.com> Date: Sat, 31 Oct 2026 15:14:16 +0000 Subject: [PATCH 2/2] chore: capture a safety-copy branch blocking a build Assisted-by: Claude:claude-opus-5-5 --- ...s-2610311514162877-on-2026-10-31-abcd-build.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 .abcd/work/issues/open/iss-2610311514162877-on-2026-10-31-abcd-build.md diff --git a/.abcd/work/issues/open/iss-2610311514162877-on-2026-10-31-abcd-build.md b/.abcd/work/issues/open/iss-2610311514162877-on-2026-10-31-abcd-build.md new file mode 100644 index 0000000000..bc39edd8ff --- /dev/null +++ b/.abcd/work/issues/open/iss-2610311514162877-on-2026-10-31-abcd-build.md @@ -0,0 +1,15 @@ +--- +schema_version: 1 +id: "iss-2610311514162877" +slug: "on-2026-10-31-abcd-build" +severity: "minor" +category: "process" +source: "agent-observation" +found_during: "starting the product thinker's selected builds" +origin: researcher-authored +production_mode: hand-written +found_at: "internal/core/peers/read.go" +remedy: "Teach the safe backup in the SHELL hazard registry (before git rebase, keep the old tip as a tag or under refs/abcd/backup/, never as a local branch), and have the peers refusal say when the holding branch has no upstream and no worktree, naming it as a probable safety copy and the tag move as the way past." +--- + +On 2026-10-31 abcd build itd-2610170638184486 was refused at the peers check by backup/sota-open-intents-pre-rebase, a local branch an agent made as a safety copy before rebasing research/sota-open-intents onto main; it held the intent's old drafts/ copy, while main and the rebased branch held it in planned/. The peers check reads every local branch under refs/heads/ (internal/core/peers/read.go) and cannot tell a safety copy from live work, and the guard then refused the branch's deletion (git-delete-unproven) because a rebase that squashed and resolved conflicts leaves no ancestry or patch-equivalence for it to prove, so the build stayed blocked until the person allowed the delete by hand. abcd teaches no safe form of the backup: a tag, or a ref outside refs/heads/, would have kept the copy and blocked nothing.