---
id: "11.1"
title: "Arata"
dept: sales-and-partnerships
status: draft
owner: Param
branded: false
last_verified: 2026-10-26
sources:
  - "brew origin/main a559de6: SCOPE.md:43-55, auth.js:106-107, connectors/protected.js:2-3, connectors/index.js:267, db/partner-copy.js:7-8 and 43, deploy.sh:19-20 and 41, ai-questions.js:4, claims.js:201, connectors/shopify.js:203-214, card-nums.js:2, docs/audit-2026-10-24-design-partners.md"
  - "brew commits deb7d90, 119dc8a, 04571a2, 19c87c6"
  - "memory: brew-live-stores, brew-prod-backend, brew-go-live-2026-10-17, brew-arata-rewrite-2026-10-15, brew-arata-reload-2026-10-20, brew-meta-connector-qa, brew-shopify-connector-qa, never-disconnect-arata-meta, brew-qa-round2-2026-10-24, brew-audit-2026-10-15, brew-absorb-all-learnings, brew-model-compare-2026-10-20, brew-viral-remakes, brew-jam-v2, brew-jam-rca-2026-10-26, brew-draft-quality, brew-meta-app-review"
---

# Arata

## Answer

Arata is the design partner furthest along: the only one with real accounts connected, Meta Ads and Shopify, so every rule that protects a live client starts here and its connections are never touched.

## Today

### Profile

| Fact | Source |
|---|---|
| Slug `arata-in`, store arata.in | [src: memory brew-live-stores] |
| A hair care brand; the code calls it a hair fall brand | [src: brew/ai-questions.js:4] |
| The first brand carried into Brew on 15 Oct; it was the hand made pack the read was modelled on, now an ordinary brand pack | [src: brew/SCOPE.md:43-55] |
| Claimed for the brand by our team's staff address; anyone with an arata.in email joins the team on their own | [src: brew/auth.js:106-107] |
| Home is production, feed.joinsquareup.com, since 25 Oct; staging is for testing only | [src: memory brew-prod-backend] [src: brew/deploy.sh:19-20] |
| A real design partner prospect, one of five; never wiped or reset | [src: memory brew-live-stores] |

### Connections

| Account | State | Source |
|---|---|---|
| Meta Ads | Ad account act_2942894532542334, connected 22 Oct. The grant is ads_read, business_management and pages_show_list; the app is on development access until Meta App Review | [src: memory brew-meta-connector-qa] [src: memory brew-meta-app-review] |
| Shopify | Connected 23 Oct through the brand's own app, route own-oauth; the offline token never expires | [src: memory brew-shopify-connector-qa] [src: memory brew-prod-backend] |
| Protection | `PROTECTED_CONNECTIONS` defaults to arata-in: disconnect, re-select and reconnect are refused unless an admin forces it | [src: brew/connectors/protected.js:2-3] [src: brew/connectors/index.js:267] |
| Both sites | The same tokens read on staging and production; nothing was refreshed or revoked in the copy | [src: brew/db/partner-copy.js:7-8] |
| Everything else | No GA4, Google Ads, Klaviyo, Judge.me or Slack connection on record | [src: brew/docs/audit-2026-10-24-design-partners.md:3] |

### What the accounts showed

| Figure | When | Source |
|---|---|---|
| About 1,200 orders a day, about 35,000 in 30 days | 23 Oct | [src: memory brew-shopify-connector-qa] |
| 97% of orders come through the GoKwik checkout app; Shopify's 4,411 abandoned checkouts are only carts that reached Shopify's own checkout | 23 Oct | [src: memory brew-shopify-connector-qa] [src: brew commit 19c87c6] |
| Cash on delivery: 2% cancelled, 37% shipped and still unpaid; never called failed | 23 to 24 Oct | [src: brew commit 04571a2] [src: brew/connectors/shopify.js:203-214] |
| 11 of 12 zero stock products keep selling at zero | 23 Oct | [src: memory brew-shopify-connector-qa] |
| One campaign's Meta frequency 4.05, where an older reading said 1.7 | 23 Oct | [src: memory brew-shopify-connector-qa] |
| Live Meta ads shown on a card: 1,577 | 22 Oct | [src: brew/card-nums.js:2] |

### History

