Skip to content

docs(claude): state CI and standards roles instead of local topology - #213

Merged
forkwright merged 1 commit into
mainfrom
fix/public-repo-hygiene
Sep 16, 2026
Merged

forkwright merged 1 commit into
mainfrom
fix/public-repo-hygiene

Conversation

@forkwright

Copy link
Copy Markdown
Owner

Removes private fleet topology from surfaces that are public in this repository.

What this closes

  • Operator home paths in the CLAUDE.md standards pointer.
  • A home-path example in docs/AGENTIC.md, replaced by a placeholder.
  • A host name in a locked-decision note about the dual-CI migration window.

At HEAD, a repo-wide search for the removed classes returns nothing: operator home paths, build-host names, CPU/GPU model numbers, internal .lan hostnames, 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.toml is identical to main'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.

The dual-CI note named a specific machine as the thing that validates the
forge deploy path; the role that actually validates it is the forge runner,
which is also how ci/kanon-ci.toml.tmpl already words the same rationale.

The standards pointer named a local checkout path under a home directory.
Name the repository and its in-repo path instead, matching the generated
kanon context block's own "Standards source" convention.

The scaffold example in docs/AGENTIC.md pinned the destination to one
operator's home-directory layout, which the destination argument does not
require: bin/typikon-init takes any path and creates it. Use the
placeholder the script's own usage string defines, so the example reads
the same on any checkout.
@forkwright
forkwright merged commit 37c5807 into main Sep 16, 2026
8 checks passed
@forkwright
forkwright deleted the fix/public-repo-hygiene branch September 16, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant