Updated Tue 8 Sep 2026, 14:05 London — daily refresh · partial sources, second day running: only git + BACKLOG.md came back from the 13:05Z collection (Slack, prod DB, Linear, TG Core Engineering and team marks all unavailable — non-git items carry from the 2 Sep sources, and any ticks made on the 7 Sep board could not be read)
Top now: send Halo’s two payouts ($1,497.32) · REV-150: arm production payouts · answer Jarrod on the missing 8.5/8.7 clauses
Two manual drafts stood in #ach-payouts-production with no send or reconciliation after them at the 2 Sep collection: 27 Aug ($1,139.16, pay on or after 28 Aug, 9 orders) and 1 Sep 19:27Z ($358.16, settlement window 25 Aug – 1 Sep, 2 orders, “this Slack notification does not initiate a transfer”). REV-191 (filed 2 Sep 06:30Z) said the same: production still runs manual-instructions mode, both drafts outstanding. Hudaifa rejoined #halo-peptides 31 Aug 15:52Z and Halo kept selling — $254 (31 Aug), $151.20 (2 Sep). Slack and the DB have been unreadable 7–8 Sep, so a send since 2 Sep is unverified — but nothing anywhere evidences one, and nothing in git through 7 Sep touches payouts.
Next actionHand Andrew both amounts with Halo’s approved banking (Mercury checking ••••2806) and the business address from app_R89kpf0lM4Jd5X_r for the BofA portal; record both bank references in Revion. The automation is Nur’s REV-150 → REV-191.
31 Aug 15:54Z Jarrod: his accountant says a Washington business must collect WA tax on these orders. You answered 16:36Z citing agreement sections 8.5 (Revion registers, collects, remits) and 8.7 (resale certificate). 31 Aug 23:48Z: “my contract ends at section 8.4, so I never saw 8.5 or 8.7.” 1 Sep 05:57Z you conceded the text is from the master document, not the one he signed, and promised to discuss with Aadil that day — nothing in #rhp-rhpeptides by the 2 Sep collection, and Slack has been unreadable since, so any later reply is unverified. His store is live for real: RC-2026-1000243, $598, AUTHORIZED 2 Sep 05:08Z (avs=Y, cvv=M). The idle-reminder sweep merged and was promoted 6 Sep (#376/#402); REV-190 keeps RHP skipped until this closes.
Next actionGet the executed RHP agreement from Aadil (on his list), decide addendum vs. accepting his position on WA tax, reply in-channel today — and mark the $598 while you are there.
Banking approved 31 Aug 12:55Z; both test refunds confirmed to her and her only reply was “Thanks so much” (31 Aug–2 Sep window). Prod DB at 2 Sep 13:05Z: 0 sessions, 0 orders for mrc_zinhzQp6eyBC since 31 Aug — the six days since are unknown (the 7–8 Sep watch-merchant reads came back empty). Aadil (2 Sep 05:46Z): “one transaction in five days” — Andrew is counting, and this is the merchant closest to adding some.
Ask Jenifer plainly when Revion goes on as the live payment option and offer to watch the first day; no reply by tomorrow → Aadil calls (his chase task).
Set live + banking approved 31 Aug 15:24Z (done). At the 2 Sep read he was still registered as https://www.biopepusa.com — the www/apex shape that broke RHP’s and Kiyora’s first checkouts. Casey created a session himself 31 Aug 15:37Z ($59.00, info@biopepusa.com) which expired with no payment intent: he reached our checkout and never submitted a card — why is unverified. #biopep-usa-llc held only our team, no welcome posted. Whether the domain got corrected or Casey retried since is unverified — Slack and the DB are down again today.
Correct the domain to https://biopepusa.com via single-field DB update (never suspend — it wipes credentials), then email Casey directly: welcome, “run the $59 test again and we void it”, accept the Slack invite.
app_uHyTgAc1QXxFQKBW (coreresearchpeptides.com) moved received → under review 1 Sep 21:07Z and was still there at the 2 Sep 13:05Z read; the DB reads since have failed, so the current state is unverified. Approving provisions credentials + Slack automatically (Middesk gating) — and Slack welcome v2 (#412, 7 Sep) now auto-posts the integration pack the moment the channel is created, so approval → channel → pack is hands-free. The 3-field apply-fast intake + admin onboarding editor (#399, 5 Sep) and activation-blocker surfacing at Set live (#401, 6 Sep) are also in.
Approve → descriptor → banking → welcome; then onboarding-check.sh app_uHyTgAc1QXxFQKBW before telling him “check Slack”. The credentials email still carries the “payments disabled” line (REV-169) — correct it in-channel.
Chased 31 Aug 09:06Z with the $143.96 abandoned-session evidence; no reply by 2 Sep, and Slack has been unreadable 7–8 Sep. Prod DB at 2 Sep: 0 sessions for mrc_4JFn-SyBlVNP since 31 Aug. Chris last spoke 28 Aug 04:07Z.
Stop nudging in Slack — hand to Aadil for a phone call with a booked slot (cal.com/team/revion); the idle-reminder email (merged + promoted 6 Sep) lands too once Nur arms it.
4SMZBX4M… + run the REV-60 cleanup scriptWhether the ticket has been resolved is still unverified (no billing-inquiry rows in the 2 Sep bundle; Linear and the DB are down again today). Verified at 2 Sep: the REV-193 plan (copied from REV-60) still lacked the cleanup section, and the 1 Sep QA run ended US-7 + US-8 FAIL with three ZZTEST applications still “received”. PR #355 needs no promotion — it reached prod 28 Aug.
Next actionrevioncaps.com/admin/billing-inquiries → Resolve, note “QA daily test — no action”. Locally: source ~/RevionCaps/creds.sh && python3 ~/RevionCaps/linear_cleanup_rev60.py.
banking_approved 2 Sep 06:28Z; 0 sessions since 31 Aug at the 2 Sep read; their dev has not written since 20 Aug (“Alright, scheduled for next week”). The 31 Aug chase proposed a 20-minute call; no answer by 2 Sep, nothing readable since.
The call is the test: Aadil books it by phone/email (contact is the dev shop, dev@guardedpaypro.com); run and void the first embedded order together.
Done since yesterday: git only — admin bulk email to merchants with recipient preview shipped (REV-208, #414, 7 Sep): pick recipients, preview, send from admin — the first broadcast channel to merchants outside Slack.
Your question (2 Sep 05:46Z, “drop-off due to people not being able to check out with their chosen card brand”) has a measured answer from Tim (2 Sep 06:04Z): declines of $380 (31 Aug 11:15Z, txn 12495306934) and $361 (1 Sep 10:01Z, txn 12500637032), both card_declined, both non-Visa — “the Visa-only wall”. Every merchant is still told “Visa only for now” (Halo 20 Aug, Zen 28 Aug). The rest of the funnel was normal: 5 completions, ~65–70% cart abandonment, zero technical failures. (The 2 Sep declines on Halo were the processor’s “Pick up card” response, code 253; the same $151.20 went through on the third attempt — a different cause.) No brand answer is visible in any source since — Slack and TG are down again today.
With Andrew/Ignacio: what enables Mastercard/Amex/Discover on the NMI MID, and by when — give Tim a date. Until then the checkout should say “Visa only” before a buyer types a card (Nur, next to REV-100).
Open since 28 Aug; Nur asked again on the morning of 29 Aug. No update in Core Engineering by 2 Sep, and TG has been unreadable 7–8 Sep — whether it went out is unverified. He kept shipping meanwhile (the Apple Pay cancel fallback #407 and the REV-171 Slack integration pack #412 both landed 7 Sep); keep him shipping.
Next actionSend it, confirm in the thread.
Hudaifa Elahi rejoined #halo-peptides 31 Aug 15:52Z (the “restore the channel” half of REV-163 is done); nobody had written there by the 2 Sep collection, and Slack has been unreadable since. Owed: $1,139.16 + $358.16. The ticket asks you to explain what was fixed (Apple Pay encoding, consent gate, order-note links) and what is coming (stable payment links, REV-159), give a payout date, and get Sufyan to retest after the payment-link fix.
Next actionCall, then post the payout date in #halo-peptides so it is on record.
Jarrod’s copy ends at 8.4 (31 Aug 23:48Z); Tim: “that text is from the master document, not the one you signed… I will discuss with Aadil today” (1 Sep 05:57Z). His accountant wants WA tax collected; Tim also tagged you 31 Aug 16:36Z on Washington registration timing ($100k trailing-12-month threshold).
Next actionSend Tim the executed RHP agreement plus your call: an addendum carrying the tax clauses, or accept his position. He transacted for real on 2 Sep ($598) — this is seven days old now.
Prod DB since 31 Aug, at the last successful read (2 Sep): Kiyora 0 sessions, Zen 0, Best Peptide 0, Biopep 1 (Casey’s own $59 attempt, expired). Tim (2 Sep 06:05Z): “we have to push merchants from all sides to transact. Slack does not work very well.” You offered to do the chasing on 31 Aug. Two automated channels now exist alongside the call: the idle-reminder email (merged + promoted 6 Sep, #376/#402, awaiting arming) and Tim’s admin bulk email with recipient preview (REV-208, #414, 7 Sep). Neither replaces a call.
Next actionPer merchant: Kiyora — switch real traffic on; Zen — one $-test with Tim watching; Best Peptide — book the 20-minute embed call; Biopep (Casey) — retry the test and accept the Slack invite.
1 Sep 20:52Z: “can we approve Apex Peptide Supply… no payment methods at all… desperate guy.” Tim (2 Sep 06:02Z): “we do not have his application.” Provisioning starts from /apply (Middesk KYB); nothing can be created by hand. The ask got cheaper since: the 3-field apply-fast intake shipped 5 Sep (#399).
Next actionSend him revioncaps.com/apply today and agree the rate — anything other than 12/14 waits on REV-189.
VAPI_PRIVATE_KEY etc. are SET on revioncaps-prod; calls are held off only by VAPI_OUTBOUND_ENABLED=false. No calling-window, DNC, or consent gates exist in vapi-outbound.ts. Unchanged since 31 Aug.
Either unset the prod keys or commission the TCPA gates. Deciding is the task.
Linear REV-164 (p3, Todo, yours since 27 Aug — state unreadable, Linear has been down 7–8 Sep). Readable by anyone who scrolls Core Engineering.
Next actionRotate it, delete the message, close the ticket.
Variants live in the “Revion Home Variants” artifact (REV-101). Waiting since 27 Aug; no letter seen by 2 Sep and TG has been unreadable 7–8 Sep. The brand-identity pass landed regardless (nur/home-brand-identity → #406, 7 Sep, with its four introduced defects fixed same-day in #408), so your letter now decides the homepage layout, not the overall look.
Reply with a letter in the Core Engineering thread.
Decided 31 Aug 13:37–13:43Z; filed as REV-187 “Integrate DocuSeal for document e-signing (replace DocuSign seats)” 1 Sep 00:16Z, unassigned at the last readable check. The 5-contract batch (REV-192, 2 Sep) used DocuSign envelopes meanwhile.
Next actionSet up the Docuseal template (generic + company/signature/signer/title/date fields), assign REV-187, and add a follow-up chase for merchants who signed but never hit /apply (your own words, 31 Aug).
Done since yesterday: nothing verifiable — Slack, TG, Linear and the prod DB were all unavailable again in today’s collection; git is the only fresh source.
Tim (2 Sep 06:12Z): “REV-150 (URGENT)”. The ticket’s three gaps: (1) settlement evidence for Halo’s NMI orders — confirm the evidence sweep + NMI reporting creds run on revioncaps-prod, clear the 2 manual_review rows; (2) ACH generation — prod ships PAYOUT_ACH_SLACK_ENABLED="false" and has no ACH_* secrets (sandbox has the set), plus the Slack roster env; (3) maturity math (t+4 FedACH days). REV-191 (2 Sep) adds: prod still had PAYOUT_MANUAL_INSTRUCTIONS_ONLY=true next to PAYOUT_AUTOPILOT_ENABLED=true — the contradiction to remove. Outstanding drafts: 27 Aug $1,139.16, 1 Sep $358.16. Nothing in git through 7 Sep touches payouts or ACH, and Linear is down again — no source shows movement.
Gaps 1–2 today (ACH values from Mercury/Aadil), penny-test file to Mercury before the first real one; then REV-191.
All movement is in git: PR #376 (branch feat/idle-merchant-reminder, off by default) merged 6 Sep (d4fd4a1), promotion-review fixes followed (#403), and the promotion PR from sandbox (#402) merged the same day; 7 Sep brought the reminder into the new palette (5d0f09e). What no source can show — today included: whether prod has REVION_IDLE_REMINDER_ENABLED=true + REVION_IDLE_REMINDER_SKIP=mrc_gu6vQA07rA7D (RH stays out until the 8.5/8.7 question closes), whether the Fly apps rolled the promotion, or whether any 14–18 UTC window has produced reminder emails.
Set/confirm both flags on prod, verify the rollout, then after the window: emails rows of kind merchant_idle_reminder delivered, merchant_idle_reminders max 1 per merchant per 72h. Pre-check block in REV-190.
Tim (1 Sep 19:13Z): “add 8.5%, 9% and 10% as well as 12/14… maybe configure any %”. REV-192 (done 2 Sep 06:58Z) sent Pura 8.5, Planet 8.5, Fit Aminos 9, Sports Tech 10, Epic 12 — “provisioning waits on that ticket”. At the 2 Sep code read: zod locks feeRate to 12|14 in three places, the admin types it as 12 | 14, sandbox-provisioning-client.ts:66 refuses other values, and settlement.ts guards fee_rate IN (12, 14) twice — an 8.5% order would be excluded from settlement with no error anywhere. Nothing in git through 7 Sep names fee rates.
One exported feeRateSchema (>0, ≤30, 2 decimals) reused everywhere; admin quick-picks + free field; range checks in provisioning and both settlement guards (keep the fee_cents integrity check); prove 8.5 round-trips to fee_cents and renders “8.5%”. Steps and greps in REV-189.
Tim filed REV-191 on 2 Sep 06:30Z, folding Aadil’s 31 Aug ask (address on a merchant’s FIRST payout, name + breakdown afterwards) into the automation: REV-151 is marked Done yet prod pays nothing without a human. Gated on REV-150. All six live merchants were banking-approved by 2 Sep, so per-merchant enrollment can be an audited flag on banking_approved.
After REV-150: auto-draft after cutoff → run-level approval → Mercury API send → auto-reconciliation; PAYOUT_MANUAL_INSTRUCTIONS_ONLY off; address line on first payouts (from the Middesk-verified application record). Acceptance in the ticket.
support_admin_alert emails to support@send.revioncaps.com showed [failed] repeatedly from ~28 Aug in the prod email log (seen at the 31 Aug board build); earlier alerts to support@revioncaps.com delivered. No bundle since has carried email-log rows, so still-failing is unverified — and nothing in git through 7 Sep touches it.
emails.ts:368 still carried the line at the 2 Sep read (REV-169, p0, Backlog since 27 Aug; in Tim’s onboarding cluster). It went to Biopep on 31 Aug; humans correct it in-channel each time — the template is the fix. Slack welcome v2 (#412, 7 Sep) reworked the channel welcome, but nothing in git names the credentials-email line.
Linear: REV-152 completed 28 Aug 15:05Z (the 31 Aug board carried it as open). Prod at the 2 Sep read: mrc_roNy1mlK9Ij5 domain https://www.biopepusa.com. PR #364 folds www for success_url/CORS; whether “verify at registration”, “log rejected checkouts” and a correction path that does not route through suspend shipped is unverified from any bundle since.
Say which of the three items shipped; if any did not, reopen REV-152 or file the remainder. Tim fixes Biopep’s row by hand meanwhile.
Checkout/conversion: REV-121 prefill hosted checkout from Woo · REV-124 loading overlay swallows clicks · REV-159 payment links die after 30 min (Halo’s auto-sent links) · REV-100 Apple Pay failures undiagnosable · REV-166 checkout link exposes buyer PII. Ops/visibility: REV-146 error log + Slack · REV-142 alert when a merchant goes silent (the RH 20h blackout) · REV-145 admin plugins page · REV-173 plugin telemetry null · REV-165 daily funnel/decline report. Onboarding: REV-144 · REV-87 · REV-169 (REV-171 shipped 7 Sep, #412). Money correctness: REV-172 gateway refunds invisible to settlement · REV-175 payout export with stale banking. Movement 7 Sep: the Apple Pay cancel dead-end now routes to the card form (#407 — REV-100’s diagnosability ask still stands), and checkout analytics got privacy hardening + payment outcome coverage (#410) on top of the server-side PostHog events (#404) — decline analysis has server truth to join against.
slack_provisioning_status/_error exist on the merchant row but nothing shows them. #biopep-usa-llc still held only our team 48 hours after creation (as of 2 Sep), and only a shell query can say whether Casey’s invite failed or sits unaccepted. Welcome v2 (#412, 7 Sep) auto-posts the integration pack once a channel exists — invite status in admin is still unexposed.
settlement.ts deducts refunded_cents but never recalculates fee_cents down; MFSA 16.4 argues the fee share should come off too. Invisible until a merchant partially refunds a settled order — cheaper to fix before one does. (Adjacent: REV-172, gateway-side refunds invisible to the sweep.)
Git 4–7 Sep on nur/home-brand-identity: “Implement the Revion identity across every Revion-controlled interface” (4 Sep), /apply-fast + onboarding editor brought into the identity (5 Sep), checkout header on the mark with the rest held at a verified production baseline, the mark named “Revion Caps”, the last R tile retired, the Clash Display gate corrected — merged as #406 (7 Sep), and the four defects the redesign introduced were fixed same-day (#408). Whether a variant letter was picked is unverified (TG down 7–8 Sep); REV-101 holds the variants.
Once Aadil’s letter lands, implement the chosen layout on top of the new identity (the logos are already in).
Asked in Core Engineering 31 Aug 13:48Z mid-triage of a phantom inquiry: “Would be sick if we had the customers number ready for anyone/me/andrew/pat to call them right away too.” The buyer’s phone is collected at checkout; the billing-inquiry queue and its alert email don’t surface it. Not in Linear at the last readable check (2 Sep).
Next actionShow the buyer’s phone on the billing-inquiry admin view + in the alert email. File in Linear with the LLM pre-check block.
Done since yesterday: git only, all 7 Sep — Apple Pay cancel now guides the buyer to the card form instead of a dead end (#407, nur/apple-pay-fallback) · Slack welcome v2 auto-posts the integration pack on channel creation, closing REV-171 (#412) · checkout analytics privacy hardened + payment outcome coverage extended (#410) · the four defects the redesign introduced were fixed same-day (#408).
Tim (2 Sep 06:04Z): ~20 real sessions in the 28 Aug – 2 Sep window, 5 completed, 2 non-Visa declines, ~9 reached our page and never submitted a card (~$2k) — “that is exactly the PostHog replays — Narboto has the invite, replay review of these session IDs is the next step.” Halo sessions to pull first: cs_1MxLyGmlAnYE1uDVNOXz $340 · cs_iCIj0VavIkfhPcP5IFQG $205.20 · cs_42nR0ZkxuLfKm7MsBVBV $292.50 · cs_aBS89ts7SbcqM7oZVV2n $321 · cs_w5dSBawUW7yVwtrTWsUW $80 · cs_1da8x8iU3zmd6bY8lThA $151.20 (expired, then completed on retry) · cs_2G4sPw1W9GLgBLT_NKYX $69; plus Biopep’s cs_f5kPI4eMiSQd1xpSPnrk $59. The analytics side kept improving: server-side payment_success/payment_failed events (#404) plus privacy hardening and wider outcome coverage (#410), both 7 Sep.
Watch each replay; one line per session — where they stopped (price / trust / card form / error) — as a comment on the day’s QA issue (REV-193 was 2 Sep’s) and in Core Engineering; anything reproducible becomes a qa issue.
Prod DB, merchant mrc_rhnnN_Yat26u (Halo), since 31 Aug: orders RC-2026-1000228, -232, -233, -235, -236, -242 — all $0.50, all AUTHORIZED, all from narbotokerimov@gmail.com (31 Aug 11:32Z → 1 Sep 16:47Z), none refunded at the 2 Sep 13:05Z read; the 7–8 Sep DB reads failed, so a refund since is unverified. Nur’s expired $0.50–$3.00 sessions and Aadil’s $106 one sit on the same merchant. Which store produced them is unverified.
Say what they were; refund the six from admin today; move that test to Narboto inc / getrevion-capsule.com. Also the 1 Sep leftovers: US-7 + US-8 FAIL, three ZZTEST applications still “received” at the last read.
Done since yesterday: nothing verifiable since the 2 Sep board — Linear, the prod DB and TG were unavailable again in today’s collection (last confirmed: REV-193 filed 2 Sep 11:55Z).
The 8 Sep 13:05Z bundle failed with the same signature as 7 Sep: every Slack section “check fly auth”, all six watch-merchant reads empty (“machine/auth?”), Linear, TG and the marks fetch unavailable, and the DB summary step crashed with a raw JSONDecodeError. The marks fetch did advance to day=2026-09-07 — the 7 Sep board published — but its marks were unreadable, so any ticks or comments the team made on it are not reflected here. On 2 Sep the cause looked like launchd PATH (no node/flyctl); two identical failures later the hints point at fly auth / machine reachability as much as PATH.
Run collect.sh by hand: flyctl auth whoami, machine state, PATH export at the top of collect.sh + generate.sh (or plist EnvironmentVariables); then a FORCE=1 re-collect + re-compose, and log an unavailable-sections count per run so a blind bundle is loud, not silent.
Merges into production: #373 (1 Sep), #378 (2 Sep), and the promotion PR from sandbox #402 (6 Sep) carrying the idle-reminder sweep (#376) + review fixes (#403). Prod CD needs the CLAMAV/CDR tokens set 28 Aug; no deploy log in any bundle since. 7 Sep then landed a further batch (#404 · #406 · #407 · #408 · #410 · #412 · #414) whose promotion state is equally unverified — the next rollout check covers both. Last charges known to have served: RHP $598 and Halo $151.20, both 2 Sep — which build served them is unverified, and the 7–8 Sep DB reads failed.
flyctl releases per app + release tag; then the Playwright checkout E2E gate on the live sandbox channel against the redesigned flow (#372/#374 assertions). Never place a payment on sandbox.revioncaps.com — prod keys.
RHP’s first real sale (2 Sep 05:08Z) and Halo’s 2 Sep morning order passed unwatched. Next: Casey’s Biopep retry, Chris (Zen), the Best Peptide embed call, Sean Finck once provisioned — watch-merchant.sh <mrc> during the order, confirm each step, void after. (In practice gated on the collector/fly access fix above — the same tooling came back empty again today.)
File one labelled Charge inquiry via the sandbox public support endpoint and confirm the alert email carries both admin links. (Claude’s live POST was classifier-blocked — needs a human-run curl or Tim’s go.)
The 31 Aug chases drew two replies (Jarrod — tax; Jenifer — thanks); Chris and Best Peptide stayed silent through 2 Sep. With Slack and the DB unreadable again today the sweep has no fresh input — fixing the collector comes first. The idle-reminder email takes over the routine nudge once armed (merged + promoted 6 Sep), and Tim’s admin bulk email (#414) adds a broadcast path.