data: aevatar 加 6 个攻坚节点 + 拆 M14 (Responses API v1) 为 5 支柱#8
Merged
eanzhao merged 2 commits intoMay 18, 2026
Merged
Conversation
新增 (基于 aevatarAI/aevatar repo 当前 issues / discussions / ADRs): - Channel-Multi-Adapter (scoped) — RFC #254 + ADR 0008-0013 - Studio-Team-First (bridged) — ADR 0017 + 17 设计文档 - Responses-API-Gateway (seed) — 里程碑 ChronoAIProject#14 (issues #611-624) - Ornn-Skill-Platform (obligation) — #367 / #598 / PR #576 - SessionStream-Abstraction (obligation) — RFC #560 - EventSourcing-Hardening (seed) — #381 / #533 / #591-#594 状态推进: - CSharp-Scripting: scoped → bridged (PR #515 + /daily 生产) - NyxID-Integration: public → bridged (PR #561 / #570 / #571) A0 / A1 聚合节点串上新节点 deps。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
之前用一个 Aevatar-Responses-API-Gateway 概括 14 个 issue, 体现不出当前焦点。 按 RFC #609 的章节拆分: - Aevatar-M14-Milestone (聚合): GitHub milestone ChronoAIProject#14, 收所有支柱 - Aevatar-ChatRuntime-Harness: blocker, #608 + #596 (eanzhao 已 assigned) - Aevatar-Responses-Ingress: HTTP 层, #611 / #612 / #614 / #615 - Aevatar-Responses-Auth-Scope: 安全层 §8, #613 / #621 - Aevatar-Session-Continuation: response.id 状态机 §13, #617-#620 - Aevatar-Tool-Classification: agent 能力层 §5, #622-#624 A1 milestone deps 中 Aevatar-Responses-API-Gateway → Aevatar-M14-Milestone。 全部 focus=true, owner=eanzhao, 当前 closure=obligation。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 tasks
eanzhao
added a commit
to eanzhao/region-map
that referenced
this pull request
May 18, 2026
…e + 前端门面) ChronoAIProject#8 之前 PR 了 additive 战略节点; 本 PR 补上链路本身的 6 个节点, 让 upstream 图能看到 inbound -> router -> team 端到端演示这条线索: 后端 / 控制层: - Aevatar-Router-Agent (eanzhao, seed): 统一 Lark + NyxID Responses 入口 到 Router, 让两条 ingress GAgent 退化为薄壳。 - Aevatar-Inbound-Team-Demo (eanzhao, seed): 端到端演示汇聚节点。 deps = 6 条 lane (Router-Agent / Studio-Team-First / EventSourcing-Hardening / Chain-Test-Coverage / Event-Intake-Lab / Console-Web-Member-Flows). - Aevatar-Chain-Test-Coverage (YueZh127, seed): 主链跨层回归覆盖。 挂 #666 / #667 / #668 / #669。 前端门面 (补上 PR ChronoAIProject#5 / PR ChronoAIProject#7 close 掉没合的内容): - Aevatar-Event-Intake-API (eanzhao, seed): 前端 Lab 调用的后端合约。 deps 保留原 PR ChronoAIProject#5 的完整战略依赖 + 加 Router-Agent。 - Aevatar-Event-Intake-Lab (abigail, seed): Agent Studio 前端 demo。 - Aevatar-Console-Web-Member-Flows (potter-sun, obligation): Studio 成员 态前端流程; 跟踪 #654 / #655。deps 加 Studio-Team-First。 纯加节点, 不删 upstream 任何现有节点。aevatar 25 -> 31。
potter-sun
pushed a commit
to potter-sun/region-map
that referenced
this pull request
May 25, 2026
…e migration ## New NyxID regions (11) Epic-level (8) — backed by new GitHub milestones ChronoAIProject#8-ChronoAIProject#15 on ChronoAIProject/NyxID: - NyxID-CLI-Wizard (M1, public, focus, owner ctkm-aelf, 5 hardening bugs) - NyxID-UX-Redesign (M1, obligation, focus, owner dannick-aelf, 4 issues) - NyxID-Channel-Phase4 (M2, obligation, owner kaiweijw, 2 issues) - NyxID-Device-Code-Grant (M2, seed, focus, owner kaiweijw, 12 issues) - NyxID-Skill-Install-CLI (M2, obligation, owner chronoai-shining, 1) - NyxID-Internal-Datasources (M1+, obligation, focus, owner kaiweijw, 5) - NyxID-Anonymous-Endpoints (M2, scoped, owner chronoai-shining, 1) - NyxID-Org-Managed-Nodes (M1+, seed, focus, owner kaiweijw, 6) Marketing (3) — backed by GitHub milestones ChronoAIProject#16-ChronoAIProject#18, mirroring Ornn's Marketing-L0/L1/L2 pattern: - NyxID-Marketing-Prelaunch (4 issues: #183 #525 #619 #657 #766 lark-cli positioning, demo brainstorm, README v2, ArmorerLabs comparison, CDN) - NyxID-Marketing-Show-HN (4 issues: #791 submission copy, #792 demo video, #793 day-of triage, #794 outreach list — all filed fresh) - NyxID-Marketing-Postlaunch (1 issue: #795 funnel analytics dashboard) ## M1-Milestone rewired around the real user-growth gate NyxID is MVP-ready. Engineering is not the gate; distribution is. M1 desc explicitly says so, and deps now reflect the marketing attack: M1-Milestone deps: + NyxID-M0-Milestone (✅ mature) + NyxID-Marketing-Show-HN (⛔ seed — real gate) + NyxID-Marketing-Prelaunch (🟠 obligation — real gate) + NyxID-Quickstart-NPM (✅ bridged, Sprint 5 gate #558 cleared) + NyxID-Landing-Page (🟢 public, dormant) Removed from M1 deps (parallel improvement, not gating): - NyxID-CLI-Wizard, NyxID-UX-Redesign, NyxID-Internal-Datasources - NyxID-Quickstart-Docker (moved to M1+, self-hosted ≠ hosted-user-growth) - NyxID-Invite-Code-System (foundation, already shipped) ## Drift fixes + existing-region updates - NyxID-OAuth-flow 1→5 + refreshed bug refs (#683 #694 #695 #735) - NyxID-Credential-Injection 1→5 + cross-ref to Org-Managed-Nodes - NyxID-MCP-Wrap 1→0 - NyxID-Hosted-Instance desc refreshed (W19 quickstart cluster closed) - NyxID-Invite-Code-System expanded → "Invite Codes + Org Model" - NyxID-NAT-Traversal + NyxID-SSH-Tunneling — dropped over-broad gh_query - NyxID-Reverse-Proxy 2→4 - NyxID-Quickstart-NPM 1→0 (Sprint 5 Show HN gate cleared 2026-05-18) - NyxID-UX-Redesign 3→4 (+#772) - Cross-product: Aevatar-NyxID-Integration 9→16, Ornn-NyxID-Integration 2→4 ## Milestone schema migration All new NyxID epic regions adopt shining's milestone_ref schema (from PR ChronoAIProject#6) in addition to gh_query, mirroring the dual-field pattern Ornn uses. Issue data flows through tools/sync_milestone_issues.py into ornn-issues.json. Auto-sync workflow (.github/workflows/sync-milestone-issues.yml) will keep ornn-issues.json fresh hourly going forward. ## GitHub side-effects (already applied) - 11 milestones created on ChronoAIProject/NyxID - 5 new issues filed (#791-#795 for Show HN prep) - ~37 issues assigned to epic milestones - 10 Device-Code-Grant sub-issues annotated with `Blocked by #NNN` lines for phase-DAG visualization - 4 W20 sprint issues moved to epic milestones (#352 #695 #706 #711 #713) — W20 sprint loses those tags, gain epic-level grouping ## Validators OK regions.json valid (82 regions). 12/12 unit tests pass. Strict drift audit shows zero drift on NyxID + Ornn; remaining drift is on Aevatar regions (eanzhao's territory, accrued naturally — not modified here).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
摘要
承接并取代 #2（#2 基于 2026-05-12 的 upstream 状态，已过时；本 PR 从最新 upstream/main rebase）。
2 个 commit，纯加节点 + 状态精化，无删除。
Commit 1:
data: 补充 aevatar 6 个新攻坚节点 + 更新现有节点状态新增 aevatar 节点:
Aevatar-ChatRuntime-Harness(obligation) — #608 + #596，M14 blockerAevatar-Channel-Multi-Adapter(scoped) — RFC #254 + ADR 0008-0013，53 文件 ChannelRuntime 收口Aevatar-EventSourcing-Hardening(seed) — 架构线 CQRS / projection 加固Aevatar-Ornn-Skill-Platform(obligation) — Day One → Ornn skill 迁移Aevatar-SessionStream-Abstraction(obligation) — RFC #560Aevatar-Studio-Team-First(bridged, focus) — ADR 0017 Team 一等公民状态精化:
Aevatar-NyxID-Integrationpublic → bridgedAevatar-CSharp-Scriptingscoped → bridgedAevatar-Workflow-YAML维持 bridged，补 promoted_atCommit 2:
data: 把 M14 (Responses API v1) 拆成 milestone + 5 支柱之前用一个
Aevatar-Responses-API-Gateway概括 14 个 issue，体现不出当前焦点。按 RFC #609 章节拆:Aevatar-M14-Milestone(聚合): GitHub milestone viz: split Downstream into 'Is blocking' / 'Already shipped on top' #14，收所有支柱Aevatar-ChatRuntime-Harness: blocker，#608 + #596Aevatar-Responses-Ingress: HTTP 层，#611 / #612 / #614 / #615Aevatar-Responses-Auth-Scope: 安全层 §8，#613 / #621Aevatar-Session-Continuation: response.id 状态机 §13，#617-#620Aevatar-Tool-Classification: agent 能力层 §5，#622-#624全部 focus=true，owner=eanzhao，当前 closure=obligation。
验证
```
python3 tools/validate_regions.py # OK: regions.json valid (67 regions)
python3 tools/test_validate.py # 12/12 OK
```
不在本 PR 范围
fork 的 main 还有一系列后续的 slim-view 改造（删 19 个节点，收紧到本周工作视图），那是个人工作视图，不进 upstream。