-
Notifications
You must be signed in to change notification settings - Fork 1
Declare weaver-spec v0.1.0 compatibility + run conformance in CI #91
Copy link
Copy link
Open
Labels
area:governancePolicies and validation rulesPolicies and validation rulescomplexity:averageModerate effort, some design neededModerate effort, some design neededenhancementNew feature or requestNew feature or requestmilestone:E0priority:highMust address first within the milestoneMust address first within the milestonesize:MMedium effort (1-3 days)Medium effort (1-3 days)type:featureNew feature or capabilityNew feature or capability
Description
Metadata
Metadata
Assignees
Labels
area:governancePolicies and validation rulesPolicies and validation rulescomplexity:averageModerate effort, some design neededModerate effort, some design neededenhancementNew feature or requestNew feature or requestmilestone:E0priority:highMust address first within the milestoneMust address first within the milestonesize:MMedium effort (1-3 days)Medium effort (1-3 days)type:featureNew feature or capabilityNew feature or capability
Projects
Status
Todo
Why
ChainWeaver has the kernel-backed executor issue (#89) and "Flow as Capability" doc (#90), but no formal declaration of spec compatibility and no CI gate to prevent future drift. This is the equivalent of agent-kernel#58.
Without this, the weaver-spec compatibility matrix cannot be filled in for ChainWeaver, and there's no automated check that ChainWeaver continues to honor Invariant I-07 (delegates execution to the kernel).
Acceptance Criteria
CapabilityTokenrequests andFrameconsumption align with the JSON Schemas incontracts/json/Dependencies
Context
Part of Milestone E0 — Connect + Align Boundaries.