Answer
The signals that tell us a design partner is thriving or slipping; no health score exists in any source, so the signals below are drawn from what the code already records and the thresholds are proposals for Param.
Today
No health score, dashboard or review exists. These records already exist and could feed one.
| Signal | What is recorded | Source |
|---|---|---|
| Who opened the brand | One row per brand and email with first seen, last seen and a count, on Postgres, since 23 Oct | brew/server.js:657-666; memory brew-access-rules |
| Weekly digest | When it last went, to whom, and whether Slack got it | brew/digest.js:8, 192 |
| Plays emails | Which ready and update emails each person got | brew/build.js:996-1003 |
| Briefs with our team | Briefs sent and not delivered, and how many need info from the brand | brew/brief-status.js:32-37 |
| Connections | Last good read, stale after 72 hours or 3 failed reads, and sign in expiry | brew/connectors/index.js:53, 474-493 |
| Waiting on the brand | A read waiting for its check, or Plays waiting for the first feed open | brew/confirm-remind.js:21-34 |
| Emails turned off | Per person mail settings: all, tags only or off | brew/jam-mail.js:14, 23-25 |
The five partners are Arata, Nutrova, Mana, Puma India and Scrubroom, all on production. memory brew-live-stores, brew-prod-backend
Tomorrow
| Version | Tag | Item |
|---|---|---|
| v1 | New | A weekly health line per partner: green, amber or red, from the signals below, reviewed every Monday. |
| v1 | New | Thriving: someone on the team opened the brand in the last 7 days, at least one jam moved, and every connection read in the last 72 hours. |
| v1 | New | Slipping: no open in 7 days, or a check or feed open waiting more than a day, or a connection stale, or a brief needing info for more than 2 days, or emails turned off by the admin. |
| v1 | New | Red: no open in 14 days, or Arata's protected connections not reading. |
| v2 | New | The same line shown to our team in the staff view, built from the records above. |
How we do it
These are proposals until Param accepts them.
Every Monday, list each partner's last open from the visitors record.
GET /api/admin/visitors?slug=<slug>Run the status job and read each partner's connection states.
gcloud run jobs execute brew-ops --region=asia-south1 --waitRead the brief pill for each partner: anything sent and not delivered, and anything needing info.
Mark each partner green, amber or red with the rules in Tomorrow, and write one line on why.
For every amber or red, the partner's owner writes to them that week, as a person, with one concrete next step.
Numbers
| Metric | Definition | Where measured | State |
|---|---|---|---|
| Weekly active partners | Partners with at least one team open in the last 7 days | access_log | Proposed |
| Active people per partner | Distinct team emails that opened the brand in 7 days | access_log | Proposed |
| Briefs shared per partner per week | Briefs shared to their team or ours | jam jamBrief.sharedAt |
Proposed |
| Stale connections | Connections with no good read in 72 hours | connections, stale flag |
Proposed |
| Days waiting on the brand | Days a check or a feed open has waited | status.json waitingSince and feedWaitSince | Proposed |
Open
- Do we score health at all during the design partnership? Proposal: yes, a weekly green, amber or red line per partner, by hand, for the first four weeks.
- What counts as thriving? Proposal: an open in 7 days, one jam moved and every connection fresh, as written in Tomorrow.
- Who reviews it? Proposal: Param, every Monday, with each partner's owner.
- Does a partner ever see its own health? Proposal: no; it is our working view only.