The daily GPT grind
Go to file
2026-03-21 12:58:38 +00:00
docs docs: v2 — incorporate direct upload model, provenance metadata, API streaming, failure categories 2026-03-01 23:13:09 +00:00
MANAGEMENT init: pre-launch master checklist 2026-03-09 22:33:02 +00:00
SCRATCH docs: add host controls decision (keep delete failsafe, add LXC controls) 2026-02-07 21:48:02 +00:00
SESSION_LOG add granular session log: Mar 1 upload pipeline + filesystem consolidation 2026-03-02 00:07:22 +00:00
Session_Summaries Add session summary — browser IDE proxy working end-to-end 2026-03-21 12:58:38 +00:00
ANTI_DRIFT_GUARDRAIL.md docs: expand drift prevention rules with AI-specific guardrails 2026-01-18 23:58:57 +00:00
ANTI_DRIFT.md consolidation pass: replace ANTI_DRIFT with current policy 2026-03-01 23:29:49 +00:00
CONSTRAINTS.md consolidation pass: replace CONSTRAINTS with current guardrails 2026-03-01 23:29:19 +00:00
DEV_CONTAINER_SPEC.md Update DEV_CONTAINER_SPEC — remove Traefik model, document API proxy + Headscale access 2026-03-15 22:59:20 +00:00
OPEN_THREADS.md Mark browser IDE as working — full proxy solution documented 2026-03-21 12:58:10 +00:00
PORTAL_MIGRATION.md docs: update portal migration - reflect Feb 2026 current state 2026-02-08 22:57:39 +00:00
PROJECT_CONTEXT.md Update PROJECT_CONTEXT 2026-03-17 — agent enhancements, base-path blocking issue, crash recovery 2026-03-17 23:06:52 +00:00
README.md Update README — GPT execution workspace context + dev container platform state 2026-03-14 22:06:20 +00:00
SESSION_LOG.md Log code-server launch issue and port conflict finding 2026-03-15 2026-03-15 21:10:16 +00:00
SESSION_START.md consolidation pass: replace SESSION_START with current checklist 2026-03-01 23:29:41 +00:00
UPSTREAMS.md Add zlh-artifacts section — catalog-driven runtime and addon distribution 2026-03-14 22:07:31 +00:00

zlh-grind

GPT Execution Workspace for ZeroLagHub

This repository exists to preserve execution continuity for long-running implementation work performed with GPT.

It is not a source-of-truth architecture repository. Canonical documentation lives in:

jester/knowledge-base


Assistant Prompt

You are údar.

In this repository you act as the execution assistant.

Your role is to:

  • implement changes
  • verify behavior
  • document work
  • maintain session continuity

Before doing work you must read:

SESSION_LOG.md OPEN_THREADS.md UPSTREAMS.md

Architecture decisions must not be made here.

If architectural interpretation is required:

Stop and defer to Claude or the canonical docs.


What This Repo Is For

This repository tracks:

  • GPT implementation work
  • session handovers
  • debugging notes
  • execution reasoning
  • cross-repo coordination

It serves as the execution ledger for the ZeroLagHub platform.


What This Repo Is NOT

This repo must never become an architecture source.

Do not add:

  • system diagrams
  • architecture decisions
  • platform policy
  • runtime design

Those belong in:

jester/knowledge-base


Platform Context (Current State)

ZeroLagHub consists of several core components.

Control Plane

zlh-api

Responsibilities:

  • container lifecycle orchestration
  • database state
  • agent provisioning payloads
  • DNS / proxy coordination

Execution Plane

zlh-agent

Responsibilities:

  • container runtime provisioning
  • game server install + management
  • dev container provisioning
  • runtime installs
  • addon installs
  • status reporting

Artifact Distribution

zlh-artifacts

Artifact server hosts:

devcontainer/
  _catalog.json
  go/
  node/
  python/
  java/
  dotnet/

addons/
  code-server/

Artifacts are fetched by the agent at provisioning time.

Nothing provisioning-related is assumed to exist locally inside containers.


Developer Containers

Dev containers support runtimes:

  • node
  • python
  • go
  • java
  • dotnet

Runtime installs are:

  • catalog driven
  • artifact backed
  • idempotent

Install root:

/opt/zlh/runtimes/<runtime>/<version>

Dev environment:

user: dev
home: /home/dev
workspace: /home/dev/workspace

Repo Role in the Platform

This repository tracks execution work across all components:

  • zlh-api
  • zlh-agent
  • zlh-portal
  • zlh-artifacts
  • infrastructure

It ensures GPT sessions remain consistent across days and chats.