Skip to content

fix(overview): attest deletion-only deltas - #164

Closed
dayebishouji wants to merge 1 commit into
aoci-spec:v0.2.0-linefrom
dayebishouji:fix/overview-deletion-attestation
Closed

dayebishouji wants to merge 1 commit into
aoci-spec:v0.2.0-linefrom
dayebishouji:fix/overview-deletion-attestation

Conversation

@dayebishouji

Copy link
Copy Markdown
Contributor

A deletion-only L5 delta reports the removed identity but delivers zero Entries. The generic Challenge scorer treats zero correct answers as a failure, drops the retained base, and makes the next Overview fall back to full delivery.

Accept the empty answer list for a retained deletion-only delta with unchanged Root and Meta after delivery confirmation and governance alignment. The current identity envelope and complete delivery claims still have to validate. Add an MCP regression that removes an orphan, verifies the deletion metadata and proof, and requests the next delta from the new base.

Validation

  • Focused Go Overview delta and Attestation tests passed.
  • Windows stdio reproduction: deletion-only now passes at 0/0 and keeps the base. The mixed deletion/update control passes at 1/1. Both reconstructed Entry sets match a fresh full delivery. Both used the same cache-off fixture setting.
  • Public text, index quality (10/10), and AOCI Verify/Check/Guide passed.
  • Local make fast and make verify could not start because make is unavailable in Git Bash.

alkor2000 pushed a commit that referenced this pull request Nov 3, 2026
A deletion-only L5 delta reports the removed identity but delivers zero
Entries, so its Challenge has no ordinal. The generic scorer graded the
empty answer list as zero correct, a failure, which dropped the retained
base and sent the next Overview back to a full delivery.

A retained deletion-only delta with unchanged Root and Meta now passes on
an empty answer list with zero reported Entries, once delivery is
confirmed and governance is aligned; the current identity envelope and the
complete-delivery claims still have to validate. Every other delivery keeps
the pass share and the identity-miss rule. An MCP regression removes an
orphan, proves the deletion delta, and asks for the next delta from the new
base. The delivery contract says so.

Ported from the contributor's branch onto the 0.2.0 line, excluding the
governance assets, which the line re-authors.

Closes #164

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alkor2000 pushed a commit that referenced this pull request Nov 3, 2026
- CHANGELOG: one Unreleased bullet each for the deletion-only delta proof
  (#164) and the replaced-selection snapshot refusal (#165), both by
  dayebishouji.
- The zh-CN database.error.snapshot_selection message follows its
  neighbours: "数据库source %s", "已保存Snapshot", no spaces around ASCII.
- The delivery contract's paragraph that #164 extended is rewrapped to the
  file's width; no word changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alkor2000

Copy link
Copy Markdown
Contributor

Landed on v0.2.0-line as 22ee057 with your authorship; the governance files were regenerated on this tree. I reproduced it first: with only your test applied, the deletion-only delta graded fail at 0/0 and dropped the base; with the fix it passes and the next delta starts from the new base. In c421d41 I rewrapped the one long line in the delivery contract, no wording changed, and added a CHANGELOG entry. Closing this PR by hand since the branch is not the default one.

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.

2 participants