Define CurryComb capability-envelope adapter boundary #50
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
Reference
Ting/CurryComb#50
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
Prepare the CurryComb side of the versioned capability envelope that HydraMem consumes directly.
Design
Use canonical TOML as the wire artifact. Create an inert, dedicated adapter boundary rather than modifying
currycomb-projection,currycomb-intake, or a credentialed effector. It emits provenance, spans, coverage, budgets, and review-authority separation as specified by the central contract.Tasks
Specification Delta
Given a bounded CurryComb source result, when it is exported to HydraMem, then the consumer receives a versioned envelope with enough provenance to validate and no admission authority.
Evidence
Fixture tests demonstrate valid transfer, incompatible-version refusal, and provenance preservation.