learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_VERIFICATION_MATRIX.md

Ecosystem Verification Matrix

Status: Draft Owner: learning_ai_common_plat Purpose: Define how ecosystem work is verified before it is considered complete.

---

1. Principle

A cross-product feature is not done when one repo compiles.

It is done when:

1. the shared contract is updated
2. the producing repo emits the expected behavior
3. the consuming repo handles it correctly
4. the tracker reflects the implementing commit(s)

---

2. Verification Layers

Layer 1: Doc verification

• contract doc updated
• checklist updated
• tracker updated
• open decisions called out if unresolved

Layer 2: Contract verification

• schema/type examples compile or validate
• sample payloads are present
• event names and field names are stable

Layer 3: Producer verification

• source repo emits or stores the expected contract shape
• unit/integration tests added where appropriate

Layer 4: Consumer verification

• downstream repo accepts and uses the contract correctly
• no translation hacks or undocumented fallback behavior

Layer 5: End-to-end flow verification

• the actual user journey works across repo boundaries

---

3. Phase-1 Golden Flow Checks

Transcript -> Note -> Memory

• transcript artifact created
• note artifact created or linked
• memory artifact created or proposed
• canonical events emitted
• provenance preserved across all steps
• tracker updated with commit links

Plan -> Routine -> Habit

• plan artifact exists
• routine generated from plan
• habit generated from plan
• canonical events emitted
• user-visible flow validated
• tracker updated with commit links

Cowork -> Trail -> Notes -> Memory

• agent run logged
• output artifact generated
• ActionTrail can replay or inspect the run
• downstream note or memory artifacts linked
• approval trail preserved where required
• tracker updated with commit links

---

4. Required Completion Evidence

For every major implementation item, attach:

1. commit hash(es)
2. affected repos
3. verification commands or tests
4. residual risks
5. tracker update

---

5. Implementation Checklist

• finalize phase-1 golden flow checks
• define repo-level verification owners
• define minimum evidence for “done”
• add links from tracker rows to verification evidence

Commits:

• 41fa2cd drafted the initial version