{
 "id": "14.5",
 "title": "Onboarding a teammate",
 "department": "People and ways of working",
 "department_slug": "people-and-ways-of-working",
 "direction": null,
 "branded": false,
 "status": "needs-you",
 "owner": "Param",
 "last_verified": "Mon Oct 26",
 "holds": "Day one to week two",
 "urls": {
  "html": "https://handbook.joinsquareup.com/people-and-ways-of-working/onboarding-a-teammate",
  "markdown": "https://handbook.joinsquareup.com/people-and-ways-of-working/onboarding-a-teammate.md",
  "json": "https://handbook.joinsquareup.com/people-and-ways-of-working/onboarding-a-teammate.json"
 },
 "other_directions": [],
 "tldr": {
  "headline": "A first-day-to-week-two path so a new teammate ships fast and safely",
  "points": [
   {
    "icon": "book",
    "text": "Day one: accounts, then read the two handbook guides and walk the demo."
   },
   {
    "icon": "gear",
    "text": "Days two to five: run brew locally and ship a small fix to staging."
   },
   {
    "icon": "lock",
    "text": "Never wipe the five partners and never disconnect Arata's Meta or Shopify."
   },
   {
    "icon": "people",
    "text": "Week two: sit in on a QA round and own one open question."
   }
  ],
  "stat": {
   "value": "30",
   "label": "days before production access"
  },
  "decide": "Accept the proposed onboarding path, with Param as buddy for engineers?",
  "mood": "waiting"
 },
 "sources": [
  "handbook/AGENTS.md, handbook/WRITING.md",
  "brew origin/main a559de6: README.md 'Run it locally', CLAUDE.md, SCOPE.md, DUMMY.md, tools/prod-env.sh:9",
  "memory brew-handbook, brew-access-rules (index line), brew-prototype-repo, brew-live-stores, never-disconnect-arata-meta"
 ],
 "open_questions": [
  "**Accept the proposed path?** Proposal: accept as written, and try it on Sai or Arvind if either has not yet run brew locally.",
  "**Who is the buddy for a new person?** Proposal: Param for engineers, Sai for anyone working with partners.",
  "**When does a new person get production access?** Proposal: after 30 days and one restore test with Param."
 ],
 "parts": {
  "Answer": "No onboarding plan exists yet, so this page proposes a day one to week two path built from what already exists, the handbook, the repo and the live sites, and lists the access a new person needs, for Param to accept.",
  "Today": "- No onboarding checklist, buddy or first-week task appears in any source. [src: memory brew-handbook]\n- The handbook is the planning home; `AGENTS.md` and `WRITING.md` are the first two reads. [src: handbook/AGENTS.md] [src: handbook/WRITING.md]\n- The code is the private GitHub repo wulfor24/brew; it runs locally with `AI_MOCK=1` and keys from `../ugc-factory/.env`. [src: memory brew-prototype-repo] [src: brew/README.md]\n- Product staff access comes from the email domain: joinsquareup.com or shopos.ai. [src: brew/tools/prod-env.sh:9] [src: memory brew-access-rules]\n- Rules a newcomer must not break on day one: never wipe the five partners; never disconnect Arata's Meta or Shopify. [src: memory brew-live-stores] [src: memory never-disconnect-arata-meta]",
  "Tomorrow": "| Item | Version | Tag |\n|---|---|---|\n| A two-week onboarding path | v1 | New, see How we do it |\n| An access checklist kept in [Tools we use](/people-and-ways-of-working/tools-we-use) | v1 | New |\n| A first-week task that ships to staging | v1 | New |",
  "How we do it": "Proposed path.\n\n### Day one\n1. Accounts: a joinsquareup.com email, GitHub access to wulfor24/brew, the handbook through Cloudflare Access, the Slack workspace.\n2. Read `AGENTS.md`, `WRITING.md`, the one-page company story and the decisions log.\n3. Walk the demo at demo.joinsquareup.com as a visitor, then staging signed in on Cozy Snugglet.\n\n### Days two to five\n1. Run brew locally:\n\n```bash\ncd brew && npm ci\nAI_MOCK=1 BUILD_RESUME_OFF=1 RESEARCH_OFF=1 LIVE_OFF=1 TREG_OFF=1 FEED_SIGNIN=0 node server.js\n```\n\n2. Read `brew/CLAUDE.md`, `SCOPE.md`, `DUMMY.md`, then [Architecture](/engineering/architecture) and [Parallel sessions](/engineering/parallel-sessions).\n3. Read [How we work with Claude](/people-and-ways-of-working/how-we-work-with-claude) and run a first session on a small fix for every brand, with a test.\n4. Ship it to staging with Param watching.\n\n### Week two\n1. Sit in on a QV round or a QA sweep.\n2. Own one Open question in a handbook page and bring a proposal to the weekly review.\n3. No production access until a restore test has been done together.",
  "Numbers": "| Metric | Definition | Where measured |\n|---|---|---|\n| Days to first staging deploy | From start date to first change on staging | Proposed |\n| Access granted on day one | Items on the checklist done on day one | Proposed |",
  "Open": "1. **Accept the proposed path?** Proposal: accept as written, and try it on Sai or Arvind if either has not yet run brew locally.\n2. **Who is the buddy for a new person?** Proposal: Param for engineers, Sai for anyone working with partners.\n3. **When does a new person get production access?** Proposal: after 30 days and one restore test with Param."
 }
}