2.2 KiB
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:
SESSION_START.mdOPEN_THREADS.mdCONSTRAINTS.mdPROJECT_CONTEXT.md(if current platform state matters)INFRASTRUCTURE.md(if VM/IP context matters)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.mdOPEN_THREADS.mdCONSTRAINTS.mdPROJECT_CONTEXT.mdINFRASTRUCTURE.mdUPSTREAMS.md
Keep these current and concise.
History And Deep Context
Use these only when deeper recovery is needed:
SESSION_LOG/— chronological implementation historySession_Summaries/— session handovers and milestone summariesSCRATCH/— temporary or investigative notesdocs/— reference and archive materialMANAGEMENT/— 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