Notes: VRAM cliff, irreversible approval, guard placement - #10
Open
ShortArrow wants to merge 7 commits into
Open
Notes: VRAM cliff, irreversible approval, guard placement#10ShortArrow wants to merge 7 commits into
ShortArrow wants to merge 7 commits into
Conversation
Measured on an RTX 3060 Ti: fully resident is 73-113 tok/s and any spill is 7-21, with nothing in between. Which side a model lands on is set by how its KV cache grows rather than by its parameter count -- gemma3:4b holds 32k in 4.95 GB while granite3.3:8b reaches 13.89 GB -- and the models that hold a long context are the ones ollama refuses to give tools to. The notes index said every number came from one machine. This one did not, so it says so and the index points at the note instead of promising.
An agent's destructive call is refused whatever was agreed in the conversation; only a choice made through AskUserQuestion is read as authorisation. That was written down as a push rule until a curl -X DELETE against ollama came back with the same refusal, with no git involved. Asked again through the same handshake, the identical command ran and freed 152 GB. The note carries what has to be read back before asking, per family of action, including the row that points the other way: a revert destroys nothing, and listing a risk that is not there is how the next real one gets waved through.
…d is A check placed just before the shell call reads the command line, so it catches an inline -m and nothing else. Measured: a message passed with -F, an --amend --no-edit, a gh --body-file, a string assembled at run time and a push of commits written elsewhere all went through. The five that had actually reached this history arrived by pull, so that check could not have stopped any of them. commit-msg is handed the finished message as a file and pre-push can enumerate the commits, which closes all five. What stays open is --no-verify, and the fact that a message explaining the guard is indistinguishable from a message carrying what it refuses.
…anese The English was written first and carried across. 握手 in Japanese is two people shaking hands; the protocol sense does not exist. Replaced with 手順. 断崖 went the same way -- a cliff is an English figure for a discontinuity, not a Japanese one -- so the heading now says what happens instead of what it resembles. While there, the guard note had eight sentences in a row ending in the same ます form. Two of them moved to 常体 inside the list, where Japanese technical writing puts it anyway. Longest run is now two.
Three notes were fixed on the Japanese side alone. The English carries no equivalent defect: handshake and cliff are ordinary English, and a run of identical sentence endings is a Japanese phenomenon.
An exception names the commit that may stand alone, so it expires by itself when the next commit touches that file. Expired lines then sit there doing nothing, and reading the file cannot tell them from live ones -- three of the six were already dead. The check now prints live, expired, or does not resolve, which also surfaces the ones a history rewrite broke. Three expired entries deleted. Two notes added to the header: what the exception actually covers, which is everything that commit did to that file, and that an expired line is meant to be removed.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
dotfiles | fe83897 | Commit Preview URL Branch Preview URL |
Aug 16 2026, 10:39 PM |
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.
Three notes drafted in English and mirrored in Japanese, plus the parity check now reporting which exceptions are still live.
Rebased onto main; fast-forward.