workbench-capy-git-dialogue-guardrails

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Workbench Capy Git Dialogue Guardrails

Workbench Capy Git对话防护机制

Use this skill when implementing, reviewing, or dogfooding the Capy Git Dialogue Responder, especially for

SYN-31

, GitHub webhook responder work, Capy-authored PR/comment loops, or any task that could let Capy write back to a GitHub, Linear, or Slack surface.

This skill is source-layer only. It does not deploy Capy, enable webhooks, write Linear, post Slack, or mutate live OAuth/runtime state.

在实现、评审或内部测试（dogfooding）Capy Git对话响应器时使用此技能，尤其是针对

SYN-31

、GitHub Webhook响应器工作、Capy自动生成的PR/评论循环，或任何可能让Capy向GitHub、Linear或Slack平台写入内容的任务。

本技能仅作用于源码层。它不会部署Capy、启用Webhook、写入Linear、发布Slack消息，也不会修改实时OAuth/运行时状态。

Read First

必读内容

DECISIONS.md

entry

2026-05-06 - Add Self-Loop Guardrails To The Capy Git Dialogue Responder

```
docs/capy-git-dialogue-responder.md
```

.capy/CAPTAIN.md

.capy/BUILD.md

, and

.capy/REVIEW.md

when checking a repo-local Capy pack

```
autopilots/capy-linear-slack-sync.md
```
only when Linear/Slack sync is in scope

DECISIONS.md

中的条目

2026-05-06 - Add Self-Loop Guardrails To The Capy Git Dialogue Responder

```
docs/capy-git-dialogue-responder.md
```
检查仓库本地Capy包时，需查看
```
.capy/CAPTAIN.md
```
、
```
.capy/BUILD.md
```
和
```
.capy/REVIEW.md
```
仅当涉及Linear/Slack同步时，才查看
```
autopilots/capy-linear-slack-sync.md
```

Required Gate

必备检查关卡

Before any write-capable action, compute this block from source evidence:

text

CAPY_GIT_DIALOGUE_GUARDRAIL
event_author:
actor_classification:
human_request_present:
last_capy_commit_sha:
last_capy_comment_ids:
mutation_allowed:
circuit_breaker_state:
action_taken:
verdict: PASS | FLAG | BLOCK

Use the local dogfood helper for bounded fixture checks:

bash

node scripts/capy-git-dialogue-guardrail.mjs --format json <event-summary.json>
node scripts/test-capy-git-dialogue-guardrail.mjs

在执行任何可写入操作之前，需根据源码证据计算以下内容块：

text

CAPY_GIT_DIALOGUE_GUARDRAIL
event_author:
actor_classification:
human_request_present:
last_capy_commit_sha:
last_capy_comment_ids:
mutation_allowed:
circuit_breaker_state:
action_taken:
verdict: PASS | FLAG | BLOCK

使用本地内部测试助手进行有限的 fixture 检查：

bash

node scripts/capy-git-dialogue-guardrail.mjs --format json <event-summary.json>
node scripts/test-capy-git-dialogue-guardrail.mjs

Mutation Rules

变更规则

Capy-authored comments, review comments, reviews, closeouts, commits, and synchronize events are observation only unless a human explicitly asks Capy to continue in that exact thread or after that exact commit.
The automatic patch budget is one patch attempt per PR per distinct human-authored review-finding batch.
Commit/comment/review churn from Capy itself is
```
FLAG
```
plus operator approval, not another patch loop.
Duplicate closeout for the same repo, PR, head SHA, and verdict tuple is a no-op.
Webhook receipt is not proof of repo state; verify PR, check, review, and git state from primary evidence.

除非人类在确切的线程中或确切的提交之后明确要求Capy继续，否则Capy自动生成的评论、评审评论、评审、收尾操作、提交和同步事件仅作为观察内容，不执行写入。
每个PR针对每一批不同的人类评审发现，自动补丁预算为一次补丁尝试。
Capy自身导致的提交/评论/评审频繁变动需标记为
```
FLAG
```
并获得操作员批准，而非进入另一个补丁循环。
针对同一仓库、PR、头SHA和裁决元组的重复收尾操作视为无操作。
Webhook接收不能作为仓库状态的证明；需从原始证据验证PR、检查、评审和Git状态。

Verdicts

裁决结果

```
PASS
```
: mutation is allowed by a current human request and the patch budget is still available, or the action is read-only observation.
```
FLAG
```
: mutation is refused because the trigger is self-authored, the patch budget is exhausted, or Capy churn requires operator approval.
```
BLOCK
```
: the event summary is malformed or primary source identity cannot be established.

```
PASS
```
：当前有人类请求允许变更，且补丁预算仍可用，或者操作是只读观察。
```
FLAG
```
：由于触发源是Capy自身、补丁预算已耗尽，或Capy频繁变动需要操作员批准，因此拒绝变更。
```
BLOCK
```
：事件摘要格式错误，或无法确认原始来源身份。

Closeout

收尾记录

text

CHANGED:
VERIFIED:
REMAINING:
PRS / LINKS:
VERDICT: PASS | FLAG | BLOCK

Do not claim live rollout. Source-layer

PASS

only means the guardrail source and dogfood fixtures passed.

text

CHANGED:
VERIFIED:
REMAINING:
PRS / LINKS:
VERDICT: PASS | FLAG | BLOCK

请勿声称已完成实时部署。源码层的

PASS

仅表示防护机制源码和内部测试fixture通过检查。