Workbench
Design, exercise, diagnose, and prove the real package experience before immutable release bytes leave the author workspace.
Workbench is a package development host, not a no-code editor and not a mock preview. It loads the real activity worker, package player, overlay, configuration, fixtures, progression, Story Events, correction policy, coordination, and narration contributions.
Product view first
The main canvas shows the Practice Mode at realistic phone, tablet, desktop, and broadcast dimensions. The collapsible sidebar contains author controls. Deep protocol traces and raw diagnostics stay available without dominating the normal iteration loop.
Core author loop
Pick a scenario
Use named fixtures for ready, active, edge, terminal, stale, unavailable, corrected, and replay states. A scenario should describe why the state matters, not merely dump JSON.
Exercise the real interaction
Tap, type, use keyboard controls, or inject declared exact observations through the live activity runtime. Inspect state, Measurements, progression, Story Events, and result presentation together.
Change viewport and accessibility context
Check phone/tablet portrait and landscape, desktop, compact overlay, 16:9 broadcast, 200% text, keyboard focus, reduced motion, contrast, and touch size.
Diagnose only when needed
Open transitions, bridge messages, schema validation, capability grants, observation identity, and fixture details when behavior is surprising.
Run conformance
Conformance verifies the claims made by the manifest, authoring brief, listing, fixtures, and artifacts. The release cannot outrun its evidence.
Automatic input loopback
Connector Lab can feed exact observations through a loopback bridge into the real Workbench activity. This proves that independently built connector bytes and package bytes agree on the complete observation identity—not just a sample JSON shape.
Workbench does not approve
Local approval is evidence for a later independent review. Workbench never publishes public code, grants native capabilities, signs a connector, or marks its own package trusted.
Domain Kits
Reuse pure vertical rules, schemas, fixtures, UI, and presentation at build time without creating runtime privilege or member configuration.
Package evolution and release compatibility
Ship fixes and improvements while preserving pinned runs, historical evidence, and honest progression lanes.