Session: CurryComb capability transfer and review carrier #51
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#42 Build: implementation Slices 2→7
Ting/CurryComb
#50 Define CurryComb capability-envelope adapter boundary
Ting/CurryComb
Reference
Ting/CurryComb#51
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.