Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Comment: | A run from R alone may share under any name; y is the protection
Intent: the maintainer decided that a share needs no name rule: "if it is in uv, it should be replaceable ... anyone with y can write it—that is our one and only protection from it being overwritten in real life. don't produce machinery that can't work." (ocx-console post 7085f98c83, relayed in ollama forum post 98286416a9). So each architecture's BQ2 seed can be one file, replaced at each build. Expression: Bounds.wider no longer refuses a share whose name lacks $$run$$; its other rules stand, ends_with_parent among them. HISTORY.md decision 133 amends decisions 107 and 132; protocol v2's refusal 1 drops the clause. The rule itself is written into Parsimony in README.md, with no guard spec, since none can check it (ollama forum post b4cb02763c: the maintainer repeated "don't make machinery that can't work" of a spec for it). Demonstrates: spec/ocx/decisions_spec.cr: a run from R alone sharing under builds/$$run$$/x, ocx2-release.tar, seed/x86_64.qcow2 or $$process_user$$run$$ starts. crystal run ci.cr: 713 examples, coverage 100.0%; its three failures, two the known rcvfrom lock (ticket 00817df826) and one a compiler's stdin read, pass rerun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | connector-oauth |
| Files: | files | file ages | folders |
| SHA3-256: |
afd3df339fd0310acddd975373de0e01 |
| User & Date: | x86-1-session 2026-11-08 18:21:47.889 |
|
2026-11-09
| ||
| 05:45 |
Register asks again for an approved login, printing the approve link
Intent: let a login an admin approved be asked again for other letters with one more press, as the maintainer expected register to do (ocx-console post 13dfe73616). Collect refused a code other than the approved one with a text register took as a failure, so no link was printed (bootstrap-qcow2 post 774683323c). Expression: collect now refuses another code as "approved for another code, and for this one it is not approved yet", so register prints the approve link for its new code. Approve already sets a login it made with exactly the letters asked and a new password. docs/invite.md says to ask for the whole set of letters and that the old password stops working. docs/interfaces.md says the same, and the done row leaves docs/backlog.md. The admin's press stays the only protection, as it is for a first ask. Demonstrates: spec/ocx/logins_spec.cr, "registers from the asker's own machine": from a new file, the link asks goi24; once pressed, the login holds exactly goi24 with a new password, and the old one no longer signs in. crystal run ci.cr is green: 713 examples, 0 failures, coverage 100.0%. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: 05ad811298 user: x86-1-session tags: connector-oauth | |
|
2026-11-08
| ||
| 18:21 |
A run from R alone may share under any name; y is the protection
Intent: the maintainer decided that a share needs no name rule: "if it is in uv, it should be replaceable ... anyone with y can write it—that is our one and only protection from it being overwritten in real life. don't produce machinery that can't work." (ocx-console post 7085f98c83, relayed in ollama forum post 98286416a9). So each architecture's BQ2 seed can be one file, replaced at each build. Expression: Bounds.wider no longer refuses a share whose name lacks $$run$$; its other rules stand, ends_with_parent among them. HISTORY.md decision 133 amends decisions 107 and 132; protocol v2's refusal 1 drops the clause. The rule itself is written into Parsimony in README.md, with no guard spec, since none can check it (ollama forum post b4cb02763c: the maintainer repeated "don't make machinery that can't work" of a spec for it). Demonstrates: spec/ocx/decisions_spec.cr: a run from R alone sharing under builds/$$run$$/x, ocx2-release.tar, seed/x86_64.qcow2 or $$process_user$$run$$ starts. crystal run ci.cr: 713 examples, coverage 100.0%; its three failures, two the known rcvfrom lock (ticket 00817df826) and one a compiler's stdin read, pass rerun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: afd3df339f user: x86-1-session tags: connector-oauth | |
| 08:33 |
unversioned_list lists what the server holds, fetching no file
Intent: listing a clone's unversioned files ran fossil uv sync first, so every clone that listed them pulled every file, each ~100 MB BQ2 seed among them (ollama forum post 5bdae9f13d, the maintainer's ask relayed by the One Place session, from ocx-console a85cc28929). Expression: ListUnversioned reads the clone's remote and lists it without a sync: over https or http, Fossil's /juvlist page, unsigned, any user or password in the remote left out, as the receipt tool is asked, read within Exchange's time and at most LISTED bytes; a file remote by reading that repository; a clone with no remote, its own files. A remote over neither, a server not reached, or a page that is not the list is refused, saying why. unversioned_get and unversioned_put still sync, as they did. docs/remote-agents.md says the list fetches no file. Demonstrates: spec/ocx/checkout_tools_spec.cr: a file added on a served repository is listed by name and size while the clone holds no unversioned file; an ssh remote and a dead server are each refused, naming why; the file-remote edit test lists as before. spec/ocx/dry_run_spec.cr: the list's dry run runs to its end with no remote. crystal run ci.cr: 713 examples, coverage 100.0%, its one error the known rcvfrom lock (ticket 00817df826), whose spec passes rerun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: 1724d0f5e2 user: x86-1-session tags: connector-oauth | |