| Date | What happened | Source |
|---|---|---|
| 15 Oct | A 50 Play rewrite stopped when the AI credit ran out; 7 Plays published by hand | [src: memory brew-arata-rewrite-2026-10-15] |
| 15 Oct | Arata agreed its team notes stay public on the demo site | [src: memory brew-audit-2026-10-15] |
| 16 Oct | Final run: 56 of 56 Plays | [src: memory brew-go-live-2026-10-17] |
| 19 Oct | Our team's deck for Arata became context the Plays work to | [src: memory brew-absorb-all-learnings] |
| 20 Oct | All Plays redone on Opus, 54 of 56, about $65 to $70 | [src: memory brew-arata-reload-2026-10-20] |
| 20 Oct | Pro against Opus compared on 54 pairs: Opus clearly better, confounded by inputs | [src: memory brew-model-compare-2026-10-20] |
| 21 Oct | Sloosh video tests run on Arata; its viral final cost 80.8 credits | [src: memory brew-viral-remakes] |
| 22 Oct | Meta connected; the connector and the privacy of its numbers fixed the same day | [src: memory brew-meta-connector-qa] |
| 23 Oct | Shopify connected; 11 store Plays rewritten by hand for $3.40 | [src: memory brew-shopify-connector-qa] |
| 23 Oct | Studio tested live on Arata: listing set, 360 degree turn, packshot | [src: memory brew-jam-v2] |
| 23 to 24 Oct | Round 2 QA report on Arata: 32 pass after round 4 | [src: memory brew-qa-round2-2026-10-24] |
| 24 Oct | Design partner audit of all five | [src: brew/docs/audit-2026-10-24-design-partners.md] |
| 25 Oct | Copied to production, last of the five; its home briefly moved back to staging for a 26 Oct onboarding, then to production again | [src: memory brew-prod-backend] [src: brew commit deb7d90] [src: brew commit 119dc8a] |
| 25 Oct | Feed drafts on Arata were collages; every product picture is now judged before it shows | [src: memory brew-draft-quality] |
| 25 Oct night | Re-check on production: 25 pass, 4 fixed, 3 pass with a note | [src: memory brew-qa-round2-2026-10-24] |
| 26 Oct | Param's screenshots of a ₹2,182 combo card led to five jam and brief fixes | [src: memory brew-jam-rca-2026-10-26] |
| 26 Oct | A WhatsApp broadcast draft led to a claim check rule | [src: brew/claims.js:201] |

### Open issues

- "Fix the pack prices" repeats across about six cards; no dedupe across Plays yet [src: memory brew-arata-reload-2026-10-20]
- Some cards speak in a we and our voice [src: memory brew-qa-round2-2026-10-24]
- MitoActive shows no Shopify units for 30 days, possibly a preorder [src: memory brew-qa-round2-2026-10-24]
- The first load after a release is slow [src: memory brew-qa-round2-2026-10-24]
- Meta App Review is blocked on business verification and two screencasts, which are recorded on Cozy, never Arata [src: memory brew-meta-app-review]

### Next step

No commercial next step, contact name or agreement is on record. See Open.

## Tomorrow

| Item | Version | Tag |
|---|---|---|
| Arata stays the first brand every fix is checked on, and its connections stay protected in code | v1 | Stays |
| A named contact, a weekly check in and a feedback log entry per call | v1 | New |
| A written design partner agreement covering data use, the demo and the end of the partnership | v1 | New |
| First brand offered posting with a yes, once v2 ships | v2 | New, proposed |
| First brand offered results, since it is the only one with Shopify and Meta connected | v3 | New, proposed |

## How we do it

1. Never disconnect, reconnect or re-select Arata's Meta or Shopify, on either site. Disconnect tests run on Cozy Snugglet.
2. Read only audits with the stored tokens are fine:

```
node tools/meta-audit.mjs arata-in
node tools/shopify-audit.mjs arata-in
node db/connector-ping.mjs arata-in
```

3. Any cleanup that touches `private/vault/meta.json`, `connections.json` or the disconnect action skips `arata-in`.
4. Before a long paid run on Arata, check the AI credit and ask other sessions not to deploy.
5. Check a fix on Arata first, then on the other four partners.

## Numbers

| Metric | Definition | Where measured | Status |
|---|---|---|---|
| Connected accounts | Real accounts reading, not simulated | Connector ledger, `db/connector-ping.mjs` | Today: 2 |
| Team members | People from arata.in who joined | `private/members.json` | Proposed, not counted yet |
| Hand offs a week | Briefs shared or sent from Arata's jams | Jam records | Proposed |
| Paid spend on Arata | AI, Studio and finals cost per month | `brands/arata-in/spend/` | Proposed |

## Open

1. **Who at Arata do we work with?** No contact name is on record. Proposal: add the main contact, their role and how they prefer to talk to this page.
2. **What is the next step with Arata?** Proposal: a 30 minute call this week to walk the Plays they rated highest, then agree a design partner agreement from [Contracts](/sales-and-partnerships/contracts).
3. **Does Arata stay on the demo site?** It agreed on 15 Oct that its team notes stay public there, but it now has real accounts connected. Proposal: keep only its public pack on the demo and ask Arata to confirm in writing.
4. **Is our team's deck for Arata a paid engagement?** The sources do not say. Proposal: record whether Arata pays our team separately, so the Brew partnership stays independent.