§196: nife carries TLS, and milestone 442 builds the provider - #997
Merged
Merged
Conversation
calef
marked this pull request as draft
September 19, 2026 22:04
Collaborator
Author
|
Lane: maintainer, written by an agent; calef's account is the author GitHub shows. Held as a draft by the maintainer, not because anything here is wrong. Adding milestone 442 means the roadmap index must be regenerated, and regenerating it also refreshes main's stale 177 row, which makes |
Collaborator
Author
|
merge-drain: STALE DRAFT. #997 has not committed in over 75 minutes (§196: nife carries TLS, and milestone 442 builds the provide). If its lane is finished: gh pr ready 997 |
calef, 2026-09-19 (22:01 UTC): carrying a TLS stack is table stakes, and on being shown that no provider builds for our bare targets today, take rustls and build the provider. rustls itself is seven crates and builds; every provider under it fails at getrandom for want of a backend nife can supply, or in SIMD paths on soft-float x86_64 that were never measured against our own target specs. Milestone 442 carries that work. Two clauses keep it honest: roots are held per source as a capability rather than in a system store, which is the circularity a trust store cannot solve; and under §195 a digest decides what may run, so TLS buys confidentiality and knowing which host answered, not authenticity, and rung 3a does not wait for it. The proposal moves into design/decisions as the record; 198's transport and hosting rows carry the ruling. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STu3VeDYnEHem3iKCbzBF2
calef
marked this pull request as ready for review
September 19, 2026 23:42
calef
force-pushed
the
maintainer/196-tls-and-its-provider
branch
from
September 19, 2026 23:42
5d5f497 to
43d1f98
Compare
calef
enabled auto-merge
September 19, 2026 23:42
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
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.
Lane: maintainer/196-tls-and-its-provider, written by an agent; calef's account is the author GitHub shows. Built on #996 (§195), whose commit it carries until that lands.
Records calef's ruling of 2026-09-19 (22:01 UTC): "Carrying a TLS stack seems like table stakes these days", and, shown that no provider builds for our targets today, take
rustlsand build the provider.rustlsfor the protocol: 7 crates, all Rust, and that part builds.getrandom(no bare-metal backend, whichentropy_backendexists to answer and nife can supply) or in SIMD paths on soft-float x86_64 that the probe never measured against our own target specs. 442's first task is that re-measurement.Gates:
script/lint0,script/citations0. The generated roadmap index is deliberately not regenerated here: doing so surfaces main's stale 177 row and trips the fatal-risks check, which #988 already fixes.🤖 Generated with Claude Code
https://claude.ai/code/session_01STu3VeDYnEHem3iKCbzBF2