The arc of seven meetings.

Cameron absent. First time the group attempted L10 as a discipline; Brayden was still teaching the format mid-meeting. The rocks segment consumed ~35 minutes and became a quarterly-planning workshop rather than a status check.

Pivotal moments

• Sandy delivers the most strategically clarifying intervention of the entire seven-week window: "Right now I'm looking at these rocks and I'm like — oh, it looks like deliverables." Foundation of the next six weeks of strategy work.
• Greg's mid-meeting time-check at 00:51 — the meeting's structural save. Without it, the strategic discussion would have eaten the entire 90 minutes.
• Sandy proposes the airplane-wings-and-engine analogy for the company's sales-vs-product split. Greg endorses it on the spot.
• Brayden was sharing the wrong screen for ~12 minutes — Sandy caught it. Repeated again later in the meeting.
• Brayden offers Sandy ownership of the GTM rock; she accepts.

Friction

• Sandy vs. Brayden on rocks-as-deliverables — tabled, not resolved.
• Greg's polite-but-firm time-check ("we're past the halfway mark"). Brayden complies immediately.
• Half-typed task assignment: Sandy asked "what is the Kasian Architecture anchor my rocks?" — Brayden admitted he never finished typing.
• Brayden's two-minute political-figure tangent — Sandy's "Sure" was clipped.
• "For the record, did not sleep again last night… two weeks in a row." Greg's reply: "Brayden, not just Tuesday, man." First peer flag on sleep pattern.

Outcome

Brayden self-scored 2.25/10 (later bumped up). Honest. Baseline for comparison. GTM rock assigned, all-hands strategy meeting scheduled, Kasian framework committed. No scorecards yet (acknowledged).

32 minutes on rocks. Scorecard skipped. Brayden assigned Q2 rocks across the team. Two real artifacts shipped overnight: the first cut of the Aiyarise app and the Kasian project charter.

Pivotal moments

• Sandy delivers the meeting's hardest call: "That's scary." — pointing at the fact that there is no signed contract with Kasian despite billing. Brayden defended ("trust there… handshake deal") then conceded ("I commend the risk management perspective"). The risk remains live across all seven meetings.
• Brayden unilaterally paused Jeremy's outreach AI work mid-meeting. Jeremy said "Sounds good" and did not push back. First clear signal of role-boundary ambiguity.
• Greg explains Mythos (Anthropic model leaked) with subject-matter authority. Brayden drifts into conspiratorial register about "secret weapons sequestered from the public."
• Sandy reframes Brayden's investor musings into a measurable trigger: "hitting these goals → decision point."
• Live demo of the Aiyarise app — Sandy raises scope question (internal vs. client-facing).

Friction

• Kasian handshake-deal challenge — Brayden defuses with humor ("Star Trek shields up red alert") rather than action.
• Brayden pausing Jeremy's work without consultation — unilateral scope arrest absorbed silently.
• Anti-gravity reversal: Brayden had been an advocate; now concedes "it was all sunshine and rainbows. It's not there yet." Quiet credibility hit.
• Two "pulled another all nighter" disclosures from Brayden.

Outcome

Q2 rocks assigned across all team members (16+ commitments). Aiyarise app V1 shipped. Kasian charter authored. Brayden's all-nighter pattern normalized but unaddressed.

Brayden's phone interrupted twice; he stepped out for the second call. Sandy and Greg chaired in his absence. IDS waived ("I think we can table this") — then Brayden admitted at close the team was "hacking through to-dos and rocks."

Pivotal moments

• Sandy's most pointed governance challenge: Brayden had unilaterally revised the team's rocks. Sandy: "with that methodology you're doing… we're not really debating some of the ideas there because I feel like we probably would benefit from a collective discussion." Brayden's response: doubled the word "unilaterally" and reframed it as quality-of-output. They talked past each other.
• Greg quietly delivered the meeting's largest artifact: a working AI-assisted contract evaluation tool, built over a weekend. He under-claimed it.
• Greg explicitly flagged Cam's continued absence: "having Cameron involved too — we talked about it last level 10, so just want to make sure we keep that in mind." Second meeting in a row.
• Sandy reverses Brayden's thought-leadership rock — pushes LinkedIn over blog: "Nobody cares about our company's website really."
• Long teach-me sidebar: Victoria on Claude/anti-gravity. Patient explanation from Greg and Brayden.

