Collaboration Stack.

Reading order

1. If you are a new Sprint Lead: read §02, §03, §08, §09 before your first client call.
2. If you are onboarding an Agent Engineer: read §04 and §07 so they understand where Linear issues and shared docs live.
3. If a client is asking to change a tool: re-read §03 or the relevant section and file an exception in the decision log.

Etiquette table — what goes where

The sprint template — 1 Linear team per engagement

Issue conventions

1. Every agent has exactly one Linear issue that serves as its home. Sub-issues hang off it. The agent’s spec lives linked from that issue’s description.
2. Every governance component instrumentation has a dedicated issue with label governance — closed only when the instrumentation passes a live drill.
3. Every decision becomes a Linear comment with a prefix DECISION: — makes the sprint decision log greppable.
4. SEV-1/2 incidents get their own incident-labelled issue with timestamped comments.
5. Pattern candidates land in an USP-candidate label queue reviewed at Gate 4.

What always gets recorded

1. Friday demo (USP-011). Always. Even if the live call had perfect attendance. Recording is the deliverable.
2. Governance drill walkthroughs. Every drill in Week 10 (Handoff) is recorded so the Workflow Owner can review before attempting.
3. “How to use this tool” explainers. Whenever a new tool or dashboard is handed to the client, a 3–5 min Loom replaces a meeting.
4. Post-mortem readouts. For SEV-2+ incidents, a short Loom walks through the timeline and the five-why analysis.
5. Sprint closeout (at Gate 4). One 10-min Loom covering what was built, what patterns were extracted, and how the support window works.

Retention & organization

Studio library (shared across engagements)

Engagement file conventions

1. One team file per engagement — named <client> · sprint v1.
2. Pages: Cover · Wireframes · Handoff · Archive. No stray pages; move abandoned explorations to Archive.
3. Client access: view-only by default. Grant edit only when asked and documented.
4. Every handoff page cross-links to the matching Linear issue.
5. At Gate 4, the file is duplicated into the Studio archive and the live file is transferred or kept per contract.

Canonical folder tree

Access model

1. Client membership is issued at the folder level — never at the file level. This makes Gate-4 revocation atomic.
2. Sensitive subfolders (contracts/) are explicitly exceptions — not inherited.
3. No external sharing of any file in these folders beyond the named members without a written approval trail.
4. At Gate 4, client membership is moved to view-only on everything except state/ (transferred if contract specifies).
5. At Day 30 post-Gate-4, Studio access reviews: any sensitive credentials in the folder must be revoked if they were shared during delivery.

Meeting discipline

1. Every recurring meeting has a pinned prep doc. If the prep doc is empty at T-4 hours, the meeting is canceled — not postponed.
2. No meeting exceeds 60 minutes. Long syncs are a sign that async is failing somewhere; find it.
3. No standing one-on-ones with the client. The shared channels are where conversations happen; bilateral back-channels create fragmented history.
4. Every meeting has a written output posted to Linear or Drive within 24 hours — not just a calendar history.
5. Gate calls always happen. Even if the gate is a rubber-stamp pass. Skipping erodes the discipline for the next one that matters.

Day-0 (T-48 h) — Studio-side setup

1. Create Google Drive folder with canonical tree (§07). Pre-populate readme.md in each subfolder.
2. Create Linear team with sprint template (§04). Pre-create the four gate issues.
3. Create shared Google Calendar; schedule all recurring events for the 11-week sprint + 30-day support window.
4. Create Figma team file with Studio library applied.
5. Create Loom folder for the engagement.
6. Draft the Slack Connect channel; send invite to the client’s designated Executive Sponsor.
7. Pre-fill state sheet template; link it inside state/.

Day-0 (T-24 h) — welcome email

1. Drive folder link — one click, which reveals the full canonical tree.
2. Slack Connect invite link.
3. Linear membership invite.
4. Calendar invites for Week 1’s kickoff and Friday demo.
5. One short Loom (< 4 min) walking through what the sprint will look like in the first two weeks.
6. Contact escalation path: who emails whom for SEV-1 in the off-chance it happens in the first week.

Day-1 kickoff — 60-min agenda

1. Introductions (5 min).
2. Walk through the Drive folder and what each subfolder will hold (10 min).
3. Walk through the Linear board and the gate structure (10 min).
4. Confirm meeting cadence; adjust recurring times if necessary (5 min).
5. Kick off Discovery: first stakeholder interview scheduled, Workflow Audit opened (20 min).
6. Closing: what the Studio needs from the client in the next 48 h (10 min).

Per engagement (Day 0 → Gate 4)

1. Drive folder, Linear team, Loom folder, Figma file, Slack Connect channel, Google Calendar all live by T-24 h.
2. Welcome email sent with all six surfaces linked.
3. At Gate 4: folder access downgraded to view-only; Linear team archived; Slack Connect closed per Security §05.

Per week (every Friday)

1. Demo recorded, named per convention, dropped in Slack and Linear.
2. Cycle rolled in Linear; incomplete items triaged (complete / carry-over / cancel).
3. Next week’s prep doc drafted before leaving for the weekend.
4. Slack channel housekept — unresolved threads chased or escalated.

Per gate (at phase boundaries)

1. Gate issue in Linear has all criteria checked off with linked evidence.
2. Gate call scheduled with prep doc pinned.
3. Gate decision (pass / conditional / hold) logged in decision log.
4. Calendar invites for the next phase’s recurring events reviewed and adjusted if needed.