Record: DIS-019f0ca2-003 Date: 01 July 2026 Source: DIS · session 019f0ca2… · grok-ops-docs-pack Status: Reminder · due 2026-07-05

GPS · Duo-location Nexus Dev

Public	https://nos2.nfsgrp.com/ch/grok-docs/dis-019f0ca2-003-saturday-reminders
Loopback	http://localhost:8190/ch/grok-docs/dis-019f0ca2-003-saturday-reminders
Space	https://nos2.nfsgrp.com/spaces-nav?group=sg-grok-ops&space=grok-docs
Repo	`data/nexdistill-doe/grok-gem-protocol-v1.json`
Plane	N2 Product · ros-server :8190

⏰ Operator reminder — Saturday 5 July 2026 Tagged from GROK DOCS · session 019f0ca2-5c17-71b0-b0c6-2993da3804df

1 Saturday agenda (two linked items)

ID	Topic	Why Saturday
REM-MD-SCRIPTS	MDs and script collections	Paul cannot see agent-written `.md` files in Spaces Nav — need visibility doctrine: what stays in repo, what must publish to LiveDOC/DIS, script collection hygiene under `scripts/`
REM-GESP-GEM	GESP-GEM policy + NexRAM `gem/…` keys	Review wired v1 (coffee boot) vs full NexRAM particle implementation; ratify DIS papers; decide MD→DIS promotion workflow

2 MDs and script collections — scope sketch

Agent default: publish operator-facing prose to GROK DOCS DIS, not orphan docs/**/*.md
Repo .md remains for git/build — but Paul reads LiveDOC in Spaces Nav
Script collections: index in GROK OPS (future) — which packs, which ROSA-delegated, scroll artifact tags
Cross-ref: sg-md-docs under Nexus Development already exists for .MD dump — align or merge?

Read DIS-002 (this pack) + eternal session on Pi pause
Confirm coffee hook fires on SessionStart / PostCompact (/hooks-list)
Decide: NexRAM gem/{session}/{tag}/{card} writer — steward epoch or ingest-grok-sessions?
Promote BOOM cards from session → boot_cards[] when ratified

Reminder stored: scroll tag reminder:2026-07-05 · GEM protocol reminders[] · miniscroll open_wip on next steward apply.