jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity
The daily GPT grind
333 Commits 1 Branch 0 Tags 2.3 MiB
Markdown 100%
9a2834bc8d
Go to file
jester 9a2834bc8d Record API Velocity lifecycle decisions
2026-04-25 20:34:52 +00:00
Codex Record API Velocity lifecycle decisions 2026-04-25 20:34:52 +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 for Alloy monitor rollout and container test prep 2026-04-17 14:45:17 +00:00
CODE_REVIEW_WORKFLOW.md Add Codex cross-repo review workflow and cleanup rules 2026-04-19 12:55:34 +00:00
CONSTRAINTS.md consolidation pass: replace CONSTRAINTS with current guardrails 2026-03-01 23:29:19 +00:00
INFRASTRUCTURE.md Tighten infrastructure doc and align backup boundary wording 2026-04-16 20:08:58 +00:00
OPEN_THREADS.md Track dev backup direction in root open threads 2026-04-19 22:04:28 +00:00
PROJECT_CONTEXT.md Update root project context for Node 24 baseline and dev shell boundary finding 2026-04-19 21:36:54 +00:00
README.md Reconcile root README with Codex ownership model 2026-04-16 19:56:10 +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 Reconcile session start guidance with Codex ownership model 2026-04-16 19:56:42 +00:00
UPSTREAMS.md Refresh upstreams doc into current dependency reference 2026-04-16 20:09:39 +00:00

README.md

zlh-grind

GPT execution workspace for ZeroLagHub.

This repository preserves execution continuity for long-running implementation work, but it is not the final architecture source of truth.

It is the working memory layer for:

  • current platform context
  • active cross-repo work
  • session startup guidance
  • repo-specific tracking handoff into Codex/

What This Repo Is For

Use this repository to preserve:

  • active execution context
  • unfinished cross-repo work
  • implementation findings that matter across repos
  • session handovers
  • operational snapshots
  • chronological session history when deep recovery is needed

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. Codex/README.md
  4. the relevant repo tracker under Codex/
  5. CONSTRAINTS.md
  6. PROJECT_CONTEXT.md (if current platform state matters)
  7. INFRASTRUCTURE.md (if VM/IP context matters)
  8. 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 platform-wide state:

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

Repo-specific truth lives under:

  • Codex/API/*
  • Codex/Portal/*
  • Codex/Agent/*

Keep root concise and keep repo-specific work in Codex.

Codex Ownership Model

Codex/ is the repo-specific execution layer.

Use:

  • Codex/API/* for jester/zpack-api
  • Codex/Portal/* for jester/zpack-portal
  • Codex/Agent/* for jester/zlh-agent

Each repo folder contains:

  • README.md — front door for that repo track
  • CURRENT_STATE.md — what is implemented now
  • OPEN_ITEMS.md — unfinished work only
  • DECISIONS.md — settled choices / do-not-re-litigate notes

Root OPEN_THREADS.md is for cross-repo/platform work only.

Cleaning Rule

Do not let stale work accumulate.

When a repo-specific item is completed:

  • remove it from that repo’s Codex/*/OPEN_ITEMS.md
  • move durable implemented behavior into CURRENT_STATE.md
  • move settled choices into DECISIONS.md
  • remove it from root OPEN_THREADS.md unless it still has active cross-repo/platform implications

If an item exists in root and also belongs to only one repo, it should usually be removed from root.

Do not re-add old items without current evidence that they are still open or have regressed.

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.

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
  • trust the relevant Codex/* tracker for repo-owned work
  • use history folders only for conflict resolution
  • update the live docs after meaningful work is completed