Skip to content

docs: add RFC-030 implementation plan#433

Draft
vansin wants to merge 29 commits into
mainfrom
docs/rfc030-implementation-plan
Draft

docs: add RFC-030 implementation plan#433
vansin wants to merge 29 commits into
mainfrom
docs/rfc030-implementation-plan

Conversation

@vansin

@vansin vansin commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add the RFC-030 engineering master plan under docs/plans/
  • record frozen product/security decisions and the Wave 1A contract digest
  • track Wave 0–3 ownership, evidence, blockers, corrective work, and release locks
  • record the 2026-07-12 independent checkpoint FAIL without discarding green unit evidence
  • require every checkpoint to update both this plan and [RFC-030] Codex TUI 人类与 Agent 共用会话桥接 — 实施跟踪 #428

Current checkpoint

Wave 1A UDS/lifecycle and Wave 1B L1 did not pass independent real-path review. The plan now records the concrete blockers, freezes the unapproved 090ce12 L3 candidate, and keeps Wave 2, safety sign-off, merge, deployment, production, and latest locked.

Why

RFC-030 had a chronological tracking issue but no dedicated implementation plan. The existing docs/release/v2.3.0/plan.md belongs to a separate GA line and is not repurposed.

Validation

Tracking: #428

This draft does not authorize merge, deployment, production enablement, package publication, or a latest switch.

…dence — committed, awaiting review

## Author
Agent: 通信SDK马
…y, security final gates locked

## Author
Agent: 通信SDK马
…fter 1A Segment B/C

## Author
Agent: 通信SDK马
Update the Wave 1A UDS/lifecycle row, per-segment checkpoint table,
and evidence log with the three post-freeze commits:

  Segment A `98676f1`  uds-server.ts       28 pass / 0 fail / 72 expect
  Segment B `04560c0`  human-owner.ts      16 pass / 0 fail / 43 expect
  Segment C `00d4ea8`  lifecycle.ts        19 pass / 0 fail / 59 expect

Combined gateway suite at C: 232 pass / 0 fail / 729 expect
(command: `bun test agent-node/src/runtime/codex-policy-gateway/`).

State semantics preserved: coordinator independent recheck and the
§8 security review remain hard-locked. Test-green is not merge-
green — merge/deploy/latest all still frozen per §1 and §9.

Author: comm eng
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.

2 participants