-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Welcome to the FROG wiki.
This wiki is the human-oriented entry point to the FROG ecosystem. It is designed to help readers understand the project faster, navigate the specification, and identify the role of each architectural layer.
The repository itself contains the normative specification of FROG.
The wiki has a different role:
- provide an accessible overview,
- explain how the repository is organized,
- help new readers choose a reading path,
- clarify key architectural distinctions,
- document ecosystem and implementation intent at a higher level.
FROG is an open graphical dataflow programming language.
It is designed to describe programs as explicit executable graphs rather than syntax-first text sequences. Its long-term goal is to provide an open, durable, hardware-agnostic foundation for graphical programming across tooling, execution, and industrial deployment contexts.
FROG is not:
- a single IDE,
- a single runtime,
- a single compiler,
- a vendor-bound product.
FROG is an open language specification with clearly separated layers for source representation, execution semantics, IR, libraries, profiles, and IDE-facing architecture.
The repository is structured by architectural responsibility:
-
Expression/— canonical source representation -
Language/— normative execution semantics -
IR/— execution-facing representation and lowering boundaries -
Libraries/— intrinsic standardized primitive vocabularies -
Profiles/— optional capability families -
IDE/— authoring, observability, debugging, and inspection architecture
If you are new to FROG, start here:
- Read the repository
Readme.md - Read
Expression/Readme.md - Continue to
Language/Readme.md - Continue to
IR/Readme.md
Then branch depending on your interest:
- language design,
- compiler / runtime work,
- IDE architecture,
- ecosystem implementation,
- future conformance work.
- What-is-FROG
- Repository-Architecture
- Recommended-Reading-Paths
- Specification-vs-Implementation
- Conformance-and-Ecosystem
- Glossary
FROG aims to become a serious open foundation for graphical dataflow programming:
- accessible enough for fast system prototyping,
- explicit enough for inspection and reasoning,
- structured enough for industrial execution,
- open enough to support multiple independent implementations.
The specification is the foundation. The ecosystem comes after. The wiki helps connect the two.