feat(assembly): add guarded material transactions - #12
Draft
waywardmonkeys wants to merge 1 commit into
Draft
Conversation
Add an Exedra-owned BindMaterial workflow over the Addressable assembly runtime. Validate selection and guard revisions, endpoint identity, referent, effective value, capability, and duplicate targets before any mutation. Dry runs and applies return matching change and undo evidence. Non-empty applies write validated slot indices in place, advance the shared revision once, and leave stale handles and pins visibly stale. Keep the generic validation seam explicitly open in proposed ADR 0003; this commit does not move assembly storage or material policy into Addressable.
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
1 participant
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.
Stacked on #11 (
codex/addressable-assembly), so this diff contains only the guarded transaction layer.This adds an Exedra-owned
BindMaterialworkflow overAddressableAssembly. Guards validate the selection revision, endpoint and referent identity, observed effective value, typed capability, and duplicate targets before any mutation. Dry runs and applies return matchingMaterialChangeandUndoMaterialevidence; a successful non-empty apply writes validated slot indices in place, advances the shared revision once, and leaves earlier handles and pins visibly stale. A failed batch changes neither state nor revision.This remains draft because the generic validation sequence overlaps
addressable_reference. Before readiness, we should decide whether the shared revision, guard, and atomicity skeleton belongs in Addressable while Exedra retains material policy, storage, and application.