Spor · people and assistants

Teammates and AI assistants, working from the same record

People and assistants can sit in different tools — your editor, your assistant’s chat — but the work memory underneath them is one shared record, not split per tool. Assistants prepare, draft, link, and update the work, and what they touch is recorded as assistant work tied to the person it acts for. You make the calls only a person should make.

Private beta · assistant work stays on the record
what you seea decision to make
decide

Turn on guest checkout for all storefronts?

The assistant built the guest-checkout path and ran it end to end against test orders. Turning it on for every store is the human call. Account checkout keeps working as it does now, and turning guest checkout back off is one switch.

decision · dec-staged-rollout question · question-checkout-without-account
One record

One item, read the way each side needs it

A person and an assistant open the same item and each get the view that fits their job.

When guest checkout is ready to turn on, you see a decision: approve it or hold it. The assistant opens the same item with everything it connects to — the decision behind it, the work that built it, the question that first raised it. It drafts, links, and keeps those connections current. The call stays yours.

  • One item, read two ways
  • A person sees a decision to make
  • The assistant sees what it connects to
what your assistant seesthe same item
itemguest-checkout-go-live kindquestion → decision statuswaiting for a person routed toMaya the decision behind itdec · dec-staged-rollout the work behind ittask · task-guest-path-build first raised inquestion · checkout-without-account undoturn the guest-checkout switch back off
one shared record every action attributed the human calls route back to people
who did whatguest checkout
built the guest pathassistant · on behalf of Maya linked the decisionassistant · on behalf of Maya held while workingkept off other lists approved & went liveMaya · the human call
On the record

Assistant work is labelled as assistant work

Every Spor action is attributed, and an assistant’s share of it reads as the assistant’s — never as the person.

An assistant carries its own identity, owned by a person, so what it does is recorded as the assistant acting for that person — it does not stand in as Maya or sign her name. You can read the guest-checkout path and see which steps were the assistant’s and which were Maya’s call. While anyone, person or assistant, has an item in hand, it’s held for them, so two sessions don’t edit over each other; the hold lifts when the work is done.

  • Assistants act under a person-owned identity
  • Each action reads as the assistant or the person who made it
  • An item is held while it’s in progress
Human calls

The calls that need judgment route back to people

A judgment call reaches a person, ready to decide — not an assistant working on its own.

Routine work an assistant can carry is a task. A call that needs judgment is an open question or a decision waiting for approval, and it routes to the person it belongs to. An assistant running on its own won’t quietly settle that call, even when it’s near the top of the list — it waits. The decision arrives ready, with the evidence already in front of you. For guest checkout, that evidence includes the path the assistant built and tested, and the fact that turning it back off is one switch.

  • Judgment calls route to the person who owns them
  • An assistant on its own won’t settle one
  • The decision arrives ready, evidence in hand
routed for a decisionto a person
decide Turn on guest checkout for all storefronts? now
An assistant running on its own won’t settle this, even when it’s near the top of the list. It waits for the person it’s routed to. routed to · Maya verified · task-guest-path-build
Private beta

Spend judgment where it counts

Human judgment is the scarce thing. Spor routes it to the calls only a person should make and lets assistants carry the legwork, on the record. Request access to put it in front of your team.

Email [email protected] sporhq.io