Skip to content

feat(amico-run): adoption stamping — the feedback loop closes (#1683) - #1694

Merged
aarontrowbridge merged 1 commit into
mainfrom
opencode/1683-adoption-stamping
Oct 3, 2026
Merged

aarontrowbridge merged 1 commit into
mainfrom
opencode/1683-adoption-stamping

Conversation

@aarontrowbridge

Copy link
Copy Markdown
Member

Part of #1679. Closes #1683. TDD green: 20 new tests (core+verb), claims suites 95/95, typecheck clean. claims stamp (recommend-outcome | solve-run citations, citation must resolve, dry-run default) + claims sweep (nightly idempotent backfill from the real events.jsonl recommendation records — proposed/outcome paired, overridden named-never-stamped). Event seam documented honestly: no machine-readable solve-run citation stream exists yet — citations ride the stamp verb. Idempotency: second sweep stamped 0, registry md5-identical.

…n-keyed idempotent stamps (#1683)

Brain flywheel slice 4 (#1679): the feedback loop closes — knowledge USED
reaches the claim. An accepted recommend-outcome or a solve-run citation
increments the cited claim's applied counter + last_applied and appends ONE
applied history entry (the pinned vocabulary, no new event class); statement
and status are never touched (adoption is a counter + a date, never a
judgment — lifecycle stays slice 5's).

- stamp: the callable verb — dry-run default, --apply writes; the citation
  must resolve into the substrate first (the event exists in the problem's
  events.jsonl AND is accepted; the run dir exists); re-stamping the same
  citation is a stamped:false no-op (the citation is the idempotency key,
  carried in the applied note's fixed convention).
- sweep: the nightly backfill — walks every problem workspace's events.jsonl
  (the ONE machine-readable adoption record that exists today: the
  recommendation events amicode_recommend appends), pairs accepted outcomes
  with their propose's provenance refs, resolves refs mechanically against
  the registry (trailing segment; projection names claims after their
  cards), stamps; overridden outcomes are named, never stamped; unmatched
  refs are named skips. Idempotent: re-sweep changes nothing (byte-tested).
- pure core in claims.ts (stampAdoption / isStamped / appliedNote /
  renderStampedNote / resolveClaimRef / planAdoptionSweep); prose below the
  frontmatter survives a stamp verbatim (renderStampedNote).
- fixtures: stamp-registry (2 claims) + sweep-problems (2 event streams, a
  no-events workspace); solve-run citations have no machine-readable stream
  yet and ride the stamp verb — the honest seam, documented in the verb.
@coderabbitai

coderabbitai Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e2fc9d77-8778-4ff3-bef7-2852accf5104
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@aarontrowbridge
aarontrowbridge merged commit 067a0e9 into main Oct 3, 2026
12 checks passed
@aarontrowbridge
aarontrowbridge deleted the opencode/1683-adoption-stamping branch October 3, 2026 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Brain flywheel 4: adoption stamping — the feedback loop closes

1 participant