One brain.
Every department.

Ad click to cash in hand, as one picture. Every order in the window lands at exactly one terminal — a leak, still-moving, or cash collected. The nodes must reconcile, or the graph is lying about where the money went. This is the literal picture of the "one brain" claim.

COD-true profit: delivered/settled revenue, COGS, courier fees, packaging, spend, contribution — in cohort and cash lenses. Money motion shows what's spent, in-field, and banked.

Courier remittances reconciled parcel by parcel. A gap under ₨50 is treated as rounding; a parcel isn't counted as missing money until 21 days have passed — the numbers of people who have actually chased a courier for money. PK-only, because CityMail doesn't report settlement.

Supplier payables with a COD-backed payment waterfall — committed vs expected. Hash-chained ledger events; a vendor never sees your total COD.

Kill/scale evidence across platforms and windows, with Ad Pilot inside it — verdicts, contracts, grading. Deeplinks take you to the exact ad; the click stays human.

Meta Ad Library diffs, swept hourly: who's new, who closed, who revived, and who's survived 30+ days — the survivors board is a cheat sheet for what works in your market.

First-party storefront analytics: pageview → cart → checkout → purchase journeys, goals and drop-offs, joined to courier-collected cash. Bounce isn't one pageview — engagers don't count.

Product, geography, discount, bundle and landing-page intelligence from Shopify analytics — which pages and provinces actually convert.

Every hook, script and storyboard must cite a winning pattern from your own account (Winning DNA, mined from 90 days of results) or the Brand Codex — or it doesn't ship.

Takes your best-performing ad and watches it frame by frame and listens to it — audio transcribed, every frame inventoried (people, props, product timing, lighting, on-screen text) — then writes the next script from what actually made it work, scored on scroll-stop, founder-trust, offer clarity and replicability.

Judge the ad before you pay Meta to judge it: keyframes plus the transcribed spoken script are read against your account's real Winning DNA → GO / FIX / HOLD with a predicted CAC band and a stated confidence. A hedge, honestly labeled — not an oracle.

WhatsApp voice notes (Urdu + English) are transcribed and mined nightly; a customer's exact sentence can become your next ad's opening line — with the verbatim receipt attached. Every quote is re-verified as a literal substring of the real message; paraphrases are dropped and the rejected count is logged, never hidden.

Numbered pins drawn on a screenshot of your own product page; a competitor's tactics converted into ready-to-run instructions for yours. It fetches your live theme's real Liquid before writing, lints the output, and copies the tactic — never their words or images. Staging theme → your approval queue.

Three couriers' "awaiting shipper advice" queues — PostEx, Leopards, TCS — merged into one desk, synced every 15 minutes: ~48 hours to save a doorstep refusal. Six reason buckets matched against free text and courier attempt codes. TCS is the only one that can structurally carry a revised address and phone; the other two carry it in remarks.

A ladder ordered by what each rung costs: refund + return ≈ ₨2,200 and you lose the customer; partial refund, keep the bottle ≈ ₨740; replacement, keep the bottle ≈ ₨790 and you keep 100% of revenue. Refund comes LAST, and rung four stays invisible until the first three are declined. The 40% / 110% figures are defaults you set — and every resolution needs a second person, with no refund markable "sent" until a human names the account it leaves from.

Book → print CN → scan-to-pack → handover → picked up: the five-stage physical pipeline the packers actually work in, with barcode scan-to-pack, audio cues and bulk label PDFs. Real consignments booked through four courier APIs — PostEx, Leopards, TCS, CityMail — with load sheets, because a courier once said "never received" about parcels that were handed over.

Stock ledger for the PK warehouse, title-mapped 3PL reconciliation for the UAE. Deducts at pack, restocks at return — and never sums across currencies.

Return rates by courier, city and reason — so "your Hyderabad orders return 41% of the time" changes how those orders get confirmed. And the bucket nobody else counts: 533 of 701 Leopards parcels and 164 of 205 PostEx parcels were never collected at all — the courier accepted the booking and never came. Chase the pickup, not the customer.

Marketplace and D2C in one warehouse queue: Daraz orders poll into the same OMS mirror at ready_to_dispatch, drawing down the same inventory ledger — packaging included. Polling is the design, not a fallback: Daraz demands an enterprise certificate and a 200 ACK inside 500ms. Live when Daraz approves.

The Karachi outlets' till: loyalty points, WhatsApp receipts, footfall counting, cross-sell mining. Fiscalization-ready — three backends built, PRAL integration pending. Same stock ledger as online — one inventory truth.

Confirms per agent — and the delivered% of what they confirmed. Praise and blame finally land on the right desks.

The content pipeline: six stages — brief → script → film/shoot → edit → review → approved — a designer's queue, calendar and board, due reminders every 15 minutes so nothing dies in a draft. Meta publishing live; TikTok next.

The internal team OS: spaces, projects, tasks, threads, voice notes, calendars with capacity — and an anonymous "Speak Freely" channel, because truth needs a safe door too.

Every source carries a headline rupee figure for revenue generated and a separate courier-verified subset that grows as parcels land — we publish both, never one without the other, and the verified part is a subset of the headline rather than a second total. Beside it, the radar: a deterministic scan (rules only, no LLM) of exactly where the business is bleeding, ranked by rupee impact — each leak naming the module that fixes it.

The system audits itself: a read-only sweep hunting for lies in the order estate — currency leaks, dead parcels, mirror gaps, unfulfilled-but-shipped. It can reconstruct any past day from the event log and re-run the identical checks — the 13–15 July incident stays a regression test long after the parcels were healed.

Plans and entitlements, per-client databases, build-time isolation rails that hard-fail a deploy on any cross-tenant leak. One deployment, built so every future tenant is walled off — a rail we run against ourselves today across our own two brands.

Your numbers in a browser toolbar, alerts included. And a token-guarded API doorway so your own agents and tools can query the business with 21 tools — the same 16 the dashboard uses, plus 5 only MCP has. It cannot write. Not by policy — by privilege: every query runs inside a read-only Postgres transaction.