Section 01
What This Workspace Is
This repository is the continuity layer behind LifeHub.
Files and folders are the source of truth.
AI operators help structure, synthesize, specify, and build.
Important logic should live in files, not only in chat.
The workspace stays portable across tools and AI providers.
Section 02
Repository Structure
00_user_guide stores practical human-facing guidance for using LifeHub without replacing governance or AI operator instructions.
LifeHub/01_inbox stores raw intake, quick captures, and unprocessed material.
LifeHub/02_projects stores staged project workspaces that move from source material toward outputs, including project-owned app workspaces in 05_apps/ when needed.
LifeHub/03_systems stores reusable system templates, methods, and operating structures.
Section 03
Working Distinctions
Thinking and intake begin in LifeHub/01_inbox and early project stages.
Systems and reusable workflow structures live in LifeHub/03_systems.
Assets are practical operational tools in LifeHub/04_assets.
Specs define behavior and requirements in LifeHub/05_specs.
Section 04
How To Start
1. If you are using LifeHub as a human, read 00_user_guide/README.md.
If you are operating as an AI agent, load Tier-A Core first, then use the Context Directory to select the route-specific workspace.
If the request is only to acclimate or orient and no concrete task is given, stop after Tier-A Core.
Load the Context Index, master index, active state, system state, session logs, lessons, or skills only when the route or task explicitly triggers them.