---
id: "17.6"
title: "Internal updates"
dept: pr-and-communications
status: draft
owner: Param
branded: false
last_verified: "2026-10-26"
sources:
  - "handbook AGENTS.md; tools/snapshot.mjs:1-6; .last-sync; git log of the handbook repo"
  - ".claude/skills/handbook-update/SKILL.md, steps 1 to 8; ~/.claude/scheduled-tasks/handbook-morning/SKILL.md"
  - "brew origin/main: docs/production.md:112-115"
  - "handbook content/company-and-strategy/decisions-log.md; content/product-marketing/release-notes.md"
  - "memory brew-handbook, brew-go-live-2026-10-17, brew-pricing-parked"
---

# Internal updates

## Answer

The team stays in the loop through this handbook and its tools, not a separate note: decisions go in the decisions log, work in Next, threads in Comments, and a short digest each morning; what is missing is a weekly note that Param, Sai and Arvind read together, which this page proposes.

## Today

| Channel | What it carries | Who | Source |
|---|---|---|---|
| This handbook | Every plan, decision and open question; read at handbook.joinsquareup.com behind a sign in | Param, Sai, Arvind | [src: handbook AGENTS.md] [src: memory brew-handbook] |
| Decisions log | Every call, newest first, never deleted | All | [src: handbook company-and-strategy/decisions-log] |
| Next | One to do across every front, a private artifact with a database | All | [src: handbook AGENTS.md] [src: .claude/skills/handbook-update/SKILL.md step 5] |
| Comments | Threads on any paragraph; @Claude answers and proposes, Param accepts | All | [src: memory brew-handbook] |
| Morning digest | The scheduled run at 9 a.m. ends with at most five lines: documents refreshed, stale ones, new tasks in Next, the check result, what waits on Param | Param | [src: ~/.claude/scheduled-tasks/handbook-morning/SKILL.md] [src: memory brew-handbook] |
| End of a session | Every handbook update ends with three lines: what changed, what is new in Next, what waits on Param | Param | [src: .claude/skills/handbook-update/SKILL.md step 8] |
| Snapshots | Handbook 1.0, 1.1 and so on, as git tags `hb-*`, never deleted; none taken yet on 26 Oct | All | [src: handbook tools/snapshot.mjs:1-6] [src: git tag -l hb-* in the handbook repo] |
| Release notes | What changed for brands, newest first, from the changelog | All | [src: handbook product-marketing/release-notes] |
| Alerts | Uptime and app alerts email param@ and hello@ | Param | [src: brew/docs/production.md:112-115] |
| Status docs | Engineering Status and Product Status as private Claude Docs from 17 Oct, which superseded the handover of 15 Oct | Param | [src: memory brew-go-live-2026-10-17] |
| Shared jams | Plans for Param and Sai, such as the pricing jam artifact | Param, Sai | [src: memory brew-pricing-parked] |

No source sets a weekly meeting, a weekly note or a place to celebrate wins [src: no source found in memory or the handbook].

## Tomorrow

| Item | Version | Tag |
|---|---|---|
| The handbook as the one place for plans and decisions | v1 | Stays |
| A weekly note every Monday, built from the week's decisions, snapshots, release notes and Next | v1 | New, Proposed |
| A wins section in the note: a partner's hand off, an approval passed, a fix that held | v1 | New, Proposed |
| A snapshot after each material change, starting with Handbook 1.0 | v1 | New |

## How we do it

1. A decision made in chat gets a row in the decisions log the same day, through the handbook-update skill [src: .claude/skills/handbook-update/SKILL.md step 3].
2. After any session that changed something the handbook describes, run the handbook-update skill; it ends with the three line report [src: handbook AGENTS.md].
3. Take a snapshot when the change is material:

```bash
cd /Users/param/Documents/ChatGPT/handbook
git tag -l 'hb-*'
node tools/snapshot.mjs take 1.0 "First full handbook"
```

[src: .claude/skills/handbook-update/SKILL.md step 6]

4. Proposed weekly note, Monday morning, written by Claude from the sources and sent by Param: decisions this week, what shipped, what waits on whom, wins, and the three questions only Param can answer.

## Numbers

| Metric | Definition | Where measured |
|---|---|---|
| Open Needs you documents | Documents with status needs-you | `registry.json` and the front matter |
| Decisions this week | New rows in the decisions log | `decisions.mjs` |
| Stale documents | Documents whose brew sources changed after they were checked | `node check.mjs` |
| Notes sent | Weekly notes sent | Proposed |

## Open

1. **Do we want a weekly note at all, or is the morning digest enough?** Proposal: a weekly note on Mondays, because Sai and Arvind do not see the digest.
2. **Where does it go?** Proposal: email from Param to Sai and Arvind, with a link to the handbook snapshot.
3. **A weekly meeting?** Proposal: 30 minutes on Mondays after the note, to answer the three questions.
4. **When is Handbook 1.0?** Proposal: when every document in every department is written.