Human Guide · Reader View

LifeHub User Guide

Human-facing guide to navigating and using LifeHub.

View canonical Markdown copy Browse registered workspace
Reader View — generated from canonical Markdown.
This page uses the LifeHub Reader Site Styler skill for presentation, but it is still derivative. If it conflicts with the Markdown source, the Markdown controls.
Polished Reader ViewDesigned for study, browsing, and mobile reading.
Markdown Source ViewIn-site display copy for side-by-side verification.
Canonical RuleRepository Markdown remains the source of truth.
Canonical Path00_user_guide/LIFEHUB_USER_GUIDE.md
Source SHA-2565bbe7bc82edb02127af4652dfb8e0529e9cfcc0f946a86aa75e7d803d090119b
Generatedregistry-2026-07-06-styler-test
PolicyLifeHub/08_admin/03_operator/READER_VIEW_POLICY.md
Design SkillLifeHub/03_systems/AI_Operator_Continuity/skills/lifehub-reader-site-styler.md

LifeHub User Guide

LifeHub is a file-based operating system for turning ideas, notes, conversations, research, projects, and business logic into organized work.

The basic rule is simple: important things should end up in files, not only in chat.

What LifeHub Helps You Do

LifeHub helps you move from loose material into usable structure:

  1. Capture raw material.
  2. Organize and clarify it.
  3. Extract the useful signal.
  4. Synthesize models or decisions.
  5. Turn models into practical assets.
  6. Define specs before software work.
  7. Build apps or automations when the underlying structure is ready.
  8. Store reviewed outputs where they can be found again.

Main Places You Will Use

Place Human Meaning
00_user_guide/ Start here when you need practical guidance on using LifeHub.
LifeHub/01_inbox/ Put new captures, handoffs, rough ideas, and unprocessed material here.
LifeHub/02_projects/ Use this for active projects that need staged work and downstream outputs.
LifeHub/03_systems/ Use this for reusable methods, standards, templates, lessons, and AI workflows.
LifeHub/04_assets/ Use this for practical tools such as SOPs, checklists, policies, and templates.
LifeHub/05_specs/ Use this for requirements and behavior definitions before implementation.
LifeHub/06_apps/ Use this only for shared or cross-project app work. Project-owned apps belong under the project.
LifeHub/07_outputs/ Use this for final reports, reviews, exports, and operator session logs.
LifeHub/08_admin/ Governance and AI operator authority. Read through it when the system itself is being changed.
Reference/ Supporting material only, not the governing workspace.

How To Work With AI Agents

Use AI agents as operators inside the file system.

Good requests usually say:

  • what you want done
  • which file or folder controls the work
  • whether you want planning, implementation, review, or inbox processing
  • whether the result should become an inbox item, project artifact, asset, spec, app change, or output

Examples:

Prepare this conversation for LifeHub Inbox.

Send this to Taskmaster as a LifeHub task.

Process my inbox.

Work on LifeHub/01_inbox/01_new/<item>.md and follow the inbox lifecycle.

For repository edits, expect Codex-style agents to work on a task branch and open a pull request rather than committing directly to main.

What Not To Do

  • Do not treat chat as the only memory for important decisions.
  • Do not put durable project outputs in the inbox forever.
  • Do not use Reference/ as the source of truth for active LifeHub rules.
  • Do not ask AI agents to build app code before the model, asset, or spec layer is clear enough.

Where Authority Lives

This guide is practical help. The authority lives deeper: