Echo capability gap ledger

[flyingrobots]

Echo capability gap ledger

Backlog card: docs/method/backlog/cool-ideas/CORE_echo-capability-gap-ledger.md

This issue mirrors the repo-native METHOD backlog card. Execution truth remains in the card until automated issue/backlog sync exists.

Echo capability gap ledger

Idea

Maintain a small ledger of Graft-discovered Echo capability needs, with evidence
from Graft-side integration slices.

Why

Echo should remain generic and dumb unless Graft proves a real missing substrate
capability. A ledger keeps that boundary honest.

Desired Outcome

Graft records concrete Echo requirements only when local fake or descriptor
work proves the need.

Acceptance Criteria

• Each gap has evidence from a Graft test, design packet, or failed integration
  attempt.
• Each gap states whether Echo lacks a generic substrate capability or Graft
  merely needs an adapter.
• Closed gaps link to the Echo PR, Graft workaround, or decision not to pursue.

[coderabbitai]

🔗 Related PRs

#65 - Add structural-history Echo package descriptor [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!