A local-first personal operating system for turning work, money, projects, follow-ups, evidence, relationships and daily pressure into visible, reviewable state.
LifeOS is a safety-first platform built around a Windows desktop command centre, a lightweight Android Companion, guarded automation and a source-backed read-only Assistant.
Current checkpoint: LifeOS Desktop
v7.0.0-beta.1— v7 complete and closed at beta
| Product | Status |
|---|---|
| LifeOS Desktop | v7.0.0-beta.1 — v7 beta complete and closed |
| LifeOS Mobile Companion | v0.1.0-beta.1 — beta complete and closed |
| LifeOS Mobile | Separate future full mobile application — not started |
| LifeOS Website | Planned public documentation and product site — not started |
| LifeOS v8 | Not started |
The Mobile Companion and the future full Mobile application are separate products. They may share contracts and libraries, but they retain different scope, UX and release tracks.
- Command Centre pressure and priority visibility
- projects, work pipeline, follow-ups and waiting-on tracking
- money pressure, payment attention and planning
- agenda, daily state, work sessions and timesheets
- evidence, receipts, timeline and provenance
- relationships and contextual records
- review-first integrations
- guarded, reversible internal automation
- source-backed Assistant answers
- review-only planning blocks
- controlled review transfer
- explicit user-controlled durable memory
Important information becomes visible state.
State affects pressure.
Pressure feeds the Command Centre.
Actions remain reviewable and controlled.
The v7 Assistant answers questions from approved local LifeOS sources without gaining an execution path.
It can:
- classify a question before retrieval
- search only enabled local sources
- retrieve a bounded set of candidate records
- rank evidence by relevance, trust, freshness and directness
- combine evidence across sources while preserving provenance
- separate facts, inferences, uncertainty and missing data
- flag stale or conflicting records
- disclose records selected, excluded and considered
- generate structured review-only plans
- transfer confirmed plan payloads into a review queue only
- use explicit, scoped and revocable memory after user confirmation
It cannot:
- send email or messages
- create or change calendar items
- mutate projects, tasks, money or other trusted LifeOS state
- approve, confirm or continue orchestration
- launch scripts, processes, plugins or hidden tools
- perform external web search or connector writes
- run autonomously or in the background
- convert AI output directly into trusted operational state
question
-> classify intent
-> search enabled local sources
-> retrieve bounded candidates
-> rank evidence
-> detect conflicts, staleness and gaps
-> answer with provenance and uncertainty
-> optionally build a review-only plan
-> optionally transfer one confirmed review artifact
-> optionally use explicit user-confirmed memory
The current source registry includes:
- Command Centre
- Follow-Ups
- Work Pipeline
- Timeline
- Evidence
- Money Pressure and payment attention
- Waiting On
- Projects
- Work Sessions
- Timesheets
- Receipts
- Relationships
- Agenda
- Daily State
Each source is permission-controlled and can be enabled or disabled independently.
The Assistant can assemble structured plans from reusable blocks:
- Goal
- Evidence
- Constraint
- Step
- Dependency
- Risk
- Decision
- Verification
- Handoff
Plans remain Review-only and Executable: No.
A controlled transfer can create one review artifact only after payload preview, target selection and explicit user confirmation. It cannot create or mutate tasks, projects, Follow-Ups, payments, calendar items, email, automation or orchestration state.
Assistant memory is:
- created only after exact preview and explicit confirmation
- scoped to Global, Workspace, Project, Relationship or Session-limited use
- classified by type and sensitivity
- auditable and locally protected
- visible in the Memory workspace
- editable through auditable revisions
- expirable, revocable and deletable
- disclosed separately from direct source evidence
Current trusted LifeOS records outrank conflicting memory. Expired, revoked and deleted memory is excluded from retrieval.
There is no automatic retention, hidden profiling or latent user model.
LifeOS is local-first, review-first and fail-closed.
- imported or generated information is not trusted automatically
- approval is separate from execution
- final confirmation is separate from approval
- stale state is revalidated before controlled execution
- only explicitly allowlisted reversible internal actions may execute
- before/after evidence and audit history are retained
- Emergency Stop remains authoritative
- external, destructive, communication, financial, script and autonomous AI actions remain blocked
The Assistant cannot bypass review, approval, final-confirmation, orchestration or Emergency Stop boundaries.
The Android Companion is intentionally lightweight and was validated on a Samsung Galaxy S9.
Current beta capabilities:
- encrypted local Quick Capture
- offline Pending outbox
- explicit same-LAN pairing with Desktop
- verified acknowledgement before Delivered state
- Desktop intake as untrusted evidence requiring review
- idempotent duplicate handling
- visible failure and explicit manual retry
- read-only Agenda and Waiting-on / Work glance
- privacy-safe opt-in notifications
- conflict handling
- pairing reset and revocation
- no cloud account
- no background sync or automatic sending
The Group 39 checkpoint completed with:
- 187 Core/Desktop tests passed
- 34 Companion tests passed
- Desktop Release build passed
- Android Release build passed
- NuGet vulnerability scan passed
- Gitleaks full-history scan passed across 280 commits with no leaks found
git diff --checkpassed- repository hygiene passed
- manual end-to-end Assistant beta flow passed
- review-only planning and controlled transfer passed
- explicit memory use, revocation and exclusion passed
- mutation, execution and tool refusal passed
- exactly 8 fictional-data screenshot proofs committed
HEADsynchronized withorigin/main- clean working tree
- Group 39 — v7 beta release checkpoint
- Group 38 — memory permissions and safety
- Group 37 — review-only planning and review transfer
- Group 36 — source expansion and answer quality
- Group 35 — Assistant foundation and safety boundary
All public screenshot demonstrations use fictional records. Northstar Systems and Project Zephyr Quill are demonstration identities only.
LifeOS.Desktop/ WPF desktop application
LifeOS.Shared/ shared platform services and storage
src/ core, Companion and supporting projects
tests/ Core/Desktop and Companion regression tests
docs/ status, releases, manual checks and screenshot evidence
tools/validation/ repository hygiene validation
.github/workflows/ continuous integration
- Windows
- .NET 10 SDK
- Android workload only when building the Companion
dotnet restore .\LifeOS.slnx
dotnet test .\LifeOS.slnx
dotnet build .\LifeOS.slnx -c Release
git diff --check
powershell.exe -NoProfile -ExecutionPolicy Bypass `
-File .\tools\validation\Test-RepositoryHygiene.ps1 `
-RepoPath C:\Projects\LifeOSLifeOS v7 is complete and closed at v7.0.0-beta.1.
The Website, documentation extraction, full Mobile application, Group 40 and v8 UI restructuring have not started. Autonomous tools, background Assistant work, external AI actions and operational mutation remain outside the product boundary.
- C#
- .NET 10
- WPF
- .NET MAUI
- local encrypted storage
- GitHub Actions
- evidence-driven release validation
Built by Codie Shannon in Whakatāne, New Zealand.