Conversation
Give catalog, capability, control, and status a shared architectural contract for ownership, lifecycle, derived state, and change notifications. Keep review instructions in the code-change guide and link the model from the project map and IEEE 802.11 domain rules. Validation: documentation link and seal checks pass; staged diff has no whitespace errors. Change: doc | behavior.add | -
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
2 participants
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.
Define a shared architectural contract for IEEE 802.11 state and component communication, giving future changes a consistent basis for design and review.
The document distinguishes catalog, capability, control, and status, and specifies their ownership, writers, readers, lifecycle, derived dependencies, and notification contracts. It describes the intended architecture without claiming that every existing implementation already satisfies it.
Link the document from the project map and IEEE 802.11 domain rules. Keep instructions for assessing changes in the code-review guide.
Documentation only; no runtime changes or baseline updates.
Validation — all passed:
doc/project/enforcement/check-links.shdoc/project/enforcement/check-seals.shgit diff --cached --checkdoc/project/enforcement/check-classification.sh HEAD^..HEADdoc/project/enforcement/check-commits.sh HEAD^..HEAD