Add Canon and Relay to the declared capability catalog - #13
Merged
Merged
Conversation
HarperZ9
marked this pull request as ready for review
September 16, 2026 09:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plexus's built-in capability catalog omitted Canon and Relay, leaving shared context and execution transport outside its declared map. This adds their current source-backed manifests and documents Canon as the context owner, Relay as the execution/connectivity owner, mneme as the recall component, and Plexus as the capability-routing component. Index remains the scanner and evidence gatherer.
The catalog includes existing Canon continuity and read-only MCP surfaces and Relay run, ledger, certificate and transport surfaces. It does not advertise in-progress Canon capture features or invent an adapter between incompatible ports. Canon-to-Relay and Relay-to-Canon routes therefore remain disconnected until a real adapter exists.
Validation: 98 tests passed using the worktree source path, built-in manifest validation passed, and negative route checks preserve the missing-adapter result. These are declared capability contracts, not live probes, enterprise acceptance or completed package consolidation.