Skip to content

widget_public_boundary.md

Latest commit

 

History

History
59 lines (48 loc) · 2.85 KB

widget_public_boundary.md

File metadata and controls

59 lines (48 loc) · 2.85 KB

Widget Example Public Boundary

This public repository exposes the specification-facing boundary for widget examples. It does not publish Graiphic's internal acceptance recipe, visual QA procedure, release checklist, or private implementation roadmap.

Widget examples remain subordinate to the owning specification documents, schemas, realization packages, conformance cases, and reference checks. They are not semantic owners of FROG.

Public Ownership Boundary

  • .frog owns diagram logic, front-panel widget instances, widget ids, bindings, initial values, labels, instance layout, and instance-level visual overrides.
  • .wfrog packages publish realization references, Default asset ids, supported classes, and host capability declarations. They are not example-specific front-panel source.
  • Default realization assets own reusable SVG templates, public parts, public anchors, public bindings, internal geometry, and default visual behavior.
  • Runtime implementations consume validated source-derived artifacts, backend contracts, native manifests, ABI surfaces, .wfrog packages, and published realization assets. They do not redefine the widget class law.

Public Fidelity Expectation

A published widget example should make the source / realization / runtime boundary inspectable. A visible front panel should not be presented as a valid published widget example if it is only a handcrafted runtime shell unrelated to the declared .frog, .wfrog, and Default realization assets.

The public expectation is architectural, not a Graiphic internal QA checklist:

  • front-panel intent is visible in source-owned data,
  • realization references resolve through published .wfrog packages,
  • Default SVG assets expose public parts, anchors, bindings, or equivalent published markers where the realization requires them,
  • runtime snapshots and diagnostics remain supporting evidence rather than the user-facing widget itself,
  • native-backed examples consume manifests and ABI artifacts rather than treating LLVM as the runtime identity.

Reference Runtime Boundary

Examples 01 through 15 define the current public reference runtime closure. Examples beyond that boundary may remain public as specification-facing, widget-facing, conformance-facing, or design-progression examples. Their presence does not require Graiphic to publish production runtime implementation work for those later examples.

Graiphic's internal validation recipes, visual acceptance procedures, development state, and proprietary runtime roadmap are maintained outside this public repository. They do not redefine the public FROG specification.