Skip to content

chore(custodian): enable CAP1 capability-ref enforcement#303

Merged
ProtocolWarden merged 1 commit into
mainfrom
feat/cap1-enforce
Jun 15, 2026
Merged

chore(custodian): enable CAP1 capability-ref enforcement#303
ProtocolWarden merged 1 commit into
mainfrom
feat/cap1-enforce

Conversation

@ProtocolWarden

Copy link
Copy Markdown
Owner

Sets audit.capabilities.enforce: true so Custodian's CAP1 detector verifies the capability this repo owns — board_unblock — points at invocation.ref code that actually resolves here (operations_center.entrypoints.maintenance.board_unblock). Anti-rot for the capability registry.

Uses the existing cross_repo.platform_manifest_repo pointer to locate the registry + manifest. Verified locally: with CAP1 active (custodian@main + PlatformManifest sibling), OperationsCenter's audit is clean — the ref resolves. Activates fleet-wide once the local custodian install is refreshed to @main; single-repo CI installs custodian@main fresh where CAP1 skips (no sibling checkout).

🤖 Generated with Claude Code

Set audit.capabilities.enforce: true so CAP1 verifies the capability this repo
owns (board_unblock) points at invocation.ref code that resolves here
(operations_center.entrypoints.maintenance.board_unblock). Uses the existing
cross_repo pointer to locate the registry + manifest. Activates when the local
custodian install is refreshed to @main; CI installs custodian@main fresh.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ProtocolWarden ProtocolWarden merged commit e874aaf into main Jun 15, 2026
18 checks passed
@ProtocolWarden ProtocolWarden deleted the feat/cap1-enforce branch June 15, 2026 19:29
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