LifeHub User Guide

# LifeHub User Guide


<!-- lifehub-reader-view-link -->
> **Reader View:** [Open the generated HTML reader view](../LifeHub/07_outputs/reader_site/pages/00_user_guide/LIFEHUB_USER_GUIDE.html). Markdown remains the canonical source of truth.

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:

```text
Prepare this conversation for LifeHub Inbox.
```

```text
Send this to Taskmaster as a LifeHub task.
```

```text
Process my inbox.
```

```text
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:

- Context loading: [LifeHub/08_admin/LIFEHUB_CONTEXT_INDEX.md](../LifeHub/08_admin/LIFEHUB_CONTEXT_INDEX.md)
- Workspace workflow: [WORKFLOW.md](../WORKFLOW.md)
- AI operator behavior: [LifeHub/08_admin/03_operator/AI_OPERATOR_GUIDE.md](../LifeHub/08_admin/03_operator/AI_OPERATOR_GUIDE.md)
- Important file index: [LifeHub/08_admin/LIFEHUB_MASTER_FILE_INDEX.md](../LifeHub/08_admin/LIFEHUB_MASTER_FILE_INDEX.md)