docs: clarify format-first, not IDE-first positioning#13
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.
Summary
This PR makes the FROG architectural differentiator more explicit: FROG is format-first and pipeline-first, not IDE-first.
Changes
Readme.mdexplaining that the IDE edits, validates, observes, and projects a FROG program, but does not own the language.Strategy/FormatFirstNotIdeFirst.mdas a non-normative strategic note explaining why the durable asset is the.frogsource, validated meaning, open FIR, lowering boundary, backend contract, and runtime/compiler consumption chain.Rationale
This clarifies why FROG avoids the structural risk of monolithic graphical platforms where editor, saved format, runtime, compiler, and hardware stack become inseparable.
Validation
Documentation-only change. No runtime or specification-law changes.