Route classic Mac and host work¶
Choose by application model, not merely by CPU or folder name.
| Surface | Implementation model | Agent route |
|---|---|---|
now-host/ |
Swift, SwiftUI, AppKit adapters | Read the host architecture; preserve native control ownership and host model boundaries |
now-guest-ppc/ |
PowerPC CFM CarbonLib 1.6 application | Load Carbon platform guidance; load Carbon UI guidance for windows, controls, events, or redraw work |
now-guest-68k/ |
Non-Carbon 68K Toolbox/MacTCP application | Load Toolbox platform guidance; load Toolbox UI guidance for interface work; do not route through Carbon skills |
ext/ |
68K INIT resident under emulation on PowerPC | Load INIT/resident platform guidance; preserve the versioned shared-table and bake gates |
| QEMU or physical-machine acceptance | Deterministic emulator or metal harness | Load emulator-harness guidance and follow the emulator and metal workflow |
Product agent integration under now-host/Sources/NOWAgentIntegration/ is
ordinary host architecture, not coding-agent protocol. Read the product agent
integration page for that
subsystem.
For every classic surface, determine the supported OS floor and application model before proposing an API. A symbol present in a modern SDK or another classic target is not evidence that it is callable in this one.