# ChatGPT Adapter

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

## Purpose

This file is the root adapter for ChatGPT-based LifeHub interfaces.

It keeps ChatGPT Project settings lightweight by pointing the conversation interface to the live GitHub source of truth instead of duplicating project rules in static ChatGPT instructions or uploaded source files.

## Live Instruction Entry

For LifeHub-related work in ChatGPT, start from the lean runtime authority below:

1. `LifeHub/08_admin/03_operator/context_runtime/TIER_A_CORE.md`
2. `LifeHub/08_admin/03_operator/context_runtime/CONTEXT_DIRECTORY.index.json`
3. `LifeHub/08_admin/03_operator/UNIVERSAL_CHATGPT_INTERFACE_INSTRUCTIONS.md` only when ChatGPT-interface behavior is in scope
4. `LifeHub/08_admin/03_operator/CHATGPT_INTERFACE_CONTRACT.md` only when interface contract behavior is in scope
5. Project-specific subcontract only when a live repo file exists and adds non-redundant rules for the current ChatGPT Project or Custom GPT.

For the private **LifeHub Command Interface** Custom GPT, the live project-specific subcontract is:

`LifeHub/08_admin/03_operator/custom_gpt_interfaces/LIFEHUB_COMMAND_INTERFACE_CUSTOM_INSTRUCTIONS.md`

## Source Of Truth Rule

The GitHub repository `TheMustardTreeMarket/LifeHub2.0` is the cloud-accessible source of truth for LifeHub.

ChatGPT memory, static Project instructions, uploaded source files, and prior chat history are helpful context only. They must yield to live repository authority when the task depends on current LifeHub state, routing, governance, structure, or project files.

## Repo Work Execution Surface Rule

For repository work, GitHub-native authorized tools are the default execution surface.

Use GitHub actions/connectors/API tools by default for:

- reading live repository files;
- creating or updating repository documents;
- preparing packets, closeouts, and small direct edits;
- opening, reviewing, updating, or merging PRs when GitHub tooling is sufficient;
- reporting confirmed repository state.

Do not default to the VM merely because the VM is available.

Use a machine/local execution environment only when the task actually requires it, such as:

- Codex Dispatch;
- Hermes Dispatch;
- local tests, builds, generators, linters, formatters, or runtime checks;
- Redis/Docker/local service inspection;
- generated artifacts that require local tooling;
- local-only worktree diagnosis or recovery;
- cases where GitHub-native tooling is unavailable, insufficient, or unsafe for the specific operation.

For local-agent work, load:

`LifeHub/08_admin/03_operator/workspace_protection/LOCAL_AI_AGENT_DISPATCH_PROTOCOL.md`

When concurrent repository-changing candidates may share a dependency, conflict domain, authoritative/shared surface, or runtime/build/deployment boundary, also load:

`LifeHub/03_systems/Agent_Bus/AGENT_BUS_PARALLEL_INTEGRATION_INTERIM_POLICY.md`

That interim policy permits domain-isolated candidates to execute and integrate independently. It requires serialized integration and post-merge revalidation only inside an affected integration group or changed shared surface. It creates no new queue, workflow, task authority, or automatic merge permission and is preserved for later incorporation into Agent Bus.

The dispatch order is direct action first. Do not assume a local command or nested worker launch will be blocked. If an authorized direct machine action is actually blocked, or a durable asynchronous worker handoff is materially safer, evaluate the separately gated GitHub Dispatch Bridge described in:

`LifeHub/03_systems/LifeHub_Mesh/01_architecture/V1_GITHUB_DISPATCH_BRIDGE_INTERIM_ARCHITECTURE.md`

The bridge is architecture-only until a safe implementation plan and runtime phase are separately authorized. GitHub dispatch issues are a narrow adapter transport exception and do not replace LifeHub Inbox, Taskmaster, project state, or Agent Bus.

When a machine or dispatch bridge is used for repo-related work, state the reason plainly and return repository truth to GitHub through commits, PRs, closeouts, and verified branch state.

## Bootstrap Behavior

When a ChatGPT Project or Custom GPT uses this adapter:

1. Use static Project/GPT instructions only as a bootstrap pointer to this file or to the relevant live Custom GPT subcontract.
2. Fetch `TIER_A_CORE.md` first when GitHub connector access is available and current LifeHub authority matters.
3. Route through `CONTEXT_DIRECTORY.index.json` before loading broader authority.
4. If GitHub cannot be fetched, state the limitation clearly before relying on memory, static files, or prior chat context.
5. Do not claim repository files, inbox items, tasks, settings, dispatches, workers, or runtime states changed unless the relevant tool action succeeded.

## Relationship To AGENTS.md

`AGENTS.md` remains the general repository router for AI operators.

This file is narrower: it defines the ChatGPT interface entrypoint and points ChatGPT to the live instruction contract that governs how ChatGPT Projects and Custom GPTs should use GitHub as authority and select the least indirect safe execution surface.