| name | c-11-memory-carryover-from-branch |
| description | Carry richer onboarding memory from a source branch into official memory only when the corresponding code has landed on the official branch. |
c-11-memory-carryover-from-branch Memory Carryover From Branch
Use this skill when a protected official code branch receives delayed or batched merges, while a developer has accumulated richer onboarding on another branch. The source branch may be a personal workbench branch, an individual feature branch, or a handpicked branch processed as part of a larger reconciliation pass.
The c-11-memory-carryover-from-branch skill is not a Git merge. It is a selective memory reconciliation step. It proves which source-branch code changes are represented in the official branch, then carries only the corresponding onboarding into official memory and refreshes verification metadata against the official code commit.
MCP Tools
Use the Agents Remember MCP memory carryover tools as the normal installed
runtime entry point:
memory_carryover_plan(repo_id="<repo-id>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>")
memory_carryover_apply(repo_id="<repo-id>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>", intent_note="<developer intent>")
Run memory_carryover_plan first. Use memory_carryover_apply only after
reviewing the candidate report. Apply mutates official memory only; it does not
move code branches. The skill tree is instruction-only; installed and
development workflows use the MCP/package route.
Candidate Kinds
Candidates are kind-tagged; include_review_required selects each by its selection key.
file-sidecar: per-file onboarding for a code path in the diff; key = the source path.route-overview: route overview whose route covers a landed path (GitHub #56); key = the normalized route (. for the repo root).memory-only-doc: a sidecar or overview changed only in branch memory while its source path is outside the code diff (e.g. a pre-existing drift re-verified mid-task); key = the doc's source path or route.entity-catalog: the repo entity catalog (onboarding/entities.md); key = the literal entity-catalog. Always review-required when differing — whole-file carry, no entry-level merging. On carry, every git-blob-set-v1 fingerprint row is recomputed against the official code ref and the apply result reports entity_fingerprint_validation (validated / mismatch / skipped, with per-entity detail); fingerprints are derived values and are validated, never trusted as copied.
Evidence Tiers
exact-landed-commit: every commit that touched the source path on the source branch is an ancestor of the official code ref — a single landed commit is not enough, so a later unlanded commit to the same path cannot be carried as landed.patch-id-match: the old-base-to-source-branch patch for the source path matches the old-base-to-official patch.final-content-match: the source file content at the source branch ref matches the content at the official ref.same-path-changed: both branches changed the same source path, but the c-11-memory-carryover-from-branch skill did not prove equivalent code.not-landed: the source path changed on the source branch but not on the official branch (or, for memory-only-doc, does not exist on the official ref).
memory-only-doc candidates use their own evidence values:
memory-only-reverification-valid (auto-carry): the source object at the branch doc's lastVerifiedCommitHash matches the official ref AND official memory has not changed the doc since the memory merge-base.source-diverged, official-memory-moved, unverifiable (review-required): the source moved under the doc; official memory changed it independently (or no merge-base resolves, e.g. the source memory is not a git checkout sharing history); or the branch doc's verification commit cannot be resolved.
Only proven tiers are auto-carry candidates. Same-path overlap is review-required by default because another developer may have changed the same file independently.
Output States
would-carryover: dry-run plan with candidate decisions.carried-over: official memory content and ledger commits were created.nothing-to-carryover: no selected candidate changed official memory.ledger-mapped-head: nothing was actionable, but an unmapped official code HEAD (e.g. a PR merge commit) was mapped to the current memory content commit and the ledger committed.blocked: apply was requested without approval, dirty official memory, missing ledger, or missing required candidate data.
Every apply result also reports memory_main_advance (GitHub #54): after the
carryover commits exist, memory main is fast-forwarded to the official
checkout tip — code main advances via the PR merge, but memory has no PR
flow, so non-main cycles previously left memory main behind indefinitely.
States: fast-forwarded, already-current (main checked out or already at
tip), diverged (independent commits on main — reported, never forced),
failed (e.g. main checked out in another worktree), skipped (no main
branch). After carryover, push memory main per the repo's git workflow when
the developer approves.
Boundaries
- The
c-11-memory-carryover-from-branch skill must not copy source branch memory for code that did not land.
- The
c-11-memory-carryover-from-branch skill must not copy source branch ledger rows into official memory.
- The
c-11-memory-carryover-from-branch skill must refresh carried onboarding metadata to the official code commit, not the source branch commit.
- The
c-11-memory-carryover-from-branch skill must not auto-carry same-path-only evidence.
- The
c-11-memory-carryover-from-branch skill must not overwrite existing different official onboarding unless replace_existing=true or explicit review-required inclusion is used.
- The
c-02-memory-quality-control skill remains the branch-accuracy drift detector; the c-11-memory-carryover-from-branch skill only imports richer memory whose code validity has been proven or explicitly approved.
