Show raw Markdown text
# LifeHub 2.0 - Layer 1 Router
<!-- lifehub-reader-view-link -->
> **Reader View:** [Open the generated HTML reader view](LifeHub/07_outputs/reader_site/pages/AGENTS.html). Markdown remains the canonical source of truth.
## Layer 1 Contract
- Keep this file lean: target roughly 50-80 lines and avoid exceeding 100 unless clearly justified.
- Root router files are maps. Workspace and project `CONTEXT.md` files are rooms. Skills, templates, and standards are tools.
- Route instead of restating full governance.
- Prefer tables, short bullets, and direct links.
- Ask when placement or scope is genuinely unclear.
## Start Here
- `LifeHub/08_admin/03_operator/context_runtime/TIER_A_CORE.md` for the lean Tier-A runtime bootstrap.
- `LifeHub/08_admin/03_operator/context_runtime/CONTEXT_DIRECTORY.index.json` for route-first context selection.
- `LifeHub/08_admin/LIFEHUB_CONTEXT_INDEX.md` only when loading-model interpretation is needed.
- `chatgpt.md` for ChatGPT interface routing into live GitHub authority.
- `LifeHub/08_admin/03_operator/OPERATOR_QUICKCARD.md` as a human/operator quick reference, not mandatory runtime context.
- `LifeHub/08_admin/03_operator/OPERATOR_SESSION_CHECKLIST.md`, `AI_REPO_OPERATING_CONTRACT.md`, and `AI_OPERATOR_GUIDE.md` only when the route or a bounded context request justifies them.
- `LifeHub/08_admin/03_operator/HERMES_WEEKLY_DOC_CONSISTENCY_CHECK.md` for lightweight runtime-doc drift checks.
- Workspace protection: before repository-changing work, consult `LifeHub/08_admin/03_operator/workspace_protection/`, especially the Hermes workspace operating contract, task worktree lifecycle, and report artifact policy. Machine-local hooks, cron, and audit reports must be installed locally from that package and kept outside repo roots.
- Concurrent repository work: load `LifeHub/03_systems/Agent_Bus/AGENT_BUS_PARALLEL_INTEGRATION_INTERIM_POLICY.md` when candidates may share a dependency, conflict domain, authoritative/shared surface, or runtime/build/deployment boundary. Domain-isolated candidates may integrate independently; serialize and revalidate only inside the affected integration group or shared surface.
## Folder Map
| Folder | Use |
|---|---|
| `LifeHub/01_inbox` | Intake control and source handoffs |
| `LifeHub/02_projects` | Active project work and project-owned downstream artifacts |
| `LifeHub/03_systems` | Reusable methods, standards, templates, lessons, and skills |
| `LifeHub/04_assets` | Reusable operational tools such as SOPs, templates, and checklists |
| `LifeHub/05_specs` | Structured requirements and behavior definitions |
| `LifeHub/06_apps` | Shared or cross-project implementation work only |
| `LifeHub/07_outputs` | Final reviews, reports, exports, and session logs |
| `LifeHub/08_admin` | Governance, context-loading rules, structure, and operator behavior |
## Task Routing
| Task | Go To | Load |
|---|---|---|
| Process inbox item | `LifeHub/01_inbox/CONTEXT.md` | `README.md`, `INBOX_INDEX.md`, target item, direct downstream file only |
| Work on project | `LifeHub/02_projects/CONTEXT.md` | project `README.md`, exact container or downstream artifact |
| Build or refine system | `LifeHub/03_systems/CONTEXT.md` | exact system `README.md`, standard, skill, lesson, or spec |
| Develop shared or cross-project app | `LifeHub/06_apps/CONTEXT.md` | relevant spec, target app folder, boundary check |
| Review outputs | `LifeHub/07_outputs/` | exact output file plus its source project, system, spec, or app file |
| Change structure or governance | `LifeHub/08_admin/` docs | Tier-A Core, context directory, then route-triggered context index, operator guide, structure snapshot, or master file index |
## Naming Rules
- Inbox items: `YYYY-MM-DD_short-topic-title.md`
- Project folders: concise `PascalCase` with no spaces
- App folders: concise `PascalCase` with no spaces
## AI Behavior
- Determine workspace, artifact type, and workflow stage before acting.
- Load only the minimum context required for the task and do not widen Tier A by default.
- Follow the relevant `CONTEXT.md` before deeper work.
- Prefer updating an existing file over creating a duplicate.
- Respect lifecycle, promotion, and app-ownership boundaries.
- Treat `LifeHub/07_outputs/reader_site/` as generated human reader output; do not use it as AI task context unless reader-view work is explicit.
## Load Only When Needed
- `LifeHub/08_admin/LIFEHUB_MASTER_FILE_INDEX.md`
- `LifeHub/08_admin/LIFEHUB_STRUCTURE_SNAPSHOT.md`
- `LifeHub/08_admin/02_product/LIFEHUB_INFORMATION_ARCHITECTURE.md`
## Root Orientation
- `00_user_guide/README.md` for human-facing operating guidance only; it is not AI operator authority.
- `README.md`
- `WORKFLOW.md`