{
 "id": "14.3",
 "title": "Rituals",
 "department": "People and ways of working",
 "department_slug": "people-and-ways-of-working",
 "direction": null,
 "branded": false,
 "status": "draft",
 "owner": "Param",
 "last_verified": "Mon Oct 26",
 "holds": "Weekly review, QA rounds, release rhythm",
 "urls": {
  "html": "https://handbook.joinsquareup.com/people-and-ways-of-working/rituals",
  "markdown": "https://handbook.joinsquareup.com/people-and-ways-of-working/rituals.md",
  "json": "https://handbook.joinsquareup.com/people-and-ways-of-working/rituals.json"
 },
 "other_directions": [],
 "tldr": {
  "headline": "We deploy and sweep constantly, yet no weekly meeting exists",
  "points": [
   {
    "icon": "rocket",
    "text": "Every tested change goes straight to staging, where Param tests on the live URL."
   },
   {
    "icon": "check",
    "text": "QV rounds follow every phase, and QA sweeps start when Sai's sheet fills."
   },
   {
    "icon": "clock",
    "text": "The handbook runs at 9 am; brands get a Monday 09:00 digest."
   },
   {
    "icon": "gear",
    "text": "A restore test runs monthly; the first was on 25 Oct."
   },
   {
    "icon": "chat",
    "text": "Proposed: a 30 minute Monday review covering Next, partners and decisions."
   }
  ],
  "stat": {
   "value": "49",
   "label": "bugs closed, one QA sweep"
  },
  "decide": "Hold a weekly 30 minute review on Mondays at 11 am IST from 2 Nov?",
  "mood": "waiting"
 },
 "sources": [
  "brew origin/main a559de6: CLAUDE.md 'Release rhythm', digest.js:1-12",
  "brew/.wt-prod/docs/production.md:43",
  "~/.claude/scheduled-tasks/handbook-morning/SKILL.md",
  "memory brew-qv-process, brew-qa-sweep-2026-10-19, brew-qa-audit-2026-10-20 (index line), brew-qa-round2-2026-10-24 (index line), always-deploy-to-test, brew-prod-backend, brew-handbook"
 ],
 "open_questions": [
  "**Hold a weekly review?** Proposal: yes, Mondays at 11 am IST, 30 minutes, agenda as above, starting 2 Nov 2026.",
  "**How often do design partner audits run?** Proposal: one full audit across the five partners every two weeks, run by Claude, triaged by Param and Sai."
 ],
 "parts": {
  "Answer": "The team's only fixed rhythms today are continuous deploys, QV rounds after every phase, QA sweeps from Sai's sheet and the handbook's 9 am run; there is no weekly meeting written down, so this page records what happens and proposes a weekly review.",
  "Today": "| Ritual | When | What happens | Source |\n|---|---|---|---|\n| Continuous deploy | After every tested change | Deploy to staging; Param tests on the live URL | [src: brew/CLAUDE.md] [src: memory always-deploy-to-test] |\n| QV round | After every phase of phased work, then 3 more before closing | Fresh reviewers, live checks on staging, fixes with tests, redeploy, re-verify | [src: memory brew-qv-process] |\n| QA sweep | When Sai's QA sheet fills | Every row triaged, fixed, then a compare pass; 19 to 20 Oct closed 49 bugs | [src: memory brew-qa-sweep-2026-10-19] |\n| Design partner audit | 20 Oct and 24 Oct so far | About 86 findings on 20 Oct; report A, B and C on 24 Oct | [src: memory brew-qa-audit-2026-10-20] [src: memory brew-qa-round2-2026-10-24] |\n| Restore test | Monthly; first on 25 Oct | Production export restored and counted | [src: brew/.wt-prod/docs/production.md:43] |\n| Handbook morning run | 9 am | Freshness and truth checks, overnight commits, Next, a short digest | [src: ~/.claude/scheduled-tasks/handbook-morning/SKILL.md] |\n| Weekly digest to brands | Monday 09:00 brand time | The product emails each team what changed | [src: brew/digest.js:1-12] |\n\nNo team meeting, weekly review, retro or planning cadence is written in any source. [src: memory brew-handbook]",
  "Tomorrow": "| Item | Version | Tag |\n|---|---|---|\n| Continuous deploy, QV rounds, QA sweeps | v1 | Stays |\n| A weekly review, 30 minutes | v1 | New, see Open |\n| A monthly ops check: restore test, spend, secrets | v1 | New |\n| A handbook snapshot after each weekly review | v1 | New |",
  "How we do it": "Proposed weekly review, Monday, 30 minutes, Param, Sai and Arvind:\n1. Next: what got done, what is stuck, what is new. 10 minutes.\n2. Design partners: one line each on Arata, Nutrova, Mana, PUMA India, Scrubroom. 10 minutes.\n3. Decisions needed: each item in Open that waits on Param, answered or given a date. 10 minutes.\n4. After: Claude writes the decisions into the decisions log and takes a handbook snapshot.\n\nProposed monthly ops check, first Monday:\n1. Restore test, see [Restore](/ops-and-infrastructure/restore).\n2. Last month's spend, see [Costs and quotas](/ops-and-infrastructure/costs-and-quotas).\n3. Secrets owners and rotation dates, see [Secrets and keys](/ops-and-infrastructure/secrets-and-keys).",
  "Numbers": "| Metric | Definition | Where measured |\n|---|---|---|\n| Weekly reviews held | Reviews that happened, out of weeks | Snapshots, Proposed |\n| Decisions per week | Rows added to the decisions log | Decisions log, Proposed |\n| QA rows open | Unfixed rows in Sai's QA sheet | The sheet, Proposed |",
  "Open": "1. **Hold a weekly review?** Proposal: yes, Mondays at 11 am IST, 30 minutes, agenda as above, starting 2 Nov 2026.\n2. **How often do design partner audits run?** Proposal: one full audit across the five partners every two weeks, run by Claude, triaged by Param and Sai."
 }
}