chore(repo): drop host topology from public config and docs - #148
Merged
Merged
Conversation
added 2 commits
September 16, 2026 10:51
The published contract is the software, not the machine it happens to build on. Four sites named a specific host, its core count, its resident services, or a local home-directory layout. - .kanon-ci.toml: strip the host name, core count, CPU class and resident service names from the concurrency pin's rationale, but keep the part that is a property of the build rather than of the machine — the ~25GB peak a single run holds under at 8 — so a reader still has the bar that tells them raising or dropping the pin is wrong. The pin itself is unchanged. - CLAUDE.md: the preamble deferred to two absolute home paths; it now states the rule (host and environment conventions live outside this repository) without naming either. - .kanon-orchestration-exceptions.toml: the justification keeps its substance — authored directly on main before the worktree convention — minus the host name and the era jargon. - standards/README.md: point at the standards path inside the kanon repository rather than at one checkout's home directory.
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
.kanon-ci.tomlconcurrency rationale: host name, core count, CPU class..kanon-orchestration-exceptions.tomljustification.defers_toauthority inCLAUDE.mdfrontmatter.standards/README.md.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.