Answer
v2 adds one power on top of v1: after a person's yes, Brew posts or schedules the finished piece on the brand's own connected accounts, and saved workflows start a Play when something happens, always stopping for that yes.
Today
What exists that v2 builds on
| Piece |
State today |
Source |
| Posting |
Brew posts nothing anywhere except the brand's own Slack thread |
SCOPE.md:14 SCOPE.md:36-37 |
| Copy and open |
The manual post: copies the words and opens the exact place to post, prefilled on Reddit, X, LinkedIn and Pinterest |
public/post-open.js:43 memory brew-copy-and-open |
| Publish pack |
Every size, the words, links and a readme saying where each part goes |
brand-directions/docs2/content/inventory.mjs ENDS |
| Post or schedule for you |
Listed as Off, New, v2 in today's inventory |
brand-directions/docs2/content/inventory.mjs ENDS |
| Workflows |
20 templates in five groups, documented and specified, not built; every template starts off and every run stops for a yes |
brand-directions/docs2/content/pages.mjs:338-360 brand-directions/docs2/content/decisions.mjs:8 |
| Workflow rules |
Starts off, every run makes a card, a post or spend waits for a yes, a weekly cap, pause, undo and history on every run |
brand-directions/docs2/content/pages.mjs:215-221 |
| Workflow states |
Off, On, Waiting, Paused |
brand-directions/docs2/content/pages.mjs:222-227 |
| Slack |
Posts cards and jams to the picked channel; a change or paid make from Slack is a proposal that runs only on a yes |
SCOPE.md:14 slack-routes.js:2 |
| Scheduling slots |
The retired Jam v2 had a "pick a day" slot picker |
memory brew-jam-v2 |
What blocks posting
| Platform |
Access held today |
What posting needs |
Source |
| Meta |
App Review asks only ads_read, business_management, public_profile; ads_management and Pages, Threads and WhatsApp permissions were removed; business verification in review |
Publishing permissions and a fresh App Review |
memory brew-meta-app-review |
| Google |
Verified for adwords and analytics.readonly on 21 Oct; any new scope triggers review again |
No organic posting surface needed for v2 |
memory brew-google-oauth-scopes |
| Shopify |
Read scopes only; public app submitted 21 Oct |
Write scopes for any page or product change |
docs/connectors-approvals.md memory brew-shopify-app-review |
| Klaviyo |
Read only private key |
A write key for drafts or sends |
docs/connectors-approvals.md |
Price proposal
v2 plan at $119 or ₹7,999 a month, $18 or ₹1,500 into the wallet, still a proposal brew working tree docs/pricing.md:17-22.
Tomorrow
| Item |
Version |
Tag |
What it is |
| Schedule it, the second exit |
v2 |
New |
Beside Hand it off in the one sheet behind Make it; shows only where the dial and the connection allow it book c1.js c-4 exits |
| Prepare |
v2 |
New |
Files ready per channel, posted with one tap from a connected account brand-directions/BRIEF.md 3.6 |
| Need your yes as the control centre |
v2 |
Changes |
Every post and schedule asks here: one question, what happens either way, Yes and Not now, undo until it goes out brand-directions/_shared/product-model.md:56-58 |
| Work columns Scheduled and Live |
v2 |
New |
After Handed off brand-directions/_shared/product-model.md:110 |
| The dial per area and channel |
v2 |
New |
Suggest, Prepare, Schedule; every brand starts at Suggest; turning down is always allowed |
| Workflows |
v2 |
New |
A saved Play with a trigger, what it reads, the jam it makes and how it ends; until posting ships for a channel it ends in a brief or a pack |
| Workflow cap |
v2 |
New |
A weekly cap per workflow so a busy trigger cannot run up a bill |
| Hand it off |
v2 |
Stays |
Never goes away |
| Copy and open |
v2 |
Stays |
Still the way to post where Brew has no write access |
Requirements with acceptance
| Requirement |
Acceptance |
| Nothing posts without a yes |
A post or schedule exists only after a Yes in Need your yes from a person allowed to give it |
| Undo until it goes out |
A scheduled post can be cancelled until its time; the cancel leaves a line in the jam |
| The post is the approved version |
What goes out matches the version, words, link and size that were approved, byte for byte |
| A failed post says so |
A refused or failed post shows the platform's reason and never reads as posted |
| Every run makes a card |
Each workflow run lands in the feed or Need your yes, with what it read and what it made |
| Starts off |
Every workflow template is off until an admin turns it on |
| Cap holds |
A workflow that hits its weekly cap moves to Paused and says why |
| Read only stays the default |
A connection without write access never shows Schedule it |
Groundwork v2 needs from v1
Each pick stores its destination channel, the brief is saved as structured data, a decision log of hearted, made and handed off, and one status field that can grow book a.js a-5 v1.
Workflow templates, first set
All 20 are listed in workflows spec. The groups are Listen, Catalog, Ads and site, Calendar, and Briefs and posting brand-directions/docs2/content/pages.mjs:360.
How we do it
- Pick the first channel and request only its publishing permission; do not bundle scopes.
- Build the groundwork in v1 first, behind switches.
- Add Schedule it behind a per brand switch; turn it on for one partner.
- Record the platform review screencast on a test brand, never on Arata memory never-disconnect-arata-meta.
- Turn on one workflow template at a time, starting off for every brand.
Numbers
| Metric |
Definition |
Where measured |
Status |
| Approved post rate |
Share of hand-offs that become an approved scheduled post |
Decision log |
Proposed |
| Undo before send |
Share of scheduled posts cancelled before their time |
Decision log |
Proposed |
| Post failures |
Posts the platform refused, per week |
Post log |
Proposed |
| Workflow yes rate |
Share of workflow runs that get a Yes |
Need your yes log |
Proposed |
Open
- Which channel posts first? Proposal: Instagram and Facebook Page posts through Meta, because the Meta app and business verification are already in progress.
- Who may approve a post? Proposal: admins and members both may approve, only admins may turn the dial up.
- Which three workflows ship first? Proposal: Answer a new question about you, Get ready for a festival, Brief your agency on a heart, since each can end in a brief before posting exists.
- Does Prepare need write access? Proposal: yes, so Prepare and Schedule ship together per channel.
- v2 price. Proposal: keep $119 or ₹7,999 as the working number and decide with Sai after the partnership.
