The 26 October documentation reconciliation brings forward Run/Highlight, standalone Build, standard Type Def, Tabs and attached-comment guides. The example results below remain a dated measurement.
A visual workspace aimed at helping people follow and validate machine-generated software through a structured FROG model and graphical dataflow.
Design a Front Panel, connect typed operations in the Block Diagram, and inspect the resulting document in Source. Context Help explains the object under the pointer and links directly to the relevant reference.
Read the documentation · Start your first document · Browse functions · Browse actual .frog examples · Browse widgets
| I want to… | Read |
|---|---|
| Learn the workspace | Getting started |
| Place and edit controls | Front Panel |
| Connect operations | Block Diagram |
| Understand an icon or terminal | Context Help and Functions |
| Try a supported graph locally | Run and Highlight |
| Build a standalone EXE | Build |
| Share a control schema | Type Definitions |
| Organize independent controls into pages | Tab Controls |
| Attach an annotation to a diagram object | Attached comments |
| Open an example with its explanation and expected results | Examples |
| Customize the editor | Studio Options |
| Check support and limitations | Current capabilities |
The strategic objective is human comprehension and acceptance as code generation expands. FROG serializes a structured model in .frog; Studio projects it into graphical dataflow using connections, color, shape, position, text, arrangement and labels. FIR/IR connect the supported program to compilers and execution targets. Direct human programming and maintenance use the same foundation. FROG remains open; Studio is Graiphic's proprietary environment.
Read Why work in Graiphic Studio? for the calculator abstraction, the intended generation/review workflow and the distinction between direction and delivered capabilities. The evidence guide explains the available checks. DARPA-specific research remains separate from the general product direction.
This repository contains the user guides and reference for Graiphic Studio. Guides explain actions and their results; function pages describe purpose, terminals, types, and current support using the Studio's existing help catalog.
The FROG specification defines the public language. A feature available in Studio's editor or private local simulation does not automatically have a public-source or target-runtime implementation. See the document model for that boundary.
The 25 October 2026 checkpoint records 625 actual example documents and 1,219 measured checks, with their backend/profile limits. It is not a qualification of every function or a new signed release. Existing screenshots illustrate named workflows; they are not new captures of every current feature. Function SVGs and connector schematics are identified as reference illustrations rather than application screenshots.
- Start with the user's task, then explain the action, result, and relevant limit.
- Keep function names and identifiers aligned with the built-in help catalog.
- Use descriptive headings, relative Markdown links, and meaningful image text.
- Use real product captures or clearly identified reference illustrations.
- Distinguish editing support, private Run/Highlight, public Source, and target execution.
docs/ contains guides, widget pages, function pages, and reference material.
assets/ contains screenshots and explanatory visuals.
The example pages and downloads are projections of the existing
FROG/Examples/index.v1.json. They preserve the actual document and dependency
bytes; they are not another operator registry or proof that a backend passed.
Studio Draft and public Source profiles remain distinct. See
example profiles and execution scope.
Regenerate locally with Python 3.11+ after the real corpus has been generated:
python tools/export_studio_help.py --source ../FROG-STUDIO/native-portable-engine --examples-index ../FROG/Examples/index.v1.json
python tools/export_studio_help.py --source ../FROG-STUDIO/native-portable-engine --examples-index ../FROG/Examples/index.v1.json --check
python -m unittest discover -s tools -p test_export_studio_examples.py
An absent canonical index is an error; the exporter does not create a placeholder.
--check is read-only. Cleanup is limited to owned generated pages and the
example files recorded in the exporter ownership manifest, with their previous
hashes checked before deletion. Exporting locally does not push or deploy this site.