# ROQIVA — the in-brand revenue system by MESHHETU Source: https://meshhetu.com/roqiva Last updated: 2026-10-17 ROQIVA Product preview · In development ⌘K Main menu - Overview - Workspace - Parts - Work item - Principle - Your stack - Ways in - Working rules Pinned - WWI-014 · Failed payments - GGate 1 · Brand PM - CC1 · Governed build Track C In development Explore the architecture while the product is being developed. [Talk to us](https://meshhetu.com/contact#brief) ROQIVA / Overview In development [Talk to us](https://meshhetu.com/contact#brief) OverviewWorkspacePartsWork itemPrincipleYour stackWays inWorking rules Track C · In development ROQIVA · Revenue Operations, Quality, Intelligence & Value Architecture # One intelligence layer across your revenue stack. ROQIVA is an integrated revenue orchestration product in development, designed to work within your existing client-controlled architecture alongside CRM, analytics, payments and operations tools. It connects signals, governed agent workflows and decisions in one system. [Discuss ROQIVA’s roadmap](https://meshhetu.com/contact#brief) [Explore services available now](https://meshhetu.com/services) - Designed for your architecture - Governed access and approvals - In development Planned architecture · by design 6 Agents Each drafts one artifact 4 Human gates Plus one outcome review 1 Brain per brand Versioned, decides nothing 0 Writes to your tools Read-only by design Parts - B Brain Store - D Detectors and Analyst Code and one agent - O Orchestrator Code - D Drafting agents Agents - M Monitor Code Open the parts Gates on every work item Gate After Who decides What they do Gate 1 Audit Brand PM confirms the problem is real and worth fixing Gate 2 Decide PM and leads pick the solution Gate 3 Build PM, designer and engineer approve the pack Gate 4 Release Brand approver signs one exact release candidate, and the brand ships Review Measure PM and analytics owner review the verdict Gates 2 and 3 may merge for a small change. Gates 1 and 4 are never skipped. The workspace ## Explore one proposed workspace for signals, decisions and gates. An interactive concept walkthrough using sample data. Navigate signals, findings, the Brain log and agent views to explore how ROQIVA is designed to work. New work item Work item WI-014 Signals 4 gaps Findings 6 Brain log 6 Agents 6 Pinned WI-014 · Failed payments get one retry Gates 4 gates · 1 outcome review PM Your PM WI-014 / Failed payments get one retry Audit last quarter’s exports. What do we capture that no decision reads? Code matched 6 signals to the decisions that read them. 4 have no decision that reads them. F-001 ranks first: Payments → CRM retry rule. Read Payments export, CRM retry-rule configuration Ranked 6 findings by value × confidence ÷ effort Waiting for Gate 1 · Brand PM Describe a revenue problem or ask the Brain Read-only Analyst Gate 1 Inside ROQIVA ## Explore the parts inside the proposed system. Brain, Detectors/Analyst, Orchestrator, drafting agents and Monitor are software capabilities. People approve decisions; your existing commercial tools remain external. Pick a part to explore. Brain 01 - Gate 3 Sent back one step - Gate 3 Approved the pack Store Brain One versioned model of the brand: tools, rules, design system, decisions, outcomes. Holds context and decides nothing. Detectors and Analyst 02 Code and one agent Detectors and Analyst Detectors match every captured signal to the decision that reads it. The Analyst judges, labels and ranks what they find. Orchestrator 03 - 2 - 3 - 4 Code Orchestrator Opens work items, runs agents in parallel, stops at gates and blocks two items touching the same page, event or segment. Drafting agents 04 Writes to the workspace only Agents Drafting agents Research, Architect, Product, Design and QA each draft one artifact. Monitor 05 Code Monitor Checks releases against their spec, catches unplanned changes and measures results against a baseline. People 06 Gate 1 · Brand PM Confirm the problem is real Approved Humans People Four gates and one outcome review, each with a named approver. Brand tools and engineers 07 External Brand tools and engineers The source of truth. Engineers build and deploy. The system never writes to them. One work item ## Follow the designed workflow from signal to result. Any gate can send the item back one step, with a reason the Brain keeps. Gates 2 and 3 may merge for a small change. Gates 1 and 4 are never skipped. Step 01 · Detectors ### Catch the data no decision reads. Detectors match every captured signal to the decision that reads it and flag the gaps. Code does the matching. No agent is involved, and no one needs to approve a log entry. No gate. The signal is logged. WI-014 Detectors Signals Detectors Code. No agent. Your PM Audit last quarter’s exports. What do we capture that no decision reads? Detectors - Read Payments export - Read CRM retry-rule configuration - Match 6 signals to decisions Code matched every signal to the decision that reads it. No agent is involved. Ask the Analyst Analyst Detectors log Scanning 4 gaps Detectors · Pack 1 · run on exports Code - payments.failure_code PaymentsCRM retry rule Gap - orders.status OrdersCustomer messages Read - search.zero_result_term Search logRange planning Gap - customer.id AppCRM audiences Read - storefront.notify_me StorefrontRestock messages Gap - orders.courier_delay OrdersCustomer messages Gap 4 of 6 signals have no decision that reads them. Code matched every signal to the decision that reads it. No agent is involved. No gate Code matched every signal. No one needs to approve a log entry. Not needed Logged Step 02 · Analyst ### Rank the gaps by what they cost. The Analyst reads the flagged gap, writes what should happen and what does happen, checks the evidence, labels it Confirmed, Supported or Hypothesis, sizes the value as a range and ranks it. Gate 1 opens the work item. Gate 1 · Brand PM confirms the problem is real and worth fixing WI-014 Analyst Findings inbox Analyst Audits the exports Your PM Rank the gaps the Detectors flagged. Analyst - Check Evidence for each gap - Rank Value × confidence ÷ effort Ranked the findings. F-001 comes first. Evidence is labelled, and nothing here is a measured result. Your PM Approve F-001. Open the work item. Ask the Analyst Analyst Findings inbox Ranking 6 ranked - F-001 Failed payments get one retry Payments → CRM retry rule Incident Supported 9 - F-002 Zero-result searches never reviewed Search log → range planning Opportunity Supported 3 - F-004 Courier delay events unused Orders → customer messages Incident Confirmed 3 - F-003 Notify-me sign-ups never read Storefront → restock messages Opportunity Hypothesis 2 - F-006 City stock shown as one national total Inventory → product page Incident Supported 1.5 - F-005 COD rule with no refusal history Orders → COD eligibility Opportunity Supported 1 Score = value × confidence ÷ effort. Sample values, not measurements. Gate 1 Brand PM confirms the problem is real and worth fixing. Approve Waiting Approved Step 03 · Research, Architect, Product ### Draft three solutions, then pick one. Research brings outside evidence. Architect checks what can be reused and what could clash. Product drafts two or three solutions with trade-offs, including the cheapest one. They run in parallel, and people choose. Gate 2 · PM and leads pick the solution WI-014 Product agent Solutions Product agent Drafts the solutions Your PM Draft solutions for F-001. Include the cheapest. Product agent - Research Outside evidence - Architect What to reuse, what could clash - Product Draft two or three solutions Product agent Three solutions with trade-offs. The cheapest is first. People choose at Gate 2. Your PM Go with the first one. Ask the Product agent Product agent Solutions for WI-014 Drafting 3 solutions A Configure Cheapest #### Branch the existing retry rule on failure type + Reuses the rule and the captured failure codes. − Only as good as the codes the gateway sends. B Build #### Build a dedicated retry service + Full control over timing and channels. − The longest path to ship. C Run manually #### Have ops reprocess failed payments daily + No engineering needed. − Does not scale past a few cases. Evidence: Supported. People choose at Gate 2. Gate 2 PM and leads pick the solution. Pick A Waiting Picked A Step 04 · Product, Design, Architect, QA ### Hand your engineers a pack ready to build. Product writes the requirements and the PRD draft. Design turns them into a reviewable prototype. Architect draws the system design. QA drafts the checks. Gate 3 releases the handoff pack: PRD, wireframe, tickets, test checklist and sources. Gate 3 · PM, designer and engineer approve the pack WI-014 Product agent PRD.md Product agent Drafts from the Brain Your PM Turn the Gate 2 decision into a spec our engineers can build. Product agent - Read Finding F-001 - Read Gate 2 decision - Read Order events - Write PRD.md Product agent Wrote PRD v1: four requirements, three events and three acceptance checks. It is a draft until Gate 3. Finding F-001 Gate 2 decision Your PM R2 Why never retry a hard decline? Product agent - Read Payments export - Read CRM retry rule A hard decline is a final refusal from the bank, so a retry rarely changes the result and can look like a second charge attempt. This rests on the failure codes in the export, not on a measured retry result. Supported Payments export CRM retry rule Unseen Card-network decline reasons were not in the export. Your PM Comment on R3 Bank-side failures have no error state. Add one. Product agent - Read Comment on R3 - Edit R3 and the Error state Added bank-side failures to R3 and to the Error state in the wireframe. Linked to the Gate 2 decision. Ask the Product agent Product agent PRD.md Empty Writing Draft v1 Revising Draft v2 ### Retry failed payments by failure type Owner · Your PM WI-014 Gate 3 #### 01Problem The CRM retry rule treats hard, transient and bank-side failures the same. Gateway failure codes are captured and never read. #### 02Goal Retry each failure type the way it should be retried, and leave unrecoverable failures alone. #### 03Requirements - R1 Capture the failure class on every failed payment attempt. - R2 Retry transient failures once, after a short delay. Never retry a hard decline. - R3 Show an error state with a next action for hard and transient failures. Show an error state with a next action for hard, transient and bank-side failures. Changed Your PM Comment Resolved Bank-side failures have no error state. Add one. Comment - R4 Send retry_attempted and retry_result with the failure class. #### 04Metrics North star Orders recovered from failed payments Input Retry success by failure type Guardrail Duplicate charges, complaint rate #### 05Tracking - retry_attempted A retry starts - retry_result A retry ends - failure_class On the order event #### 06Acceptance - Tracked events fire on retry - The failure path completes - The screen matches the wireframe #### 07Open questions Open Card-network decline reasons were not in the export. Who owns them? Gate 3 PM, designer and engineer review the pack. Not sent Waiting for review Step 05 · Brand engineers, QA ### Sign one exact release before it ships. The brand’s engineers build and deploy. The system never writes to their tools. QA reports passed, failed and not tested. The measurement plan is agreed before release. Gate 4 · Brand approver signs one exact release candidate, and the brand ships WI-014 QA agent RC-1 QA agent Checks the build Your PM Run the checks on RC-1. QA agent - Run Checks from the pack - Write QA report QA agent One check failed, and a failure blocks release. Two were not tested, and they are not reported as passed. Brand engineer Fixed the error screen. Please re-check it. QA agent - Re-run Screen matches the wireframe Passed. The two untested checks still need a person or test access. Ask the QA agent QA agent QA report · RC-1 Running Blocked Checked 2 passed · 1 failed · 2 not tested 3 passed · 0 failed · 2 not tested Release blocked Ready to sign - Tracked events fire on retry Passed - Failure path completes Passed - Screen matches the wireframe Failed Passed - Live gateway behaviour No test access Not tested - Tone of the error copy Needs a person Not tested Rollback rule agreed before release: pause the branch if duplicate charges appear. A failure blocks release. Not tested is never reported as passed. Gate 4 Brand approver signs one exact release candidate. Sign RC-1 Waiting Signed Step 06 · Monitor ### Judge the result against a frozen baseline. The Monitor checks the release against its spec, catches unplanned changes and measures the result against a baseline. The verdict and the reason go back to the Brain. Outcome review · PM and analytics owner WI-014 Monitor Outcome Monitor Code. No agent. Monitor - Check Release matches the approved spec - Check Unplanned changes - Compare Result against the frozen baseline Monitor The result holds against the baseline, so the verdict is Keep. The verdict and its reason go to the Brain. Monitor · WI-014 Measuring Verdict · Keep - Release matches the approved spec Code - Unplanned changes Code - Result against the frozen baseline Code Baseline, frozen Result Shape only. No values: an illustration of baseline against result, not a measurement. Keep The result holds against the baseline. Tune It helps, but a threshold or a rule needs adjusting. Roll back It hurt a guardrail or changed something unplanned. The verdict and its reason go back to the Brain. An inconclusive result is reported as inconclusive. Outcome review PM and analytics owner review the verdict. Not sent Waiting for review The principle ## Split every decision three ways. Code counts. An agent drafts. A named person decides anything that changes the business. code Code computes. agent Agents draft. person People decide. Your accounts ## Keep the whole system inside your own stack. ROQIVA is being designed for deployment within approved client infrastructure, with controlled access to existing commercial tools. Final data flows, integration boundaries and operating responsibilities depend on the chosen architecture. Outside your cloud MESHHETU - Designs the system - Configures it - Governs releases Inside your cloud ROQIVA - Brain - Analyst - Monitor - Six agents - Work items and gates - Workspace Proposed governed, read-only inputs - CRM - Payments - Analytics - Operations Stays yours - Your data Never leaves your accounts - Your model access Your provider, your account - Your teams Operate it day to day - 01 ### Keep data and prompts in your accounts. Data and prompts stay in the brand’s accounts, so residency and inference consent are the brand’s own decisions. - 02 ### Pin every release yourself. The brand pins releases. An upgrade passes the eval gate before the brand takes it. - 03 ### Run first-line support in-house. The brand’s team is first-line support and MESHHETU is second line. - 04 ### Replace hosted terms with your own review. The brand’s security review replaces the hosted data terms. Two ways to get there ## Explore prospective deployment approaches. These are prospective integration and deployment approaches, not production-ready options. Final scope is subject to product development and security review. C1 In development ### Blueprint and governed build A proposed custom implementation following an agreed blueprint and client engineering plan Who builds To be agreed in a future implementation scope Needs from the brand An engineering owner and architectural review Ready In development C2 Planned ### Packaged deployment A planned packaged ROQIVA deployment inside approved client infrastructure Who builds To be agreed after product readiness and security review Needs from the brand Infrastructure, identity, security and integration approvals Ready Planned; not production-ready What holds, always ## Hold ROQIVA to five working rules. 01 ### The founders do not write production code for the brand. 02 ### The acceptance tests are the contract. A slice is done when it passes them. 03 ### No brand data leaves the brand’s accounts. 04 ### The brand pins every release. Skills and prompts change only through the eval gate. 05 ### Brain first: no later slice starts before the Brain slice is accepted. ROQIVA ## Explore what ROQIVA could unlock for your stack. Discuss the product roadmap and how a future ROQIVA deployment might fit your architecture. Strategic consulting and modular intelligence are available from MESHHETU today. [Book a working session](https://meshhetu.com/contact#book) [See services available now](https://meshhetu.com/services)