spor private beta Request access
Spor · context and memory

The work documents itself as it happens

Nobody keeps a wiki that nobody reads. With Spor, the background you need shows up when work starts, and the record gets written when the work is done. Fix the context once and everyone who comes after you inherits the fix.

Private beta · runs alongside the tools your team already uses
across a sessionon its own
01
The briefing arrives A new session opens the task to build the guest checkout path. The briefing is already there, carrying the decisions, rules, and questions that bear on the work.
02
The right context finds you As you build, the standing rule that refunds keep an audit trail comes along, and so does the approach the team already ruled out. No leaving the work to go search.
03
The record writes itself When the work is done, the outcome is written back on its own. Whoever comes next starts from where you left off instead of starting cold.
briefing · build the guest checkout pathcompiled
decision · keep one cart, attach buyer later rule · refunds keep an audit trail question · can shoppers pay without an account?
Kept and linked to its sources, and rebuilt whenever any of them changes. Not throwaway text.
On start

The background shows up with the work

When work starts, Spor puts a short briefing in front of you. You stop hunting for what the team already worked out.

The briefing is drawn from the shared record: the decisions that bear on the work, the rules that apply, and the discussion that came before. It is saved and kept, and it links back to each source, so you can see where every point came from. When something it relied on changes, the briefing is rebuilt.

  • Drawn from decisions, rules, and prior discussion
  • Links back to every source it used
  • Rebuilt when a source it relied on changes
As you work

What’s related comes to you

Related decisions, the approaches the team already ruled out, and the standing rules show up on their own when they matter.

You don’t have to remember to look any of it up. A standing rule is something the team always does, like keeping an audit trail on every refund. It comes along automatically wherever it applies. The same goes for the path the team already tried and set aside, so nobody walks back into it cold.

  • Standing rules follow the work that triggers them
  • Ruled-out approaches surface before you repeat them
  • No looking it up, no remembering to ask
came along with this workno lookup
rule · refunds keep an audit trail decision · keep one cart, attach buyer later ruled out · charge the card first
Each showed up because it applies here, not because someone went looking.
fix the context, onceit sticks
beforeThe earlier briefing buried how saved-card data is handled as a footnote, easy to miss.
the fixIt’s pulled to the front, and every future briefing treats it as a hard requirement, not a nice-to-have.
Fix once

Fix it once, lose nothing

When a briefing steers someone wrong, you don’t reword a one-off prompt. You record a fix that sticks.

Pull the important point to the front, drop the one that doesn’t belong, or add a line of guidance. Every future briefing for that work inherits the fix, and you can trace who made it. When the work is done, the outcome is written back to the record on its own. Jotting down a finding is one quick step, and nothing you write is dropped.

  • A context fix carries into every later briefing
  • Outcomes are written back when work is done
  • Anything that doesn’t fit is kept, not dropped
More of the product

Where the context comes from

The record The connected record underneath Briefings are drawn from the same connected record the work lives in. Decision queue Start each item already briefed Open anything in the queue and its background is already in front of you. People + AI Assistants work from the same context Drafts start from what the team already knows, not a blank page. Integrations Pull the background anywhere Ask for the briefing on a piece of work from whatever tool you’re in.
Private beta

Let the work keep its own record

Spor runs alongside the tools your team already uses, so context shows up on time and the record stays current. Request access to try it on your own work.

sporhq.io · no card, no demo gate