Spor · context and memory

The work keeps its context

Nobody keeps a wiki that nobody reads. Spor brings the relevant decisions, rules, prior attempts, and open questions to a piece of work when it starts, and the useful outcome is written back when the work is done. When the context is wrong, you fix it once in the record, and every briefing after you inherits the fix.

Private beta · runs alongside the tools your team already uses

across a sessionon its own

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.

The relevant context comes to 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.

The outcome is written back When the work is done, the useful outcome is kept in the record. Whoever picks it up 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?

Saved, linked to its sources, and rebuilt when any of them changes. Not a prompt you retype each session.

On start

The relevant background arrives 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.

A briefing is not disposable prompt text. It is saved, it links back to each source it drew on, and when a source it relied on changes, it is rebuilt. The decisions that bear on the work, the rules that apply, and the discussion that came before all sit in one place, so you can see where every point came from.

Relevant is not always similar. The rule that matters here may not use the same words as the task, and the current answer may be a decision that replaced an older one. Spor brings what actually applies, not just what reads alike.

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 arrive when they bear on what you’re doing.

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 wherever it applies. So does the path the team already tried and set aside, so nobody walks back into it cold. What arrives is what’s relevant, even when it doesn’t use the same words as the task in front of you.

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 fixRecorded once: it’s pulled to the front, and every later briefing treats it as a hard requirement, not a nice-to-have.

Fix once

Fix it once in the record

When a briefing steers someone wrong, you don’t reword a one-off prompt that helps you and no one else. You fix the context once in the record, and the fix sticks.

Pull the point that matters to the front, drop the one that doesn’t belong, or add a line of guidance. Every later briefing for that work inherits the fix, and you can trace who made it and when. The next person and the next assistant start from the corrected context, not from the mistake.

The same holds when the work is done: the useful outcome is kept in the record. Writing down a finding is one quick step, and nothing you record is dropped.

A context fix carries into every later briefing
Outcomes are kept in the record 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 context

Spor runs alongside the tools your team already uses, so the relevant context arrives when work starts and the record stays current as it changes. Request access to try it on your own work.

Email [email protected] sporhq.io