Ecosystem Opportunities¶
This is the maintainer-facing short list of actionable ecosystem findings. Keep it concise. Detailed evidence belongs in dated sweep reports and linked draft issues.
Operating Rules¶
- Track opportunities that could change ORCA Framework commands, memory, install, cross-harness behavior, QA, or workflow.
- Track setup opportunities that could simplify or repair GitHub, Linear, MCP, connector, auth, permission, or host-specific install flows.
- Prefer cross-harness opportunities over host-specific features unless the host-specific feature unlocks immediate user value.
- Mark whether each item is
Adopt now,Investigate soon,Watch, orIgnore for now. - Avoid duplicates. If an item already exists in ecosystem-watch, update that entry and link it here.
- Link harness-level compatibility shifts to harness-watch when they affect the matrix or host guidance.
Adopt nowitems must link a draft issue or explain why issue creation was blocked.- repeated session-improvement candidates can be promoted here when the same low-grade friction becomes a framework maintenance priority
- integration-stack drift, better default bundles, and broken setup guidance should also be tracked here
- recommendation-fit changes should only promote a tool when a major use case fit clearly improved
Opportunity Fields¶
Each active opportunity should use this shape:
- Capability:
- Source harness or repo:
- Source evidence:
- Category:
- Adoption shape:
- Cross-harness or host-specific:
- Setup method:
- Affected hosts:
- Current recommendation:
- Proposed recommendation:
- Why it matters:
- Required ORCA Framework change:
- UX impact:
- Status:
- Related issue:
- Next recommended action:
Active Opportunities¶
commands¶
No active opportunities yet.
memory¶
No active opportunities yet.
install¶
No active opportunities yet.
cross-harness¶
No active opportunities yet.
QA¶
No active opportunities yet.
workflow¶
No active opportunities yet.
Recently Closed¶
No closed opportunities yet.