jester/zlh-grind

History

jester be9244e2af Add Monitoring to Codex index		2026-05-01 21:06:45 +00:00
..
Agent	Add Agent token future-state guidance	2026-04-30 22:01:12 +00:00
API	Add API agent trust model guidance	2026-04-30 22:03:54 +00:00
Brand	Upload files to "Codex/Brand"	2026-04-30 22:53:33 +00:00
Monitoring	Align monitoring contract with Alloy scrape model	2026-05-01 21:06:35 +00:00
Portal	Update Portal current state after repo sync	2026-04-30 19:30:39 +00:00
README.md	Add Monitoring to Codex index	2026-05-01 21:06:45 +00:00

README.md

Codex

Codex is the repo-specific execution layer for active work.

Purpose:

keep zlh-grind root focused on platform-wide context
track API, Portal, Agent, and Monitoring work separately
make it easier to remove completed items instead of letting them linger in one shared backlog

Use this structure:

Codex/API/* for jester/zpack-api
Codex/Portal/* for jester/zpack-portal
Codex/Agent/* for jester/zlh-agent
Codex/Monitoring/* for monitoring host / observability coordination

File roles:

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

Operational rules:

remove completed items from OPEN_ITEMS.md promptly
move durable context into CURRENT_STATE.md or DECISIONS.md
keep root OPEN_THREADS.md for cross-repo / platform items only
if Codex/* conflicts with older historical notes elsewhere in zlh-grind, prefer the newer Codex entry unless there is stronger evidence in the source repo