docs(plugin-quality): settle write-once as an agent discipline (#3866) - #4968
Merged
Merged
Conversation
Record Option A: write-once is a documented discipline with after-the-fact verify, not a filesystem lock. Mechanical seal is unpaid. A sealed packet asserts bytes at seal time, which unblocks #3867. Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Contributor
|
PR body contract — issue linkage This PR body does not yet satisfy the issue-linkage contract:
Edit the body and this comment updates itself on the next run. |
kyle-sexton
added a commit
that referenced
this pull request
Sep 28, 2026
…pshot section The branch was built from a copy that predated #4968 and dropped its write-once paragraph and claim table; restore them and point the snapshot sentence at the new section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PT4esxbdC7eQiwQxy35Mie
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
2 participants
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.
Closes #3866
Summary
Write-once on the plugin-quality evidence packet is a documented agent discipline with after-the-fact verify, not a filesystem lock. Mechanical seal is unpaid (Option A).
Decision
Claim: The producing agent holds Write (and the main thread can Edit). Nothing makes a sealed file physically unwritable.
packet-seal.sh verifyreports CHANGED after the fact;recordthen refuses to reseal, so later files in that packet stay UNSEALED. That loss is terminal for the packet. A sealed packet asserts bytes at seal time, not current world state (unblocks the snapshot question on #3867 without closing it).Basis:
packet-seal.shrecord/verify (reseal refuses over a CHANGED entry); the three write-once rules inskills/audit/reference/evidence-packet.md;agents/auditor.mdWrite grant. Option B (chmod / write proxy that refuses sealed files) is unpaid: it must not break the documented re-seal ofpacket.sha256, and it is a cross-platform lock the plugin does not currently own.As of: 2026-09-28.
Recheck: a paid slice that makes sealed packet files physically unwritable on the platforms this plugin supports without breaking the documented re-seal of
packet.sha256, orpacket-seal.shgaining an--acknowledge-divergencepath.Docs + checklist only.
packet-seal.sherror text unchanged.plugin-quality0.7.27.Test plan
skills/audit/reference/evidence-packet.md