Skip to content

Repository files navigation

LifeOS

A local-first personal and work operating system for turning work, money, projects, evidence, household activity, integrations, AI review and daily pressure into visible, reviewable state.

LifeOS is a safety-first platform built by Codie Shannon around purpose-built Desktop, Full Mobile, Mobile Companion and Website products. It is an operations system for controlled review, execution, provenance and evidence—not a generic task list or template.

Current checkpoint: LifeOS v28.0.0-alpha.22 completes the approved configuration-free development lane through Group 208. Provider Consent & Permission Profiles add explicit purpose, capability, approval, pause, revocation and expiry without enabling OAuth, credentials or provider access. Configuration, credentialed integration testing, signing, deployment and owner acceptance remain release gates.

LifeOS v28 CV Builder Foundation

Product status

Product Status
LifeOS Desktop Configuration-free development complete through Group 208, including ordinary-mode Provider Consent, Provider Adapter Registry, Connection Health, Configuration Readiness, Device Transfer Review, Local Account & Sync, Relationships, Focus Timer, Agenda, Weekly Review, Life, Household, Documents, Money Pressure, Work Time and Projects, validated forms, actionable problems and local-data recovery
LifeOS Full Mobile Purpose-built Android application aligned through Group 132, including opportunity capture, career review and derivative sharing
LifeOS Mobile Companion Separate lightweight companion product; beta complete and closed
LifeOS Website Product, documentation, onboarding, factual portfolio and release-candidate evidence surface
Shared Core Authoritative contracts, deterministic validation, read models, provenance, audit, conflict and safety boundaries
Current release lane v28 configuration-free development complete through SG-208 Pack 2; external configuration and release gates remain

Full Mobile and Mobile Companion are separate products. They can share contracts and libraries, but retain different scope, UX and release tracks.

What LifeOS brings together

  • Command Centre pressure and priority visibility
  • work records, sessions, billable time, projects, next actions and proof linkage
  • money records, invoices, payments, financial review and reports
  • document and evidence intake with original preservation
  • agenda, daily state, household, grocery and shared-routine workflows
  • relationship, communication and follow-up context
  • Google and Microsoft provider foundations with review-first integration intake
  • guarded provider contracts, explicit approval boundaries and audit
  • native deterministic intelligence plus optional provider-backed AI review
  • scheduled-communication proposals without silent or automatic sending
  • Career Studio opportunity, application, materials and preparation flows
  • documentation, packaging, validation and closed-beta readiness tooling
Important information becomes visible state.
State affects pressure.
Pressure feeds review.
Review controls action.
Evidence preserves trust.

Product surfaces

Desktop

The deep administration surface for detailed review, filtering, reporting, audit, evidence and planning across Work, Career, Money, Life, Household, Projects, integrations, Assistant and Settings.

Full Mobile

A separate .NET Android application—not a responsive copy of Desktop—for quick capture, review, execution, status and queued offline actions.

Mobile Companion

A lighter product for local quick capture, pairing, delivery acknowledgement, notifications and review-first Desktop intake. It is not interchangeable with Full Mobile.

Website

The product, documentation and evidence foundation. Website packaging, onboarding and the cross-product release-candidate gate are complete through Group 120.

Current capability lanes

  • Work and operating day: work sessions, billable records, timesheet proof and operating-day review.
  • Money and documents: trusted local financial records, preserved evidence, review-first extraction and derivative reporting/export.
  • Career Studio: opportunity and application pipelines, evidence-backed materials, interview preparation and bounded analytics.
  • Household and Grocery: inventory, meals, stores, recurring essentials, shared routines, receipt candidates and spending review.
  • Provider integrations: normalized, source-backed candidates with explicit review, duplicate detection, conflict handling and provenance.
  • Guarded provider contracts: permission, preview, confirmation, audit, cancellation and Emergency Stop boundaries; external writes remain disabled at the current checkpoint.
  • Native intelligence and optional AI: deterministic local insights remain primary; external AI is optional, bounded and review-first.
  • Scheduled communications: proposals, timing, readiness and audit are modeled without automatic sending or autonomous messaging.
  • Product readiness: documentation and packaging hub, closed-beta baseline, release proof and validation tooling.

Safety model

LifeOS is local-first, review-first and fail-closed.

  • Imported or generated information is not trusted automatically.
  • Trust promotion and authoritative linking require explicit review.
  • Conflicts preserve both versions until explicit resolution.
  • Provider access is bounded; external writes remain disabled.
  • No autonomous financial posting, payment initiation, career applications, messaging, grocery ordering or destructive evidence handling.
  • Original documents and evidence are preserved; exports and previews are derivatives.
  • Provenance, freshness, confidence and audit history remain visible where relevant.
  • AI cannot silently mutate authoritative LifeOS state.

Evidence

Official evidence is stored under docs/screenshot-groups/. The standard target is eight approved screenshots per screenshot group; a group may document a smaller genuine-capture override when the available product surfaces do not support eight distinct truthful views.

Recent evidence:

All public demonstrations must use fictional, sanitized or explicitly approved proof data.

Repository structure

LifeOS.Desktop/       WPF desktop application
LifeOS.Shared/        shared platform services and storage
src/LifeOS.Core/      domain contracts, services and deterministic rules
src/LifeOS.Mobile/    full Android mobile application
src/LifeOS.Companion/ lightweight Android companion application
src/LifeOS.Website/   public website and documentation surface
tests/                Core, Mobile, Companion and Website regression tests
docs/                 status, release notes, manual tests and screenshot evidence
tools/                validation, packaging and evidence helpers
.github/workflows/    continuous integration

Build and validate

Requirements:

  • Windows
  • .NET 10 SDK
  • Android workload when building mobile projects
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\LifeOS

Current development boundary

LifeOS v28.0.0-alpha.22 completes configuration-free development through Group 208. Provider Consent & Permission Profiles now has a real ordinary-mode local workspace on the shared storage, forms and problem-state spine. SG-208 Pack 2 is closed with exact, inspected product and validation evidence. SG-128 visible Pack 2 evidence remains open; v27 release-candidate evidence remains preserved in SG-120.

Author

Built by Codie Shannon in Whakatane, New Zealand.

About

Local-first personal and work operating system with Windows Desktop, full Android mobile, review-first integrations, evidence-backed intelligence and explicit safety controls.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages