Development record
Memory notes give the status line one written file, but the shipped home-gitignore intent states the status line writes nothing at all
Memory notes give the status line one written file, but the shipped home-gitignore intent states the status line writes nothing at all
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2610091918433290-an-agent-working-in-an-abcd-managed.md:73— "This is an exception to the product thinker's ruling of 2026-10-05 that the status line writes nothing (iss-2610050556383525), and it covers exactly that one figure, in one file per session" - End B:
.abcd/development/intents/shipped/itd-2610140858048004-abcd-s-home-keeps-itself-out-of-a.md:37— "the status line excepted: it writes nothing at all (iss-2610050556383525)"
itd-2610091918433290 grants the status line one write, a fill figure per session, as an exception to iss-2610050556383525. itd-2610140858048004 exempts the status line from laying the ignore file because it writes nothing at all, citing the same issue. Once the planned exception is built, the shipped statement is false, and the shipped exemption's reasoning goes with it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1218.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262039286595. Same unbuilt exception, seen from the shipped home-ignore intent.
Frontmatter
| id | iss-2610262044370559 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262044370559-memory-notes-give-the-status-line-one.md
open on GitHub ↗ · commit history ↗
References2
- itd-2610091918433290Agents keep memory notes with /abcd:memory, recalled when they matterrelated
- itd-2610140858048004abcd's home keeps itself out of a dotfiles repositoryrelated
mentions3
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610050556383525Product thinker ruling, 2026-10-05: abcd does not touch a person's ~/.claude/ folder, and nothing in it calls abcd, with one exception the person consents to: the status line, which is essential for product thinkers and which a plugin cannot set (a plugin's settings may set only agent and subagentStatusLine; the hooks abcd needs can all live in the plugin's hooks/hooks.json). Today ahoy install offers and writes the statusLine entry, and the person's settings had also gained a SubagentStop entry that called a stale abcd build (the defect that recreated ~/.abcd the same day). Because the status line runs on every refresh in every session, the risks the ruling accepts are: a stale or missing binary at the wired path; a status-line verb that writes state; a line left behind after an uninstall; the person's previous status command recorded once and gone stale; a concurrent write corrupting settings.json so the harness ignores the whole file; a wired path a project or another user can replace; and settings synced to a machine without that path.
- iss-2610262039286595The memory-notes intent lets the status line write one fill file, but the configuration page says the status line writes nothing at all