Session: CurryComb capability transfer and review carrier #51

Open
opened 2026-09-07 06:45:05 +00:00 by larandar · 0 comments
Owner

Proposal

Create the CurryComb review-carrier and capability-transfer boundary required by the viable HydraMem MCP.

Design

This Session is adopted by implementation Epic #42. It owns one CurryComb review surface and depends on the capability-envelope leaf. It is blocked from implementation dispatch until the central contract Session publishes its immutable revision.

Completion evidence

The dedicated adapter emits a valid envelope that HydraMem can consume through the shared fixture, while retaining source/review/knowledge authority separation.

## Proposal Create the CurryComb review-carrier and capability-transfer boundary required by the viable HydraMem MCP. ## Design This Session is adopted by implementation Epic #42. It owns one CurryComb review surface and depends on the capability-envelope leaf. It is blocked from implementation dispatch until the central contract Session publishes its immutable revision. ## Completion evidence The dedicated adapter emits a valid envelope that HydraMem can consume through the shared fixture, while retaining source/review/knowledge authority separation.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Ting/CurryComb#51
No description provided.