Skip to content

Re-Sync Cross-Repo Handoffs Block + Congruence Fixes From the 2026-07-03 Fleet Audit #100

Description

@basecradle-ai

Trigger

The 2026-07-03 fleet congruence audit (a cross-repo review of the constitution and all six CLAUDE.mds, founder-approved) landed two capital PRs: basecradle#397 (constitution amendments) and basecradle#398 (capital CLAUDE.md — including an edit to the verbatim-shared ## Cross-Repo Handoffs block). This handoff is your repo's re-sync plus the audit's repo-local congruence fixes, batched because they touch the same file.

Task 1 — Re-sync the shared block (mechanical, byte-verified)

Replace your CLAUDE.md's entire ## Cross-Repo Handoffs section (from its ## header to the next ## header) with the canonical from capital main:

gh api repos/basecradle/basecradle/contents/CLAUDE.md -H "Accept: application/vnd.github.raw"

What changed in the block, for your awareness: (1) the gate lists now match Earned Autonomy — release/publish actuation and cross-repo dispatch are the capital's gates, not the founder's (credentials, scope/new-repo decisions, and founder-only ambiguity remain his); (2) the dispatcher sentence now states the router is live for on-server agents; (3) the CLOSER: line protocol is now fleet law in Receiving work step 4; (4) GitHub-native auto-merge is anchored in the Repo-sovereignty bullet. Byte-verify the copied block against the canonical (diff must be empty) — the byte-match is the verification, so this task is exempt from /code-review. The NOC drift-guard's grace window is running: land the re-sync promptly.

Task 2 — Guarded local branch deletion (audit C1)

Your Conventions/Workflow line mandates blind git branch -D <branch> after a squash-merge. Adopt the capital's guarded form: try git branch -d first; when it refuses (expected for squash-merges), verify content equivalence — the branch's changes must be fully contained in main (e.g. git diff <branch> main -- <files the branch touched> is empty, or git diff main..<branch> is 0 lines when main has not moved past the branch) — and only then git branch -D. Never force-delete without the check: a non-empty diff of the branch's own work means unshipped changes.

Task 3 — Qualify the Closes #N convention line (audit C2)

Your Conventions workflow bullet says PRs reference issues with the closing keyword, unqualified — while your own Releasing section (and the shared block) forbid it for release and handoff issues. Adopt the router's inline qualifier on that line: the keyword is for ordinary in-repo issues only, NOT for handoff/gated issues — see the shared block.

Task 4 — Refresh the stale helper-home clause

Fleet Bot Identity says the gh-app-token helper's "permanent home is decided with capital #277" — #277 (the router) has shipped. Replace with the current fact: on the laptop the helper lives in the founder's Claude workspace; on the fleet server each agent's own provisioned credentials serve the role.

Task 5 (optional, captain's call)

Your local "the pypi publish gate is not a human gate" carve-out predates the anchor fix — the shared block and constitution now carry it. Keep or trim for redundancy as you see fit.

Definition of Done

  • PR merged under your own bot identity on green CI (self-review the authored, non-re-sync edits first per your conventions).
  • The ## Cross-Repo Handoffs block byte-matches capital main (state the verification in your completion comment).
  • Completion comment on this issue: what changed, PR link, byte-diff result.

CLOSER: you (the receiving captain) — verify the DoD and close this issue by hand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    handoffRouter wakes this repo's agent on the issue

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions