Cloudworkz OS
Welcome flow · v1.0 · first wave
Onboarding · First wave

Welcome to Cloudworkz OS.

You're one of the first five on the new company operating system. This is your setup guide — pick your name below, work through the steps, and you'll be live by your day-one date.

I am
Welcome

Claudia Chavez

Visual brand · Yachay principal
Your day one — Sunday 24 May, afternoon

How Cloudworkz OS works

Four surfaces, four jobs. Each one does what the others don't. You don't need to live in all four — your stack tells you which to open for which job.
TThe Vault
Source of truth
Where Tom + Claude work and where canonical state lives. You don't edit it directly — your work flows in through the other three surfaces.
TTeam HTML
Daily read
A single web page you bookmark. Shows the company's goals, this-week priorities, and everyone's commitments. Open it once each morning.
NNotion
Ops board
Where you'd usually live — kanban, tasks, comments, blockers. Your operational day-to-day on the cross-team work.
SSlack
Comms layer
React with 📝 on any message to capture it into the OS. 🧠 captures to your daily log. 🗣️ transcribes audio attachments.
How it ties together: The vault is the brain. The HTML page is the view. Notion is the kanban. Slack is the comms. Every action you take on Notion or Slack flows back into the vault, where Claude reads it and where Tom acts on it. You don't manage the wiring — you just work, and the OS keeps itself in sync.

How meetings live in your OS

Meetings aren't a fifth surface — they flow through the four. Fireflies records the call, the transcript lands in the vault, the daily-log-writer engine pulls the decisions into your Daily/, ad-hoc Slack audio captures via 🗣️ reaction. Your specific routes:
Recorded
Fireflies auto-joins your Sunday onboarding session with Tom and any future Yachay strategy calls. Nothing for you to configure — the bot joins from the calendar invite.
Stored
Transcripts land in Intelligence/meetings/, searchable across the vault. Ask Claude in any session: "pull the Yachay session transcript".
Summarised
Decisions surface in your Daily/YYYY-MM-DD.md by the next morning via the daily-log-writer engine. You don't write the summary; you read it.
Captured ad-hoc
In Slack, react 🗣️ on any audio attachment to transcribe it into the OS. 📝 captures a text snippet to Tom's triage inbox. 🧠 captures to your own daily log.

Your Claude skill stack

Custom skills that auto-load when you open Cowork. You don't invoke them by name — they trigger on the work you're doing.
Tier 3 · Function
ai-video-production
Loads when you start visual-brand or video work. Includes the four-rung structure from your uptooling brief plus the May 2026 tool stack research. Use it to interrogate any rung approach.
Tier 1 · Universal
vault-operator
Background agent — runs every four hours, writes a roll-up note into your Daily/ folder. You don't invoke it; it just keeps your daily log fresh.

Your step-by-step setup

