Decide the fate of the Sentry and Elder in the chatroom (CHATROOM_SPEC.md open question 4). Sentry's triage can fold into dispatch (Epic C, Jev classification) or survive as a role; the Elder's merge is exactly what conspiracy mode needs for synthesis (C5), so "fold it away" is no longer neutral. Record the decision and whether the legacy murder pipeline constant is grandfathered, renamed, or retired.
Acceptance criteria — falsifiable checks
CHATROOM_SPEC.md question 4 is answered with a [decided YYYY-MM-DD] line naming what happens to Sentry and to Elder. grep -qE '(Sentry|Elder).*\[decided' CHATROOM_SPEC.md — fails now, passes after.
If the decision retires the legacy constant: a follow-up note is added to JEV_STRATEGIES.md or CHATROOM_SPEC.md marking the pipeline murder constant deprecated for the chatroom path. If grandfathered: the decision text says so explicitly. grep -qiE 'sentry|elder' CHATROOM_SPEC.md | grep -c . stays > 0 and the decided line exists.
Terminology constraint (docs/SCOPE.md): the word "murder" is never introduced into chatroom copy; if the legacy JSON constant is renamed, that is a pipeline change and its own task, not part of this decision record.
Epic: #1. Depends on: none (Smokey's decision)
## Goal
Decide the fate of the Sentry and Elder in the chatroom (`CHATROOM_SPEC.md` open question 4). Sentry's triage can fold into dispatch (Epic C, Jev classification) or survive as a role; the Elder's merge is exactly what `conspiracy` mode needs for synthesis (C5), so "fold it away" is no longer neutral. Record the decision and whether the legacy `murder` pipeline constant is grandfathered, renamed, or retired.
## Acceptance criteria — falsifiable checks
1. `CHATROOM_SPEC.md` question 4 is answered with a `[decided YYYY-MM-DD]` line naming what happens to Sentry and to Elder. `grep -qE '(Sentry|Elder).*\[decided' CHATROOM_SPEC.md` — fails now, passes after.
2. If the decision retires the legacy constant: a follow-up note is added to `JEV_STRATEGIES.md` or `CHATROOM_SPEC.md` marking the pipeline `murder` constant deprecated for the chatroom path. If grandfathered: the decision text says so explicitly. `grep -qiE 'sentry|elder' CHATROOM_SPEC.md | grep -c .` stays > 0 and the decided line exists.
## Test command
`grep -qE 'Sentry.*\[decided|Elder.*\[decided' CHATROOM_SPEC.md && echo PASS`
## Blockers / unknowns
Terminology constraint (docs/SCOPE.md): the word "murder" is never introduced into chatroom copy; if the legacy JSON constant is renamed, that is a pipeline change and its own task, not part of this decision record.
Decided 2026-10-27 by Smokey: the Sentry survives as a new role — the nest watchdog. It watches for a crow acting outside its contract and on a suspected breach quarantines, then escalates (suspend claiming/delivering, post a flag, open ask_owner for reinstate or retire; fail safe). Aberrance is judged from Jev verdicts and guardrail hits above the high band, never the Sentry's own opinion; every flag logs its score. Triage folds into dispatch (Epic C). Spec updated: CHATROOM_SPEC.md section 6 (role), section 4 (flag kind), section 12, question 4 closed.
Decided 2026-10-27 by Smokey: the Sentry survives as a **new role** — the nest watchdog. It watches for a crow acting outside its contract and on a suspected breach **quarantines, then escalates** (suspend claiming/delivering, post a `flag`, open `ask_owner` for reinstate or retire; fail safe). Aberrance is judged from Jev verdicts and guardrail hits above the high band, never the Sentry's own opinion; every flag logs its score. Triage folds into dispatch (Epic C). Spec updated: CHATROOM_SPEC.md section 6 (role), section 4 (`flag` kind), section 12, question 4 closed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Epic: #1. Depends on: none (Smokey's decision)
Goal
Decide the fate of the Sentry and Elder in the chatroom (
CHATROOM_SPEC.mdopen question 4). Sentry's triage can fold into dispatch (Epic C, Jev classification) or survive as a role; the Elder's merge is exactly whatconspiracymode needs for synthesis (C5), so "fold it away" is no longer neutral. Record the decision and whether the legacymurderpipeline constant is grandfathered, renamed, or retired.Acceptance criteria — falsifiable checks
CHATROOM_SPEC.mdquestion 4 is answered with a[decided YYYY-MM-DD]line naming what happens to Sentry and to Elder.grep -qE '(Sentry|Elder).*\[decided' CHATROOM_SPEC.md— fails now, passes after.JEV_STRATEGIES.mdorCHATROOM_SPEC.mdmarking the pipelinemurderconstant deprecated for the chatroom path. If grandfathered: the decision text says so explicitly.grep -qiE 'sentry|elder' CHATROOM_SPEC.md | grep -c .stays > 0 and the decided line exists.Test command
grep -qE 'Sentry.*\[decided|Elder.*\[decided' CHATROOM_SPEC.md && echo PASSBlockers / unknowns
Terminology constraint (docs/SCOPE.md): the word "murder" is never introduced into chatroom copy; if the legacy JSON constant is renamed, that is a pipeline change and its own task, not part of this decision record.
Decided 2026-10-27 by Smokey: the Sentry survives as a new role — the nest watchdog. It watches for a crow acting outside its contract and on a suspected breach quarantines, then escalates (suspend claiming/delivering, post a
flag, openask_ownerfor reinstate or retire; fail safe). Aberrance is judged from Jev verdicts and guardrail hits above the high band, never the Sentry's own opinion; every flag logs its score. Triage folds into dispatch (Epic C). Spec updated: CHATROOM_SPEC.md section 6 (role), section 4 (flagkind), section 12, question 4 closed.Decision already recorded: Sentry survives as nest watchdog, quarantine-then-escalate (CHATROOM_SPEC.md section 6, flag kind section 4, question 4 closed). Closing.