Orientation · Reader View

LifeHub Repository Overview

Top-level repository orientation and workspace entry.

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 PathREADME.md
Source SHA-2564a9a3e8bc7ca51b2ce3e99c1985bdb9b7b34f447abcacebe61c6e8bae852c49b
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 2.0

LifeHub is a long-term, file-based, AI-assisted operating system for turning raw information into structured knowledge, usable assets, specifications, applications, and reviewable outputs.

For practical human operating guidance, start with 00_user_guide/README.md.

For AI operator context loading and governance, start with LifeHub/08_admin/LIFEHUB_CONTEXT_INDEX.md. It points operators to the session-start checklist before the full guide.

What This Workspace Is

This repository is the continuity layer behind LifeHub.

The operational workspace now lives inside LifeHub/. Repository infrastructure and supporting reference material remain outside that folder.

  • 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.

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.
  • LifeHub/04_assets stores reusable operational artifacts such as SOPs, checklists, policies, and templates.
  • LifeHub/05_specs stores structured requirements for workflows, dashboards, systems, and software.
  • LifeHub/06_apps stores shared or cross-project application implementation work when specs are ready.
  • LifeHub/07_outputs stores final exports, reports, reviews, and delivery-ready artifacts.
  • LifeHub/08_admin stores the authoritative governance layer for LifeHub itself.
  • Reference/ stores supporting material only. It is not the authoritative layer.
  • .git/, .github/, and .devcontainer/ stay at repository root as technical infrastructure.

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.
  • Project apps implement approved project specs in structured LifeHub/02_projects/<Project>/05_apps/ workspaces.
  • Root LifeHub/06_apps is only for shared or cross-project implementations.
  • Outputs collect reviewed deliverables in LifeHub/07_outputs.
  • Admin and governance documents live in LifeHub/08_admin.

How To Start

  1. If you are using LifeHub as a human, read 00_user_guide/README.md.
  2. If you are operating as an AI agent, read LifeHub/08_admin/LIFEHUB_CONTEXT_INDEX.md.
  3. If the request is only to acclimate or orient and no concrete task is given, read Tier A only, then stop.
  4. Use the context tiers in that file to decide what to load next.
  5. Work from the relevant project, system, spec, or app folder instead of keeping important logic only in chat.