Daily Operating Rhythm — Collins × Akash

2026-07-13 · How every workday runs: the daily meeting, Slack (our team chat), the scoreboard, the metrics Collins owns, the end-of-day report, and the logoff checklist. Locks before day 1 (Jul 14).

The day in one paragraph

Collins starts Jul 14, part-time, about 20 hours a week. Each workday has a simple shape. 1–2 PM: Akash and Collins meet live — every day during the part-time ramp. 2–4 PM: Collins builds on his own. 4 PM: Collins posts a short end-of-day report in Slack (#daily-reports). Akash's mornings stay free for deep thinking. Nothing is run by chat back-and-forth; the meeting and the scoreboard run the work.

⚑ Confirm at kickoff: whose 1 PM?

Collins works Philippines time. Akash works Eastern time. The daily meeting is "1 PM" — but we have not fixed whose clock. 1 PM in one zone is the middle of the night in the other. First thing at kickoff: pick the exact time that works for both, in both zones, and write it down. Until then, treat every "1 PM" on this page as "to be confirmed."

1 · The daily meeting (1–2 PM)

The agenda (same order every day)

SegmentWhat happens
Scoreboard readOpen the scoreboard, not memory. Yesterday's actuals vs target, per lane. Any red lane gets named with its owner. Skip the green ones.
YesterdayFrom the end-of-day report: what shipped (links), what broke, what got checked. Questions only — the report already said it.
TodayCollins names his ONE priority and the slate plan. Akash confirms or re-aims in one sentence.
DecisionsCollins' saved-up questions. Akash answers each fast, or parks it with a date. This is the one place decisions queue.
Taste-passAkash reviews the day's creative and gives a go / fix. In week 1 this is daily.

2 · Slack — our team chat

Slack is the main place we talk as a team. Collins joins on day 1. WhatsApp stays only for quick pings until he is fully set up in Slack.

ChannelWhat goes here
#daily-reportsCollins posts his 4 PM end-of-day report here. Daily numbers land here too.
#client-onboardingEverything about onboarding new clients — Collins' first build. Questions, status, hand-offs.
#call-insBooked calls and inbound-call notes. Who called, what they need, what happens next.
#notesQuick thoughts, ideas, and small questions that are not a full report.
#documentsLinks to docs, plans, and finished work — one place to find shared files.

Rule of thumb: reports and numbers → #daily-reports · client setup → #client-onboarding · call activity → #call-ins · loose notes → #notes · file links → #documents.

3 · The scoreboard that drives the meeting

The Loop Engine (our auto-scoreboard) is BUILT and running — checked against the brain (our shared memory database) today. It is further along than the old gap notes assumed:

What still needs dialing in (week-2 work for Collins)

#GapFixOwner
1No single daily page yet — the data lives in the databaseBuild the scoreboard page: 8 lanes with target / actual / gap, red lane first, plus Collins' production row. The meeting opens this page.Claude/agents — before day 1
2Collins' daily production lanes are not registered metrics yetRegister his lanes: daily-slate done (5/5 formats), ads staged, and the sales-automation speed and coverage metrics.Claude/agents
3Feeds for those lanesWire them from what exists: the content queue, the staged-ads list, and the follow-up queue.Collins (week 2 — he owns keeping his lanes fed and accurate)
4Targets are starter guesses with 1 week of historyRun 2 clean weeks of set targets and logged actuals before tightening them.System

4 · The metrics Collins owns

LaneLead metric (his daily behavior)Lag metric (what it should cause)Starter target
Daily productiondaily slate done — newsletter + organic + AI-UGC video + carousel + statics shippedqualified applications from content5/5 formats, every workday
Content strategypublish-ready pieces · scripts drafted · statics madequalified applications from content20 scripts/wk · 40 statics/wk
Repurposingsource recordings processedextra assets published≥7 assets per recording
Ad productionads staged — QA'd, captioned, pausedcost-per-lead trend on live testsDaily batch; number set at kickoff
Sales automationspeed-to-lead minutes · follow-up coverage · no-show recoveryqualified calls bookedBaseline in week 3, then targets

Stays Akash's number: cash collected, qualified calls held, ad spend and budgets, and finance. Collins' automation feeds these; he never owns the number.

5 · The end-of-day report (4 PM)

At 4 PM, Collins posts a short report in Slack #daily-reports. The tool builds most of it. Collins adds his judgment. He checks it before it posts.

The tool builds this part (Collins never types it)

Collins writes this part (5 judgment fields)

  1. What I changed or built that the log can't explain in one line.
  2. What I checked, and the proof.
  3. Blocked: the exact blocker and the decision I need (Loom if stuck >30 min — never wait in silence).
  4. What I need from Akash (this becomes tomorrow's meeting decision list).
  5. Tomorrow's first move.

What he checks BEFORE it posts

6 · Logoff checklist (~10 min)

#StepManual?
1Commit and push his work branch from the Codespace. That is the whole file story — no manual drive uploads, no separate backups. Git holds the code and docs; the brain holds the state. (Daily host snapshots are already automated — not his job.)Yes — one command
2Board current: his cards show true status; finished cards moved; next actions updated.Yes — 2 min
3Tomorrow staged: content queue loaded for the full slate; ad inputs picked. No morning scavenger hunt.Yes — until automated (week 2)
4Run the end-of-day command — it builds the report (§5), prompts his 5 fields, writes the handoff row to the brain (tasks land as rows — he does NOT hand-update task lists anywhere), and posts to #daily-reports.5 fields only
5Check pass (§5): "waiting on Akash" list, log complete, nothing auto-sending.Yes — the judgment step

Build before day 1 (Claude/agents): the end-of-day command — steps 4–5 as one command that reads the brain, builds the report, writes the handoff row, and posts to #daily-reports. Week-1 fallback: Collins fills the daily-update template by hand and pastes it in #daily-reports; the tool half gets built for him next day. The checklist holds either way.

Decisions this doc still needs from Akash

Checked against the brain 2026-07-13: 8 department lanes · this week's targets set · daily actuals fresh today · 25 metric definitions · Sunday run 07-12. Terms accepted on the Jul 13 call; start Jul 14. Companion docs: builder-vision-handoff · collins-start-plan · collins-first-call-agenda (all 2026-07-13, this folder).