learning_ai_common_plat/docs/ecosystem/README.md

Ecosystem Docs

Canonical home for ByteLyst ecosystem-wide architecture and rollout documentation.

Use this folder for:

• ecosystem strategy
• shared contracts and schemas
• cross-repo ownership and adoption plans
• rollout sequencing
• verification matrices
• implementation tracking and commit-linked progress

Recommended structure:

• ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md — strategy, opportunities, gaps, priorities
• ECOSYSTEM_IMPLEMENTATION_TRACKER.md — canonical execution tracker with checkboxes and commit references
• ECOSYSTEM_AGENT_OPERATING_MODEL.md — delegation, review, merge, and tracker-update process for Saravana, Codex, Windsurf, and Cursor
• ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md — canonical artifact model
• ECOSYSTEM_EVENT_TAXONOMY.md — shared events and action-log contract
• ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md — shared session, todo, resume, dispatch semantics
• ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md — approvals, trust levels, device posture
• ECOSYSTEM_OWNERSHIP_MATRIX.md — temporary four-party ownership model
• ECOSYSTEM_VERIFICATION_MATRIX.md — what “done” means for cross-product features
• ECOSYSTEM_CONTRACT_TEST_STRATEGY.md — how to prevent contract drift across repos
• ECOSYSTEM_MARKETPLACE_UNIFICATION.md — shared marketplace model
• ECOSYSTEM_PERSONAL_TIMELINE_PRD.md — unified user activity stream
• PHASE1_TRANSCRIPT_NOTE_MEMORY_EXECUTION_PLAN.md — execution-ready plan for the first golden flow
• PHASE2_PLAN_ROUTINE_HABIT_EXECUTION_PLAN.md — execution-ready plan for the second golden flow
• PHASE3_COWORK_ACTIONTRAIL_NOTE_MEMORY_EXECUTION_PLAN.md — execution-ready plan for the audited artifact flow
• delegation/ — ready-to-send task packs and launcher lines for Saravana, Codex, Windsurf, and Cursor
• adoption/ — per-product adoption notes

Ownership model:

• learning_ai_common_plat holds the canonical ecosystem docs
• product repos hold repo-local adoption and implementation details
• claw-code-oss and claw-cowork remain reference sources for runtime and execution patterns

Tracking convention:

• every major ecosystem doc should include:
  • status
  • owner
  • open decisions
  • acceptance criteria
  • implementation checklist
  • commit-link section
• use ECOSYSTEM_IMPLEMENTATION_TRACKER.md as the portfolio-level progress ledger

Current implementation package:

• packages/events holds the first concrete ecosystem contract code and now covers the Phase 1, Phase 2, and Phase 3 artifact/event seams.