diff --git a/docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md b/docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md index a8f74eb2..ae073783 100644 --- a/docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md +++ b/docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md @@ -169,3 +169,20 @@ Later: 3. ActionTrail can replay a run using the shared action-log structure. 4. Approval checkpoints can be handed off to Auth App without losing run context. 5. Product-specific runtimes can remain different internally while still producing the same contract externally. + +--- + +## 11. Implementation Checklist + +- [ ] finalize entity list and minimum required fields +- [ ] define run vs session vs task boundaries +- [ ] define checkpoint/resume semantics +- [ ] define dispatch payload contract +- [ ] define action-log hook points +- [ ] define ActionTrail replay requirements +- [ ] define first conforming implementation plan for Cowork and FlowMonk + +Commits: + +- `eae3409` drafted the initial stub +- implementation commits: pending diff --git a/docs/ecosystem/ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md b/docs/ecosystem/ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md index 0dfe6b06..2da0840b 100644 --- a/docs/ecosystem/ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md +++ b/docs/ecosystem/ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md @@ -146,3 +146,20 @@ type ApprovalRecord = { 3. Auth App can approve an agent action using one canonical approval payload. 4. ActionTrail can render why an approval was required and what trust state triggered it. 5. Device-risk changes can alter approval behavior without changing product-local policy code. + +--- + +## 10. Implementation Checklist + +- [ ] finalize trust input model +- [ ] finalize risk taxonomy +- [ ] define approval reuse rules +- [ ] define fresh-approval-required action classes +- [ ] define degraded-device behavior +- [ ] define Auth App approval payload +- [ ] define ActionTrail approval rendering requirements + +Commits: + +- `eae3409` drafted the initial stub +- implementation commits: pending diff --git a/docs/ecosystem/ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md b/docs/ecosystem/ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md index e6f7d83c..b82ac7bf 100644 --- a/docs/ecosystem/ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md +++ b/docs/ecosystem/ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md @@ -527,3 +527,20 @@ The ecosystem's biggest unrealized strength is not any single app. It is the com - strong harness and runtime patterns already proven in `claw-code` and `claw-cowork` The main gap is that these strengths still live in adjacent repos instead of one intentional platform model. The next step should be standardizing the shared contracts that let each repo keep its own product identity while participating in one ByteLyst operating system. + +--- + +## 14. Execution Tracking + +Implementation progress should not be tracked ad hoc in this strategy doc. + +Use: + +- [`ECOSYSTEM_IMPLEMENTATION_TRACKER.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md) for portfolio-level status +- the implementation checklist section inside each canonical spec for feature-level status + +Strategy doc commits: + +- `d28e9d0` +- `341cde7` +- `3e572b6` diff --git a/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md b/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md new file mode 100644 index 00000000..3f230dc0 --- /dev/null +++ b/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md @@ -0,0 +1,117 @@ +# Ecosystem Implementation Tracker + +> **Status:** Active tracker +> **Owner:** `learning_ai_common_plat` +> **Purpose:** Single place to track cross-product ecosystem implementation progress, owners, status, and commit links. + +--- + +## 1. Tracking Rules + +Use this document as the execution ledger for ecosystem work. + +Rules: + +1. Every implementation item should have exactly one status owner. +2. Every completed item should include at least one commit reference. +3. Use checkboxes for executable tasks and update them in the same PR/commit series that implements the work. +4. If a task spans multiple repos, list all affected repos in the row. +5. If a task is blocked, state the blocker explicitly instead of leaving it ambiguous. + +Status values: + +- `not-started` +- `in-progress` +- `blocked` +- `done` + +Commit link format: + +- short hash only when local +- GitHub commit URL once pushed + +Example: + +- `eae3409` +- `https://github.com/saravanakumardb1/learning_ai_common_plat/commit/eae3409` + +--- + +## 2. Core Spec Status + +| Spec | Status | Owner Repo | Notes | Commits | +| ---------------------------------------------- | ----------- | ------------------------- | ------------------------------------------------------ | ------------------------------- | +| `ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md` | done | `learning_ai_common_plat` | strategy baseline created and strengthened | `d28e9d0`, `341cde7`, `3e572b6` | +| `ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md` | in-progress | `learning_ai_common_plat` | draft stub exists, schema decisions still open | `eae3409` | +| `ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md` | in-progress | `learning_ai_common_plat` | draft stub exists, runtime normalization still open | `eae3409` | +| `ECOSYSTEM_APPROVALS_AND_TRUST_MODEL.md` | in-progress | `learning_ai_common_plat` | draft stub exists, policy matrix still needs hardening | `eae3409` | +| `ECOSYSTEM_EVENT_TAXONOMY.md` | not-started | `learning_ai_common_plat` | next required spec | — | +| `ECOSYSTEM_MARKETPLACE_UNIFICATION.md` | not-started | `learning_ai_common_plat` | depends on artifact/runtime conventions | — | +| `ECOSYSTEM_PERSONAL_TIMELINE_PRD.md` | not-started | `learning_ai_common_plat` | depends on artifacts + events | — | + +--- + +## 3. Phase 1 Checklist + +### Foundation + +- [x] Create canonical ecosystem docs home in `docs/ecosystem/` + Commits: + - `5f4134e` +- [x] Draft cross-pollination strategy + Commits: + - `d28e9d0` + - `341cde7` + - `3e572b6` +- [x] Draft artifact schema stub + Commits: + - `eae3409` +- [x] Draft runtime contract stub + Commits: + - `eae3409` +- [x] Draft approvals and trust model stub + Commits: + - `eae3409` +- [ ] Draft event taxonomy + Commits: + - pending + +### First implementation tracks + +- [ ] LysnrAI transcript -> NoteLett note -> MindLyst memory + Repos: + - `learning_voice_ai_agent` + - `learning_ai_notes` + - `learning_multimodal_memory_agents` + - `learning_ai_common_plat` + Commits: + - pending +- [ ] FlowMonk plan -> ChronoMind routine -> EffoRise habit + Repos: + - `learning_ai_flowmonk` + - `learning_ai_clock` + - `learning_ai_efforise` + - `learning_ai_common_plat` + Commits: + - pending +- [ ] Cowork -> ActionTrail -> NoteLett -> MindLyst audited artifact flow + Repos: + - `oss/learning_ai_claw-cowork` + - `learning_ai_trails` + - `learning_ai_notes` + - `learning_multimodal_memory_agents` + - `learning_ai_common_plat` + Commits: + - pending + +--- + +## 4. Current Gaps Before Broad Implementation + +- [ ] event taxonomy spec is missing +- [ ] no shared adoption docs exist yet under `docs/ecosystem/adoption/` +- [ ] no repo ownership matrix exists yet +- [ ] no verification matrix exists yet +- [ ] no contract-test strategy is documented yet + +These should be resolved before claiming the ecosystem docs are fully implementation-ready. diff --git a/docs/ecosystem/ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md b/docs/ecosystem/ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md index 3a6ff8a0..79bd6553 100644 --- a/docs/ecosystem/ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md +++ b/docs/ecosystem/ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md @@ -172,3 +172,20 @@ Phase 1 adopters: 3. A MindLyst memory can record provenance to source transcript/note artifacts. 4. A Cowork output can be stored as an `agent-output` artifact and later opened in NoteLett. 5. ActionTrail can render provenance from the envelope alone. + +--- + +## 9. Implementation Checklist + +- [ ] finalize canonical envelope field names and required/optional splits +- [ ] define first 5 artifact types in stable form +- [ ] define link relation vocabulary +- [ ] define provenance minimum payload +- [ ] define storage/binary attachment rules +- [ ] define migration strategy for first adopters +- [ ] add examples for LysnrAI, NoteLett, MindLyst, Cowork, and ActionTrail + +Commits: + +- `eae3409` drafted the initial stub +- implementation commits: pending diff --git a/docs/ecosystem/README.md b/docs/ecosystem/README.md index b1677cd0..98dae477 100644 --- a/docs/ecosystem/README.md +++ b/docs/ecosystem/README.md @@ -9,10 +9,12 @@ Use this folder for: - cross-repo ownership and adoption plans - rollout sequencing - verification matrices +- implementation tracking and commit-linked progress Recommended structure: - [`ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_CROSS_POLLINATION_OPPORTUNITIES.md) — strategy, opportunities, gaps, priorities +- [`ECOSYSTEM_IMPLEMENTATION_TRACKER.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md) — canonical execution tracker with checkboxes and commit references - [`ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_SHARED_ARTIFACT_SCHEMA.md) — canonical artifact model - `ECOSYSTEM_EVENT_TAXONOMY.md` — shared events and action-log contract - [`ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md) — shared session, todo, resume, dispatch semantics @@ -26,3 +28,14 @@ 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`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md) as the portfolio-level progress ledger