Seven steps. About 30 minutes. Tick each box as you go — progress saves locally in your browser.
0 of 7 steps complete
  • 01Install Cowork desktop
    Download from claude.ai/cowork. Sign in with claudia@cloudworkz.com. Skip if already installed.
  • 02Accept your vault access invite
    Tom will Slack you the Relay invite individually (sent per-person, not via this page). Accepting it gives you read+write access to the company's shared knowledge folders.
  • 03Bookmark your three surfaces
    Team HTML page · Notion ops board · Slack workspace. Right-click each → Add to bookmarks.
  • 04Test your skill stack loads
    Open Cowork, start a new chat, type show me your call surface. You should see ai-video-production in the list. If it doesn't appear, message Tom in Slack before the session.
  • 05Read your two briefs
    Your uptooling brief V2 in full again (it's been a few days): Team/cloudworkz/Profiles/tom-king/Outbox/2026-05-23-claudia-uptooling-brief-V2.md. Then the rollout brief V1 §3 and your row in §7: Projects/Team-Rollout/README.md. Open both in Obsidian. ~20 minutes total.
  • 06Have your Yachay references ready
    For Sunday's session: the three Yachay paintings you'd use for rung 3, your view on which AI-video tool you'd pick for rung 1, any blockers you've already spotted on the four-rung climb.
  • 07Block 60–90 minutes Sunday afternoon
    Tom will Slack DM you the exact time on Saturday. Find a quiet room. Bring your laptop with Cowork open and the bookmarks loaded.

Your first piece of work

Cloudworkz operates on goal-not-task. You get a goal and the context — you come back with how you'd do it, then execute.
Rung 1 of 4

The silent slideshow

A 60-second silent slideshow from the Unlock investor deck V12, carrying the why-1-in-10 argument with Ken-Burns motion. Tool your call. The acceptance test is functional — someone who's never seen the deck gets the core claim from 60 seconds of silent video.
Approach doc due: Mon 25 May EOD Piece due: Fri 5 Jun Format: 1080p mp4

Your week — first commitments

Approach-first cadence: doc before deliverable, three options before pick, why before execution.
Sun 24 May PM
Onboarding session with Tom. 60–90 minutes.
Mon 25 May EOD
Rung 1 approach doc into your Outbox. Three options, the one you'd pick, why.
Tue 26 May EOD
Personal-discovery doc returned (template arrives Sunday).
Wed 27 May EOD
Capability-matrix approach-back to Tom.
Fri 29 May 17:00
One-week checkpoint. The five-question test (see below).
Fri 5 Jun
Rung 1 piece due.

Where to push back

Surfaces for different kinds of friction. None of these is private — disagreement is a signal we want.
Quick + verbal
Slack DM Tom. 📝 reaction on any message captures it into his triage inbox.
Skill or framework friction
If your skill stack loads wrong, flag in Slack. Friday Decision Lab is the formal forum.
Longer written pushback
Drop a one-pager in your Outbox folder. Slack Tom the path.
Timeline disagreement
Raise the alternative timeline with the constraint that's making the current one wrong.

The Friday test — answers you should have by 17:00 BST

If you can't answer any of these by Friday 29 May, flag it — the rollout adjusts before week two.
  1. Where do I look for what's mine to do today?
    The team HTML page first thing. Your Notion ops board for cross-team items. Your Outbox for drafts waiting on you.
  2. Where do I push back when I see a problem?
    Slack DM Tom with a 📝 reaction (instant capture), or a written one-pager in your Outbox for longer pushback.
  3. Where does my work land when it's done?
    Your Outbox for approach docs and drafts to Tom. Yachay-specific pieces under Projects/Yachay/.
  4. Where do I find the company's framework or prior decision?
    Your auto-loaded skill stack handles the framework load. Or ask Claude in any session: "load Resources/frameworks/{name}".
  5. Which Claude surface do I open for which job?
    Cowork desktop for everything by default. claude.ai web if you're away from your machine. Claude-in-Slack for quick captures.
Welcome

Fiorella Ravelo Dávila

Marketing Operations · growth lane
Your day one — Monday 25 May, morning

How Cloudworkz OS works

Four surfaces, four jobs. You'll mostly live in Notion + the HTML page, with Slack as the comms layer and the vault as the system of record behind the scenes.
TThe Vault
Source of truth
Where Tom + Claude work and where canonical state lives. You won't edit it directly — Notion and Slack pipe your work into it.
TTeam HTML
Daily read
A single web page you bookmark. Shows the company's goals, this-week priorities, everyone's commitments. Open it once each morning.
NNotion
Ops board
Your primary surface. Marketing kanban lives here. Comments and status changes sync back to the vault automatically.
SSlack
Comms layer
React with 📝 on any message to capture it into the OS. 🧠 captures to your daily log. 🗣️ transcribes audio attachments.
How it ties together: The vault is the brain. The HTML page is the view. Notion is the kanban. Slack is the comms. Every action you take on Notion or Slack flows back into the vault — Claude reads it, Tom acts on it. You don't manage the wiring — you just work.

How meetings live in your OS

Meetings flow through the four surfaces — Fireflies records, transcripts store in the vault, decisions summarise into your Daily/, ad-hoc Slack audio captures via 🗣️ reaction. For marketing specifically, every campaign-review call becomes searchable signal you can build on. Your specific routes:
Recorded
Fireflies auto-joins your Monday group onboarding + the paired session with Tom + your Friday weekly review. Marketing kick-offs and campaign reviews get auto-joined when they're on the calendar.
Stored
Transcripts land in Intelligence/meetings/. Marketing-specific calls get tagged so you can pull e.g. "all conversion-lane discussions in the last month" via Claude in Cowork.
Summarised
Campaign decisions surface in your Daily/YYYY-MM-DD.md within hours of the call. The marketing-orchestrator skill pulls these in when you're planning the next campaign.
Captured ad-hoc
In Slack, react 🗣️ on any audio attachment to transcribe + route. 📝 captures a text snippet to Tom's triage inbox. 🧠 captures to your daily log. Useful for voice notes between sessions.

Your Claude skill stack

Custom skills that auto-load when you open Cowork. Trigger on the work you're doing — no naming needed.
Tier 2 · Dept orchestrator
cw-marketing-orchestrator
The marketing-side router. Knows when to call 10×4 vs brand-voice vs the design-system reference. Loads automatically for you.
Tier 3 · Function
10x4-persona
Loads when you're interrogating campaigns or content against personas. 10 P-codes × 4 motivational engines — the canonical model, not "5 archetypes".
Tier 3 · Function
brand-voice
Loads when you're drafting external-facing copy. Cloudworkz voice; references the brand doc.
Tier 1 · Universal
vault-operator
Background agent — runs every four hours, writes a roll-up note into your Daily/ folder. You don't invoke it; it just keeps your daily log fresh.

Your step-by-step setup

Seven steps. About 30 minutes. Tick each box as you go — progress saves locally in your browser.
0 of 7 steps complete
  • 01Install Cowork desktop
    Download from claude.ai/cowork. Sign in with your Cloudworkz email. Skip if already installed.
  • 02Confirm vault access
    Your Relay invite was confirmed Friday 22 May. Open Obsidian, confirm the 16 shared folders are visible. If anything's missing, flag in Slack.
  • 03Bookmark your three surfaces
    Team HTML page · Notion ops board · Slack workspace. Right-click each → Add to bookmarks.
  • 04Test your skill stack loads
    Open Cowork, start a new chat, type show me your call surface. You should see cw-marketing-orchestrator, 10x4-persona, brand-voice. Flag in Slack #leadership if any are missing.
  • 05Read the briefs
    Rollout brief V1 §3, §5, §7: Projects/Team-Rollout/README.md. Open in Obsidian. ~15 minutes.
  • 06Read your row in the config
    Tom shares the cw-team-rollout-config-v1 rollout config after he submits it. Confirms your client, your surface, your stack, the four-question answers.
  • 07Prepare for Monday AM
    Bring your view on conversion-lane status (with Vanessa + Claudia), T034 status, and which campaign you'd ship in week one as your acceptance-test piece.

Your first piece of work

Cloudworkz operates on goal-not-task. You get a goal and the context — you come back with how you'd do it, then execute.
This week's acceptance test

A campaign brief shipped without Tom in the loop

Pick the campaign — investor demo invitation, post-Roose first-touch email sequence, conversion-lane validation. Run it end-to-end. The acceptance test is functional: the work ships, the metric moves, and Tom didn't touch it. The growth/acquisition split makes growth yours; Will owns acquisition.
Approach due: Tue 26 May EOD Campaign shipped: Fri 29 May Review: Friday weekly

Your week — first commitments

Approach-first cadence: doc before deliverable, three options before pick, why before execution.
Mon 25 May AM
Group onboarding session. 60–90 minutes with Will, Werner, Roy.
Mon 25 May PM
Paired 20-min session with Tom. Bookmarks confirmed; one-piece-of-work commitment locked.
Tue 26 May EOD
Personal-discovery doc + campaign-brief approach returned.
Wed 27 May EOD
Capability-matrix approach-back to Tom.
Fri 29 May 17:00
One-week checkpoint. The five-question test. Weekly review with Tom.

Where to push back

Disagreement is a signal we want. None of these is private.
Quick + verbal
Slack DM Tom. 📝 reaction on any message captures it into his triage inbox.
Skill or framework friction
If 10x4-persona surfaces the wrong persona for a campaign, flag — we extend the skill in week two.
Lane friction with Will
Growth/acquisition split unclear on a deliverable? Raise at Monday's session — we settle it there.
Longer written pushback
Drop a one-pager in your Outbox folder. Slack Tom the path.

The Friday test — answers you should have by 17:00 BST

If you can't answer any of these by Friday 29 May, flag it — the rollout adjusts before week two.
  1. Where do I look for what's mine to do today?
    Team HTML page first. Your Notion ops board for marketing kanban. Slack threads where you're @-mentioned.
  2. Where do I push back when I see a problem?
    Slack DM Tom with a 📝 reaction (instant capture), or a written one-pager in your Outbox for longer pushback.
  3. Where does my work land when it's done?
    Notion ops board for marketing tasks. Your Outbox for drafts and approach docs to Tom. Notion comments sync back to the vault automatically.
  4. Where do I find the company's framework or prior decision?
    Your auto-loaded skill stack handles the framework load. Or ask Claude: "load Resources/frameworks/10x4-persona".
  5. Which Claude surface do I open for which job?
    Cowork desktop for everything by default. claude.ai web if you're away from your machine. Claude-in-Slack for quick captures.
Welcome

Werner Snyman

CTO · Lane 1 products + Lane 2 OS substrate
Your day one — Monday 25 May, morning

How Cloudworkz OS works

Four surfaces, four jobs. You'll work across all four — vault for your framework files and product specs, Notion for cross-team visibility, HTML for the daily read, Slack for comms.
TThe Vault
Source of truth
Substrate A — your framework files, product specs, and substrate design notes live here. You'll edit through Obsidian directly when working on those.
TTeam HTML
Daily read
A single web page you bookmark. Shows the company's goals, this-week priorities, everyone's commitments.
NNotion
Ops board
Cross-team visibility on your product/content work. Decisions made in the vault appear here for team comments, which sync back.
SSlack
Comms layer
React with 📝 on any message to capture it into the OS. 🧠 captures to your daily log. 🗣️ transcribes audio attachments.
Substrate clarity: Substrate A = vault + Cowork + Relay (operational). Substrate B = BOSS OS, the Supabase Content Engine and orchestration layer you're building (Lane 2). Substrate C = code repos (Roy's lane). All three coexist; this OS is Substrate A.

