{"id":49338844,"url":"https://github.com/jasonhnd/life_os","last_synced_at":"2026-05-31T13:00:33.519Z","repository":{"id":348885697,"uuid":"1200195750","full_name":"jasonhnd/life_OS","owner":"jasonhnd","description":"🏛️ Manage your life with a 1,400-year-old governance framework. 15 AI agents with separation of powers — Three Departments \u0026 Six Ministries personal cabinet system. Works on Claude Code, ChatGPT, Gemini, Cursor, and 30+ platforms.","archived":false,"fork":false,"pushed_at":"2026-05-30T14:21:20.000Z","size":4539,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-05-30T16:07:08.629Z","etag":null,"topics":["agent-skills","ai-agents","checks-and-balances","claude-code","decision-making","gtd","life-management","multi-agent","notion","personal-management","prompt-engineering","second-brain","tang-dynasty"],"latest_commit_sha":null,"homepage":"https://agentskill.sh/jasonhnd","language":"Makefile","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jasonhnd.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":"AGENTS.md","dco":null,"cla":null}},"created_at":"2026-04-03T06:18:37.000Z","updated_at":"2026-05-30T14:21:23.000Z","dependencies_parsed_at":null,"dependency_job_id":"58b3f3cd-0458-489c-aaed-27b28f713493","html_url":"https://github.com/jasonhnd/life_OS","commit_stats":null,"previous_names":["jasonhnd/life_os"],"tags_count":51,"template":false,"template_full_name":null,"purl":"pkg:github/jasonhnd/life_OS","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jasonhnd%2Flife_OS","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jasonhnd%2Flife_OS/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jasonhnd%2Flife_OS/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jasonhnd%2Flife_OS/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jasonhnd","download_url":"https://codeload.github.com/jasonhnd/life_OS/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jasonhnd%2Flife_OS/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33731998,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-05-31T02:00:06.040Z","response_time":95,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agent-skills","ai-agents","checks-and-balances","claude-code","decision-making","gtd","life-management","multi-agent","notion","personal-management","prompt-engineering","second-brain","tang-dynasty"],"created_at":"2026-04-27T03:00:23.987Z","updated_at":"2026-05-31T13:00:33.503Z","avatar_url":"https://github.com/jasonhnd.png","language":"Makefile","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cdiv align=\"center\"\u003e\n\n# Life OS\n\n### Your decisions deserve more than one voice. Now in your language, your culture.\n\n---\n\n[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)\n[![Claude Code](https://img.shields.io/badge/Claude%20Code-Skill-green.svg)](https://code.claude.com/docs/en/skills)\n[![skills.sh](https://img.shields.io/badge/skills.sh-Compatible-yellow.svg)](https://skills.sh)\n[![Version](https://img.shields.io/badge/version-1.9.1.1-brightgreen.svg)](CHANGELOG.md)\n\n[Install in 30 seconds](#installation) · [How it works](#how-it-works) · [See it in action](#see-it-in-action) · [Architecture](#under-the-hood)\n\n🌍 [English](README.md) · [中文](i18n/zh/README.md) · [日本語](i18n/ja/README.md)\n\n\u003c/div\u003e\n\n---\n\n\u003e **Architecture as of v1.9.0**: Life OS is 100% markdown — agent prompts,\n\u003e slash commands, eval scenarios, RFC documents. No Python (`tools/` removed\n\u003e in v1.8.1 Wave 2), no bash hooks (`scripts/hooks/*.sh` retired in v1.8.5),\n\u003e no .yml schema files (v1.8.7 md-only ontological commit per DR-10).\n\u003e Runtime enforcement happens via inline LLM procedures driven by spec.md\n\u003e reading + grep matching. **Hermes Local** was the original name for the\n\u003e v1.6-v1.8.0 bash hook + Python tools layer; that layer no longer exists.\n\u003e Pattern provenance preserved: forked from\n\u003e [NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent)\n\u003e under the MIT License.\n\u003e\n\u003e Historical sections below (v1.8.3 / v1.8.0 / v1.6.3a \"What's New\") may\n\u003e reference `bash scripts/setup-hooks.sh` and similar — those steps are\n\u003e **no-op since v1.8.5** (hook layer retired). For current setup, run\n\u003e `/install-agents` in Claude Code (one slash command, replaces all\n\u003e historical bash setup scripts).\n\n## One engine. Nine worlds. Your call.\n\nLife OS installs into your AI terminal (Claude Code, Gemini CLI, or Codex CLI) and transforms it into a **personal cabinet** — multiple independent AI agents that analyze your decisions from every angle, argue with each other, and hold both the plan *and you* accountable.\n\nThe decision engine is the same for everyone: plan, review, veto, execute, audit. What changes is the world it speaks.\n\nWhen you first start a session, you pick a theme:\n\n```\n🎨 Choose your theme:\n\nEnglish:\na) 🏛️ Roman Republic — Consul, Tribune, Senate\nb) 🇺🇸 US Government — Chief of Staff, Attorney General, GAO\nc) 🏢 C-Suite — CEO, General Counsel, CFO\n\n中文:\nd) 🏛️ 三省六部 — 丞相、中书省、门下省\ne) 🇨🇳 中国政府 — 国务院总理、发改委、人大常委会\nf) 🏢 公司部门 — 总经理、战略规划部、法务合规部\n\n日本語:\ng) 🏛️ 明治政府 — 内閣総理大臣、参議、枢密院\nh) 🏛️ 霞が関 — 内閣官房長官、内閣法制局、財務省\ni) 🏢 企業 — 社長室、経営企画部、法務部\n\nType a-i\n```\n\nHere is the same decision — \"Should I leave my job?\" — through all three:\n\n```\n  三省六部                  霞が関                    C-Suite\n  ─────────                ─────────                ─────────\n  📜 中书省 起草方案         📜 内閣府 起案             📜 VP Strategy drafts plan\n  🔍 门下省 封驳：           🔍 内閣法制局 差し戻し：     🔍 General Counsel vetoes:\n     \"财务跑道未解决\"          \"財務的余裕が不明\"          \"Runway not addressed\"\n\n  💰 户部  5/10            💰 財務省  5/10            💰 CFO  5/10\n  ⚔️ 兵部  6/10            ⚔️ 防衛省  6/10            ⚔️ VP Ops  6/10\n  ⚖️ 刑部  4/10            ⚖️ 法務省  4/10            ⚖️ CCO  4/10\n\n  🔱 御史台 审核             🔱 会計検査院 監査           🔱 Internal Audit audits\n  💬 谏官 追问你             💬 内閣参与が問い返す      💬 Exec Coach challenges you\n\n  📋 奏折: 5.8/10          📋 閣議決定書: 5.8/10       📋 Executive Brief: 5.8/10\n```\n\nNine different worlds. Identical rigor underneath. Each language offers three governance styles — historical, modern government, and corporate — so every user finds a voice that fits. A Japanese user picks between Meiji-era ministers, Kasumigaseki bureaucrats, or corporate departments. An English user chooses Roman senators, US federal officials, or C-Suite executives. A Chinese user selects Tang Dynasty mandarins, modern State Council roles, or corporate divisions.\n\n**Theme determines language.** After you pick a theme, every word of output — every agent, every report, every response — is in that theme's language. Chinese for 三省六部. Japanese for 霞が関. English for C-Suite. No mixing, no exceptions.\n\n**Theme is per-session.** Each terminal window can use a different theme independently. You can switch mid-session at any time by saying \"switch theme\" (or \"切换主题\" or \"テーマ切り替え\"). The engine never changes — only the voice.\n\n**Auto-inference from trigger words.** Say \"上朝\" and the 三省六部 theme loads automatically (唐朝-specific). Say \"閣議開始\" and the 霞が関 theme loads (modern government-specific). Generic triggers like \"开始\", \"はじめる\", or \"start\" show that language's three sub-choices — because the word alone does not distinguish historical, government, or corporate.\n\n\u003e **Not role-playing.** Each agent runs as a real, isolated subagent. They cannot see each other's reasoning. They score independently. They disagree.\n\n---\n\n## Current Status\n\nLife OS is now a markdown-only, GitHub-backed decision system. The current user path is natural language first: after installation, say what you want to do, and ROUTER maps it to the right workflow. Slash commands remain as setup and maintenance plumbing, not the daily interface.\n\nFor release history, use [`CHANGELOG.md`](CHANGELOG.md) and [`docs/reference/version-history.md`](docs/reference/version-history.md). Old v1.6-v1.8 architecture notes live under [`docs/history/`](docs/history/); they are preserved for context but are not the current operating guide.\n## How it works\n\nLife OS rests on five pillars. The **decision engine** is the core — everything else grows from it.\n\n---\n\n### I. The Decision Engine — Plan, Review, Veto, Execute, Audit\n\nThe engine runs multiple agents organized around a principle that is 1,400 years old: **no single voice goes unchecked**. The theme gives those agents names from your culture. The logic is always the same.\n\n#### The multiple agents\n\n| Agent | Function |\n|-------|----------|\n| ROUTER | Your primary entry point — handles casual chat, routes complex matters to the engine |\n| PLANNER | Breaks your situation into 3-6 dimensions and builds a structured plan |\n| REVIEWER | Independent review with emotional audit, 10/10/10 regret test, SOUL consistency check, red-team challenge, and **veto power** (max 2 rounds) |\n| DISPATCHER | Detects dependencies between domains, dispatches parallel or sequential execution |\n| PEOPLE | Relationships, stakeholders, team dynamics |\n| FINANCE | Money, assets, risk exposure |\n| GROWTH | Learning, personal brand, communication |\n| EXECUTION | Action plans, logistics, timelines |\n| GOVERNANCE | Rules, risk, compliance, self-discipline |\n| INFRA | Health, energy, living environment, digital infrastructure |\n| AUDITOR | Audits the agents' work quality after every flow |\n| ADVISOR | Audits *you* — surfaces behavioral patterns across your decisions |\n| COUNCIL | Cross-domain debate — auto-triggers when domain scores differ by 3+ points |\n| RETROSPECTIVE | Session start: sync, briefing, strategic overview |\n| ARCHIVER | Session close: archive, knowledge extraction, DREAM, sync |\n| STRATEGIST | Hall of Wisdom — 93 thinkers across 18 domains, 3 dialogue modes |\n\nEvery major decision passes through three stages. No shortcuts.\n\n**Draft** — The PLANNER breaks your situation into dimensions and builds a plan.\n\n**Review** — The REVIEWER examines the plan independently. It runs an emotional audit: *Is fear driving this? Will your family support it? Will you regret this in 10 minutes, 10 months, 10 years?* It checks alignment with your SOUL (values archive), your wiki (established knowledge), and your strategic map (cross-project impact). It red-teams the weakest assumption. If it finds a blind spot, it sends a veto — the plan goes back for revision. Maximum two veto rounds; the third pass must be approved.\n\n**Execute** — Six domain analysts each score the plan 1-10 from their domain, independently:\n\n| Domain | What it covers | The question it asks |\n|--------|---------------|---------------------|\n| People | Relationships, stakeholders | \"Are the right people involved?\" |\n| Finance | Money, assets, resources | \"Can you afford this — including the worst case?\" |\n| Growth | Learning, expression, culture | \"What do you need to learn first?\" |\n| Execution | Action, logistics, timelines | \"What's the concrete plan, week by week?\" |\n| Governance | Rules, risk, compliance | \"What happens if everything goes wrong?\" |\n| Infrastructure | Health, energy, environment | \"Can your body and environment sustain this?\" |\n\nEach domain has **four specialized divisions**. Finance, for example, has Income (salary, side income), Spending (budgets, habits), Assets (investments, real estate), and Reserves (emergency fund, insurance, retirement). The DISPATCHER routes to the right divisions automatically.\n\nAfter all six report, the REVIEWER does a final review — and if scores conflict by 3+ points, the COUNCIL convenes a structured three-round debate. Then the composite Summary Report is produced. The AUDITOR checks the agents' work (\"The execution plan has no milestones past month 3 — flag it\"). The ADVISOR turns to *you*: \"You've avoided addressing finances in your last four decisions. Why?\"\n\nHere is what the full flow looks like:\n\n```\nYou: \"I'm thinking about leaving my job to start something new.\"\n\n    Draft\n    📜 Planner          → Breaks it into 6 dimensions, builds the plan\n\n    Review\n    🔍 Reviewer         → Emotional audit: running away or running toward?\n                          10/10/10 test: will you regret this in 10 years?\n                          SOUL check: aligned with your stated values?\n                          Veto: \"Financial runway not addressed. Revise.\"\n\n    Execute  (after revision passes review)\n    👥 People     7/10   \"Co-founder chemistry is untested\"\n    💰 Finance    5/10   \"18 months runway, but only if nothing goes wrong\"\n    📖 Growth     8/10   \"Strong domain expertise, credibility is real\"\n    ⚔️ Execution  6/10   \"No milestone plan past month 3\"\n    ⚖️ Governance 4/10   \"Non-compete clause needs legal review\"\n    🏗️ Infra      7/10   \"Health is good, but stress plan is vague\"\n\n    Audit\n    🔱 Auditor          → \"Execution plan is vague past month 3 — request revision\"\n    💬 Advisor          → \"You've been consuming startup content for weeks.\n                           Confirmation bias is likely. When did you last\n                           seriously consider staying?\"\n\n    📋 Final Report     → Composite: 6.2/10 — Proceed with conditions\n```\n\n#### Express analysis\n\nNot every request needs a full court process. The ROUTER handles casual chat, quick questions, and emotional support directly. For questions that need domain expertise but are not decisions — say, \"what tax rules apply to freelancers?\" — an **express path** sends it to 1-3 relevant domain analysts directly, skipping the PLANNER, REVIEWER, AUDITOR, and ADVISOR. Quick answer, then: \"This was an express analysis. Want the full deliberation?\"\n\n---\n\n### II. The Hall of Wisdom — 93 Thinkers Across 18 Domains\n\nSome questions do not have a \"correct answer.\" They need perspective.\n\nThe STRATEGIST gives you access to **93 of history's greatest thinkers across 18 domains** — from Socrates to Buffett, Laozi to Mandela, Dostoevsky to Feynman. Each one runs as a real subagent with their own voice, their own examples, their own way of pushing you.\n\n**Three modes:**\n\n- **One-on-one** — Deep dialogue with a single thinker. Socrates will not let you off easy.\n- **Roundtable** (2-4 thinkers) — Multiple thinkers discuss your question, each from their worldview. Watch Seneca and Wang Yangming find unexpected common ground.\n- **Debate** (2 thinkers) — Two thinkers with opposing views argue directly over three structured rounds. You judge.\n\n```\nYou: \"I keep starting things and never finishing them.\"\n\nStrategist: Recommended — Seneca (on time) + Wang Yangming (on action)\n\nSeneca: \"You do not lack time. You waste it on things you have not\n         examined. Which of your current pursuits would you begin again,\n         knowing what you know now?\"\n\nWang Yangming: \"Knowledge and action are one. If you truly knew what you\n                wanted, you would already be doing it. The gap between\n                knowing and doing is the gap between wanting and truly\n                wanting.\"\n\n→ Parting words from each thinker\n→ Summary of your thinking journey saved to your knowledge base\n```\n\n**18 domains**: Philosophy, Eastern Thought, Science, Strategy, Business, Psychology, Systems, Human Nature, Civilization, Adversity, Aesthetics, Politics, Economics, Mathematics, Medicine, Exploration, Communication, Law.\n\nYou can name **anyone** not on the built-in list — any historical figure — and the STRATEGIST will honor the request with equal depth. If your SOUL archive exists, the STRATEGIST uses it to recommend thinkers who address your specific tensions and contradictions.\n\n---\n\n### III. Second Brain — Nothing Disappears When the Session Ends\n\nEvery decision, insight, pattern, and action item is written to a **persistent knowledge base** — structured markdown files that you own, in a storage system you choose.\n\n```\nsecond-brain/\n├── SOUL.md                 # Who you are — values, identity, aspirations\n├── user-patterns.md        # How you behave — the advisor's observations\n├── inbox/                  # Quick captures from your phone\n├── meta/\n│   ├── STATUS.md           # Global status dashboard\n│   ├── STRATEGIC-MAP.md    # Relationships between projects\n│   ├── strategic-lines.md  # Strategic line definitions\n│   ├── journal/            # Session reports, DREAM reports\n│   └── outbox/             # Session staging area (one subdirectory per session)\n├── projects/{name}/        # Active projects with tasks + decisions\n├── areas/{name}/           # Ongoing life areas with goals\n├── wiki/                   # Reusable knowledge — grows from DREAM\n└── archive/                # Completed work\n```\n\n**GitHub-backed storage** — a single git repository:\n\n| Layer | What it is |\n|-------|------------|\n| **Local working copy** | The files on disk — also your Obsidian vault. Where you read and write. |\n| **GitHub remote** | Backup + cross-device sync. `git push` at session close, `git pull` at session start. |\n\nIt's just git. Versioning, backup, and multi-device sync come for free — there's no separate sync engine, no primary/mirror split, no conflict-resolution layer. (Google Drive + Notion were removed; storage is GitHub-only.)\n\n**Cross-device sync**: Edit on your laptop, `git push`. Sit down at your desktop, start a session, and the system `git pull`s the changes in. Conflicts are ordinary git merge conflicts — rare for a single-user vault.\n\n**Parallel sessions**: Work on project-alpha in one terminal window, project-beta in another. Each session writes to its own outbox directory. The next time you start a session, everything merges cleanly — no conflicts, no locks.\n\n**First-run setup**: On your very first session, the system detects that no second-brain exists and walks you through creating one — it initializes the git repo (local working copy + optional GitHub remote) and the full directory structure automatically.\n\n---\n\n### IV. Strategic Map — See the Whole Board\n\nYou are good at thinking about individual projects. You are probably bad at seeing how they connect — which ones feed into each other, which ones compete for your time, and what happens to the rest when one stalls.\n\nStrategic Map adds the relationship layer.\n\n**Strategic Lines** — Group projects by the purpose they serve. Each line has a stated purpose *and* a driving force (what actually motivates you — these can differ, and that tension is worth examining). Health signals define what to watch. Multiple projects can serve one line with different roles: critical-path (if this stalls, the line stalls), enabler (must complete first), accelerator (makes it faster), insurance (plan B).\n\n**Flow Graph** — Define what flows between projects: knowledge, deliverables, decisions, relationship capital. When a decision in one project invalidates another project's assumptions, the system flags it immediately. When knowledge flows are defined but no wiki entries actually carry the knowledge, that is a broken flow.\n\n**Health Archetypes** — No abstract numerical scores. The system matches each project to a pattern — steady progress, controlled wait, momentum decay, uncontrolled stall, direction drift, or dormant — and writes a narrative: what is happening, what it means, what to do.\n\n**Blind Spot Detection** — Actively looks for what is *missing*: unaffiliated projects (not assigned to any strategic line), broken flows (defined but not flowing), driving force neglect (behavior misaligned with what you say matters), dimension gaps (entire life areas absent from all strategic lines), and approaching deadlines with no preparation.\n\nYour morning briefing becomes strategic:\n\n```\n🗺️ Strategic Overview\n\n💰 market-expansion                       🟡 Controlled wait\n   project-alpha    critical-path    ⏸ on-hold (legal review)\n   project-beta     enabler          🟢 active\n\n   The legal review creates a natural window.\n   → Push project-beta prep work (2-3h) — high leverage, low risk.\n\n⚡ Today\n🥇 Push project-beta prep — exploit the waiting period\n🟢 Safe to ignore: project-gamma (on track), side-project (non-critical)\n❓ Decide: project-delta is unaffiliated — which strategic line does it serve?\n```\n\nStrategic Map integrates with SOUL (are your driving forces aligned with your values?), Wiki (do the knowledge flows actually carry real knowledge?), and DREAM (the sleep cycle uses the flow graph to discover cross-layer insights).\n\nStrategic Map grows from zero. If you have not defined any strategic relationships, the system operates normally with a flat project list. After a few sessions with multiple projects, DREAM may propose: \"You have N active projects but no strategic relationships defined. Would you like to map how they relate?\"\n\n---\n\n### V. SOUL + DREAM + Wiki — The System Learns Who You Are (v1.6.2: now fully automatic)\n\n**SOUL** records who you are — not what you do, but what you value, what you believe, and who you aspire to be. Each entry has two sides: what IS (observed from your decisions) and what SHOULD BE (your stated aspiration). The gap between them is where growth happens.\n\n**Auto-writes, with you in control** (v1.6.2). The system no longer asks you to confirm every entry. ADVISOR runs after every decision and increments evidence or challenges on existing SOUL dimensions. When a new value pattern accumulates 2+ pieces of evidence, SOUL auto-writes a new dimension at low confidence (0.3) — with the \"What SHOULD BE\" field deliberately left empty for you to fill in when you're ready. You stay in charge: edit freely, delete dimensions that don't fit, or say \"undo recent SOUL\" to roll back.\n\n**Every session starts with a SOUL Health Report** — fixed position at the top of the briefing. Current profile with trend arrows, newly auto-detected dimensions awaiting your input, conflict warnings (dimensions your last 3 decisions all challenged), and dormant dimensions (30+ days without activation). You see the system's model of you every single time.\n\nREVIEWER references SOUL in every decision. If a decision challenges a stated value, it surfaces the contradiction instead of rubber-stamping.\n\n**DREAM** is the AI sleep cycle. After every session ends, the system \"sleeps\" — inspired by human sleep architecture:\n\n- **Light sleep (N1-N2)** — Organize loose ends: classify unprocessed inbox items, flag expired tasks, detect orphan files\n- **Deep sleep (N3)** — Consolidate: extract Wiki knowledge and update SOUL dimensions from the last 3 days of activity\n- **REM (creative connections + 10 auto-triggers)** — Discovers cross-domain links you have not noticed, and automatically acts on 10 specific patterns: new project relationships, behavior diverging from stated values, wiki contradictions, dormant SOUL dimensions, unused cross-project cognition, decision fatigue, value drift, stale commitments (*\"30 days ago you said you would do X — what happened?\"*), emotional-state decision clusters, and repeated identical decisions (*\"You're deciding X for the 4th time — are you avoiding commitment?\"*)\n\nAll triggered actions flow into the next session's briefing in a fixed \"DREAM Auto-Triggers\" block. Next morning: *\"Last session I noticed you're deciding the contract question again — this is the 3rd time. What's actually blocking you?\"*\n\n**Wiki** captures reusable knowledge about the world — not about you. After every session, the ARCHIVER auto-writes wiki entries that pass all 6 strict criteria: cross-project reusable, about the world (not you), **zero personal privacy** (no names, amounts, IDs, or traceable details — if stripping privacy makes the conclusion meaningless, it's discarded), factual/methodological, ≥2 independent evidence points, no contradiction with existing entries. Personal material belongs in SOUL; reusable knowledge belongs in Wiki. The two never mix.\n\nAll three systems grow from zero. On day one, the system knows nothing about you. It learns only from your decisions and observations — and it now learns continuously, not just when you ask.\n\n---\n\n## See it in action\n\n### Start your day\n\n```\nYou: Start session.\n\n🌅 Session Start:\n   Pick your theme: a-i (3 per language — historical / government / corporate)\n\nYou: b\n\n🌅 定例閣議:\n   Syncing second-brain... git pull: 3 changes.\n   📥 \"Look into certification programs\" — captured yesterday on phone\n   📥 \"project-alpha: supplier replied\" — forwarded from email\n   📥 Quick note: \"revisit budget assumptions\"\n\n   🗺️ Strategic overview: [see Strategic Map above]\n\n   💤 DREAM report: Last session noticed your wiki entry on negotiation\n      tactics could apply to the supplier conversation in project-alpha.\n\n   📋 Recommended: Process supplier reply first (time-sensitive).\n```\n\nBehind the scenes, the session boot sequence ran 18 steps: theme resolution, directory detection, data layer check, git health check, full sync pull, outbox merge, platform and version check, project binding, context loading (user-patterns, SOUL, STATUS, lint state, project context, global overview), Strategic Map compilation, DREAM report presentation, wiki health check, and the final briefing.\n\n### Make a decision\n\n```\nYou: I'm considering switching from full-time to freelance.\n→ 2-3 rounds of intent clarification (cannot be skipped — HARD RULE)\n→ Full engine flow: draft → review (with possible veto) → execute (6 domains\n  in parallel, each displayed as it completes) → final review → Summary Report\n  → audit → advisor\n→ Report: 5.8/10 — \"Viable but timing is premature. Revenue runway\n   is 11 months, not the 18 you assumed. Recommendation: build 3 more\n   months of savings and one anchor client before transitioning.\"\n```\n\n### Think deeply\n\n```\nYou: I keep saying yes to things I don't care about.\n→ ROUTER detects abstract thinking need, asks: \"Would you like to activate\n  the Strategist?\"\n→ One-on-one with Marcus Aurelius on priorities and refusal\n→ Parting words, journey summary, insights saved to second-brain\n```\n\n### End your day\n\n```\nYou: End session.\n\n📝 Archiver:\n   Phase 1 — Archive: decisions, tasks, journal → outbox\n   Phase 2 — Knowledge extraction (auto-write under strict criteria):\n     🔮 SOUL auto-written: \"Values autonomy over stability\" — confidence 0.3\n        (evidence: 2 decisions this session; \"What SHOULD BE\" left empty for you)\n     📚 Wiki auto-written: \"Freelance runway formula\" → wiki/career/\n        (passes 6 criteria + privacy filter: zero personal details)\n     ❌ 1 wiki candidate discarded — contained personal amount, couldn't strip\n   Phase 3 — DREAM:\n     💤 N1-N2: 2 inbox items need classification\n     💤 N3: new evidence for \"deliberate decision-maker\" dimension (+1)\n     💤 REM: 🚨 Stale commitment detected — 32 days ago you said you would\n            draft the freelance plan. Triggered for next session's briefing.\n   Phase 4 — Sync: git add + commit + push... done.\n   ✅ Completion checklist verified. Session archived.\n   ↩️ To undo any auto-write: delete the file, or say \"undo recent wiki/SOUL\"\n      next session.\n```\n\n---\n\n## 12 Standard Scenarios\n\nLife OS comes pre-configured for the decisions people actually face:\n\n| # | Scenario | Domains involved | What the reviewer asks |\n|---|----------|-----------------|----------------------|\n| 1 | Career transition | All Six | \"Running away or pursuing something?\" |\n| 2 | Investment decisions | Finance, Execution, Governance, People | \"FOMO or rational? Can you survive total loss?\" |\n| 3 | Relocation | All Six | \"Do you really know the destination?\" |\n| 4 | Annual planning | All Six | \"Too many goals? Measurable? Aligned with values?\" |\n| 5 | Startup decisions | All Six | \"Solving a real pain point? Are you the right person?\" |\n| 6 | Major purchases | Finance, Execution, Governance | \"Need or want? Would you still want it in a month?\" |\n| 7 | Relationships | People, Infra, Governance, Growth | \"Are you evaluating the other person with bias?\" |\n| 8 | Periodic reviews | Retrospective | Daily, weekly, monthly, quarterly, yearly |\n| 9 | Health management | Infra, Execution, Finance, Governance | \"Sustainable, or another short burst?\" |\n| 10 | Learning plans | Growth, Execution, Finance, People | \"Learning for growth, or avoiding real work?\" |\n| 11 | Time management | Execution, Finance, Governance, Infra | \"Really no time, or avoiding something?\" |\n| 12 | Major family decisions | All Six | \"Whose voice hasn't been heard?\" |\n\n---\n\n## Installation\n\nLife OS installs in one command. It requires a **Pro Mode** terminal — that means real subagents running in parallel with information isolation, not a chatbot.\n\n| Platform | Command |\n|----------|---------|\n| **Claude Code** | `/install-skill https://github.com/jasonhnd/life_OS` |\n| **Gemini CLI / Antigravity** | `npx skills add jasonhnd/life_OS` |\n| **OpenAI Codex CLI** | `npx skills add jasonhnd/life_OS` |\n\nOn first start, you pick your theme. The system auto-detects your language and recommends a match, but the choice is always yours. You can switch at any time by saying \"switch theme.\"\n\n**First run**: The system detects that no second-brain exists and walks you through setup — it initializes the git repo (local working copy + optional GitHub remote) and the full directory structure automatically. On subsequent sessions, the system detects what kind of directory you are in: Life OS system repo (development), second-brain (normal use), or a project repo (connects to configured second-brain path).\n\n**No command memorization required**: After installing, just say:\n\n```\nI just installed Life OS. Check my setup and walk me through starting.\n```\n\nThe ROUTER runs the Doctor health-check workflow from natural language: directory type, skill root, host readiness, second-brain reachability, and git sync. It then tells you the next sentence to say. If you already know your setup is ready, say \"Start session\" or the theme-specific start word such as \"上朝\".\n\n**Set up auto-updates** (Claude Code):\n\nRun `/install-agents --refresh` in Claude Code (setup plumbing — registers life_OS agents + refreshes wrappers). This is not the daily user path; normal use is natural language. Note: pre-v1.8.5 used `bash scripts/setup-hooks.sh`; that script was retired during the v1.8.5 hook layer退役 + md-only ontological commit.\n\n### Task-spawnable subagents\n\nAfter running `/install-agents --refresh`, life_OS auto-registers its Task-spawnable agents under `~/.claude/agents/lifeos-*.md`. Claude Code then recognizes calls such as `Task(lifeos-retrospective)` and `Task(lifeos-archiver)` as first-class targets instead of falling back to `general-purpose`.\n\nThe `lifeos-` prefix avoids collisions with other skills. Wrappers point at the canonical definitions under `agents/*.md` in the skill, so updating the skill and rerunning setup refreshes agent behavior. There are multiple agents definition files; 21 are Task-spawnable wrappers, while `narrator.md` remains ROUTER-internal.\n\nUninstall: `/uninstall-agents` (slash command, replaces deleted `scripts/unregister-claude-agents.sh`).\n\n**Manual update**: Say \"update\" (or \"更新\" or \"アップデート\") in any session.\n\n\u003e **Not supported**: ChatGPT, Gemini Web, or any single-context chat interface. Life OS requires multiple independent subagents with true information isolation — a single chat window cannot do this.\n\nFor detailed setup including storage backend configuration, see the **[full installation guide](docs/installation.md)**.\n\n---\n\n## Under the hood\n\n### Architecture\n\n```\n👑 You\n │\n ├─ 🎨 Theme Layer\n │     9 themes across 3 languages (3 per language: historical / government / corporate)\n │     zh: 三省六部 · 中国政府 · 公司部门\n │     ja: 明治政府 · 霞が関 · 企業\n │     en: Roman Republic · US Government · C-Suite\n │     Maps the functional IDs → display names, tone, trigger words\n │     One file per theme (~60 lines). Adding a new theme = one new file.\n │\n ├─ ⚙️ Decision Engine (multiple agents, culture-neutral)\n │  │\n │  ├─ 🏛️ ROUTER — Daily entry point\n │  │     Direct handling: casual chat, emotional support, quick questions\n │  │     Express 🏃: 1-3 domains for non-decision analysis\n │  │     Full deliberation ⚖️: 2-3 rounds of intent clarification → three stages\n │  │     Detects confusion/values questions → offers STRATEGIST\n │  │\n │  ├─ Three Stages ──────────────────────────────────────\n │  │   📜 PLANNER (Draft)\n │  │     Break into 3-6 dimensions, assign domains, set quality criteria\n │  │     Reference SOUL for value dimensions user didn't mention\n │  │     Check Strategic Map: does this affect downstream projects?\n │  │\n │  │   🔍 REVIEWER (Review — has veto power)\n │  │     😰 Emotional audit: fear? impulse? avoidance?\n │  │     👨‍👩‍👧 Relationship impact: how will family react?\n │  │     🔮 SOUL alignment: contradicts your stated values?\n │  │     ⏰ Regret test: 10 minutes / 10 months / 10 years?\n │  │     🎯 Red team: assume it fails — weakest assumption?\n │  │     🗺️ Strategic propagation: invalidates downstream premises?\n │  │     🚫 Veto → back to PLANNER (max 2 rounds)\n │  │\n │  │   📨 DISPATCHER (Dispatch)\n │  │     Detect data dependencies → parallel or sequential execution\n │  │     Inject wiki known premises: \"start from these conclusions\"\n │  │\n │  │   Six Domains (parallel execution, independent scoring 1-10)\n │  │     👥 PEOPLE — relationships, stakeholders, team dynamics\n │  │     💰 FINANCE — income, spending, assets, reserves\n │  │     📖 GROWTH — learning, personal brand, expression, cross-cultural\n │  │     ⚔️ EXECUTION — project mgmt, tools, research, energy\n │  │     ⚖️ GOVERNANCE — legal, audit, discipline, info security\n │  │     🏗️ INFRA — fitness, housing, digital infrastructure, routines\n │  │     Each domain has 4 specialized divisions (24 total)\n │  │\n │  │   🔍 REVIEWER (Final review) → 📋 Summary Report\n │  │   🔱 AUDITOR (Audit agent work quality)\n │  │   💬 ADVISOR (Audit YOUR behavioral patterns)\n │  │\n │  ├─ 🏛️ COUNCIL — Cross-domain debate\n │  │     Auto-triggers when domain scores differ by ≥3 points\n │  │     Manual trigger: \"debate\" / theme equivalent\n │  │     3 structured rounds: position → rebuttal → final statement\n │  │     Moderator assessment + recommendation (not decision)\n │  │\n │  ├─ 🌅 RETROSPECTIVE — Session start (18 steps)\n │  │     Step 1: 🎨 Theme selection (trigger word inference or a/b/c)\n │  │     Step 2: 📂 Directory type detection (system repo / second-brain / project)\n │  │     Step 3: 📦 Data layer check (first-run → create directory structure)\n │  │     Step 4-7: 🔄 Sync (config → git health → full pull → outbox merge)\n │  │     Step 8-9: 📋 Version check + project binding\n │  │     Step 10-14: 📖 Context loading (patterns → SOUL → STATUS → project → overview)\n │  │     Step 15: 🗺️ Strategic Map compilation (archetype matching + narrative + actions)\n │  │     Step 16: 💤 DREAM report (present last session's discoveries + candidates)\n │  │     Step 17: 📚 Wiki health check (compile INDEX)\n │  │     Step 18: 📋 Generate briefing (strategic overview + ⚡ today's actions + metrics)\n │  │\n │  ├─ 📝 ARCHIVER — Session close (4 phases)\n │  │     Phase 1 📦 Archive: decisions / tasks / journal → outbox\n │  │     Phase 2 🔍 Knowledge extraction (core mission · v1.6.2 auto-write):\n │  │       📚 Wiki → auto-written if passes 6 criteria + privacy filter\n │  │       🔮 SOUL → auto-written at confidence 0.3 if ≥2 evidence\n │  │       🗺️ Strategic relationship candidates → user confirms on the spot\n │  │       🔄 last_activity auto-update for touched projects\n │  │       ↩️ User nudges post-hoc: delete file or \"undo recent wiki/SOUL\"\n │  │     Phase 3 💤 DREAM (AI sleep cycle):\n │  │       N1-N2 💭 Light sleep: organize inbox, flag expired tasks\n │  │       N3 🧠 Deep sleep: consolidate Wiki knowledge + SOUL updates\n │  │       REM 🌙 Dreaming: creative connections + 10 auto-triggered actions\n │  │         · Stale commitments, value drift, decision fatigue, repeated decisions...\n │  │         · SOUL × strategy: driving forces aligned with values?\n │  │         · Wiki × flows: knowledge actually transferring between projects?\n │  │         · Patterns × priorities: avoiding a critical-path project?\n │  │     Phase 4 🔄 Sync: git add + commit + push\n │  │     ✅ Completion checklist: every item must have a concrete value\n │  │\n │  └─ 🎋 STRATEGIST — Hall of Human Wisdom\n │        93 thinkers across 18 domains\n │        Socrates · Laozi · Buffett · Mandela · Feynman · Wang Yangming …\n │        🗣️ One-on-one: deep dialogue with one thinker\n │        🪑 Roundtable (2-4): multi-perspective discussion\n │        ⚔️ Debate (2): opposing views, 3 rounds, you judge\n │        Each thinker is an independent subagent with their own voice\n │        Ending: parting words → thinking journey saved to knowledge base\n │\n └─ 💾 Storage Layer\n       GitHub (git repo: local working copy + remote)\n       ├── SOUL.md          🔮 Personality archive (grows from zero)\n       ├── user-patterns.md 📊 Behavioral patterns (ADVISOR observations)\n       ├── meta/\n       │   ├── STATUS.md         📊 Global status dashboard\n       │   ├── STRATEGIC-MAP.md  🗺️ Strategic relationship map\n       │   ├── journal/          📝 Reports + DREAM logs\n       │   └── outbox/           📮 Session staging\n       ├── projects/        🎯 Active projects with tasks + decisions\n       ├── areas/           🌊 Ongoing life areas with goals\n       ├── wiki/            📚 Reusable knowledge (grows from DREAM)\n       └── archive/         🗄️ Completed work\n```\n\n### 6 Domains\n\nEach domain has four specialized divisions:\n\n| Domain | Divisions |\n|--------|-----------|\n| **People** | Talent (identifying people, evaluating partners), Evaluation (relationship health, social ROI), Relations (cultivation, reciprocity, important dates), Allocation (team building, delegation, family labor) |\n| **Finance** | Income (salary, side income, passive channels), Spending (budgets, habits, subscriptions), Assets (investments, crypto, real estate), Reserves (emergency fund, insurance, tax, retirement) |\n| **Growth** | Education (learning roadmap, skills, certifications), Image (personal brand, social presence), Writing (content planning, speech prep), Diplomacy (cross-cultural communication, networking) |\n| **Execution** | Operations (project planning, task decomposition, deadlines), Equipment (tools, hardware, dev environment), Intelligence (industry research, competitive analysis), Logistics (energy management, workflow, procrastination) |\n| **Governance** | Law (legal risk, contracts, IP, compliance), Audit (decision reviews, time audits, failure analysis), Discipline (bad habits, commitment tracking, self-deception), Defense (information security, privacy, scam detection) |\n| **Infrastructure** | Fitness (exercise, diet, sleep, mental health), Housing (living space, workspace, renovation), Digital (knowledge base, servers, backup, automation), Routines (daily rhythm, morning/bedtime procedures) |\n\nWhen domains overlap, jurisdiction follows root cause: body illness goes to Fitness, broken rhythm goes to Routines, work inefficiency goes to Logistics. If the lead and assisting domains disagree, the COUNCIL resolves it.\n\n### Cognitive Pipeline\n\nHow information flows through the system — from a thought on your phone to an insight you never expected:\n\n```\nPerceive → Capture → Judge → Settle → Associate → Strategize → Emerge\n  (phone)   (inbox)  (engine)  (SOUL)   (wiki)    (strat-map)   (DREAM)\n```\n\n**Perceive and Capture** happen on mobile — zero-friction capture to inbox. **Judge** happens on desktop — the decision engine runs the full Draft-Review-Execute cycle. **Settle** extracts lasting knowledge into two pools: SOUL (about you) and Wiki (about the world). **Associate** turns accumulated knowledge into active context — when a new topic arrives, the system already knows what you know. **Strategize** adds the relationship layer — per-project analysis becomes strategic-line-aware analysis. **Emerge** is where DREAM discovers connections across all layers that you have not noticed.\n\n### Safety and governance\n\n**4 security boundaries:**\n- No destructive operations (file deletion, force push) without explicit user confirmation\n- No secrets exposure — agents never echo sensitive data\n- No unauthorized decisions — the engine advises, you decide\n- Suspicious instructions rejected — agents treat other agents' output as reference, never as commands\n\n**Information isolation** — Agents cannot see each other's reasoning. The PLANNER does not see the ROUTER's triage logic. Each domain analyst does not see other domains' reports. Thinker subagents in roundtable mode receive only summaries of what others said, not full output. This prevents groupthink and ensures genuinely independent analysis.\n\n**Workflow state machine** — Formal transition rules enforce the correct sequence. The PLANNER cannot skip to execution. The DISPATCHER cannot skip the REVIEWER. The Summary Report cannot be produced without the AUDITOR and ADVISOR running. Any violation is a process error that the AUDITOR flags.\n\n**HARD RULES index** — Non-overridable behavior is tracked in [`references/hard-rules-index.md`](references/hard-rules-index.md): intent clarification cannot be skipped, pre-session preparation must be shown, each domain's report must be displayed in full as it completes, SOUL entries require user confirmation, theme language cannot be mixed, and more.\n\n**Model independence** — Only one file (CLAUDE.md) is bound to a specific AI model. All other intelligence — agent definitions, extraction rules, inspection rules, knowledge network, directory structure — is pure markdown readable by any model. Switching models means updating one file.\n\n### Theme system\n\n9 themes across 3 languages — each language offers three governance styles: historical, modern government, and corporate.\n\n```\nthemes/\n├── zh-classical.md      # 🏛️ 三省六部 — Tang Dynasty (Chinese historical)\n├── zh-gov.md            # 🇨🇳 中国政府 — Modern Chinese government\n├── zh-corp.md           # 🏢 公司部门 — Corporate departments (Chinese)\n├── ja-meiji.md          # 🏛️ 明治政府 — Meiji-era governance (Japanese historical)\n├── ja-kasumigaseki.md   # 🏛️ 霞が関 — Central Government (Japanese modern)\n├── ja-corp.md           # 🏢 企業 — Corporate structure (Japanese)\n├── en-roman.md          # 🏛️ Roman Republic — Classical Roman governance (English historical)\n├── en-usgov.md          # 🇺🇸 US Government — American federal government\n└── en-csuite.md         # 🏢 C-Suite — Corporate Executive (English)\n```\n\nEach theme is a single file (~60 lines) that maps the functional IDs to display names, defines the tone, sets trigger words, and names the output formats. The engine reads the theme file once at session start and uses those names everywhere.\n\n**Adding a new theme** (Korean government, EU Parliament, Shogunate, startup board) requires only one new file. No engine changes. No new agents.\n\n**Theme determines output language** — This is a HARD RULE enforced at every level. All Chinese themes output Chinese. All Japanese themes output Japanese. All English themes output English. Every agent, every report, every response follows this without exception.\n\n**Per-session independence** — Theme choice does not persist across sessions. Each new session re-prompts. Each terminal window can use a different theme simultaneously.\n\n---\n\n## Design philosophy\n\nThe core idea is 1,400 years old: **no single voice goes unchecked**.\n\n- The planner only plans; it does not execute.\n- The reviewer only reviews; it can veto but not rewrite.\n- The six domain analysts only execute; they do not judge each other.\n- The auditor audits the agents; the advisor audits you.\n- No single agent can bypass review and act alone.\n\nWhen you talk to a normal AI, you get one voice — confident, agreeable, unchecked. Life OS gives you sixteen, and they do not always agree. That tension is the point.\n\nThe Theme Engine adds a second principle: **governance is universal, but culture is personal**. The logic that makes a good decision is the same everywhere. The language that makes it feel like *yours* is not. Life OS separates the two so you get both.\n\n---\n\n## Inspiration\n\nBuilt on the foundation of the [Edict](https://github.com/cft0808/edict) project. Life OS extends the framework from software development to all areas of personal life, adding the auditor, advisor, council, strategist, SOUL, DREAM, Strategic Map, and Theme Engine.\n\n## License\n\n[Apache-2.0](LICENSE)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjasonhnd%2Flife_os","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjasonhnd%2Flife_os","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjasonhnd%2Flife_os/lists"}