LifeOS

LifeOS is not another general-purpose chatbot. It is a calm, privacy-first household coordination layer that helps a family understand what is happening, what preparation is implied, and what might otherwise be forgotten.

What it does

A parent selects calendars already on the iPhone. LifeOS turns those events into a Today/Tomorrow brief and a bounded fourteen-day preparation queue, with evidence, lead times, and concrete “Do by” dates. On supported devices, a parent can ask Apple’s on-device model to make one event’s readiness check specific. Every proposed task is editable and requires confirmation; every time or Home-arrival reminder has a separate preview and confirmation.

The “Teach LifeOS once” memory loop is explicit and local. After confirming an event-linked task, a parent may separately approve a reusable recipe scoped to that exact event title in that same selected calendar. The recipe can make a later suggestion more useful, but it cannot create tasks, schedule reminders, write calendars, or act on its own. Memory can be inspected, disabled, re-enabled, or deleted.

How we built it

Codex was the primary build environment. It reconciled the product brief, established the GitHub Spec Kit constitution/spec/plan/task workflow, implemented and reviewed the SwiftUI app and Node relay, drove failing-first security and behavior tests, and verified simulator, signed-device, privacy, credential, and release gates. The current checked-in candidate records 273 unit executions (272 passed; one production-provider evaluator intentionally skipped), 7/7 UI tests, and 30/30 relay tests.

GPT-5.6 is a privacy-gated second opinion, not an authority. After the user reviews the exact minimized payload, the fixed server-side relay can ask GPT-5.6 to synthesize and rank only locally grounded readiness candidates. The relay fixes the model, schema, and prompt; sends no tools; requests store:false; validates output again; and keeps the OpenAI credential off the phone. LifeOS remains useful offline if that path is unavailable.

What’s next

User-approved semantic on-device memory, private turn-based conversation, and a minimized Hermes trip-planning handoff—each retaining the same review-before-action boundary.

Built With

• apple-foundation-models
• avfoundation
• core-location
• eventkit
• github-spec-kit
• node.js
• openai-codex
• openai-gpt-5.6
• speech
• swift
• swiftdata
• swiftui
• usernotifications
• xcode
• xcodegen
• xctest