You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
One instruction release: core in managed settings, index in the hook, procedures as skills, runs pinned to a tag #81
rules/org-rules.md, fetched from main by seat runs and the Lead, which may also get it a second time through managed settings.
hq's prompts/agents.md.
Every rules change today needs a console paste. The reviewed design (2026-11-11) is one release of the rules and two ways to deliver it:
a small core lives in managed claudeMd and changes rarely;
the operative index is in the plugin's SessionStart hook;
procedures are skills;
seat runs and the Lead assemble their system prompt from a pinned release (tag plus content digest), not from main.
Acceptance criteria
rules/ holds a core file of at most 1.5 KB and an index that, with the session context, stays under the hook's 10,000-character cap. A check fails a PR that exceeds either.
Procedures (tracking, filing, merging, signing, version holds, fonts) are plugin skills, and the index names each one with when it applies.
A release is a tag on agent-plugins with a content digest. hq's assign.yml and agents/lead/run.sh assemble the rules from a pinned tag and log the tag and digest. A missing or mismatched release is a wrapper-level failure (no review posted, no Lead hash saved), not a run without rules.
managed/settings.json's claudeMd is the core only. A check fails a PR that changes the core without an owner issue for the paste.
One console paste by Raghav moves the live settings to the core. After it, a rules change needs no paste.
Files likely touched
rules/
plugins/setkernel/hooks/session-context.sh
plugins/setkernel/skills/*
managed/settings.json
the checks
in setkernel/hq: .github/workflows/assign.yml, agents/lead/run.sh
Three findings from the scenario review of 2026-11-11 (checked against the code) belong here:
A run never checks which plugin revision it loaded. plugin.json has no version, so every commit on main is a release. Nothing records or compares the revision a seat run or a person's session used. The pinned tag and digest in this issue's criteria fixes this for runs. People's sessions should print the revision in the hook context.
A bad commit on main reaches every interactive session with no staged rollout and no automatic way back. Both guards are onFailure: block, so a broken guard blocks every Bash call. Main's one required review is the only gate. Pinned runs limit the blast radius to people's sessions.
Nothing compares the live console settings with managed/settings.json. bin/generate compares only local files, and the README says to read the OTEL_LOG_MANAGED_SETTINGS log by hand. A drift check is worth adding beside the core-size check.
Activity
realRaghavGupta commentedon Nov 11, 2026
Three findings from the scenario review of 2026-11-11 (checked against the code) belong here:
plugin.jsonhas no version, so every commit on main is a release. Nothing records or compares the revision a seat run or a person's session used. The pinned tag and digest in this issue's criteria fixes this for runs. People's sessions should print the revision in the hook context.onFailure: block, so a broken guard blocks every Bash call. Main's one required review is the only gate. Pinned runs limit the blast radius to people's sessions.managed/settings.json.bin/generatecompares only local files, and the README says to read theOTEL_LOG_MANAGED_SETTINGSlog by hand. A drift check is worth adding beside the core-size check.— Claude Lead