Repository navigation
Extract plural SCM compatibility realization shape - #7405
Merged
Merged
Conversation
briansrls
force-pushed
the
agent/scm-compatibility-r1
branch
4 times, most recently
from
July 29, 2026 18:43
a349400 to
350fd30
Compare
briansrls
force-pushed
the
agent/scm-compatibility-r1
branch
from
July 29, 2026 19:27
350fd30 to
8d75ecb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extract the R1 compatibility-realization shape from the independently landed Git, Mercurial, and Pijul R0 models. The shared carrier contains only demonstrated presentation/capability roles: opaque target and generation handles, an independent fidelity disposition for every retained or lost axis, state-bearing projection/read-back identities, and modeled-or-unavailable conditional advance. Each adapter retains its upstream-native typed receipt.
This also removes the Git-shaped projection slot and Git-specific scenario names from the C0 native interaction contract. A submission carries realization receipts keyed by realization and target; a later independently read-back receipt replaces the prior row idempotently. Adding a fourth realization supplies a handler without editing the contract or introducing
ScmKind/vendor dispatch.Projection and read-back handles now fingerprint the actual observed repository state. The producer/version remains part of the read-back identity, but cannot collapse distinct Git, Mercurial, or Pijul observations. Capture facts have one authority: the per-axis fidelity profile. There is no separate exclusive capture flag that could contradict it.
R1 deliberately does not model semantic integration, policy admission, repair capability, executed advance, commit authority, or an
Appliedreceipt. Executed advance and repair states wait for the later realization that actually produces those receipts.Test plan
main_wetprojection: PASSregen_stage0 --verify: PASS (regen_divergence_count=0)cargo fmt --all --check: PASSgit diff --check: PASS