Lịch · Multi-Agent Ownership Protocol

⚠️ Trạng thái hiện tại

Trang này là static landing tạm. Phase 2.1 Next.js scaffold (calendar + state viewer + auth) đang chờ Owner sign-off design doc + 7 open questions.

Repo hiện chứa: protocol framework + schema + skill templates, KHÔNG có app code chính thức.

Phase roadmap

✅
Phase 1 (2026-05-24) — SHIP. STATE.md schema v2 + ACTIVE.md registry + 3 skill ecosystem (/status + /status-update + /status-report) + memory naming protocol v3 + private repo + Calendar monthly retrospective.
🔨
Phase 2.x (planning) — Web UI Next.js 14 + Tailwind + NextAuth. 3 layer: docs public / sanitized counts auth / full state encrypted. ETA 15-22h dev × 5 session.
📋
Phase 3+ (future) — Archive rotation closed sessions >30 ngày · conflict resolution UI · ownership transfer audit log · scale ≥4 agent simultaneously.

Tham khảo

📦

GitHub repo

Private repo · framework + schema + skill templates

📖

README

Architecture overview + cross-reference

🎨

Web UI Design v1

Next.js 14 + Tailwind + NextAuth · 3 layer design

🏷️

Naming convention v3

agent_id = claude-<display-name>

📐

STATE.md schema v2

Eisenhower 4Q + owned_by field spec

🗂️

Operations tier

~/Operations/ integration (local-only)

Vì sao protocol này tồn tại

Khi Owner mở >1 Claude Code session simultaneously, mỗi session là agent độc lập có thể đụng Edit cùng STATE.md → race condition.

Protocol v3 solve qua 4 lớp:

Naming convention — agent_id = claude-<display-name>
STATE.md schema v2 — task có field owned_by:
ACTIVE.md registry — track active sessions cross-ref STATE
Skill update — /status-update HARD BLOCK cross-agent touch · /status render ownership badge + drift check