book: Std pages, network and security #594

Open
opened 2026-10-29 14:25:45 +00:00 by orion · 3 comments
Collaborator

Slice of the epic #582. Starts after #585 (the concept, the vertical slice and the book gates) is merged.

Scope

Write one hand-written page in book/std/ per module: network, ip, dns, http, web, tls, digest, cipher, signature. Each replaces docs/standard-library/<module>.md.

Acceptance criteria

  • Every page has the kind page and is written as book/CONCEPT.md, "How a page is written", says: the first paragraph says what the page covers, headings name ideas, prose first, no history, no internal references, no Related/Next sections
  • Every trb run and trb error block has its output block with the real output; torb docs check book, torb docs index --check book and torb docs site book --check pass in CI
  • The signature features of book/CONCEPT.md that the area touches are shown, not just named
  • The old pages of docs/ this slice replaces are deleted in the same PR, unless a skill is still built from them (then they stay, unpublished, and the PR says which)
  • Each page opens with what the module is for and an example of the most common task, then covers the handful of tasks people use it for, each with an example and its output; it does not list every declaration
  • Each page names its module in the front matter (package: std/<module>), so the site links the generated API reference of torb doc std
  • Examples that need a network run against a server the example starts itself on localhost, or are trb check blocks with a sentence saying what they print; nothing reaches the internet in CI

Children

Slice of the epic #582. Starts after #585 (the concept, the vertical slice and the book gates) is merged. ## Scope Write one hand-written page in `book/std/` per module: `network`, `ip`, `dns`, `http`, `web`, `tls`, `digest`, `cipher`, `signature`. Each replaces `docs/standard-library/<module>.md`. ## Acceptance criteria - [ ] Every page has the kind `page` and is written as `book/CONCEPT.md`, "How a page is written", says: the first paragraph says what the page covers, headings name ideas, prose first, no history, no internal references, no Related/Next sections - [ ] Every `trb run` and `trb error` block has its `output` block with the real output; `torb docs check book`, `torb docs index --check book` and `torb docs site book --check` pass in CI - [ ] The signature features of `book/CONCEPT.md` that the area touches are shown, not just named - [ ] The old pages of `docs/` this slice replaces are deleted in the same PR, unless a skill is still built from them (then they stay, unpublished, and the PR says which) - [ ] Each page opens with what the module is for and an example of the most common task, then covers the handful of tasks people use it for, each with an example and its output; it does not list every declaration - [ ] Each page names its module in the front matter (`package: std/<module>`), so the site links the generated API reference of `torb doc std` - [ ] Examples that need a network run against a server the example starts itself on localhost, or are `trb check` blocks with a sentence saying what they print; nothing reaches the internet in CI ## Children - [ ] #664 (network, ip) - [ ] #665 (dns, web) - [ ] #666 (http) - [ ] #667 (tls) - [ ] #668 (digest, cipher) - [ ] #669 (signature)
Author
Collaborator

[loop:torbscript] intake: in scope (book std pages, slice of epic #582; dependency #585 is merged), no duplicate, no design-record collision, no seed impact. Next: refine (nine module pages, about 110 KB of old material, are too much for one PR).

[loop:torbscript] intake: in scope (book std pages, slice of epic #582; dependency #585 is merged), no duplicate, no design-record collision, no seed impact. Next: refine (nine module pages, about 110 KB of old material, are too much for one PR).
Author
Collaborator

[loop:torbscript] release refine: split into #664 (network, ip), #665 (dns, web), #666 (http), #667 (tls), #668 (digest, cipher), #669 (signature), each with the criteria of this issue and its own Replaces in docs/ list. All carry loop, none is ready (made ready one after the other, CI is congested).

[loop:torbscript] next: waiting (children #664 to #669)

[loop:torbscript] wait until 2026-10-30T09:00Z: children are filed, not ready; they are made ready as PR slots free up.

[loop:torbscript] release refine: split into #664 (network, ip), #665 (dns, web), #666 (http), #667 (tls), #668 (digest, cipher), #669 (signature), each with the criteria of this issue and its own `Replaces in docs/` list. All carry `loop`, none is `ready` (made ready one after the other, CI is congested). [loop:torbscript] next: waiting (children #664 to #669) [loop:torbscript] wait until 2026-10-30T09:00Z: children are filed, not ready; they are made ready as PR slots free up.
Author
Collaborator

[loop:torbscript] wait until 2026-10-30T12:00Z: children #664 to #669 are not ready yet; the worker slots are full, they become ready as slots free up.
next: waiting (children #664 to #669) until 2026-10-30T12:00Z

[loop:torbscript] wait until 2026-10-30T12:00Z: children #664 to #669 are not ready yet; the worker slots are full, they become ready as slots free up. next: waiting (children #664 to #669) until 2026-10-30T12:00Z
Sign in to join this conversation.
No labels
loop
ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
torbscript/language#594
No description provided.