Skip to content

burn-down(docs): relocate 4 design artifacts to bdchatham-designs (Design 05 Phase-C)#205

Merged
bdchatham merged 1 commit into
mainfrom
relocate/seictl-burn-down
Jun 13, 2026
Merged

burn-down(docs): relocate 4 design artifacts to bdchatham-designs (Design 05 Phase-C)#205
bdchatham merged 1 commit into
mainfrom
relocate/seictl-burn-down

Conversation

@bdchatham

Copy link
Copy Markdown
Contributor

Phase-C fan-out, seictl batch (Design 05 / PLT-497) — the burn-down half (paired add: bdchatham-designs#20).

Removes 4 design artifacts now relocated to the designs repo, moves the runbook to .agent/runbooks/, and repoints inbound cross-links:

doc disposition
docs/design/cluster-cli.md bdchatham-designs designs/cluster-cli/
docs/design/in-pod-governance-signing.md designs/governance-signing/ (+ 2 keyring.md cross-links repointed)
docs/design/validation-substrate.md designs/validation-substrate/ (corpus exemplar)
docs/bugbash/cluster.md designs/bugbash-cluster/
docs/runbooks/seictl-smoke.md .agent/runbooks/ (stays in-repo)
docs/design/nodedeployment-cli.md stays — Sonar-gated (real ref in nodedeployment/cmd.go:5)

Audit (canonical origin/main 62b06dd, gating): in-pod-governance-signing had 2 documentation cross-links in sidecar/docs/keyring.md (repointed here); the other three were clean of any inbound refs.

docs/ is not fully evacuated — nodedeployment-cli.md remains until Sonar (PLT-493). This was prepared in an isolated git worktree off origin/main, leaving the active feature branch untouched.

⚠️ Merge order: merge bdchatham-designs#20 first, then this. · Linear: PLT-497

🤖 Generated with Claude Code

…sign 05 Phase-C, PLT-497)

Design artifacts move to the DRI's designs repo (Design 05). Removes 4 relocated
docs from docs/; moves the seictl-smoke runbook to .agent/runbooks/; repoints 2
documentation cross-links in sidecar/docs/keyring.md to the new location.

Relocated → bdchatham-designs (paired add: PR #20):
  docs/design/cluster-cli.md, docs/design/in-pod-governance-signing.md,
  docs/design/validation-substrate.md, docs/bugbash/cluster.md

Runbook → .agent/runbooks/seictl-smoke.md (stays in-repo; agent-discoverable).

NOT removed (Sonar-gated, Design 05 §5): docs/design/nodedeployment-cli.md —
real code reference in nodedeployment/cmd.go:5 ("See docs/design/nodedeployment-cli.md
for output shape and exit-code"). Stays in docs/ until Sonar (PLT-493) or the
§3.1 code-change election. docs/ is therefore NOT fully evacuated this round.

Inbound audit (gating, canonical origin/main 62b06dd):
  in-pod-governance-signing → 2 doc cross-links (sidecar/docs/keyring.md) — repointed here.
  cluster-cli / validation-substrate / bugbash-cluster → 0 refs (clean).
Rename map → all four land under bdchatham-designs designs/<arc>/.

Paired with bdchatham-designs#20 (merge that first). Linear: PLT-497.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cursor

cursor Bot commented Jun 13, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only relocation with no runtime or CLI behavior changes; link rot is mitigated by merging the designs repo PR first.

Overview
Design 05 / PLT-497 burn-down: four large design documents are removed from seictl now that canonical copies live in bdchatham-designs (cluster-cli, in-pod-governance-signing, validation-substrate, and docs/bugbash/cluster.md).

sidecar/docs/keyring.md is updated so both references to the governance design point at the external repo instead of the deleted in-tree path.

The harbor seictl smoke runbook is relocated to .agent/runbooks/seictl-smoke.md (still in this repo). docs/design/nodedeployment-cli.md is intentionally left in place (Sonar / PLT-493).

Merge bdchatham-designs#20 before this PR so outbound links resolve.

Reviewed by Cursor Bugbot for commit 79a68bf. Bugbot is set up for automated code reviews on this repo. Configure here.

@bdchatham bdchatham merged commit 6eb1243 into main Jun 13, 2026
3 checks passed
@bdchatham bdchatham deleted the relocate/seictl-burn-down branch June 13, 2026 18:58
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