> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Join hardening behind a production A/B gate

> Improve meeting-join reliability behind a production A/B gate, so every change is measured against the current path before it merges.

**Is Vexa's meeting-join reliability measured before a change ships?**

**Today:** Not systematically. Join failures are handled case by case, without a standing production measurement gate.

**Sponsorable:** yes — The gate, and the hardening work measured through it.

***

*Make joining more reliable, and prove it before it ships.*

|                 |                                              |
| --------------- | -------------------------------------------- |
| **Status**      | **sponsorable**                              |
| **Size**        | M                                            |
| **North star**  | 2 · Dependable capture                       |
| **Measured by** | served-transcript share and named-word share |

## What it does

* Hardens the join path against the conditions that block a bot.
* Runs behind a production A/B gate.
* A change merges on measured improvement, not on a plausible story.

## What exists today

Join failures are handled case by case, without a standing measurement gate.

## What this adds

The gate, and the hardening work measured through it.

## How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so "done" means done on your meetings. Your name goes on the release note. Sponsorship buys **the order of the queue** — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

## Two doors

<Columns cols={2}>
  <Card title="Sponsor this" icon="handshake" color="#0D9373" href="https://cal.com/dmitrygrankin/web?utm_source=docs&utm_medium=roadmap&utm_campaign=sponsor&utm_content=join-hardening" horizontal arrow cta="Book fifteen minutes">
    Fifteen minutes. Bring the constraint you are under.
  </Card>

  <Card title="Watch this" icon="envelope" color="#0D9373" href="mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Join%20hardening%20behind%20a%20production%20A/B%20gate&body=watch" horizontal arrow cta="Email me">
    One email when it ships. The mail is already written — send it as it is.
  </Card>
</Columns>

## Questions

<AccordionGroup>
  <Accordion title="Is Vexa's meeting-join reliability measured before a change ships?">
    Not systematically. Join failures are handled case by case, without a standing production measurement gate.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    The gate, and the hardening work measured through it.
  </Accordion>

  <Accordion title="What happens when it ships?">
    It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*