Ops / CoS · Active · Pepper Potts

Exec team ops + cadence design

Phase-1 exec coordination is live. Daily/weekly cadence design still pending with Ryan.

Active INTERNAL

Owner · Dept

Pepper Potts · Ops / Chief of Staff

Status

Active. Phase-1 exec coordination live; daily/weekly cadence design pending with Ryan. No invented routines — cadence only after a workflow is trusted (Four C’s).

Desktop path

Desktop\Modern-Solution-Ops\00-Shared-Knowledge-Base\ops\COMMUNICATION-PROTOCOL.md

What is live

Hierarchy: Ryan ↔ Pepper only for strategy; Pepper ↔ execs for tasking; execs ↔ their operators.
Leadership channel: Pepper + all Phase-1 execs — weekly priorities and cross-lane decisions (not a task dump).
Prefer 1:1 DM Pepper → one exec for concrete tasks.

Four C’s Cadence (from protocol)

C	Meaning	MS default
Context	Who we are, goals, brand, folders	`00-Shared-Knowledge-Base` + dept folders
Connections	Live tools	Plugins + Composio (Tony owns matrix). Cloudflare Pages → Marketing/Miranda.
Capabilities	Skills / recipes	Named skills per org map; bike-method feedback before expanding
Cadence	Routines	Only after a workflow is trusted

No daily/weekly routine invented here. Cadence design waits on Ryan.

Status

Desktop path

What is live

Four C’s Cadence (from protocol)

Key links