docs(hygiene): state build-host role instead of machine identity - #139
Merged
Merged
Conversation
added 2 commits
September 16, 2026 10:51
The published repo should not name the machines it happens to build or deploy next to. Replace the host-specific justifications with the invariant each one was protecting: - .kanon-ci.toml: drop the named build host from the --jobs 8 rationale and keep the invariant it was protecting -- runs are not guaranteed to have the executor to themselves, so the pin bounds the combined footprint of whatever runs overlap, not one run's own -- and say under what condition raising or removing it is safe. - deploy/epistole.service: describe the banned MemoryMax= in terms of cgroup co-tenancy with build jobs rather than named host classes. - .github/workflows/ci.yml: cite the empirical kanon-lint gap as a local gate run rather than a named build host.
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.
Removes private fleet topology from surfaces that are public in this repository.
What this closes
.github/workflows/ci.ymlcomment, replaced by the distinction that actually mattered: a gate run off the hosted runner..kanon-ci.tomlpipeline rationale. The co-tenancy reason for the--jobs 8pin is preserved.At HEAD, a repo-wide search for the removed classes returns nothing: operator home paths, build-host names, CPU/GPU model numbers, internal
.lanhostnames, private host-operations repo references, and co-resident service names.What this provably cannot close
This is a forward-only commit. Every removed string remains reachable in this repository's history, and nothing here rewrites or removes it. Anyone with read access can recover all of it from prior commits.
It also does not touch commit author metadata, a separate class that content-level changes do not reach at all.
Both are deliberately left to the forge's history-cut capability rather than hand-rolled here, so one owner performs the operation once across the fleet.
Verification
Prose and comments only — no executable code changed. Verified by config equivalence rather than a build: the parsed
.kanon-ci.tomlis identical tomain's, so CI behaviour is unchanged by construction. That is a stronger claim for a comment change than a green test run, and costs no build slot.