ChatGPT Adapter
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:
LifeHub/08_admin/03_operator/context_runtime/TIER_A_CORE.mdLifeHub/08_admin/03_operator/context_runtime/CONTEXT_DIRECTORY.index.jsonLifeHub/08_admin/03_operator/UNIVERSAL_CHATGPT_INTERFACE_INSTRUCTIONS.mdonly when ChatGPT-interface behavior is in scopeLifeHub/08_admin/03_operator/CHATGPT_INTERFACE_CONTRACT.mdonly when interface contract behavior is in scope- 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 the VM only when the task actually requires a local execution environment, 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
When the VM 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:
- Use static Project/GPT instructions only as a bootstrap pointer to this file or to the relevant live Custom GPT subcontract.
- Fetch
TIER_A_CORE.mdfirst when GitHub connector access is available and current LifeHub authority matters. - Route through
CONTEXT_DIRECTORY.index.jsonbefore loading broader authority. - If GitHub cannot be fetched, state the limitation clearly before relying on memory, static files, or prior chat context.
- Do not claim repository files, inbox items, tasks, or settings were changed unless the 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.