Alefita Insights — Directions and Theses

Editorial rule: only insights/theses/directions/requirements that come from Alefita belong here, with provenance (date/time, quote or close paraphrase). Agents: forbidden to add specs, TODO lists, plans, or their own theses — the wikifita consolidates facts; human foresight is the exception (see the wikifita CLAUDE.md at repo root).

• 2026-08-26 (~19:20 BRT) — "the Swift wrapper maybe is part of a monorepo; from that monorepo come the site, the desktop apps for three platforms and the iOS mobile app. Android I don't think comes from the same point, maybe it takes the bundles — maybe native Jetpack Compose. Verify later." — thesis pointing at a possible shared monorepo for OpenAI desktop/iOS/web, with Android possibly separate (native).
• 2026-08-26 (~19:20 BRT) — on Windows/Linux agent-mode: "the Work mode would try to spin up the sandboxed VM/container and fail; on Linux it's the closest, but we're not in flow B yet." — note that the platform sandbox is the blocker for work/codex modes on non-macOS (analysis when flow B starts).
• 2026-08-26 (~19:08 BRT) — the standalone requirement: "only the binary installed and updated" is acceptable; ideally fully standalone; the direction is: standalone with Proof of Work or Device Attestation when available (macOS), a robust standalone for both flows A and B.
• 2026-08-26 (~18:10 BRT) — on user agents: they matter for versioning; a standalone must mirror the exact analyzed values, and implement a version-spoofing pipeline later (directional requirement).