NEXT_TASKS: settle the vendored-pin architecture in §3, file the enforcer gap (#278) - #279
Merged
Merged
Conversation
…rcer gap (#278) Three additions to §3, all re-verified against the four repos and the claw issue tracker on 2026-07-30 before being written down. **Records the settled architecture, because the alternative was tried and reverted.** claw PR #21 moved the id-label canonical source into culturebotai-claw on 2026-07-22 and was reverted by claw PR #22 on 2026-07-25 as off-model for claw-as-mirror. The settled design (claw #19, restated in #22) is that CultureMech is the hub and claw/shared/idlabel is a passive mirror, with both directions covered — spokes against hub via CultureMech's audit_vendored_fleet.sh, and mirror against hub via claw's matches-hub job, which claw PR #24 put on a nightly schedule (closing claw #23; until then it fired only on claw-side changes and so could never notice the hub moving). CommunityMech never carried the reverted scheme — CANON_REPO here is CultureBotAI/CultureMech and .vendored_canon_ref is 6be694f3, matching MIM and TraitMech — so this paragraph guards against re-proposing it rather than correcting anything. **Closes out the check_vendored_sync.sh drift** TraitMech's backlog had flagged against CommunityMech specifically: the three spokes now carry byte-identical copies (sha256 f05b5ad6…) against the same pin, converged by TraitMech #182 alongside CommunityMech #247 and MIM #157. **Records the gap that surfaced while checking it, filed as #278.** Neither guard covers check_vendored_sync.sh or .vendored_canon_ref themselves. The script doing the checking exists only in the three spokes and never in the hub, so there is no canonical copy to diff it against — a one-copy edit to the checker would go unnoticed by exactly the mechanism designed to catch one-copy edits. Verified: all three spokes at f05b5ad6…, CultureMech has no such file, and audit_vendored_fleet.sh correspondingly lives only in the hub. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Backlog maintenance only — follows #275, which merged before this content was written. Every claim below was re-derived against the four repos and the claw tracker before being recorded.
Records the settled architecture, because the alternative was tried and reverted
A stale version of this has been circulating in sibling backlogs, so it is worth pinning down. claw PR #21 moved the id-label canonical source into
culturebotai-clawon 2026-07-22 and was reverted by claw PR #22 on 2026-07-25 as off-model for claw-as-mirror. The settled design (claw #19, restated in #22) is that CultureMech is the hub andclaw/shared/idlabel/is a passive mirror of it, with both directions covered:scripts/audit_vendored_fleet.sh(nightlyvendored-fleet-audit.yml)matches-hubjob, which claw PR Add SPRUCE Peatland Warming Microbial Community #24 put on a nightly schedule (closing claw Add Rice-Duckweed Bacillus SynCom (division-of-labor biocontrol) #23) — until then it fired only on claw-side changes and so could never notice the hub movingSo: do not repoint
CANON_REPOor bump.vendored_canon_refto a claw commit. Any note that this is "blocked on claw being made public", or that claw Actions fail on exhausted runner minutes, is stale.CommunityMech never carried the reverted scheme — verified today,
CANON_REPOhere isCultureBotAI/CultureMechand.vendored_canon_refis6be694f3, matching MIM and TraitMech. The paragraph guards against re-proposing it rather than correcting anything.Closes out the drift TraitMech flagged
TraitMech's backlog recorded
check_vendored_sync.shas having drifted specifically in CommunityMech. It has since converged: all three spokes carry byte-identical copies (sha256f05b5ad6…) against the same pin, closed by TraitMech #182 alongside CommunityMech #247 and MIM #157. Nothing to do.The gap that surfaced while checking it — filed as #278
Neither guard covers
check_vendored_sync.shor.vendored_canon_refthemselves:check_vendored_sync.shf05b5ad681a5…f05b5ad681a5…f05b5ad681a5…The script doing the checking exists only in the three spokes and never in the hub, so there is no canonical copy to diff it against. The three are identical today; nothing keeps them that way, and a one-copy edit to the checker would go unnoticed by exactly the mechanism designed to catch one-copy edits.
audit_vendored_fleet.shcorrespondingly lives only in the hub. Same class of gap as the ungated enummeaning:groundings in §0 and the palette↔enum gap closed by #268.Verification
Each claim was checked rather than carried over: the five claw references (#19, #21, #22, #23, #24) all exist with the stated states and merge dates; the sha256 comparison and the hub's missing copy were computed across all four working trees;
CANON_REPOand.vendored_canon_refwere read from this repo's script.🤖 Generated with Claude Code