Repository navigation
docs: assess industrial maritime and power descriptions - #2061
Merged
Merged
Conversation
4 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
Compare controller, navigation-computer and power-equipment descriptions with existing SDL contracts. Reuse recursive realization semantics and identify the minimum optional vocabulary, public attachment and addressability additions.
Requirement UIDs
Related Issues
Closes #2059
ADR Impact
Changes
Test Plan
10 targeted semantic test cases passed. Changed-path docs-prose (Vale and shared STE), file-local repository policy, relative links and git diff --check passed. Review found one repeated helper-path error; both references were corrected and the supported import verified. User accepted the review cap after repairs. Source assessment: 1f4d05e; starting evidence also checked at 33c09e9. IEC comparison uses its public abstract plus public ENTSO-E examples; no complete conformance claim. No executable changes or mutation tests.
Ground Control Checks
Traceability
Checklist
Documentation
Updated: see diff.