Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
110 changes: 110 additions & 0 deletions .agent/memory/candidates/graduated/2d53056e593c.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,110 @@
{
"id": "2d53056e593c",
"key": "manual_2d5305",
"name": "manual_2d5305",
"claim": "Several tooling and API gotchas recur across a working session even after being individually caught once, because a single encounter doesn't automatically generalize into a standing rule: the PR-list API's merged field being unreliable (must check the single-PR endpoint); squash-merged branches never showing as git ancestors (verify by content/ID presence, not ancestry); a stale local checkout after an earlier push in the same session diverging silently; and diff-scoped CI lint checking a whole touched file, not just the changed hunk. Each of these needs to be treated as a standing checklist item to consult before the relevant operation, not a one-off lesson learned and then re-derived from scratch the next time it's encountered.",
"conditions": [
"across",
"after",
"ancestors",
"ancestry",
"api",
"automatically",
"because",
"before",
"branches",
"caught",
"changed",
"check",
"checking",
"checklist",
"checkout",
"consult",
"content",
"diff-scoped",
"diverging",
"doesn",
"each",
"earlier",
"encounter",
"encountered",
"endpoint",
"even",
"field",
"file",
"generalize",
"git",
"gotchas",
"hunk",
"individually",
"into",
"item",
"just",
"learned",
"lesson",
"lint",
"local",
"merged",
"needs",
"never",
"next",
"once",
"one-off",
"operation",
"pr-list",
"presence",
"push",
"re-derived",
"recur",
"relevant",
"rule",
"same",
"scratch",
"session",
"several",
"showing",
"silently",
"single",
"single-pr",
"squash-merged",
"stale",
"standing",
"time",
"tooling",
"touched",
"treated",
"unreliable",
"verify",
"whole",
"working"
],
"evidence_ids": [
"2026-08-01T06:53:43.671436+00:00"
],
"cluster_size": 1,
"canonical_salience": 8.0,
"staged_at": "2026-08-01T06:53:43.671436+00:00",
"status": "accepted",
"decisions": [
{
"ts": "2026-08-01T06:53:43.671436+00:00",
"action": "staged",
"reviewer": "learn"
},
{
"ts": "2026-08-01T06:53:50.650448+00:00",
"action": "graduated",
"reviewer": "host-agent",
"notes": "Several gotchas recurred even after individual capture -- worth the meta-lesson that a checklist consulted before the operation, not recall alone, is what actually prevents repetition.",
"provisional": false,
"evidence_snapshot": [
"2026-08-01T06:53:43.671436+00:00"
],
"lessons_sha": "4bce83c74754"
}
],
"rejection_count": 0,
"accepted_at": "2026-08-01T06:53:50.650434+00:00",
"reviewer": "host-agent",
"rationale": "Several gotchas recurred even after individual capture -- worth the meta-lesson that a checklist consulted before the operation, not recall alone, is what actually prevents repetition."
}
128 changes: 128 additions & 0 deletions .agent/memory/candidates/graduated/718c9430f44b.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
{
"id": "718c9430f44b",
"key": "manual_718c94",
"name": "manual_718c94",
"claim": "When resolving real overlap between a new draft and an existing, more comprehensive doctrine, \"avoid duplication\" does not automatically mean \"make the newer, simpler thing subordinate to the older, more complex one.\" It means determining which document actually serves which situation and sizing each to its own job. A heavyweight protocol built for a rare, hard problem (e.g. concurrent multi-agent edits to the same repo, or reconciling a fork separated from its source by months of drift) should not become the default an agent reads first for the common, simple case (one branch, one agent, no concurrent editing) just because it existed first and is more thorough. Getting this backwards is not caught by re-reading a project's own stated single-source-of-truth value, since that value is genuinely being honored in some sense (no literal duplication) even while the sizing is wrong -- it may require direct correction from a human collaborator who can see the actual audience mismatch.",
"conditions": [
"actual",
"actually",
"agent",
"audience",
"automatically",
"avoid",
"backwards",
"because",
"become",
"between",
"branch",
"built",
"case",
"caught",
"collaborator",
"common",
"complex",
"comprehensive",
"concurrent",
"correction",
"default",
"determining",
"direct",
"doctrine",
"document",
"draft",
"drift",
"duplication",
"each",
"editing",
"edits",
"even",
"existed",
"existing",
"first",
"fork",
"genuinely",
"getting",
"hard",
"heavyweight",
"honored",
"human",
"job",
"just",
"literal",
"make",
"mean",
"means",
"mismatch",
"months",
"more",
"multi-agent",
"new",
"newer",
"older",
"one",
"overlap",
"own",
"problem",
"project",
"protocol",
"rare",
"re-reading",
"reads",
"real",
"reconciling",
"repo",
"require",
"resolving",
"same",
"see",
"sense",
"separated",
"serves",
"simple",
"simpler",
"since",
"single-source-of-truth",
"situation",
"sizing",
"some",
"source",
"stated",
"subordinate",
"thing",
"thorough",
"value",
"which",
"while",
"who",
"wrong"
],
"evidence_ids": [
"2026-08-01T06:53:43.608740+00:00"
],
"cluster_size": 1,
"canonical_salience": 8.0,
"staged_at": "2026-08-01T06:53:43.608740+00:00",
"status": "accepted",
"decisions": [
{
"ts": "2026-08-01T06:53:43.608740+00:00",
"action": "staged",
"reviewer": "learn"
},
{
"ts": "2026-08-01T06:53:50.501493+00:00",
"action": "graduated",
"reviewer": "host-agent",
"notes": "The hierarchy-inversion mistake this session, requiring direct human correction rather than self-catching -- worth a durable lesson about resolving overlap correctly, not just avoiding literal duplication.",
"provisional": false,
"evidence_snapshot": [
"2026-08-01T06:53:43.608740+00:00"
],
"lessons_sha": "c7f4daa0894a"
}
],
"rejection_count": 0,
"accepted_at": "2026-08-01T06:53:50.501478+00:00",
"reviewer": "host-agent",
"rationale": "The hierarchy-inversion mistake this session, requiring direct human correction rather than self-catching -- worth a durable lesson about resolving overlap correctly, not just avoiding literal duplication."
}
Loading
Loading