Features/Phase 0 - rstix structure#148
Closed
SecurityEnthusiast wants to merge 3 commits into
Closed
Conversation
|
|
mostafa
force-pushed
the
feature/phase01-stix-foundation
branch
from
4105f32 to
d85ba2f
Compare
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
3 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.
Phase 0 was needed to introduce 'Rstix' as an independently consumable crate without destabilizing the existing workspace. The change adds crate scaffolding, feature wiring, and a fuzz compile target, then validates full workspace and crate-specific build/lint/test gates. Reviewers should focus on feature-flag topology, workspace integration boundaries, and whether infrastructure-only scope is preserved. Parsing/model/validation logic is intentionally out of scope.