Spor · the connected record

Trace any decision back to where it began

Spor keeps a single connected record of everything your team works on. Each decision, task, and open question is its own small record, linked to what it came from. So you can follow any finished piece of work backward and see exactly why it was done that way.

Private beta · works with the AI tools you already use
the trail behind · guest checkout 5 steps
Guest checkout is live shipped · guest-checkout-live
the work behind it
Build the guest checkout path task · task-guest-path-build
the decision behind it
Roll guest checkout out to staff stores first decision · dec-staged-rollout
you are here
which built on
Keep one cart, attach the buyer later decision · dec-cart-then-identify
first raised in
Can shoppers pay without an account? question · question-checkout-without-account
One record each

One clear record for each thing

Every decision, task, and open question is its own small record with a summary that stands on its own.

A teammate asks “Can shoppers pay without an account?” That question becomes one record. The decision to keep one cart and attach the buyer later becomes another. The task to build the guest checkout path becomes a third. Each one reads clearly on its own, so you understand it without opening five other things first.

  • A question, kept as one record
  • A decision, with its summary in a line
  • A task, separate from the talk around it
the kinds it keeps6 of them
decisionWhat the team chose, and why
taskA piece of work to do
questionSomething still open
ruleA standing rule the team holds
noteA document or written record
personA teammate or AI assistant
how records connectin plain words
depends onThis needs that finished first
closesThis settles an open question
replacesThis took the place of that
came fromThis was first raised there
Stays connected

Everything stays connected

Records link to what they came from and what depends on them.

The task to build guest checkout points back to the decision that shaped it. That decision points back to the earlier one to keep one cart and attach the buyer later. That one points back to the question a teammate first raised. From a finished feature, you can walk the whole trail back to the start without asking anyone.

  • Each record names the work behind it
  • Follow the trail back, step by step
  • No “why did we do it this way?” shrug
Nothing lost

Nothing gets lost

The record sits beside the work and keeps its whole history.

An attempt the team abandoned stays in the record with the reason it was dropped. An idea considered and rejected stays too, with why. So the team stops re-arguing calls it already settled, and whoever picks it up next, person or AI session, doesn’t repeat a dead end. The answer is attached to the work, not lost in a thread someone has to dig up.

  • Abandoned attempts stay, with the reason
  • Rejected ideas stay, with why
  • Settled calls don’t get re-argued
kept, with the reasonnot deleted
rejected Charge the card before building the cart kept because Shoppers abandoned when asked to pay first. Kept so the call isn’t quietly reopened.
replaced A guest-checkout switch for every store replaced bydec-staged-rollout
Private beta

Keep the trail behind your work

When the answer is attached to the work, your team stops losing what it figures out. Request access to start your team’s connected record.

sporhq.io · no card, no demo gate