- Home
- Expression
- Examples
- Language
- IR
- Libraries
- Profiles
- IDE
- Conformance
- invalid
- 01 missing required section
- 02 wrong top level section type
- 03 connector defines logical ports
- 04 malformed front panel structure
- 05 duplicate source identifier
- 06 widget must not be promoted to public interface
- 06 invalid top level root shape
- 07 invalid section placement
- 08 widget reference must not be treated as widget value
- 08 connector references unknown interface port
- 10 front panel presence must not be treated as execution meaning
- 12 public interface declaration must not require front panel widget existence
- 14 layout or adjacency must not be treated as executable participation
- 16 inferred evaluation order must not be treated as dependency or connectivity
- 18 layout grouping or apparent nesting must not be treated as structure boundary
- 20 inferred region crossing by layout must not be treated as structure terminal usage
- 22 inferred persistent value by feedback shape must not be treated as structure owned state
- 24 inferred default initial value must not be treated as explicit state initialization
- 26 inferred scheduler order must not be treated as explicit state read timing
- 28 inferred runtime flush order must not be treated as explicit state write visibility
- 30 inferred runtime observation point must not be treated as explicit state snapshot boundary
- 32 inferred runtime update epoch must not be treated as explicit state version boundary
- 34 inferred runtime reconciliation pass must not be treated as explicit state merge boundary
- 36 inferred runtime stabilization phase must not be treated as explicit state commit boundary
- 38 derived execution identity must not replace recoverable source attribution
- 40 private runtime identity must not be treated as open execution ir identity
- 42 private runtime identity must not be treated as backend contract identity
- 44 private runtime schedule must not be treated as open execution ir structure
- 46 private runtime schedule must not be treated as backend contract structure
- 48 private runtime debug state must not be treated as open execution ir observation surface
- 50 identity loss must not be disguised as intentional non primary correspondence
- 52 primary execution object without recoverable source anchor is invalid
- 54 schema valid ir shape does not justify ir architectural collapse
- 56 semantic acceptance does not by itself establish schema valid canonical ir
- 58 region without recoverable structure owner is invalid
- 60 structure boundary terminal role must not be lost in canonical execution ir
- 62 structure terminal role loss must not be treated as valid canonical execution ir
- 64 multi contributor source attribution must not be collapsed into single source ownership
- 66 declaration reference must not be treated as primary execution identity in canonical execution ir
- 68 memory identity loss must not be treated as valid canonical execution ir
- 70 structure family identity collapse must not be treated as valid canonical execution ir
- 72 correspondence category loss must not be treated as valid canonical execution ir
- 74 primary non primary and contributor correspondence categories must not be merged in canonical execution ir
- 76 public interface boundary correspondence must not be collapsed into front panel or widget correspondence in canonical execution ir
- 78 widget value correspondence must not be collapsed into widget reference or ui object operation correspondence in canonical execution ir
- 80 widget reference correspondence must not be collapsed into ui object operation correspondence in canonical execution ir
- 82 property read correspondence must not be collapsed into property write correspondence in canonical execution ir
- 84 method invocation correspondence must not be collapsed into property write correspondence in canonical execution ir
- 86 property read correspondence must not be collapsed into method invocation correspondence in canonical execution ir
- 88 ui object operation correspondence must not be collapsed into ui in and ui out sequencing correspondence in canonical execution ir
- 90 ui in correspondence must not be collapsed into ui out correspondence in canonical execution ir
- 92 explicit ui sequencing correspondence must not be collapsed into ordinary dataflow connectivity correspondence in canonical execution ir
- 94 explicit ui sequencing correspondence must not be collapsed into control structure boundary correspondence in canonical execution ir
- 96 explicit ui sequencing correspondence must not be collapsed into explicit state boundary correspondence in canonical execution ir
- 98 explicit ui sequencing correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 100 ordinary dataflow connectivity correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 102 control structure boundary correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 104 explicit state boundary correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 106 explicit state boundary correspondence must not be collapsed into ordinary dataflow connectivity correspondence in canonical execution ir
- 108 control structure boundary correspondence must not be collapsed into ordinary dataflow connectivity correspondence in canonical execution ir
- 110 primary source attribution correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 112 primary source attribution correspondence must not be collapsed into ordinary dataflow connectivity correspondence in canonical execution ir
- 114 primary source attribution correspondence must not be collapsed into control structure boundary correspondence in canonical execution ir
- 116 primary source attribution correspondence must not be collapsed into explicit state boundary correspondence in canonical execution ir
- 118 multi contributor attribution correspondence must not be collapsed into public interface boundary correspondence in canonical execution ir
- 120 multi contributor attribution correspondence must not be collapsed into ordinary dataflow connectivity correspondence in canonical execution ir
- illegal feedback without explicit memory
- interface widget role confusion
- ui reference without ui primitive
- compiler
- executable
- structural
- valid
- 01 pure addition
- 02 ui value roundtrip
- 03 ui property write
- 04 stateful feedback delay
- 05 public interface and widget participation distinct
- 07 widget reference remains distinct from widget value
- 11 public interface declaration does not require front panel widget existence
- 13 explicit diagram participation remains distinct from layout or adjacency
- 15 explicit connectivity remains distinct from inferred evaluation order
- 17 explicit structure boundaries remain distinct from layout grouping or nesting
- 19 explicit structure terminals remain distinct from inferred region crossing by layout
- 21 explicit structure owned state remains distinct from inferred persistent value by feedback shape
- 23 explicit state initialization remains distinct from inferred default initial value
- 25 explicit state read timing remains distinct from inferred scheduler order
- 27 explicit state write visibility remains distinct from inferred runtime flush order
- 29 explicit state snapshot boundary remains distinct from inferred runtime observation point
- 31 explicit state version boundary remains distinct from inferred runtime update epoch
- 33 explicit state merge boundary remains distinct from inferred runtime reconciliation pass
- 35 explicit state commit boundary remains distinct from inferred runtime stabilization phase
- 37 explicit source attribution must remain recoverable across derivation
- 39 open execution ir identity must remain distinct from private runtime identity
- 41 backend contract identity must remain distinct from private runtime identity
- 43 open execution ir structure must remain distinct from private runtime schedule
- 45 backend contract structure must remain distinct from private runtime schedule
- 47 open execution ir observation surface must remain distinct from private runtime debug state
- 49 intentional non primary correspondence must remain explicit in canonical execution ir
- 51 primary execution object must keep explicit source attribution in canonical execution ir
- 53 schema valid canonical ir must still preserve ir architectural distinctions
- 55 semantically accepted program may also emit schema valid canonical ir
- 57 region ownership must remain recoverable in canonical execution ir
- 59 structure boundary terminals must remain recoverable in canonical execution ir
- 61 structure terminal roles must remain recoverable in canonical execution ir
- 63 multi contributor source attribution must remain explicit in canonical execution ir
- 65 declaration reference must remain distinct from primary execution identity in canonical execution ir
- 67 explicit memory identity must remain recoverable in canonical execution ir
- 69 structure family identity must remain recoverable after derivation
- 71 correspondence category must remain recoverable in canonical execution ir
- 73 primary non primary and contributor correspondence categories must remain distinct in canonical execution ir
- 75 public interface boundary correspondence must remain distinct from front panel and widget correspondence in canonical execution ir
- 77 widget value correspondence must remain distinct from widget reference and ui object operation correspondence in canonical execution ir
- 79 widget reference correspondence must remain distinct from ui object operation correspondence in canonical execution ir
- 81 property read correspondence must remain distinct from property write correspondence in canonical execution ir
- 83 method invocation correspondence must remain distinct from property write correspondence in canonical execution ir
- 85 property read correspondence must remain distinct from method invocation correspondence in canonical execution ir
- 87 ui object operation correspondence must remain distinct from ui in and ui out sequencing correspondence in canonical execution ir
- 89 ui in correspondence must remain distinct from ui out correspondence in canonical execution ir
- 91 explicit ui sequencing correspondence must remain distinct from ordinary dataflow connectivity correspondence in canonical execution ir
- 93 explicit ui sequencing correspondence must remain distinct from control structure boundary correspondence in canonical execution ir
- 95 explicit ui sequencing correspondence must remain distinct from explicit state boundary correspondence in canonical execution ir
- 97 explicit ui sequencing correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 99 ordinary dataflow connectivity correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 101 control structure boundary correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 103 explicit state boundary correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 105 explicit state boundary correspondence must remain distinct from ordinary dataflow connectivity correspondence in canonical execution ir
- 107 control structure boundary correspondence must remain distinct from ordinary dataflow connectivity correspondence in canonical execution ir
- 109 primary source attribution correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 111 primary source attribution correspondence must remain distinct from ordinary dataflow connectivity correspondence in canonical execution ir
- 113 primary source attribution correspondence must remain distinct from control structure boundary correspondence in canonical execution ir
- 115 primary source attribution correspondence must remain distinct from explicit state boundary correspondence in canonical execution ir
- 117 multi contributor attribution correspondence must remain distinct from public interface boundary correspondence in canonical execution ir
- 119 multi contributor attribution correspondence must remain distinct from ordinary dataflow connectivity correspondence in canonical execution ir
- 01 minimal canonical frog
- 02 optional sections absent is still valid
- 03 optional front panel absent is still valid
- 04 optional connector absent is still valid
- 05 optional icon absent is still valid
- 06 optional ide absent is still valid
- 07 optional cache absent is still valid
- 08 optional connector present and consistent
- 09 optional front panel present and structurally valid
- 10 distinct source identifiers are valid
- compiler
- executable
- structural
- invalid
- Reference Implementation
- example-artifact-requirements
- frogc
- internal-artifacts
- pipeline
- common.py
- CLI
- ContractEmitter
- Deriver
- LLVM
- bridge
- examples
- tools
- Loader
- Lowerer
- Runtime
- UIHost
- Validator
- Roadmap
- Strategy
- Governance
- Contributing
- CLA