Refresh v0.3.19 SFCS public docs - #64
Draft
JROChub wants to merge 4 commits into
Draft
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
1 participant
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
docs/sfcs.mdaround the actual shipped surface:from_source,from_program, dense integer/memory execution traces, synthesis plans,.phaembedding verification, and the offlinejulian sfcsCLI.docs/sfcs.mdtoscripts/check_release_consistency.pyso the SFCS guide cannot drift outside the active release gate again.Notes
This keeps Rootprint v1 and
.phafingerprint boundaries intact while making the public direction clear: native SFCS is the Power House path that bypasses traditional zkVM and circuit-compiler flows for the targeted workload class.Validation
Not run locally; no checkout is mounted in this environment. The touched files are Markdown plus the release-consistency path list.