Add Monitoring to Codex index

This commit is contained in:
jester 2026-05-01 21:06:45 +00:00
parent 130fc5eeda
commit be9244e2af

View File

@ -4,19 +4,20 @@ Codex is the repo-specific execution layer for active work.
Purpose: Purpose:
- keep `zlh-grind` root focused on platform-wide context - keep `zlh-grind` root focused on platform-wide context
- track API, Portal, and Agent work separately - track API, Portal, Agent, and Monitoring work separately
- make it easier to remove completed items instead of letting them linger in one shared backlog - make it easier to remove completed items instead of letting them linger in one shared backlog
Use this structure: Use this structure:
- `Codex/API/*` for `jester/zpack-api` - `Codex/API/*` for `jester/zpack-api`
- `Codex/Portal/*` for `jester/zpack-portal` - `Codex/Portal/*` for `jester/zpack-portal`
- `Codex/Agent/*` for `jester/zlh-agent` - `Codex/Agent/*` for `jester/zlh-agent`
- `Codex/Monitoring/*` for monitoring host / observability coordination
File roles: File roles:
- `README.md` front door for that repo track - `README.md` - front door for that repo track
- `CURRENT_STATE.md` what is actually implemented now - `CURRENT_STATE.md` - what is actually implemented now
- `OPEN_ITEMS.md` only unfinished work - `OPEN_ITEMS.md` - only unfinished work
- `DECISIONS.md` important settled choices / do-not-re-litigate notes - `DECISIONS.md` - important settled choices / do-not-re-litigate notes
Operational rules: Operational rules:
- remove completed items from `OPEN_ITEMS.md` promptly - remove completed items from `OPEN_ITEMS.md` promptly