Owner Agent Design POV

OneAgent

One presence. Every surface. Always in context. This is the design team's point of view on what Owner Agent is, how it should behave, and why.

Derek Orr · April 2026

Design

Eight principles

Owner Agent is designed against the failure modes of AI products. Each principle exists because a team somewhere shipped the opposite and paid for it.

01
Outcomes, not operations
Show what changed, not what ran. Never expose function names or parameter JSON in the conversation.
update_menu({"id":42,"active":true})
Menu updated — 12 items active
02
Trust scales with stakes
Low-impact changes confirm after the fact. Only irreversible actions need pre-approval. Never block the user unnecessarily.
Auto Review Block
03
Thinking is ambient
One state indicator. No step-by-step transcript. The agent should radiate confidence, not narrate its reasoning.
✕
04
Context is visible, never announced
The agent knows where it is and acts accordingly. It never says “I can see you're on the menu page.”
Hestia → Menu → Pizza
In context
05
One voice, everywhere
Same name, same mark, same tone across Vesta, Owner App, and Hestia. The agent doesn't introduce itself differently on each surface.
06
Conversation is the canvas
No artifact cards in the thread. If something changed, the product reflects it. The chat remains clean.
artifact card
Product updated
07
Chips before questions
Offer suggestions as chips, not open-ended questions. Never block input to ask for clarification the user didn't want to give.
What would you like to update?
Hours
Menu
Photos
08
Failure is honest
One sentence. What it can't do and why. No hedging, no apology, no suggestion to contact support.
Can't edit that — requires admin access.
✕

Design

The mark

The Owner mark has five states. Each signals a distinct mode of presence — not just what the agent looks like, but what it's doing right now.

Resting
Available, ambient. Not actively processing. A slow breath.
Listening
Input is open. The agent is attending. Rings expand outward.
Thinking
Processing. A single dot orbits — not a spinner, not a transcript.
Working
Executing a task. The beam signals active agency, not passive waiting.
Completed
Task done. A brief affirmation, then back to resting.

Design

Five surfaces

Owner Agent lives at five levels of presence. The surface is chosen by context, not by the user — the agent decides the appropriate footprint.

01
FAB + chips
Collapsed. Always accessible. The minimum footprint — a floating button with contextual chip suggestions.
Update hours
View reports
Add item
02
Docked panel
Focused. Sidebar presence. The user is actively working with the agent alongside the main product UI.
03
Floating
Centered dialog. Task-focused but non-blocking. Appears over content without replacing it.
04
Contextual inline
Embedded within the product. Agent output appears in-place, within the context it relates to.
05
Full overlay
Immersive. Deep task mode. The entire surface belongs to the agent for complex, multi-step work. Entry is intentional; exit is always easy.

Design

Anatomy

Every Owner Agent surface shares the same component model. The wireframe below is the canonical reference.

Owner Agent
Message area
Your menu hasn't been updated in 3 months. Want me to refresh it?
Yes — do it
Tool call
Update menu · Approve?
Chips
Approve See changes Not now
Ask anything…
Owner Agent can make mistakes. Review before approving.
Header
Context title + minimize and close controls. No Owner mark icon — the brand presence is ambient, not repeated in the chrome.
Messages
Agent text is plain prose, flush left. User messages are dark pills. No avatar, no timestamp, no status indicator.
Tool calls
The trust contract made visible. Propose → Approve → Undo. Never auto-execute irreversible actions. The BorderBeam on this card signals active state.
Chips
Contextual, not generic. “Approve / See changes / Not now” is better than “Yes / No / Cancel”. Scroll horizontal when they overflow.
Composer
Ask anything. Mic and send only. No attachments, no formatting, no slash commands visible by default.
Disclaimer
One sentence. Present on every surface. Non-negotiable — it's the honesty principle applied at the system level.

Context

Three stories

These are the scenarios that test whether the principles hold. Real operators, real situations, real stakes.

Onboarding

First Day

Paula from Tons of Ribs BBQ just signed up via grader.owner.com. Owner Agent surfaces three improvements proactively. She approves. Her site updates. She never opened the editor.

~3 hours recovered on day one
Operations

Mid-Rush

Saturday 7:42 PM. Kitchen is 8 tickets behind. “Pause online orders” — one message. Agent confirms. Operator breathes. No dashboard, no settings menu, no delay.

12-step flow collapsed to 1
Support

Self-Serve

A customer calls about hours. Owner Agent answers from Help Center context. CS never picked up the phone. Resolution time: 4 seconds.

4-second resolution, zero CS touches

Context

The ecosystem

Owner Agent is not a feature. It's the connective tissue across four distinct surfaces, each with different constraints and different operators.

Vesta
POS · kitchen-facing
Owner App
Mobile · operator
Hestia
Web dashboard
Owner Agent
Universal presence
Vesta
POS surface. Minimal footprint. Keyboard-first. The agent avoids visual noise on a screen that's under pressure.
Owner App
Mobile presence. Gesture-aware FAB. Works on-the-go, in the walk-in, mid-service.
Hestia
Full desktop experience. Docked panel. Deep task mode. Where the serious configuration work happens.
Owner Agent
Not a feature of each surface. The same presence across all of them. One name, one mark, one voice.

Context

Where we are

Owner Agent is not a side project. It is the product strategy. Every surface we build from here should be designed with the assumption that an agent will operate on it — reading context, proposing actions, executing with approval.

The principles in this document are intentionally ahead of where the product is today. That gap is the work. The goal of this POV is to close it with intention, not by accident.

Q2 is the foundation quarter. We are establishing the component model, the trust contract, and the first production surface. Everything else builds on top.

Milestone Description Surface Status
Component model Canonical wireframe + token set agreed and documented All In progress
FAB + chips v1 Collapsed presence with contextual chip suggestions Hestia In progress
Tool call UI Propose → Approve → Undo pattern, first irreversible action Hestia Planned
Docked panel Sidebar mode for focused operator sessions Hestia Planned
Mobile presence Owner App FAB + chips, gesture-aware Owner App Exploratory
POS integration Vesta surface — minimal, keyboard-first Vesta Exploratory

Owner Agent — Design POV

Derek Orr · April 2026