How meetings live in your OS

Meetings flow through the four surfaces — Fireflies records, transcripts store in the vault, decisions summarise into your Daily/, ad-hoc Slack audio captures via 🗣️ reaction. For your work specifically, framework-architecture calls become a searchable substrate for the next design pass. Your specific routes:
Recorded
Fireflies auto-joins your Monday group session + Content Engine design sessions, Lane 1 product calls, and Substrate B scoping calls on the calendar.
Stored
Transcripts land in Intelligence/meetings/. Framework/substrate discussion transcripts are searchable across the vault — useful when re-deriving a design decision you took two weeks ago.
Summarised
Framework decisions surface in your Daily/YYYY-MM-DD.md within hours. Your product and belief-map skills reference these when called by other orchestrators (e.g. Fiorella's marketing skill).
Captured ad-hoc
In Slack, react 🗣️ on any audio attachment to transcribe + route. 📝 captures a text snippet to Tom's triage inbox. 🧠 captures to your daily log. Friday Decision Lab summaries land here.

Your Claude skill stack

Custom skills that auto-load when you open Cowork. Your stack covers the product-side orchestrator pattern and the belief-map reference; the design-system skill home is being decided this week and will land in your stack once locked.
Tier 2 · Dept orchestrator
cw-product-orchestrator
The product-side router. Knows when to call belief-map-v3 and other product-side skills. Loads automatically for you.
Tier 3 · Function
belief-map-v3
HNW investor belief structure. Loads when you're working on positioning, perimeter, or risk semantics.
Tier 1 · Universal
vault-operator
Background agent — runs every four hours, writes a roll-up note into your Daily/ folder.

Your step-by-step setup

Seven steps. About 30 minutes. Tick each box as you go — progress saves locally in your browser.
0 of 7 steps complete
  • 01Confirm Cowork desktop is signed in
    Should already be set up from Friday. If not: download from claude.ai/cowork.
  • 02Confirm vault access
    Your Relay invite was confirmed Friday 22 May. Open Obsidian, confirm the 16 shared folders are visible.
  • 03Bookmark your three surfaces
    Team HTML page · Notion ops board · Slack workspace.
  • 04Test your skill stack loads
    Open Cowork, start a new chat, type show me your call surface. You should see cw-product-orchestrator, belief-map-v3. Flag in Slack if any are missing.
  • 05Read the briefs
    Rollout brief V1 §3, §5, §7: Projects/Team-Rollout/README.md. Skill-architecture brief §3 (your stack) + §7 (alignment rules): Projects/Team-Rollout/skill-brief.md. Open both in Obsidian. ~25 minutes total.
  • 06Prepare your stage-1 brief
    Per the delegation task on Tom's list: stage-1 OS team setup parity from a product point of view. Three options for what you'd build first to get Substrate A and Substrate B properly aware of each other, the one you'd pick, why.
  • 07Prepare for Monday AM
    Bring stage-1 brief + view on where the hybrid model needs Substrate A changes you haven't anticipated + cascade-stamper status.

Your first piece of work

Cloudworkz operates on goal-not-task. You get a goal and the context — you come back with how you'd do it, then execute.
This week's acceptance test

Substrate B → Notion → vault round-trip

One Werner-driven content decision flows vault → Notion ops board → team comment → vault triage inbox, end-to-end, by Friday 29 May. The acceptance test is one full round-trip — you make a decision, the team sees it, someone comments, the comment lands back as triage, you respond.
Stage-1 brief: Mon 25 May EOD Round-trip: Fri 29 May Cascade-stamper: Fri 29 May

Your week — first commitments

Approach-first cadence: doc before deliverable, three options before pick, why before execution.
Mon 25 May AM
Group onboarding session. 60–90 minutes.
Mon 25 May EOD
Stage-1 OS team setup parity brief returned to Tom.
Tue 26 May EOD
Personal-discovery doc returned.
Wed 27 May EOD
Capability-matrix approach-back to Tom.
Fri 29 May
Substrate B round-trip live. Cascade-stamper + 4 schema-fields + reversibility tests landed.
Fri 29 May 17:00
One-week checkpoint. The five-question test.

Where to push back

Disagreement is a signal we want. None of these is private.
Hybrid-model adjustments
If the hybrid model needs Substrate A changes Tom hasn't anticipated, flag at Monday's session — we adjust the brief, don't paper over.
Design-system skill semantics
Where the design-system skill home lands is being decided this week. If you hit a gap calling it during work, flag in Slack — Friday Decision Lab is the formal forum if it persists.
Gating other people's work
If your Substrate B work is gating someone else's week, raise it on the team HTML surface so they see it.
Longer written pushback
Drop a one-pager in your Outbox folder. Slack Tom the path.

The Friday test — answers you should have by 17:00 BST

If you can't answer any of these by Friday 29 May, flag it — the rollout adjusts before week two.
  1. Where do I look for what's mine to do today?
    Team HTML page first. Your Notion ops board for product/content items. Vault Daily/ for the auto-rollup.
  2. Where do I push back when I see a problem?
    Slack DM Tom with a 📝 reaction. Friday Decision Lab for skill-architecture or framework-level disagreement.
  3. Where does my work land when it's done?
    Vault directly for framework + product-spec source. Notion ops board for cross-team decisions. Your Outbox for drafts.
  4. Where do I find the company's framework or prior decision?
    Your auto-loaded skill stack. For older decisions: Intelligence/decisions/. For Lane 1 product specs: Context/services.md + your project folders under Projects/.
  5. Which Claude surface do I open for which job?
    Cowork desktop for everything by default. claude.ai web if you're away from your machine. Claude-in-Slack for quick captures.
Welcome

William Corke

Acquisition · finance ownership
Your day one — Monday 25 May, morning

How Cloudworkz OS works

Four surfaces, four jobs. You'll live in Notion + the HTML page, with the cost-tracking dashboard rendered into the HTML surface as you build it.
TThe Vault
Source of truth
Where canonical state lives. Tom + Claude work here. Your work flows in through Notion + Slack.
TTeam HTML
Daily read
The web page you bookmark. Goals, priorities, commitments. Your cost-tracking dashboard renders into this surface as you build it.
NNotion
Ops board
Your primary surface. Ops + finance kanban lives here. Comments sync back to the vault.
SSlack
Comms layer
React with 📝 on any message to capture it. 🧠 captures to your daily log. 🗣️ transcribes audio attachments.
Lane clarity: Growth/acquisition split — acquisition is yours, growth is Fiorella's. Finance ownership is yours end-to-end. The cost-tracking app you build (Aircall + tokens + agent time) becomes the surface for what acquisition costs us.

How meetings live in your OS

Meetings flow through the four surfaces — Fireflies records, transcripts store in the vault, decisions summarise into your Daily/, ad-hoc Slack audio captures via 🗣️ reaction. For finance specifically, Friday Decision Lab transcripts become the audit trail for every pacing call. Your specific routes:
Recorded
Fireflies auto-joins your Monday group session, GG pacing reviews with Roy, and the formalised Friday Decision Lab. Aircall recordings live separately in Aircall but pipe into your cost-tracking dashboard.
Stored
Transcripts land in Intelligence/meetings/. Pacing-decision transcripts are searchable — useful when reviewing how a budget call landed three weeks ago.
Summarised
Pacing + budget decisions surface in your Daily/YYYY-MM-DD.md within hours. The friday-decision-lab skill loads transcripts when you're planning next week's agenda.
Captured ad-hoc
In Slack, react 🗣️ on any audio attachment to transcribe + route. 📝 captures a text snippet to Tom's triage inbox. 🧠 captures to your daily log. Useful for voice memos after an Aircall call.

Your Claude skill stack

Custom skills that auto-load when you open Cowork. The Friday Decision Lab skill formalises your weekly OKR review pattern.
Tier 2 · Dept orchestrator
cw-finance-orchestrator
The finance-side router. Knows when to call friday-decision-lab vs cost-tracker. Loads automatically for you.
Tier 3 · Function
friday-decision-lab
Formalises the OKR-review cadence so you can run it weekly without re-deriving it. Loads when you're planning or reviewing Friday agendas.
Tier 3 · Function
cost-tracker
Wrapper around the Aircall + token + agent-time data sources. Loads when you're working on the live cost-tracking app or weekly cost reviews.
Tier 1 · Universal
vault-operator
Background agent — runs every four hours, writes a roll-up note into your Daily/ folder.

Your step-by-step setup

Seven steps. About 30 minutes. Tick each box as you go — progress saves locally in your browser.
0 of 7 steps complete
  • 01Confirm Cowork desktop is signed in
    Should already be set up from Friday. If not: download from claude.ai/cowork.
  • 02Confirm vault access
    Your Relay invite was confirmed Friday 22 May. Open Obsidian, confirm the 16 shared folders are visible.
  • 03Bookmark your three surfaces
    Team HTML page · Notion ops board · Slack workspace.
  • 04Test your skill stack loads
    Open Cowork, start a new chat, type show me your call surface. You should see cw-finance-orchestrator, friday-decision-lab, cost-tracker. Flag if missing.
  • 05Approve the Unlock G Suite domain access
    Per the task on Tom's list — Claude needs domain-level access for the cost-tracking app to pull Aircall data via Google Workspace.
  • 06Read the briefs
    Rollout brief V1 §3, §5, §7: Projects/Team-Rollout/README.md. Open in Obsidian. ~15 minutes.
  • 07Prepare for Monday AM
    Bring your approach for the cost-tracking app — data sources, dashboard shape, gating questions it answers, three options, the one you'd pick, why.

Your first piece of work

Cloudworkz operates on goal-not-task. You get a goal and the context — you come back with how you'd do it, then execute.
This week's acceptance test

Cost-tracking dashboard v0 — live data

A first cost-tracking dashboard view, live and pulling real data, by Friday 29 May. Aircall costs, agent time, token spend per session. The acceptance test: Tom opens the dashboard Friday afternoon and sees what this week cost the company and where the leverage is.
Approach due: Tue 26 May EOD G Suite approval: Mon 25 May Dashboard v0: Fri 29 May

Your week — first commitments

Approach-first cadence: doc before deliverable, three options before pick, why before execution.
Sat 23 / Sun 24 May
GG (Opulence Bloodstock) lead-count number pulled with Roy. Frames the 29 May pacing decision.
Mon 25 May AM
Group onboarding session. 60–90 minutes.
Mon 25 May
Unlock G Suite domain approval to Claude.
Tue 26 May EOD
Personal-discovery doc + cost-tracking approach returned.
Wed 27 May EOD
Capability-matrix approach-back to Tom.
Fri 29 May
Cost-tracking dashboard v0 live. Quarterly budget build complete. Pacing decision drafted for the team meeting.
Fri 29 May 17:00
Friday Decision Lab — the cadence formalises here. The five-question test.

Where to push back

Disagreement is a signal we want. None of these is private.
Skill too narrow
If cost-tracker is too narrow for cross-cutting accountancy work, flag — we widen it or add a sibling skill.
Pacing decision needs more
If GG pacing needs more than just the lead-count number to land, raise at the Monday session.
Aircall data friction
Auth issues on Aircall pulls — ping Roy directly. That's his lane (Substrate C).
Longer written pushback
Drop a one-pager in your Outbox folder. Slack Tom the path.

The Friday test — answers you should have by 17:00 BST

If you can't answer any of these by Friday 29 May, flag it — the rollout adjusts before week two.
  1. Where do I look for what's mine to do today?
    Team HTML page first. Your Notion ops board for ops + finance items. Cost-tracking dashboard once it's live.
  2. Where do I push back when I see a problem?
    Slack DM Tom with a 📝 reaction. Friday Decision Lab for the formal forum.
  3. Where does my work land when it's done?
    Notion ops board for ops/finance items. Cost-tracking dashboard for live data. Your Outbox for drafts.
  4. Where do I find the company's framework or prior decision?
    Your auto-loaded skill stack. For older finance decisions: CW — Finance & Reporting/. For company strategy: Context/strategy.md.
  5. Which Claude surface do I open for which job?
    Cowork desktop for everything by default. claude.ai web if you're away from your machine. Claude-in-Slack for quick captures.
Welcome

Roy Mendoza

OS technical wiring · Substrate C
Your day one — Monday 25 May, morning

How Cloudworkz OS works

Four surfaces, four jobs. You own the wiring layer — the integrations that pipe data between Substrate C tools and the OS. Daily Pipedrive snapshots into the team HTML are your visibility surface.
TThe Vault
Source of truth
Your daily Pipedrive snapshots land here, which the team HTML surface picks up. Substrate A — the OS layer that knows about everything.
TTeam HTML
Daily read
Where Tom + the team see your sales-loop work without you reporting it manually. Your snapshots render here.
NNotion
Ops board
Sales kanban + ops board. Where cross-team automations get prioritised, scoped, blocked.
SSlack
Comms layer
React with 📝 on any message to capture it into the OS. 🧠 captures to your daily log. 🗣️ transcribes audio attachments.
Substrate clarity: Substrate A = vault + Cowork + Relay (the OS). Substrate B = Werner's BOSS OS (Content Engine + orchestration layer). Substrate C = code repos — your lane. Pipedrive integration, WhatsApp, Aircall, Fireflies recovery, all the integrations that feed the OS.

How meetings live in your OS

Meetings flow through the four surfaces — Fireflies records, transcripts store in the vault, decisions summarise into your Daily/, ad-hoc Slack audio captures via 🗣️ reaction. And the Fireflies pipe itself is yours to own. When transcript signal goes missing, your transcript-recovery skill loads and routes you to the recovery pattern. Your specific routes:
Recorded
Fireflies auto-joins your Monday group session + technical scoping calls with Werner. WhatsApp + Aircall recordings flow through your integrations into Intelligence/meetings/ as separate sources.
Stored
Transcripts land in Intelligence/meetings/. Sales-loop architecture transcripts are searchable. Your daily Pipedrive snapshot renders into team HTML — meeting-driven sales decisions land there visibly.
Summarised
SOP-affecting decisions surface in your Daily/YYYY-MM-DD.md within hours. If a transcript shows the daily-pipedrive-snapshot SOP needs an update, the summary flags it for you to edit.
Captured ad-hoc + Fireflies recovery
In Slack, react 🗣️ on any audio attachment to transcribe + route. Your lane: when the Fireflies pipe drops signal (which it did during the May migration), transcript-recovery skill loads with the recovery pattern. Goal: signal restored by Friday 29 May per your first piece.

Your Claude skill stack

Custom skills that auto-load when you open Cowork. Process-focused rather than framework-focused — your work is wiring, not interrogation.
Tier 2 · Dept orchestrator
cw-sales-orchestrator
The sales-side router. Knows when to call pipedrive-snapshot vs transcript-recovery. Loads automatically for you.
Tier 3 · Function
pipedrive-snapshot
Daily-rhythm wrapper around your Pipedrive integration. Loads when you're working on the SOP or the daily snapshot run.
Tier 3 · Function
transcript-recovery
Wrapper around the Fireflies pipe + synthetic-content-flag pattern. Loads when you're recovering or validating transcript signal.
Tier 1 · Universal
vault-operator
Background agent — runs every four hours, writes a roll-up note into your Daily/ folder.

Your step-by-step setup

Seven steps. About 30 minutes. Tick each box as you go — progress saves locally in your browser.
0 of 7 steps complete
  • 01Install Cowork desktop
    Download from claude.ai/cowork. Sign in with roy@cloudworkz.com.
  • 02Accept your vault access invite
    Tom will Slack you the Relay invite individually (sent per-person, not via this page). Once accepted, confirm the 16 shared folders appear in Obsidian after install.
  • 03Bookmark your three surfaces
    Team HTML page · Notion ops board · Slack workspace.
  • 04Test your skill stack loads
    Open Cowork, start a new chat, type show me your call surface. You should see cw-sales-orchestrator, pipedrive-snapshot, transcript-recovery. Flag in Slack if any are missing.
  • 05Read the briefs + the Sales-Loop spec
    Rollout brief V1 §3, §5, §7: Projects/Team-Rollout/README.md. Sales-Loop toolchain spec, your starting point: Projects/Sales-Loop/whatsapp-pipedrive-toolchain-v1.md. Open both in Obsidian.
  • 06Read the daily Pipedrive snapshot SOP
    Lands Sunday at Departments/Sales/sops/daily-pipedrive-snapshot-v1.md. That's the rhythm you own from Tuesday morning.
  • 07Prepare for Monday AM
    Bring your view on Fireflies recovery (transcript signal lost during migration), git-repo home for the overnight WhatsApp+Pipedrive code, and approach for week one — three options, the one you'd pick, why.

Your first piece of work

Cloudworkz operates on goal-not-task. You get a goal and the context — you come back with how you'd do it, then execute.
This week's acceptance test

Daily Pipedrive snapshot cycle live + Fireflies recovered

One full daily Pipedrive snapshot cycle complete by Wednesday 27 May. Fireflies pipe restored — transcript signal back to the vault — by Friday 29 May. The acceptance test for the snapshot cycle: Tom opens the team HTML surface Wednesday morning and sees yesterday's sales-loop state without asking you for it.
Approach due: Tue 26 May EOD Snapshot live: Wed 27 May Fireflies: Fri 29 May

Your week — first commitments

Approach-first cadence: doc before deliverable, three options before pick, why before execution.
Sat 23 / Sun 24 May
GG (Opulence Bloodstock) lead-count number pulled with Will. Frames the 29 May pacing decision.
Mon 25 May AM
Group onboarding session. 60–90 minutes.
Tue 26 May EOD
Personal-discovery doc + week-one approach returned. Daily Pipedrive snapshot SOP live.
Wed 27 May
One full daily snapshot cycle complete. Visible on team HTML.
Wed 27 May EOD
Capability-matrix approach-back to Tom.
Fri 29 May
Fireflies pipe restored — transcript signal back to the vault.
Fri 29 May 17:00
One-week checkpoint. The five-question test.

Where to push back

Disagreement is a signal we want. None of these is private.
Skill is a stub
transcript-recovery is a v0 stub. If it doesn't capture the Fireflies recovery pattern you actually need, flag — we extend it in week two.
Git-repo blocked
If the git-repo decision with Werner blocks Substrate C work, raise at the Monday session — we settle it there.
SOP doesn't match reality
If the daily Pipedrive snapshot SOP doesn't match the actual Pipedrive shape after first run, edit the SOP — Departments/Sales/sops/ is yours.
Longer written pushback
Drop a one-pager in your Outbox folder. Slack Tom the path.

The Friday test — answers you should have by 17:00 BST

If you can't answer any of these by Friday 29 May, flag it — the rollout adjusts before week two.
  1. Where do I look for what's mine to do today?
    Team HTML page first. Your Notion ops board for sales kanban. Vault Daily/ for the snapshot rhythm.
  2. Where do I push back when I see a problem?
    Slack DM Tom with a 📝 reaction. SOP edits go in Departments/Sales/sops/ directly.
  3. Where does my work land when it's done?
    Daily snapshots into the vault → render in team HTML. Code into the git-repo home (decision Mon). SOPs in Departments/Sales/sops/.
  4. Where do I find the company's framework or prior decision?
    Your auto-loaded skill stack. For sales-loop spec: Projects/Sales-Loop/. For company strategy: Context/strategy.md.
  5. Which Claude surface do I open for which job?
    Cowork desktop for everything by default. claude.ai web if you're away from your machine. Claude-in-Slack for quick captures.
Cloudworkz OS
Welcome flow v1.0 · First wave · One-week checkpoint Fri 29 May 17:00 BST · Questions? Slack Tom directly or react 📝 on any message.
Built 2026-05-25T20:23:39 · render: cw-welcome-onboarding