Repository navigation
Fix temporal approval and operating baseline guidance, release 0.21.8 - #102
Merged
Merged
Conversation
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.
A later approval could be presented as proof of an earlier operating failure, and pending successors could interrupt otherwise valid operating baselines. Temporal diagnostics now distinguish unproven authorization evidence from confirmed failures, retain resolved out-of-period limitations as information, and restore actionable warnings when selected examination coverage overlaps them.
Shared baseline selection preserves valid Policy, program Document, Training and retention authority until actual effective cutover. Recurring work, workforce acknowledgments, readiness and evidence packets use the same selection. New scope, missing approval, stale content, invalid activation, retirement and real period gaps retain their normal checks. Historical fallback reads the actual committed companion rather than proposed working content.
Formal audit range/as-of dates govern examination views; Program-scoped causes and cached validation cannot borrow another scope's coverage. Global structural errors stay strict. This patch adds informational diagnostic counts and optional validation context without changing source formats or model 13.
Validation includes independent combined code/security reviews, full Node 24 validation, temporal and governed-content regressions, actual browser history/Run and successor checks, a fresh generated consumer validation/build, package inspection and audit. Coordinated release: filegrc and create-filegrc 0.21.8.