zlh-grind/Codex
2026-05-01 20:54:27 +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 Add monitoring decisions 2026-05-01 20:54:27 +00:00
Portal Update Portal current state after repo sync 2026-04-30 19:30:39 +00:00
README.md Add Codex repo-specific tracking structure 2026-04-16 19:07:09 +00:00

Codex

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

Purpose:

  • keep zlh-grind root focused on platform-wide context
  • track API, Portal, and Agent 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

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