Three execution routes
| Route | Implemented mechanism | Evidence boundary |
|---|---|---|
| Recompiled Swift | ShimKit views and service commands cross the Android bridge | A facade is a supported subset, not the entire Apple framework |
| Backstep | Mach-O mapping, relocation, supported imports and fixture entry | 121 package tests passed on macOS arm64; not arbitrary app compatibility |
| OS guest | Guest execution, exported layers and return input channel | Dated device experiments; results depend on guest and host build |
Execution boundaries · Loader internals · Passkeys and storage
Close the guest touch loop
Host contact → inverse transform
Initial touches must land in the guest display region. Remove rotation and scale. Active contacts can continue outside the initial region within the implemented bound.
Contact state → bounded queue
Down starts contact; adjacent moves may coalesce; up/cancel ends it. The queue reserves terminal capacity so a gesture does not remain stuck.
Transport → guest state
Socket readiness and byte pacing affect delivery. Sending input is not evidence that the guest processed it. Observe changed guest state.
New guest frame → Android UI
The frame envelope validates bytes; ACK means acceptance, not scanout. The pending slot can replace accepted intermediate frames before drawing.
Canvas → composition → presentation
A closed-loop receipt associates the interaction, changed state and render/capture. Input-to-state and input-to-panel latency are different measurements.
Manipulate coordinates and queue state → · Step through layers and transport →
A recompiled ShimKit button uses host view events; it does not take this guest-kernel route. Keep the selected runtime visible in all measurements.
Name the contract, not a percentage
Use implemented for inspected code, passed for a named executed case, not run for absent evidence, and unsupported for an explicit rejection. Service checks need the source revision, target device, exact inputs and expected results. The Terminal proposal should carry those receipts rather than a broad “iOS supported” score.
References and evidence
Implementation references describe a working-tree snapshot. They are not all present in a public repository. The source inventory records file hashes; historical notes are not new device tests.
- [input] Daybreak, GuestCoordinates.kt / GuestTouchQueue.kt. Inspected working tree, 2026-09-10; same Android directory. Coordinate inversion, contact lifetime and move coalescing. Private workspace source; collaborator access required.
- [frame] Daybreak, GuestFrameDelivery.kt / GuestLayerStream.kt. Inspected working tree, 2026-09-10; android/app/src/main/java/com/daybreak/host/skia/. Envelope integrity, duplicate handling, frame-local resources. Private workspace source; collaborator access required.
- [map] Daybreak, SegmentMapper.swift / ApplyLinkEdit.swift / Execute.swift. Inspected working tree, 2026-09-10; machparse/Sources/MachParse/. Mapping, relocation, protection and host-stack entry. Private workspace source; collaborator access required.