Skip to content

fix: recover original Vision receipts after checkpoint repair - #8763

Draft
AetherX-Technologies wants to merge 1 commit into
loopx-project:mainfrom
AetherX-Technologies:codex/receipt-vision-recovery-20261114
Draft

AetherX-Technologies wants to merge 1 commit into
loopx-project:mainfrom
AetherX-Technologies:codex/receipt-vision-recovery-20261114

Conversation

@AetherX-Technologies

Copy link
Copy Markdown
Contributor

A checkpoint supplement can remove the Vision source selected by an older Turn and strand its writeback. Reconstruct plain Vision sources from complete canonical history at the recorded admission time, then require the existing semantic owner to accept fresh evidence.

Preserve the original Todo/effect binding in both the live producer and recovery contract when the Todo has already completed. Explicit empty or conflicting guards still fail closed; first unbound reviews and verified legacy settlement remain supported.

Validation: frozen failure cases turn green; 52 history checks, 62 interaction checks, 12 explicit-guard checks, 6 producer checks, and 36 typed-owner tests passed. A snapshot rehearsal followed the public recovery plan, retained the complete original identity, and recorded one writeback/debit despite an exact retry; a mismatched Todo was rejected. Independent review checked raw evidence. Full-suite CI was not rerun locally.

Signed-off-by: AetherX-Technologies <icybreeze9th@gmail.com>
@mergify

mergify Bot commented Nov 15, 2026

Copy link
Copy Markdown

This pull request has merge conflicts with main and cannot be merged
until they are resolved. Please rebase or merge the base branch, @AetherX-Technologies.

Choose the remote for the base repository, not an out-of-date fork.
For a fork clone, first inspect git remote -v; upstream must point
to https://github.com/loopx-project/loopx.git. If it is absent, add it
with git remote add upstream https://github.com/loopx-project/loopx.git.
Then run:

git fetch upstream
git rebase upstream/main
# Resolve each conflict, git add the resolved files, then git rebase --continue.
git push --force-with-lease origin HEAD

For a same-repository clone whose origin points to
https://github.com/loopx-project/loopx.git, use origin instead of
upstream for fetch/rebase. If you prefer merging the base, use
git merge <base-remote>/main and push normally.

Keep the DCO Signed-off-by trailer on every commit when you rebase.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify Bot added the needs-rebase Mergify: the pull request has merge conflicts with its base branch label Nov 15, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-rebase Mergify: the pull request has merge conflicts with its base branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant