Undisturbed OS.
The studio builds its own advisory operating system — and uses it on itself first.
The first AX OS — the operating layer for advisory practice. Built in public, used on the studio first.
Undisturbed OS — one operating layer for every engagement, meeting, material, and follow-up
If a tool can't survive its own operator, it has no business being recommended to anyone else
Built in public, phase by phase — this page is the live log of what shipped
If a tool can't survive its own operator, it has no business being deployed to anyone else. The studio uses its own infrastructure on itself first — every engagement runs through it, every meeting, every bundle, every follow-up. Eat your own dog food is not a slogan here. It is the only way the work earns the right to be recommended.
This page is the log. What the studio is building, why, where it stands, what shipped this week. Updated as the work moves.
Run a meeting end-to-end with Undisturbed OS.
Four steps. From the calendar that says at 2pm, to the link the client opens at 5pm. At every step, AI handles what's mechanical — prep, ordering, recap, action items. The operator handles what's judgment.
01
Backstage
Schedule
Click a meeting from your week.
The system pulls upcoming meetings from Google Calendar — the source of truth for when. The right project, the right client, the right context all line up the moment you click.
Surfaces materials linked to this meeting's project, last touch, and client history. Prep that used to take an hour happens before you finish reading the agenda.
01
Backstage
Schedule
Click a meeting from your week.
The system pulls upcoming meetings from Google Calendar — the source of truth for when. The right project, the right client, the right context all line up the moment you click.
Surfaces materials linked to this meeting's project, last touch, and client history. Prep that used to take an hour happens before you finish reading the agenda.
02
Backstage
Bundle
Drag materials into the order you want.
Notion documents, Supabase files, links, screenshots — everything goes into one polymorphic stack. The bundle is what the meeting will actually show. Built in minutes, not hours.
Suggests an opening order, flags pieces missing from last quarter's bundle, drafts a one-sentence framing for each material. You correct, not author from scratch.
02
Backstage
Bundle
Drag materials into the order you want.
Notion documents, Supabase files, links, screenshots — everything goes into one polymorphic stack. The bundle is what the meeting will actually show. Built in minutes, not hours.
Suggests an opening order, flags pieces missing from last quarter's bundle, drafts a one-sentence framing for each material. You correct, not author from scratch.
03
Frontstage
Present
Press Present. Stage lights dim.
Full-screen, dark register. The bundle becomes one editorial surface for screen-share. No tab-switching, no "give me a second to find that" mid-meeting. The client sees the studio's voice carry through.
Speaker notes per material — talking points pulled from the source. The operator stays in the conversation, not in the deck.
03
Frontstage
Present
Press Present. Stage lights dim.
Full-screen, dark register. The bundle becomes one editorial surface for screen-share. No tab-switching, no "give me a second to find that" mid-meeting. The client sees the studio's voice carry through.
Speaker notes per material — talking points pulled from the source. The operator stays in the conversation, not in the deck.
04
Bridge
Follow-up
Share the link.
A public page at /f/[slug] auto-generates. The client opens it and receives exactly what was shown — same dark register, same order, no login required. The bridge between meeting and memory.
Drafts the recap, extracts action items with owners and dates, generates the entire Bridge page from the meeting and bundle. The follow-up that used to take days exists by the time the meeting ends.
04
Bridge
Follow-up
Share the link.
A public page at /f/[slug] auto-generates. The client opens it and receives exactly what was shown — same dark register, same order, no login required. The bridge between meeting and memory.
Drafts the recap, extracts action items with owners and dates, generates the entire Bridge page from the meeting and bundle. The follow-up that used to take days exists by the time the meeting ends.
Four steps. One workspace. The AX advisor's eat your own dog food, on display — at the layer of the work itself.
operator
Backstage
Data-dense interface only the consultant sees. Client management, pipeline, insight notes.
operator
Backstage
Data-dense interface only the consultant sees. Client management, pipeline, insight notes.
stage
Frontstage
Editorial interface screen-shared during meetings. Material library, Bundle, Present mode.
curated
Bridge
Public follow-up page the client receives. Same dark register, no auth required. URL pattern: /f/[slug].
The machine does production. I do judgment.
A fair question: a solo studio promises weekly signals, monthly patterns, a quarterly report — and runs client loops on top. The honest answer is that most of that calendar is production work, and production is exactly what the OS absorbs. What's left — the part that can't be delegated to a machine — is judgment. That's where the hours go.
OS handles
Which ones matter, and the second line — what it means for AX
I decide
Pulls the week's tooling, policy, and capability moves into draft signal cards
Gathers public filings and disclosures into a pattern draft structure
The substrate read, and where the pattern doesn't transfer
Assembles the quarter's signals, outcomes, and notes into a report skeleton
The through-line — what the quarter actually meant, and what to watch next
Meeting prep, material bundling, follow-up pages — every client loop's scaffolding
The actual advice. This is the part that gets priority when things get busy
Four phases.
Phase 0
Complete
Foundation
Architecture decisions, full schema (20 entities + 3 join tables, RLS migration v2), Supabase project in Seoul region, Google OAuth + Calendar API, Notion integration, design system, four-week MVP roadmap.
Phase 0
Complete
Foundation
Architecture decisions, full schema (20 entities + 3 join tables, RLS migration v2), Supabase project in Seoul region, Google OAuth + Calendar API, Notion integration, design system, four-week MVP roadmap.
Phase 1
Starting
Design system + core flow
Design tokens, base components, auth + Companies + Projects. The bones that everything later sits on. Week 1 begins now.
Phase 1
Starting
Design system + core flow
Design tokens, base components, auth + Companies + Projects. The bones that everything later sits on. Week 1 begins now.
Phase 2
Queued
Bundles + Present mode
Material library, drag-to-bundle editor, full-screen presentation interface. The studio's actual workflow on stage.
Phase 2
Queued
Bundles + Present mode
Material library, drag-to-bundle editor, full-screen presentation interface. The studio's actual workflow on stage.
Phase 3
Queued
Public follow-up + client portal
Public follow-up pages for clients (no auth), beginnings of a client-facing portal for ongoing engagements.
Phase 3
Queued
Public follow-up + client portal
Public follow-up pages for clients (no auth), beginnings of a client-facing portal for ongoing engagements.
Phase 4
Queued
Contracts + invoices
Contract drafting, invoice generation, the parts of advisory practice that traditionally live in PDFs and email — folded back into the operating layer.
Phase 4
Queued
Contracts + invoices
Contract drafting, invoice generation, the parts of advisory practice that traditionally live in PDFs and email — folded back into the operating layer.
What's shipped, in order.
Newest first. Each entry is what actually changed in the codebase that week — not what's planned. Plans live in the phase cards above.
May 2026 · Week 4
Naming · Category
The product gets a name. So does the category.
The internal codename — "the platform" — was placeholder vocabulary, not a product name. This week the category and the product both got their proper names. AX OS — a new category of software, the operating layer for AX advisory practice. Undisturbed OS — the first instance of an AX OS, built by the studio for the studio. The category and the product, named in the same week the work to ship it begins.
01
Backstage
The product gets a name. So does the category.
Click a meeting from your week.
The internal codename — "the platform" — was placeholder vocabulary, not a product name. This week the category and the product both got their proper names. AX OS — a new category of software, the operating layer for AX advisory practice. Undisturbed OS — the first instance of an AX OS, built by the studio for the studio. The category and the product, named in the same week the work to ship it begins.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
May 2026 · Week 3
Phase 1 — Week 1
Phase 1 kickoff — design system in code.
Started Phase 1. Translating the design decisions from Phase 0 into actual Tailwind tokens, shadcn-generated base components, and the dual-register layout shell. Backstage gets density. Frontstage gets editorial breathing room. The bridge is where they meet — and where most of the design effort actually lives.
01
Backstage
Phase 1 kickoff — design system in code.
Click a meeting from your week.
Started Phase 1. Translating the design decisions from Phase 0 into actual Tailwind tokens, shadcn-generated base components, and the dual-register layout shell. Backstage gets density. Frontstage gets editorial breathing room. The bridge is where they meet — and where most of the design effort actually lives.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
May 2026 · Week 2
Naming · Category
Phase 0 closed. Foundation locked.
Schema finalized: 20 entities + 3 join tables. Supabase project up in Seoul region with RLS migration v2 applied (consultant + client_user role types — the client portal isn't built yet but the security is). Google OAuth + Calendar API connected through Supabase Auth provider. Notion integration created (Materials DB connection next). Design system decided: three surfaces (backstage / frontstage / bridge), shared color palette, font swap as the register shift. Four-week MVP roadmap signed off. The bones are set.
01
Backstage
Phase 0 closed. Foundation locked.
Click a meeting from your week.
Schema finalized: 20 entities + 3 join tables. Supabase project up in Seoul region with RLS migration v2 applied (consultant + client_user role types — the client portal isn't built yet but the security is). Google OAuth + Calendar API connected through Supabase Auth provider. Notion integration created (Materials DB connection next). Design system decided: three surfaces (backstage / frontstage / bridge), shared color palette, font swap as the register shift. Four-week MVP roadmap signed off. The bones are set.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
May 2026 · Week 1
Phase 0 — Architecture
Architecture decisions written down.
Wrote architecture.md, schema.md, mvp-roadmap.md. The kind of documents most projects skip and pay for later. Decision: Next.js App Router for routing, Supabase for everything backend (DB, auth, storage), Notion for materials (the studio's writing already lives there), Google Calendar for meetings (it's where clients already book). The studio doesn't want to be a system-of-record — it wants to be the operating layer on top of where the work already is.
01
Backstage
Architecture decisions written down.
Click a meeting from your week.
Wrote architecture.md, schema.md, mvp-roadmap.md. The kind of documents most projects skip and pay for later. Decision: Next.js App Router for routing, Supabase for everything backend (DB, auth, storage), Notion for materials (the studio's writing already lives there), Google Calendar for meetings (it's where clients already book). The studio doesn't want to be a system-of-record — it wants to be the operating layer on top of where the work already is.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
April 2026
Project initiated
Why this exists.
Started running AX Loops with mid-market clients. By the third engagement, the workflow was clearly the same — Companies, Projects, Meetings, Bundles of materials, Follow-up pages, Contracts, Invoices. Existing tools each handle one piece. None handle the seam between operator work and client presentation. So: build the operating layer the studio needs, use it on the studio first, and then — only then — recommend the pattern to clients running their own AX.
01
Backstage
Why this exists.
Click a meeting from your week.
Started running AX Loops with mid-market clients. By the third engagement, the workflow was clearly the same — Companies, Projects, Meetings, Bundles of materials, Follow-up pages, Contracts, Invoices. Existing tools each handle one piece. None handle the seam between operator work and client presentation. So: build the operating layer the studio needs, use it on the studio first, and then — only then — recommend the pattern to clients running their own AX.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
Undisturbed OS.
The studio builds its own advisory operating system — and uses it on itself first.
The first AX OS — the operating layer for advisory practice. Built in public, used on the studio first.
Undisturbed OS — one operating layer for every engagement, meeting, material, and follow-up
If a tool can't survive its own operator, it has no business being recommended to anyone else
Built in public, phase by phase — this page is the live log of what shipped
If a tool can't survive its own operator, it has no business being deployed to anyone else. The studio uses its own infrastructure on itself first — every engagement runs through it, every meeting, every bundle, every follow-up. Eat your own dog food is not a slogan here. It is the only way the work earns the right to be recommended.
This page is the log. What the studio is building, why, where it stands, what shipped this week. Updated as the work moves.
Run a meeting end-to-end with Undisturbed OS.
Four steps. From the calendar that says at 2pm, to the link the client opens at 5pm. At every step, AI handles what's mechanical — prep, ordering, recap, action items. The operator handles what's judgment.
01
Backstage
Schedule
Click a meeting from your week.
The system pulls upcoming meetings from Google Calendar — the source of truth for when. The right project, the right client, the right context all line up the moment you click.
Surfaces materials linked to this meeting's project, last touch, and client history. Prep that used to take an hour happens before you finish reading the agenda.
02
Backstage
Bundle
Drag materials into the order you want.
Notion documents, Supabase files, links, screenshots — everything goes into one polymorphic stack. The bundle is what the meeting will actually show. Built in minutes, not hours.
Suggests an opening order, flags pieces missing from last quarter's bundle, drafts a one-sentence framing for each material. You correct, not author from scratch.
03
Frontstage
Present
Press Present. Stage lights dim.
Full-screen, dark register. The bundle becomes one editorial surface for screen-share. No tab-switching, no "give me a second to find that" mid-meeting. The client sees the studio's voice carry through.
Speaker notes per material — talking points pulled from the source. The operator stays in the conversation, not in the deck.
04
Bridge
Follow-up
Share the link.
A public page at /f/[slug] auto-generates. The client opens it and receives exactly what was shown — same dark register, same order, no login required. The bridge between meeting and memory.
Drafts the recap, extracts action items with owners and dates, generates the entire Bridge page from the meeting and bundle. The follow-up that used to take days exists by the time the meeting ends.
Four steps. One workspace. The AX advisor's eat your own dog food, on display — at the layer of the work itself.
operator
Backstage
Data-dense interface only the consultant sees. Client management, pipeline, insight notes.
stage
Frontstage
Editorial interface screen-shared during meetings. Material library, Bundle, Present mode.
curated
Bridge
Public follow-up page the client receives. Same dark register, no auth required. URL pattern: /f/[slug].
The machine does production. I do judgment.
A fair question: a solo studio promises weekly signals, monthly patterns, a quarterly report — and runs client loops on top. The honest answer is that most of that calendar is production work, and production is exactly what the OS absorbs. What's left — the part that can't be delegated to a machine — is judgment. That's where the hours go.
OS handles
Which ones matter, and the second line — what it means for AX
I decide
Pulls the week's tooling, policy, and capability moves into draft signal cards
Gathers public filings and disclosures into a pattern draft structure
The substrate read, and where the pattern doesn't transfer
Assembles the quarter's signals, outcomes, and notes into a report skeleton
The through-line — what the quarter actually meant, and what to watch next
Meeting prep, material bundling, follow-up pages — every client loop's scaffolding
The actual advice. This is the part that gets priority when things get busy
Four phases.
Phase 0
Complete
Foundation
Architecture decisions, full schema (20 entities + 3 join tables, RLS migration v2), Supabase project in Seoul region, Google OAuth + Calendar API, Notion integration, design system, four-week MVP roadmap.
Phase 1
Starting
Design system + core flow
Design tokens, base components, auth + Companies + Projects. The bones that everything later sits on. Week 1 begins now.
Phase 2
Queued
Bundles + Present mode
Material library, drag-to-bundle editor, full-screen presentation interface. The studio's actual workflow on stage.
Phase 3
Queued
Public follow-up + client portal
Public follow-up pages for clients (no auth), beginnings of a client-facing portal for ongoing engagements.
Phase 4
Queued
Contracts + invoices
Contract drafting, invoice generation, the parts of advisory practice that traditionally live in PDFs and email — folded back into the operating layer.
What's shipped, in order.
Newest first. Each entry is what actually changed in the codebase that week — not what's planned. Plans live in the phase cards above.
01
Backstage
The product gets a name. So does the category.
Click a meeting from your week.
The internal codename — "the platform" — was placeholder vocabulary, not a product name. This week the category and the product both got their proper names. AX OS — a new category of software, the operating layer for AX advisory practice. Undisturbed OS — the first instance of an AX OS, built by the studio for the studio. The category and the product, named in the same week the work to ship it begins.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
01
Backstage
Phase 1 kickoff — design system in code.
Click a meeting from your week.
Started Phase 1. Translating the design decisions from Phase 0 into actual Tailwind tokens, shadcn-generated base components, and the dual-register layout shell. Backstage gets density. Frontstage gets editorial breathing room. The bridge is where they meet — and where most of the design effort actually lives.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
01
Backstage
Phase 0 closed. Foundation locked.
Click a meeting from your week.
Schema finalized: 20 entities + 3 join tables. Supabase project up in Seoul region with RLS migration v2 applied (consultant + client_user role types — the client portal isn't built yet but the security is). Google OAuth + Calendar API connected through Supabase Auth provider. Notion integration created (Materials DB connection next). Design system decided: three surfaces (backstage / frontstage / bridge), shared color palette, font swap as the register shift. Four-week MVP roadmap signed off. The bones are set.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
01
Backstage
Architecture decisions written down.
Click a meeting from your week.
Wrote architecture.md, schema.md, mvp-roadmap.md. The kind of documents most projects skip and pay for later. Decision: Next.js App Router for routing, Supabase for everything backend (DB, auth, storage), Notion for materials (the studio's writing already lives there), Google Calendar for meetings (it's where clients already book). The studio doesn't want to be a system-of-record — it wants to be the operating layer on top of where the work already is.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.
01
Backstage
Why this exists.
Click a meeting from your week.
Started running AX Loops with mid-market clients. By the third engagement, the workflow was clearly the same — Companies, Projects, Meetings, Bundles of materials, Follow-up pages, Contracts, Invoices. Existing tools each handle one piece. None handle the seam between operator work and client presentation. So: build the operating layer the studio needs, use it on the studio first, and then — only then — recommend the pattern to clients running their own AX.
Each of the studio's five deliverables — AI Charter, Council Guide, 30/90/180 Roadmap, Data Risk Matrix, Standards Mapping — addresses one of these gaps directly. Outcomes are measured against these baselines.