docs(hygiene): state build-host role instead of fleet topology - #506
Merged
Merged
Conversation
This repository is published. The machine it happens to build on, the private
stores it stages content from, and one operator's checkout layout are not part
of its public contract. Replace named hosts, services, stores, and home paths
with the role that is actually true of the software.
- .kanon-ci.toml: drop the host name, core count and co-resident service names
from the concurrency pin's rationale, but keep what is a property of this
build rather than of any machine - unpinned peaks clear 100GB, and 8 holds a
single run under ~25GB - so a reader about to raise the number or delete the
line still has the bar that tells them why that would be wrong. The pin
itself is unchanged.
- .kanon-lint-ignore: record the worktree deviation without naming the hosts,
the dispatch infrastructure, or an operator-local worktree path.
- CLAUDE.md: drop the machine-topology deferral, and cite the standards by
their path inside `forkwright/kanon` rather than inside one home directory.
- docs/reference-store.md: removable drives, not a named host's drives; the
staging area and staging library by role, not by private store name.
CONTRIBUTING.md carries a second copy of the concurrency rationale, but it
already states the role ("the memory budget on the CI host") and names no
machine, so it is left as written and does not dangle.
AGENTS.md is untouched. Its host reference sits inside the `kanon:auto-start`
block and belongs to the generator; the two home-directory standards paths
above that block are the same class as the CLAUDE.md ones and are left for the
AGENTS.md pass.
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
AGENTS.mdandCLAUDE.mdstandards pointers, replaced by repo-qualified references.defers_toauthority in both frontmatter blocks.docs/reference-store.md, replaced by its role noun..kanon-lint-ignore.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.