Cross-meeting dynamics

The system view.

The structural patterns that recur across all seven meetings — the team's two-body problem, the three quieter voices, the unaddressed facts, and the culture-reinforcement signals that are starting to emerge.

The two-body problem

Brayden generates the surface area. Sandy contains it. Everyone else orbits the binary.

The team's behavior in every meeting is best modeled as a two-body system: Brayden (centrifugal energy, generates scope, demos artifacts, evangelizes) ↔ Sandy (centripetal discipline, contains scope, reframes deliverables, qualifies leads).

Greg, Cameron, Jeremy, and Victoria orbit this binary, sometimes pulling in one direction or the other, but the meeting's structural energy comes from the Brayden-Sandy dyad.

This is healthy in principle and load-bearing in fact. The risk is that Sandy is doing the structural work without explicit authority — her interventions land 60–70% of the time, fail 30–40% of the time, and the failures compound into the recurring patterns: rocks-as-deliverables, tool-as-procrastination, scope-creep on Kasian.

A formal co-facilitation arrangement would convert Sandy's 60–70% landing rate into 90%+ without changing her actual behavior — just by giving her a procedural lever to act on the patterns she already sees.
The three quieter voices

Each speaks less than the Brayden-Sandy dyad. For different reasons.

Greg · quiet by choice

When he speaks, it lands. His airtime is approximately right; the gap is that his frameworks and audits are not being formalized into team artifacts fast enough.

Jeremy · quiet by deference

His airtime is too low for his role. The fix is round-robin enforcement and active naming during strategic discussion.

Victoria · quiet by self-location

Her airtime is too low for her perceptiveness. The fix is to defend her substantive contributions and invite her into facilitation responsibility.

Recurring friction patterns

Five patterns repeat across the seven weeks.

Rocks-as-deliverables (4/1); KPI agility (4/8); thought leadership (4/15); folder-discipline (4/22); tooling-as-procrastination (4/29); carrot-vs-pumpkin (5/13). Same modality each time: hedge, repeat, outlast, restate. Sandy is the only person in the corpus who reliably outlasts Brayden's reframing-as-agreement maneuver.

Time-check (4/1); IDS-first agenda (4/22); left-tackle (5/13). Greg's observations land, get adopted verbally, then drift in the absence of procedural enforcement.

4/22 CRM/WIP separation argument; 4/15 task system mess flag. The team has not built a norm for amplifying its quietest voices. This is a process gap, not a personal weakness.

4/8 (Aiyarise app), 4/29 (Obsidian dashboards), 5/13 (kernel demo). The artifacts are real and impressive. The meeting cost of demoing them is consistently 15–35 minutes. They should be async shares, not L10 segments.

Five consecutive meetings of absence without explanation. Greg explicitly flagged it twice. The creditor relationship is never raised in any meeting. When Cam does attend (5/6, 5/13), the impact is structurally significant — Maslow analogy, in-person Kasian advocacy, ego-disclosure that softens the loan dynamic publicly.

The unaddressed structural facts

Three things are visible across the corpus and are not being addressed in the L10.

01

Cameron's creditor relationship

$30k loan, 10% flat, 12-month max term (Mar 2026). The loan exists; it is never discussed. The 5/13 "I never thought I'd work for you" monologue is the only public acknowledgment that the financial asymmetry exists.

Recommendation: one quarterly conversation about this relationship — not necessarily in the L10, but explicit.

02

Brayden's all-nighter pattern

Mentioned in 5 of 7 meetings, occasionally twice. The team laughs and moves on. Greg's two gentle flags ("Brayden, not just Tuesday" 4/1; "you doing an all-nighter to get something done is good to get us started — but…" 5/6) are not enough.

This is a sustainability risk for the company's single largest dependency.

03

The post-Shea team scope

Jeremy is now the only AI Systems Developer. Greg flagged his own May 29 deliverable as at-risk due to family pressure. The team's technical-delivery capacity has materially contracted.

This has not been formally re-rocked.

The culture-reinforcement signals

The cultural maturity is outpacing the structural meeting discipline.

Signal 01

The "leveling up" small-group call

Referenced by Greg in 5/13 — an off-cycle conversation where the team agreed to "be authentic, be critical, lean on people when life gets in the way." A maturing operational norm.

Signal 02

The Brayden text Victoria read aloud

The explicit articulation of "providing space for you to be an actual human while developing your professional skill set" as the company's employment paradigm. Genuinely differentiated culture-language.

Signal 03

The Cameron disclosure

"I never thought I'd work for you, but I honestly don't care… that's part of that old paradigm, it no longer serves" — a Principal Advisor publicly softening his own ego on the company's behalf. Rare and valuable.

The team is genuinely building something culturally distinctive. The challenge is that the cultural maturity is outpacing the structural meeting discipline.

Decision-quality patterns

Tactical decisions ship. Strategic decisions improve with friction. Process decisions persistently drift. Risks are surfaced and orphaned.

Type of decisionQualityPattern
Tactical
who-does-what-by-when
High To-do lists ship cleanly each week. Jeremy's CRM, Sandy's GTM doc, Victoria's grants — all delivered on or near commitment.
Strategic framing
Kasian, ETRO, Paul, ICP
Mixed → improving Each major framing decision in weeks 4–7 required Sandy or Cameron to push 2–3 times. When they push, the decision improves; when they don't, the meeting decides nothing.
Process / governance
rocks method, scorecards, IDS, agenda
Persistently poor Process issues are surfaced, agreed to, then drift back. CRM/WIP consolidation (4/22) and IDS-first agenda reorder are the only durable process wins.
Risk acknowledgment
Kasian contract, agent safety, security, all-nighters
Surfaced but unassigned Sandy raised no-Kasian-contract risk on 4/8. Still no contract by 5/13. Greg raised agent-safety on 5/6. Still no owner by 5/13.