Friction

• Unilateral rock filtering — process critique met with output justification.
• Anti-gravity tooling disillusionment from Greg, Victoria, and Brayden — ironic for an AI governance consultancy.
• Task system mess: two parallel task systems unintegrated, 509 action items un-sifted. Brayden: "It's more on me to clean things up." No deadline.
• Victoria self-flags airtime anxiety: "I haven't really talked a lot today." No one explicitly invites her in earlier.

Outcome

Ratings 8, 8.5, 8, 8. Contract evaluation tool — the cycle's largest single artifact — entered the pipeline. Strategy meeting scheduled with Cam included for the following Monday. Process governance still unresolved.

Victoria chaired the opening because Brayden joined mid-stream. The IDS segment got 25 minutes of a 60-minute meeting because Brayden's headlines monologue and the Construction Live tangent consumed the front half.

Pivotal moments

• Sandy challenged Brayden's PM-derived "folder per file" instinct on the CRM/WIP design: "Why do we care so much about folders?" — and won the substantive argument with Jeremy as her quiet co-validator.
• Greg delivers the most structurally important meta-observation of the seven weeks: "It's kind of ironic that we're talking about rocks yet the most important thing, the biggest thing is the last thing we talked about… let's talk about [issues] first and then see if we can fit in the other stuff later." Brayden adopted it on the spot. The only durable agenda-design improvement the team has made.
• Grants rock moved from Q3 to Q2 with end-of-May deadline.
• Brayden's mid-IDS pivot into a long Construction Live / Rahul monologue — overtly mystical framing ("aura, vibration, frequency"). Ate ~5 minutes of IDS time. No teammate redirected him.

Friction · Victoria's withdrawal moment

Victoria raised a substantive counter-position on CRM/WIP separation; was steamrolled by Brayden's re-explanation; capitulated under time pressure with "I think we're just running long now. So I don't want to…"

This is a behaviorally significant moment — the team has not yet built a norm where the quietest voices' substantive concerns get heard on their merits.

Other friction

• Shred AI / Kasian invoice misunderstanding — Greg surfaced it; Brayden reframed it as communication breakdown rather than process failure. Threshold question never resolved.
• Cam absent again; given his $30k creditor relationship + advisor role, his consistent non-attendance is structurally notable.
• Time discipline: 10 minutes over. Greg, Sandy, Jeremy all docked points.

Outcome

CRM/WIP consolidated into a single "Active" tab with separate upstream Directory; Brayden owns the action. Agenda revision proposed and adopted in real time. Two-three proposals per week target affirmed. $50K MRR by June 30.

The meeting Brayden himself described as breaking the L10 format: "the drawback was that we didn't adhere to the structure basically whatsoever." Opening was a 15-minute Obsidian dashboard demo from Brayden — pure founder-talking-time.

Pivotal moments

• The Kasian / Benny / Milestone proposal IDS segments were substantively excellent. Three of four ICs left with clear scope, ownership, and sequencing for their proposal drafts.
• Sandy delivers the corpus's most direct correction of the founder: "Brayden, please don't go and create another dashboard for this." Brayden's response: "I already have it going." He took the correction verbally and admitted the behavior had already preceded the correction.
• Brayden disclosed he had unilaterally built a proposal-generation system that was Jeremy's rock. Greg's only reaction: "It figures." Role boundaries continue to be honored verbally and violated operationally.
• Sandy reframed Kasian: "We are not here to solve like a skills matrix problem in the world. That's not our core business." Brayden conceded.
• Greg's three-layer phased framing for the Kasian skills matrix invented and held under pressure.

Friction

• Severe agenda drift — Brayden's Obsidian demo at the top set the tone. Scorecard, rocks, and to-dos almost entirely skipped.
• Founder dominance — Brayden's word count is several multiples of any other speaker. The meeting moves at his pace.
• Role-boundary blur — Brayden building Jeremy's rock unilaterally, then pulling pricing decisions off Jeremy.
• Cameron Barnes absent without comment. Victoria silent for 98 minutes.
• Pricing strategy explicitly deferred without a deadline — a key risk for the proposal-week push.

Outcome

Brayden self-scored 8.75. The team self-scored 8–8.5. The numbers are charitable. Victoria's chat-only one-word close — "traditional level 10 meeting abolished today" — is the most precise self-diagnosis the team has produced. Claude subscription committed under Sandy's pressure (was due Monday, still not done at Wednesday meeting).

