docs: define IFC profile variability and publication rules - #1383
Merged
Merged
Conversation
Collaborator
Author
|
Ground Control delivery — this pull request delivers issue #1354; Phase E runs on merge. |
Collaborator
Author
|
Ground Control delivery — this pull request delivers issue #1354; Phase E runs on merge. |
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
The general IFC algebra can distinguish independent owners, but the published security vocabulary cannot directly represent their selective releases. Define governed finite profile publication, requirement-relative support, execution weakening and historical migration, with explicit limits on current contract and runtime support.
Requirement UIDs
SEM-233SEM-235Related Issues
Refs #1354
ADR Impact
Changes
Test Plan
113 targeted tests passed. ADR pins, changed-path requirement governance, file-local policy, lint and Markdown links passed. Required publish hooks passed; pre-push review returned ship with no findings. Tests are bounded semantic/contract evidence, not owner-aware runtime adoption.
Ground Control Checks
Traceability
Checklist
Documentation
Updated: see diff.