jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity
The daily GPT grind
259 Commits 1 Branch 0 Tags 2.3 MiB
Markdown 100%
e51664d2f1
Go to file
jester e51664d2f1 Remove moved root reference docs after relocation to docs/reference
2026-04-13 21:51:34 +00:00
docs Move non-core root reference docs under docs/reference 2026-04-13 21:51:08 +00:00
MANAGEMENT Add pricing and packaging planning session prompt 2026-04-12 18:54:51 +00:00
SCRATCH Add billing + Stripe + portal handover doc (developer mode chat capture) 2026-04-11 21:51:35 +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 — hosted IDE via Traefik wildcard curl-verified 2026-03-22 21:56:41 +00:00
ANTI_DRIFT_GUARDRAIL.md docs: expand drift prevention rules with AI-specific guardrails 2026-01-18 23:58:57 +00:00
CLAUDE_GPT_COORDINATION.md Add Claude-GPT coordination guide - general rules for repo ownership, SCRATCH hygiene, infrastructure reality 2026-04-10 12:45:10 +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
INFRASTRUCTURE.md Set exact OPNsense router WAN IPs in infrastructure inventory 2026-04-10 14:30:51 +00:00
OPEN_THREADS.md Refresh open threads with completed billing, auth, onboarding, and dashboard work 2026-04-12 21:41:22 +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.md with current infrastructure and Velocity plugin model 2026-04-10 19:15:53 +00:00
README.md Tighten README as zlh-grind front door 2026-04-13 21:32:28 +00:00
SESSION_LOG.md Append 2026-04-12 session summary for billing, auth, onboarding, and dashboard work 2026-04-12 21:42:51 +00:00
SESSION_START.md Clarify session startup flow after README front door 2026-04-13 21:32:46 +00:00
UPSTREAMS.md Add zlh-artifacts section — catalog-driven runtime and addon distribution 2026-03-14 22:07:31 +00:00

README.md

zlh-grind

GPT Execution Workspace for ZeroLagHub.

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

It is the execution workspace and working memory layer for active implementation.

It is not the final architecture source of truth.

What This Repo Is For

Use this repository to preserve:

  • active execution context
  • unfinished work
  • implementation findings
  • session handovers
  • operational snapshots
  • chronological session history

The goal is simple: a new session should be able to enter this repository, read a small set of files, and continue work safely.

Front Door

Start here, then continue in this order:

  1. SESSION_START.md
  2. OPEN_THREADS.md
  3. CONSTRAINTS.md
  4. PROJECT_CONTEXT.md (if current platform state matters)
  5. INFRASTRUCTURE.md (if VM/IP context matters)
  6. UPSTREAMS.md (if cross-repo context matters)

Do not start by digging through history unless the live docs are insufficient.

Live Working Set

These root files are the live control panel for the repo:

  • SESSION_START.md
  • OPEN_THREADS.md
  • CONSTRAINTS.md
  • PROJECT_CONTEXT.md
  • INFRASTRUCTURE.md
  • UPSTREAMS.md

Keep these current and concise.

History And Deep Context

Use these only when deeper recovery is needed:

  • SESSION_LOG/ — chronological implementation history
  • Session_Summaries/ — session handovers and milestone summaries
  • SCRATCH/ — temporary or investigative notes
  • docs/ — reference and archive material
  • MANAGEMENT/ — non-core planning material

These support the live docs, but they are not the normal starting point for a fresh session.

Repo Boundary

This repository should not become a dumping ground for every possible context artifact.

Do not let root-level docs multiply without a clear reason.

Root docs should answer only one question:

What must a new session know right now to continue work safely?

Session Rule

Never assume speculative features are implemented.

When in doubt:

  • trust the live working set first
  • use history folders for conflict resolution
  • update the live docs after meaningful work is completed