docs(repo): state host role instead of machine identity - #82
Merged
Merged
Conversation
This repository is published; the machine it happens to build on is not part of its public contract. Three CLAUDE.md sites named a private host-operations repo and its GPU by model number, and the CI pipeline header justified its concurrency pin with a specific core count and co-resident workload. Each site now states the role that is actually true of the software: machine topology and GPU mode selection are owned by the host-operations environment, and research mode is mutually exclusive with inference mode on a single-GPU host. The concurrency pin keeps its reason, minus the core count: cargo's default parallelism is the host's total core count, so an unpinned run sizes itself to the whole machine rather than to its share of it, and contends with whatever else is running there. A dedicated machine does not retire the pin, because concurrent runs and co-resident services still share those cores. No generated block was touched; the kanon:auto markers in CLAUDE.md and README.md are untouched.
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
CLAUDE.mdfrontmatter and body..kanon-ci.tomlconcurrency rationale. The co-tenancy reason for the pin is preserved, because the original justified the pin by contention with other work rather than by exhausting the machine.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.