Learn
Why Ava should prefer connectors before browsers
A connector can express the exact action, resource, identity, and result. A browser can reach almost anything a person can see, but it also inherits ambiguity, UI drift, and more ways to produce an unknown outcome.
Available today: bounded Help-documented integrations—not a general Ava connector platform or cloud browser.
Direction: connector first when adequate, browser when required, and human return at identity, uncertainty, consequence, or missing authority.
The Owner retains authority and supplies applicable credentials or grants; identity, uncertainty, consequence, or missing authority returns the action to a human.
The main point and the boundary
Connectors come first because they make the action, resource, identity, result, and failure state explicit. Browsers remain useful for visual or unsupported workflows, but UI drift and ambiguous confirmations make evidence and recovery more important.
Today, Superboard has only bounded Help-documented integrations—no general Ava connector platform or cloud browser. Do not mistake the policy for current capability. The Direction is exactly three steps: connector first when adequate; browser when required; human return at identity, uncertainty, consequence, or missing authority.
Connectors make the contract explicit
A well-designed connector names the operation and validates its inputs. It can return stable identifiers, structured errors, idempotency evidence, and a bounded resource scope. That makes the action easier to review, retry, attribute, and test.
The connector is not automatically safer: its credential scope and action design still matter. It is simply a stronger starting contract.
Browsers cover the long tail
Many important services expose incomplete APIs, keep consequential controls in the UI, or require a visual check. Browser execution can bridge that gap and can reproduce the workflow a person already understands.
It also faces layout changes, pop-ups, login challenges, stale pages, accidental duplicate submits, and unclear confirmation states. Those risks need evidence and recovery, not confidence alone.
Available today
Available today: no general external agency
Current Superboard has bounded product integrations documented in Help, including the current Google Calendar path. It does not provide a general Ava connector platform or cloud browser that can operate arbitrary services for the Owner.
Product copy must describe only the connections visible in current Help.
What remains with the Owner
Choosing a connector or browser never creates authority. The Owner retains the purpose and real authority, provides any applicable credentials or grants, and makes the consequential call when identity, uncertainty, consequence, or missing authority requires human judgment.
Direction
Direction—not current: connector, browser, human return
Remember these three steps as Direction, not as available Superboard behavior: first, Ava uses a connector when it is adequate; second, she uses a browser when the workflow requires it; third, she returns to a human when identity, uncertainty, consequence, or missing authority creates the boundary.
Both paths report evidence to the same Card rather than creating detached execution histories.