Refactor signals documentation as formal RFC-style specification#866
Merged
Conversation
Simplify page titles and transform signals specification from verbose documentation into concise, normative RFC-style format. Fix schema alignment issues and add testable JSON validation. - Simplify page titles (remove "Protocol" prefix for cleaner navigation) - Update last-modified date to January 25, 2026 - Add RFC 2119 normative language reference - Fix activate_signal requirements to use `is_live` boolean matching schema - Add $schema reference to JSON example for CI validation - Remove invalid `tasks` field from capabilities example - Condense explanatory sections into focused spec requirements - Add Transport Requirements section - Add explicit Conformance section for agents and orchestrators - Restructure Core Concepts to be more specification-focused Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
7 tasks
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.
Summary
Simplify page titles and transform signals specification from verbose documentation into concise, normative RFC-style format. Fixes schema alignment issues and adds testable JSON validation.
Changes
activate_signalrequirements to useis_liveboolean matching actual schema$schemareference to JSON example for CI validationtasksfield from capabilities exampleTesting
All 262 tests pass, including schema validation. JSON example validates against
get-adcp-capabilities-response.json.