Cameron Barnes attends his first L10. He is treated as a peer from the start; the team does not patronize him with onboarding. The Kasian IDS ate 45 of 90 minutes and would have been worse without Cameron.

Pivotal moments

• Cameron's Maslow's-hierarchy analogy crystallized what Sandy had been arguing for ~30 minutes (lead Kasian with a strategic vision, not features). Brayden renamed it "Aiyarise Hierarchy of AI Implementation" within thirty seconds. The newcomer landed the metaphor that unlocked the meeting.
• The Paul McCulla IDS produced a clear next-step: Sandy to draft a one-pager covering the mission statement and forum value-prop.
• Cameron asked the mission-statement question — first time mission-statement language gets explicitly questioned in the corpus.
• Greg surfaced two new risk categories: agent safety (Pocket Oets database-deletion story) and security expertise gap. Brayden agreed, namedropped a Rahul/cybersecurity contact, and the topics dissolved into the rocks dashboard without an owner.
• Greg's coded critique of Brayden's lone-wolf workstyle: "You want to move fast, do it yourself; you want to do a good job and travel far, do it together… you doing an all-nighter to get something done is good to get us started — but I think we need to incorporate everyone." Brayden: "I love that." Pure validation, no commitment to change.

Friction

• Sandy had to repeat her substance-over-form correction three times across the Kasian segment before Brayden actually changed his approach.
• Greg's argument that Kasian work needed Jane's HR data first; Brayden countered with a 3-minute voice-agent monologue proposing they skip the prerequisite. Talked-around, not resolved.
• ETRO proposal — Brayden visibly hadn't done his homework on Sandy's April 27 email. Sandy gently called it out.
• Jeremy effectively absent from the strategic discussion — 2 substantive contributions in 90 minutes.

Outcome

Kasian deliverables to be reframed as a strategic pyramid before sending individual feature proposals. ETRO to ship today by 2:15 PM. Cameron formally inside the team's strategic-decision loop. Risks acknowledged, not assigned.

Shea Cameron was not named once. He departed 2026-05-12. No moment of recognition, debrief, or oblique reference. No reassignment of his work. The silence is itself the loudest signal.

Meeting opened with ~22 minutes of unstructured discussion about AI evangelism, narrative, and 10-year horizons before good news.

Pivotal moments

• Sandy delivered the meeting's most consequential single contribution: "It's a strategic choice at this point absolutely that we don't bother with those people… Don't waste time. Don't waste energy." Brayden conceded — "My heart wants to change the world's perspective, but proof is in the pudding."
• Greg's "left tackle" analogy — asking who Kasian's protective player is in the AI build-out — landed cleanly. Brayden seized it.
• Sandy's "carrot vs. pumpkin" reframe: Brayden proposed restyling the proposal-system demo as a Kasian carrot; Sandy: "It might be too concrete a carrot… they don't know if they want a carrot or a pumpkin." Cameron explicitly validated her.
• The 35-minute live demo of the proposal/quote/deck/RFI kernel system. Genuine technical artifact. Should have been an async share.
• Cameron's culture monologue: "I never thought I'd work for you, but I honestly don't care. Like to me it's just a matter of uplifting us all… that's part of that old paradigm. It no longer serves."
• Victoria reads aloud Brayden's private text about "providing space for you to be an actual human." Functions as culture-reinforcement after Shea's departure.
• Greg flagged his May 29 standardized intake rock at risk (single-parenting, mother-in-law in hospice).

Friction

• Brayden's evangelism vs Sandy's qualification realism — Brayden accepted verbally; subsequent demo and Friday-meeting plan show the instinct hasn't fully shifted.
• Brayden's frustration with Kasian: "they can't seem to get their s*** together or poop in a group." Briefly profanity-laundered.
• Greg's pointed meeting-effectiveness critique at close: "basically the framework of the meeting, we didn't really follow that at all." Scored 6.5 with the word "catch-all."

Post-departure signals

• Shea not named once.
• Cameron's ego-disclosure and Victoria reading aloud Brayden's text function as culture-reinforcement signals after the departure.
• Greg's "leveling up" callback referred to a recent small-group call — possibly where the team handled the Shea fallout privately.
• Jeremy is now the sole AI Systems Developer. No expansion of his ownership was discussed.