# Mia Life OS v0.1 Concept

## 1. Overview

Mia Life OS is the life-operating layer connected to MCC.

MCC is the command center for M&T OS and the AI Company. Mia Life OS is the layer that connects Tomoki's daily life, work, side businesses, AI development, FX, field logs, health, and notes into that command center through Mia.

The goal is not to make Tomoki operate more tools.

The goal is:

Tomoki inputs, decides, approves, rejects, changes direction, and creates new project ideas.

Mia organizes, routes, reports, and keeps context.

Codex implements, fixes, tests, and maintains systems.

AI Workers research, write, sell, analyze, review, and document.

Everything flows back into MCC.

## 2. Roles

### CEO: Tomoki

Responsibilities:

- decide purpose
- create direction
- approve or reject
- change direction
- create new project ideas

Tomoki should avoid becoming the operator, researcher, implementer, or administrator unless a CEO approval gate is reached.

### COO: Mia

Responsibilities:

- receive rough input
- classify and prioritize
- route work to the right AI worker
- maintain context
- prepare reports
- protect CEO time
- decide what should become a project, business lane, task, or memory

Mia turns life events and ideas into company operations.

### CTO: Codex

Responsibilities:

- system design
- implementation
- refactoring
- tests
- Git
- deployment preparation
- technical review

Codex turns Mia's operating design into working systems.

### AI Workers

Responsibilities:

- Research AI: market, product, technical, and FX research
- Documentation AI: reports, templates, docs, handoff notes
- Finance AI: revenue, cost, ROI, FX and business metrics
- Operations AI: schedules, checklists, workflows, follow-up
- QA / Review AI: tests, review, risk checks
- Sales / Writing AI: proposals, sales messages, application drafts

AI Workers are employees, not tools.

## 3. Target Areas

Mia Life OS starts with these areas:

- field logs
- inventory management
- MCC updates
- CrowdWorks applications
- sales prospect lists
- YouTube planning
- FX research
- daily notes
- health and life logs

These areas should not become separate command centers. They should become inputs, modules, projects, business lanes, or memory inside MCC.

## 4. Information Flow

Default flow:

Inbox -> Mia classification -> AI worker assignment -> work / research / draft -> Mia review -> CEO approval -> execution / archive / next project

Detailed flow:

1. Tomoki enters a rough note, question, instruction, or idea.
2. Mia classifies it as Life, Work, Business, AI Development, FX, Field Log, Health, or Other.
3. Mia decides whether it is:
   - answer now
   - save to memory
   - create Smart Inbox record
   - create Codex Handoff
   - create Proposal
   - route to AI Worker
   - wait for CEO approval
4. AI Workers execute zero-cost work first.
5. Mia summarizes results.
6. Tomoki approves, rejects, changes direction, or creates a new idea.

## 5. Inbox -> Classification -> AI Workers -> CEO Approval

Mia Life OS uses one input principle:

Tomoki should not decide the tool first.

Tomoki talks to Mia first.

Examples:

- "今日の現場で気づいたこと"
- "この在庫管理を売れる形にしたい"
- "クラウドワークスでGAS案件を探して"
- "FXで今週見るべき材料をまとめて"
- "体調悪いから作業量を軽くしたい"
- "YouTubeのネタを10個出して"

Mia decides the route.

CEO approval is required only for:

- added cost
- external publication
- API key / secret / OAuth / permission expansion
- data migration or destructive changes
- constitution or organization changes
- final delivery approval

## 6. Current Capabilities

MCC already provides foundations for Mia Life OS:

- CEO Office for daily operation
- Unified Mia Input
- Smart Inbox
- Codex Handoff
- Codex Handoff Queue and batches
- Project Registry
- Business Registry
- Organization / Department Registry
- Worker Registry
- Infrastructure Dashboard
- Google OAuth authorization state
- Version5 Business OS Foundation
- Revenue lanes and business pipeline
- Manual-first, zero-cost operation

Mia Life OS v0.1 should use these existing pieces before adding new systems.

## 7. Future Vision

Mia Life OS should become the layer where AI blends into Tomoki's daily life.

Future direction:

- daily CEO briefing based on work, business, health, and life state
- field log automation
- inventory sales workflow
- CrowdWorks application workflow
- sales prospect research and proposal drafting
- YouTube idea to script to publish pipeline
- FX research and decision support
- health-aware work planning
- Google Docs / Sheets memory layer
- personal/company memory unification
- AI Workers that keep working while Tomoki only reviews outcomes

Long-term vision:

Tomoki and AI operate as one living company.

MCC remains the command center.

Mia Life OS becomes the daily interface between Tomoki's life and the AI Company.

## 8. Roadmap

### v0.1: Concept and Scope

- define Mia Life OS purpose
- define CEO / COO / CTO / AI Worker roles
- define target areas
- define information flow
- add this concept document to MCC
- keep implementation out of scope

### v0.2: Life Inbox Design

- design Life / Work / Business / AI Development / FX / Health classification
- define how Unified Mia Input routes life notes
- define memory types and privacy boundaries

### v0.3: Life Memory

- define daily notes, health logs, work notes, and business memory
- prepare Google Docs / Sheets storage model
- keep LocalStorage fallback

### v0.4: AI Worker Routing

- map target areas to departments and AI Workers
- define zero-cost worker tasks
- define CEO approval gates for external actions

### v0.5: Daily Briefing

- morning: today, approvals, risks, energy, focus
- evening: completed, blocked, tomorrow, business progress

### v0.6: Business Workflows

- CrowdWorks application drafts
- sales list preparation
- inventory offer preparation
- field log productization

### v0.7: FX / Research Workflows

- market watch structure
- FX research logs
- risk and decision notes
- no automated trading by default

### v0.8: Health-Aware Operations

- health and life logs
- workload adjustment suggestions
- rest and focus recommendations

### v0.9: Integrated Review

- CEO Office shows life + company state without overload
- Mia Assistant can answer life/project/business questions
- AI Workers can propose improvements

### v1.0: Life OS Foundation

- Tomoki can use Mia as the single daily interface
- MCC aggregates life, work, business, AI development, FX, and logs
- AI Workers continue work with Tomoki focused on approval and direction

## 9. Boundary With M&T OS

M&T OS remains the top-level operating constitution and company OS.

MCC remains the command center.

Mia Life OS is not a replacement for MCC.

Mia Life OS is the daily-life layer that feeds MCC and lets Tomoki operate life and business through Mia.

The design must never increase CEO operations. If Tomoki has to manage more screens or decide technical routing manually, Mia Life OS has failed.