Skip to content

Caller-supplied derived-payload erasure (lawful deletion door) - #11101

Closed
gunbai-bot[bot] wants to merge 1 commit into
session/still-crab-505from
session/still-crab-505-derived-erasure
Closed

gunbai-bot[bot] wants to merge 1 commit into
session/still-crab-505from
session/still-crab-505-derived-erasure

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds DerivedPayloadErasure and classify_review_sheet_with_erasure: the caller supplies the deletion subject. ListingGone does not erase.
  • Writes DerivedField to empty (or noops if already empty). Never writes OperatorEntered, never drops the row, standing stays ListingGone. Located writes or a located refuse (still projected, standing not gone, listing not on sheet, duplicate request).
  • classify_review_sheet is empty-erasures. Live review_sheet_ensure is unchanged. derived_payload_erasure_frontier is Scaffold until a caller binds it.
  • Identity split (our key vs eBay item id) is not in this change.

Stacked on #10986. Does not belong in that PR.

Test plan

  • listing_gone_with_judgement_is_retained_and_marked still greens
  • gone + erasure blanks title, keeps judgement, does not patch standing
  • erasure while still projected refuses
  • erasure while standing is still Observed refuses
  • erasure of a listing not on the sheet refuses
  • already-empty derived converges
  • duplicate erasure listing refuses

Made with Cursor

…xpressible without treating ListingGone as a delete.

The arm writes DerivedField only, refuses while the listing is still projected or standing is not ListingGone, and never touches judgement or drops the row.

Co-authored-by: Cursor <cursoragent@cursor.com>
@gunbai-bot

gunbai-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

Closing so draft #11097 (same head) can take the stacked base. That is the dashboard-attached PR.

@gunbai-bot gunbai-bot Bot closed this Sep 11, 2026
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.

0 participants