Review: G-01 — Daily Operations Rhythm (Operating Procedure)

← Back to Operating Procedures slug: g-01-daily-operations-rhythm

G-01 — Daily Operations Rhythm (Operating Procedure)

G-01 Daily Operations Rhythm — cascade, deviation, Ledger contract, review cycle. Status: NOT OPERATIONAL (4 Major NCs).

In Review

Reviewer

—

Reviewed at

—

Steps

Open questions

8 / 8

Open Questions (procedure-level)

Open

NC-1 cascade: should the Daily Big 3 cascade rule be enforced as a hard gate in Step 3b, or flagged as an advisory when Weekly/Quarterly parents are unset?

Open

NC-2 deviation: what is the canonical recovery procedure for a missed weekday /daily-ops run? Backfill standup file, post-mortem Listing, or both?

Open

NC-3 Ledger contract: confirm the minimum required property set for a daily_focus Listing (hs_name, name, body) and whether Ledger should reject writes missing any of them.

Open

NC-4 review cycle: what cadence should scheduled process reviews run on — monthly, per-audit-cycle, or event-triggered?

Open

NC-5 Data Quality table: does "FIRST section of briefing" apply to the conversational briefing output, the persisted standup file, or both?

Open

NC-7 CLI --filters: should the fix be an API CLI parameter repair, or should daily_focus lookup move to GROQ against Sanity instead of HubSpot Listings?

Open

Phase 2 spawns (2g-2m): should each spawn emit an acknowledgement artifact so individual verification is possible without sub-agent-auditor architecture?

Open

Status override: with Status = NOT OPERATIONAL despite 53.8% score, should QMS framework display both metrics, or suppress the percentage when hard overrides fire?

Steps

#1·Phase 1 — Startup
Load `skills/enforcement/vf-platform-context.md`
audit Item 7 confirmed file present; command spec loads it
VERIFIED
#2·Phase 1 — Startup
Load `skills/enforcement/vf-self-correction.md`
audit Item 7 confirmed file present; command spec loads it
VERIFIED
#3·Phase 1 — Startup
Load MEMORY.md + topic files relevant to ops
(implied by 22 successful standups)
VERIFIED
#4·Phase 1 — Startup
Load `.claude/commands/daily-ops.md`
command spec present and invocable
VERIFIED
#5·Phase 1 — Startup
Load session context / WCP open items
not individually observed
UNTESTED
#6·Phase 2 — Data Gather
Run `./scripts/datetime.sh`
script exists, not individually verified by audit
UNTESTED
#7·Phase 2 — Data Gather
Run `scripts/google/get-calendar.js`
UNTESTED
#8·Phase 2 — Data Gather
Run `scripts/google/get-inbox.js`
UNTESTED
#9·Phase 2 — Data Gather
Run `scripts/hubspot/get-social-schedule.js`
UNTESTED
#10·Phase 2 — Data Gather
Run `scripts/canonical/article-query.js --audit`
UNTESTED
#11·Phase 2 — Data Gather
Run `scripts/canonical/unified-audit.js`
UNTESTED
#12·Phase 2 — Data Gather
Spawn Sentinel (relationship monitor)
individually
UNTESTED
#13·Phase 2 — Data Gather
Spawn Pulse (portfolio health)
individually
UNTESTED
#14·Phase 2 — Data Gather
Spawn Beacon (status)
individually
UNTESTED
#15·Phase 2 — Data Gather
Spawn Prelude (media pre-prod)
individually
UNTESTED
#16·Phase 2 — Data Gather
Spawn Encore (media post-prod / recording verify)
individually
UNTESTED
#17·Phase 2 — Data Gather
Spawn Marshal (PM state)
individually
UNTESTED
#18·Phase 2 — Data Gather
Spawn Ledger (HubSpot write state)
individually
UNTESTED
#19·Phase 2 — Data Gather
Query HubSpot Listings for `weekly_big3`
CLI `--filters` silently dropped (NC-7)
BLOCKED
#20·Phase 2 — Data Gather
Query HubSpot Listings for `quarterly_big3`
CLI `--filters` silently dropped (NC-7)
BLOCKED
#21·Phase 2 — Data Gather
Query HubSpot Listings for `daily_focus` (yesterday rollforward)
CLI `--filters` silently dropped (NC-7)
BLOCKED
#22·Phase 3 — Integrate & Present
Present Data Quality table as FIRST section of briefing
NC-5. Spec ambiguity: rule applies to briefing output (conversation) vs persisted standup file. Rule cannot be measured.
BLOCKED
#23·Phase 3 — Integrate & Present
Cascade Daily Big 3 from Weekly ← Quarterly
NC-1. Chronically broken: Q2 Quarterly unset through Apr 16 making cascade structurally impossible. Apr 20 was first date with parents set; Daily still did not cascade.
BLOCKED
#24·Phase 3 — Integrate & Present
Present per-section briefing (schedule, inbox, ops, pulse, media, BU state)
UNTESTED
#25·Phase 4 — Standup Handoff
Write `.claude/daily/{date}-standup.md` with per-leader sections
22 files present; 88% weekday coverage across 35-day window; Apr 20, Apr 17, Apr 16 read and confirmed
VERIFIED
#26·Phase 4 — Standup Handoff
V / Sage / Pax / 7 BU Leader sections populated
audit Item 3a confirmed on Apr 20 standup
VERIFIED
#27·Phase 5 — Daily Big 3 Set and Persist
Suggest Big 3 items aligned to Weekly → Quarterly cascade
downstream of Step 3b (NC-1)
BLOCKED
#28·Phase 5 — Daily Big 3 Set and Persist
Chris confirms the three items
depends on 5a
UNTESTED
#29·Phase 5 — Daily Big 3 Set and Persist
Ledger persists confirmed Big 3 as `daily_focus` Listing with full contract (`hs_name`, `name`, body)
NC-3 + NC-7. Apr 20 `daily_focus` not found; Listing 549307086996 has null `name`/body. Ledger write contract gap + CLI enumeration gap compound the failure.
BLOCKED
#30·Phase 6 — Deviation Handling
On missed / failed `/daily-ops`, execute documented recovery procedure
NC-2. No recovery procedure exists. Mar 26 and Mar 31 weekday misses have no backfill, post-mortem, or audit record.
NOT BUILT
#31·Phase 7 — Review Cycle
Run scheduled process review: compare observed behavior to stated intent, cite evidence, reach judgment
NC-4. 60+ days of operation, zero review artifacts. 40+ commits are feature/wiring, not review.
NOT BUILT

Review History

4/22/2026, 4:01:16 AM draft → in_review
Seeded from markdown for Chris review.

8 open questions must be answered before approving.