Read by subsystem
Start with the implementation and evidence map, then explore passkeys, key storage and authentication.
| Subsystem | Question | Interactive model |
|---|---|---|
| Execution paths → | Where does compatibility live? | Process and kernel boundaries |
| Backstep loader → | How does a Mach-O fixture enter host memory? | Relocation, binding, permissions, rejection |
| Rendering → | How do layers become displayed pixels? | Exploded layers, clipping, delivery failure |
| Input → | How does a host touch reach a guest? | Live inverse coordinates, contact queue |
Inspect and reproduce
Cider / Backstep experiment kit → A selected source snapshot with its own manifest, checksum, and isolated macOS build/test record. The archive remains local pending distribution licensing and provenance review.
Current development workflows → Source compilation, playgrounds, and guest experiments are distinct routes.
Daybreak Terminal specification → A proposed service workbench and observable compile–run–interact loop. This page is not a device controller.
Evidence and open work
Source inventory → Primary references and working-tree hashes identify the scope of the explanations.
Backstep issues → The development repository is private; collaborators need access. These explanatory pages can be read without an account.
Testing targets include Pixel 3a, 6, 7, 9, and 10a, BlueBerry, Daylight DC-1, and Nothing Phone (3). The roster comes from the project team. It does not establish equal app, graphics, or service support across the fleet.
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.
- [checkpoint] Daybreak, iOS Runtime Checkpoint and Next Gate. docs/research/ios-runtime-next.md, updated September 8–9, 2026. Dated evidence, remaining fixture boundary and rendering discrepancies. Private workspace source; collaborator access required.