boardx / boardx/boardx-dev-template

[F10] R1:CoordBrain 影子模式(只读观察 + 零误判周期)

Open
#794 0 comments 0 reactions 0 assignees View on GitHub
area:coord sprint:p30-02
Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## 交付契约(user_visible_behavior)

CoordBrain DO(每项目一个,与 RepoHub 同 worker)上线但只读:Cron tick 对全部机械 SOP 规则(全绿可合并判定 / ready-for-dev 派工判定 / PR 超时催办判定 / stale 租约回收判定 / andon 冻结判定)产出「它将做的决策」写入 coord.shadow.* 事件流,绝不执行;devportal 可见影子决策列表供人核对;跑满一个完整工作周期(G5 已拍板:24 小时或一个 C-cycle,取长者)后,影子决策与人类实际决策的对照记录归档,误判数为零。

## Story

[requirements/feature-list-draft.md](https://github.com/boardx/boardx-dev-template/blob/main/phases/phase-p30-devportal-platform/requirements/feature-list-draft.md) — 章节 `R10`

## 验证(完成的唯一标准:每条命令退出码 0)

- [ ] `pnpm --filter @repo/coord-brain test`
- [ ] `bash phases/phase-p30-devportal-platform/scripts/verify-shadow-cycle.sh`
- [ ] `curl -sf https://coord-gateway.boardx.workers.dev/api/coord/brain/shadow -H "Authorization: Bearer $COORD_API_TOKEN" | jq -e '.decisions | type == "array"'`

证据落盘:`phases/phase-p30-devportal-platform/sprints/sprint-02/evidence/F10.verify.log`

## 实现指引(notes)

C 线闸门:R2-R5 全部以本 feature 的零误判台账为前置(保序 R1→R2→R3→R4→R5 严格串行,前级未 passing 不得开工后级;每级自带一键降回人工且降级方向永远 fail-open 到人)。周期参数已拍板(G5):影子事件流时间跨度 ≥24h 且覆盖 ≥1 个完整 C-cycle(取长者),断言写实在 verify-shadow-cycle.sh。@repo/coord-brain 为新包(五类机械规则纯函数单测,含边界样例——andon 活跃时合并判定必须为冻结)。人类核对流程写进 evidence/R1-shadow-audit.md,不允许「自评零误判」。实现载体优先评估 Cloudflare Agents SDK。

## 设计参照

(无 UI 或沿用现有界面)

## 前置依赖

- 无

## 元数据

| phase | sprint | 能力平面 | 优先级 | wave | area |
|---|---|---|---|---|---|
| p30 | 02 | CAP-DATA | P2 | - | coord |

## 开工流程(agent 必读)

> 本 issue 是仓库的**只读投影**;权威是 [`phases/phase-p30-devportal-platform/feature_list.json`](https://github.com/boardx/boardx-dev-template/blob/main/phases/phase-p30-devportal-platform/feature_list.json)。若两者不一致,以仓库为准。

1. 环境:`./init.sh`(验证失败先修基础状态,别在坏地基上开工)。
2. 认领:`pnpm harness claim --phase p30 --feature F10 --owner <你的-agent-id>`(同一 owner 同时最多一个 in_progress)。
3. 读上下文:[`requirements/`](https://github.com/boardx/boardx-dev-template/blob/main/phases/phase-p30-devportal-platform/requirements)(原始需求)、[`ui-signoff.md`](https://github.com/boardx/boardx-dev-template/blob/main/phases/phase-p30-devportal-platform/ui-signoff.md)(已确认 UI 的组件落点与 data-testid)、[`sprints/sprint-02/session-handoff.md`](https://github.com/boardx/boardx-dev-template/blob/main/phases/phase-p30-devportal-platform/sprints/sprint-02/session-handoff.md)(上一轮交接)。
4. 实现:只做本 feature 的最小实现,不顺手重构无关区域;不碰 `active-features.json`(脚本派生只读)。
5. 验证:逐条跑上方 verification,输出留到 `phases/phase-p30-devportal-platform/sprints/sprint-02/evidence/F10.verify.log`;然后 `pnpm harness verify --sprint p30/02 --feature F10` 门控转 passing——**不允许手改 status**。
6. 提交:分支 `worker/-p30-f10-`,PR 关联本 issue(`Closes #<本 issue 号>`),收尾更新 progress.md 与 session-handoff.md。

完整硬约束见 [`AGENTS.md`](https://github.com/boardx/boardx-dev-template/blob/main/AGENTS.md);多 agent 协作规则见 [`.harness/instructions/multi-agent-coordination.md`](https://github.com/boardx/boardx-dev-template/blob/main/.harness/instructions/multi-agent-coordination.md)。

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with requirements/feature-list-draft.md at R10, then read the @repo/coord-brain package context and phases/phase-p30-devportal-platform/scripts/verify-shadow-cycle.sh. Run ./init.sh before implementing; done means all three listed verification commands exit 0, the shadow endpoint returns a decisions array, and the audit evidence is saved to phases/phase-p30-devportal-platform/sprints/sprint-02/evidence/F10.verify.log.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.