WebLife × Framework Friday · 2026-05-12

Five Pillars Reveal

Install the roadmap. Reveal the five pillars. Address survey questions. Reset the commitment standard.

01Install the 6-stage roadmap — see where you are
02Reveal the Five Value Pillars — where we're going
03Answer two questions from this week's surveys
04Reset the commitment standard

Before we get into it

Wins this week

SadukaGoogle Ads daily briefing routine

ShenaliAmazon monthly performance report

BihaniVenia deliverables tracking (completed)

LaleeshaOnboarded live last session

Dr. YashodaTeam task dashboard (today's survey)

The Path

The 6-Stage Roadmap

From day-one setup to full AI-first orchestration. Most of this cohort will move through Stages 0–3.

STAGE 0

Environment Ready

STAGE 1

Daily Operations

STAGE 2

Context Builder

STAGE 3

Workflow Builder

STAGE 4

AI-First Operator

STAGE 5

Orchestrator

— this cohort works through 0 → 3 —

Snapshot

Where each of you is today

Pull up the HQ adoption page in the next tab. This is the live picture.

Stage 2 — Context Builder

Saduka · Sasindee · Upeksha — most active members on adoption

Stage 0 with active builds

Adam (venture lead) · Bihani · Thushan — commitments running

Stage 0, opportunity to start

Yashoda · Shenali · Hafiz · Laleesha · Ibrahim · Shehara

Forward-looking · not a report card

A note on the data

The roadmap shipped at the end of last week — after our last session.

Most of you haven't seen it in HQ yet. That's expected. Stage 0 with nothing marked isn't anyone behind — it's a new tool we just put in front of you.

Going forward: this is the roadmap. Mark milestones as you go. Why it matters:

It helps you see your own progress.
It helps Adam see how the team is graduating.
It helps Lucas and me see where to support.

Yashoda — your team-task dashboard. Shenali — the Amazon report. Real examples of work that belongs on the roadmap once you mark it.

⏱ 0:15–0:20

CRITICAL: Do NOT scold or audit. The roadmap is brand new. Tone is forward-looking.

Say:

"Quick note before we go further. This roadmap shipped at the end of last week — after our last session together. Most of you probably haven't even seen it in HQ yet. That's fine."

"If your data here shows Stage 0 with nothing marked, that's expected. You haven't had a chance to mark anything yet. This isn't anyone behind — this is a new tool we just put in front of you."

"Going forward, this is the roadmap we expect you to be working through. These six stages are the path of adopting FridayOS. As you go, mark your milestones in HQ."

"Yashoda — you filed a survey today telling me you've got the daily practices in place and you built a team dashboard. When you get a chance, mark those milestones. Shenali — same with the Amazon report. Those are real examples of the work that belongs on the roadmap."

Transition

Stages = HOW · Pillars = WHY

The HOW

Stages

What to learn next. A practical path you walk one step at a time.

The WHY

Pillars

The outcomes you're working toward. The reason the stages matter.

Over the next several sessions we'll spend a full session on each pillar. Today is the high-level reveal.

High-level reveal

The Five Value Pillars

AI-Led Operational Throughput

AI is doing the doing. More work without proportional headcount.
Owned Operational Software

You or your agents build and own the tools. Not renting another SaaS.
Auditable Strategy & Planning

Decisions and reasoning documented and traceable. AI can read the why.
Captured Institutional Wisdom

Knowledge lives outside heads. It compounds.
Managed AI Economics

You know what AI costs and what it delivers. You steer the economics deliberately.

Pillar 03 — Auditable Strategy & Planning

Yashoda's question

Dr. Yashoda · survey filed 2026-05-12

"Still have concerns about governance side. Want to understand more on governance."

FridayOS governance is in the repo and auditable:

Capability Catalog

what the system can do

Decision Log

every decision + reasoning

Doctrine

the principles

Open Questions

what's still unresolved

Gating Protocol

what requires approval

⏱ 0:30–0:36

Yashoda's survey, submitted today:

"Still have concerns about governance side. Want to understand more on governance."

Lead by asking HER to articulate, then respond.

Say: "Yashoda — you filed a survey today and said you still have concerns on the governance side, you want to understand more. Tell me more — what specifically?"

LISTEN. Don't pre-answer. Let her say what she means.

Then respond:

"FridayOS has formal governance and it's all in the repo. There's a Capability Catalog — what the system can do. A Decision Log — every real decision is logged with reasoning. A Doctrine — the principles. Open Questions — what's still unresolved. And a Gating Protocol — what requires explicit approval before it happens."

"It's auditable. You can read why we did everything. That's exactly what Pillar 3 — Auditable Strategy & Planning — is about. We'll go deep on it in a future session."

"For now: read 2-governance/friday-os-doctrine.md and the recent entries in decisions/. Bring your specific questions to the Pillar 3 session. Good?"

If her concern is something different (e.g., venture-level control, data privacy), hear her out, name it back, point to the right doc, offer a 1:1 follow-up.

Pillar 02 — Owned Operational Software

Shenali's question

Shenali · survey filed 2026-05-08

"Friday automatically set up the jay-trivedi/amazon_sp_mcp repo without surfacing ownership, trust, access-control, or long-term maintenance risks."

A thoughtful operator catching a real risk. Renting a third-party MCP is not the same as owning the software.

For this repo

Written breakdown by end of week

Ownership · trust posture · access · maintenance plan.

Going forward

Every third-party MCP gets vetted

Part of the repo-creation methodology Lucas is publishing.

⏱ 0:36–0:42

Shenali's survey, submitted 2026-05-08:

"Friday automatically set up the jay-trivedi/amazon_sp_mcp repo without surfacing ownership, trust, access-control, or long-term maintenance risks."

Have Shenali restate the concern in her own words for the group.

Say: "Shenali — you flagged something important in your survey. Friday adopted a third-party MCP repo on your behalf without surfacing the ownership, trust, and maintenance risk. Say it back in your own words for the group."

(Let her restate. The group needs to hear it from her.)

Then validate: "This is a real concern. Not a complaint — a thoughtful operator catching a real risk. Lucas?"

HAND TO LUCAS if he's prepared. If not, Fred carries:

"Two things. One — for the specific repo, we'll get you a written breakdown by end of week. Two — going forward, every third-party MCP or component gets vetted before adoption. Lucas is publishing the repo-creation methodology and this becomes part of it."

"This maps to Pillar 2 — Owned Operational Software. Renting a third-party MCP is not the same as owning the software. The question you asked is the right question every time something external gets adopted."

Pre-session: confirm with Lucas whether he's ready to take this live.

Pillar 01 — AI-Led Operational Throughput

Where are you the bottleneck?

Where in your day is throughput slow because you are the bottleneck?

Where could AI lead instead of assist?

Already running Pillar 1 builds: Saduka (Google Ads briefing) · Shenali (Amazon reporting) · Yashoda (team task dashboard).

⏱ 0:42–0:50

Pillar 1 — AI-Led Operational Throughput

Say: "Pillar 1 is AI-Led Operational Throughput. AI doing the doing. Quick prompt — where in your day is throughput slow because YOU are the bottleneck?"

"Where could AI lead instead of assist?"

Open the floor. Patterns to surface as they come up:

Adam — context-switching across delegated projects (named last week)
Hafiz — IDE setup blocking output
Saduka — Google Ads daily briefing (Pillar 1 build already running)
Shenali — Amazon reporting (Pillar 1 build)
Yashoda — team task dashboard (Pillar 1 build)

If Saduka, Shenali, or Yashoda want to briefly show what they built — 2–3 min each. Optional. No pressure.

HARD CLOSE at 0:50 — you need 8 min for the Commitment Standard, which is the load-bearing piece. If discussion runs long, cut it firmly. This slide is the one to compress if you're behind.

If you're sharing today — here's how

Sharing framework

Walk us through what you built using these prompts. Keeps shares useful for everyone — the room knows what to expect, you don't have to figure out structure on the spot.

What problem were you solving?
What did you build?
What result or leverage did it create?
What are you still trying to figure out?
What kind of feedback or ideas are you looking for?

Reset · most important segment

The Commitment Standard

A commitment in HQ is how you show your group that you're taking ownership.

Everyone always has a commitment
in HQ. Not optional.
Updated at least weekly
A weekly touch — not a project plan, not task management.
Tied to the roadmap + the pillars
A real project. Something with meaningful impact.
Make it scary
It should challenge you. Worth celebrating when done.
Beginners — smaller is fine
First commitment can be smaller. You're building toward this standard.

NOT a project management tool. NOT anything you happened to build with AI. NOT a one-shot prompt or small task.

⏱ 0:50–0:58 (most important segment)

DO NOT let people start making commitments live. The session is the reset of the standard, not a commitment round.

Say:

"I want to reset what a commitment is, because some of you have one, some don't, and some have one but aren't sure why."

"You're going to be building a lot with AI. You're on the roadmap to becoming AI-first. A commitment in HQ is how you show your group that you're taking ownership."

"Ownership is one of our core values. Not having a commitment isn't a minor admin gap. It's not taking ownership. It's not setting an example for each other."

"The standard, going forward:"

Everyone always has a commitment in HQ. Not optional.
Updated at least weekly. Not a project plan, not task management. A weekly touch.
Tied to the roadmap + the pillars. Pick where you'll have meaningful impact — a build, a collection of builds, something bigger than a one-shot prompt. A real project.
Make it scary. A commitment should challenge you. When it's done, it's worth celebrating. It moves your role, your department, your company forward.
Beginners — smaller is fine. Your first commitment may be smaller. That's okay. You're building toward this standard.

"What it's NOT — a project management tool. NOT anything you happened to build with AI. NOT a one-shot prompt or a small task."

Homework this week:

"If you don't have a commitment in HQ — add one. (Yashoda, Hafiz, Laleesha, Ibrahim, Shehara, Shenali — that's you.)"
"If you do — look at it. Does it still pass the test? Update it or replace it."
"Mark milestones in HQ for builds you've already completed. Highest-leverage thing you can do this week."

"We're not setting commitments live today. I want you to think about this. Look at the pillars. Decide where YOU want to make impact. The commitment lands in HQ this week."

Take away

What's next

Next session

Sharing becomes the norm

If you built something, you share it. We'll go deep on Pillar 1 — AI-Led Operational Throughput.

Starting today

Commitment standard in effect

Next session, I expect everyone to have a commitment in HQ — and those who already have one to have looked at it again.

Questions before we close?

⏱ 0:58–1:00

Say:

"Two things to take away:"

"One — next session, sharing becomes the norm. If you built something, you share it. We'll start with Pillar 1 — AI-Led Operational Throughput — as the deeper dive."

"Two — the HQ commitment standard is in effect starting today. By next session I expect to see everyone has a commitment in HQ, and the people who already have one have looked at it again."

"Questions before we close?"

HOLD for Q&A. If none, end clean: "Thanks team. See you next week."

Post-session: run /meeting close on the transcript. Captures commitments, pillar distribution from the opening prompt, and follow-ups for Yashoda's governance question + Shenali's MCP concern.