lane-system.md

Lane System

Runtime Lanes

OpenBuildApp separates target-specific execution into explicit lanes.

Web Lane

• MVP priority: yes
• sandbox strategy: isolated browser profile or containerized browser session
• observation strategy: DOM, screenshots, accessibility tree, interaction events, timing marks
• replay strategy: deterministic action sequence with state hash checkpoints
• verification limits: depends on DOM and browser instrumentation availability

Desktop Lane

• MVP priority: no
• sandbox strategy: VM or OS sandbox with window-tree bridge
• observation strategy: screenshots, window trees, accessibility APIs, input trace
• replay strategy: UI automation plus state snapshots
• verification limits: weaker structural introspection than web lane

Mobile Lane

• MVP priority: no
• sandbox strategy: emulator-only first
• observation strategy: screenshots, view hierarchy, accessibility, input events
• replay strategy: emulator automation and deterministic seed state
• verification limits: timing and animation capture are device-sensitive

Adapter Contract

Each lane adapter must implement:

• bootstrapTarget
• captureBaseline
• recordInteraction
• collectObservationBundle
• captureReplayState
• listVerificationLimits
• teardownTarget

Unsupported lanes must fail closed and emit a structured lane.unsupported event.