Handoffs
Pick up where they stopped
Check in a session. A teammate or their agent continues from it, dead ends included.
Knowledge retention
Keep what agents figure out
What's learned in a session stops vanishing when it closes. It builds up instead.
Current facts
Work from what's true now
Decisions are one-line facts. Changed ones are retired, never edited, so agents follow what holds.
See a handoff
Alice hands her work to Bob. Bob picks it up. Click through.
Why did checkout p99 jump after Tuesday's deploy?
Checking the CDN: cache hit ratio flat all window. Not the CDN.
Pool metrics: 10 connections, saturated at peak.
pool_size 40 in config/db.yml brings p99 back in staging.
Still unexplained: why the deploy doubled connection use.
Sessions
No sessions yet.
Alice spends the afternoon on a checkout slowdown. Her agent learns a lot.
/check_in
sac_upload_session("Checkout p99: pool starvation, not the CDN")
Checked in to Checkout latency regression
alice → bob I'm moving to payments. Checkout work is in Rove. Over to you.
Sessions
alice@rovetech.org · Oct 12
Checkout p99: pool starvation, not the CDN
- Found
- A pool of 10 saturates at peak; 40 fixes it in staging.
- Ruled out
- The CDN. Cache hit ratio was flat all window.
- Next step
- Find why Tuesday's deploy doubled connection use.
She's moving on. Her agent checks in what it figured out, and she tells Bob where it is.
Pick up Alice's checkout work.
sac_list_sessions("Checkout latency regression")
Loaded Alice's session from Oct 12
She traced p99 to pool starvation and ruled out the CDN.
Her next step was the deploy's connection use. Starting there.
Sessions
alice@rovetech.org · Oct 12 opened by bob
Checkout p99: pool starvation, not the CDN
- Found
- A pool of 10 saturates at peak; 40 fixes it in staging.
- Ruled out
- The CDN. Cache hit ratio was flat all window.
- Next step
- Find why Tuesday's deploy doubled connection use.
Bob's agent pulls her session and starts from her next step. Nothing is re-tested.
Tuesday's deploy added a retry that opens a second connection per request.
Reusing the connection brings p99 back with the pool at 40.
/check_in
Checked in to Checkout latency regression
Sessions
alice@rovetech.org · Oct 12
Checkout p99: pool starvation, not the CDN
bob@rovetech.org · Oct 13
Traced the doubled connections to the new retry
Bob started where Alice stopped. No meeting, no replay.
Topic, Session, Fact
Topic
The boundary
One problem or project, and everything learned about it. Who sees it is decided here.
Session
What happened
One piece of agent work, compacted. Not the transcript, just what's worth keeping.
Fact
What holds
One sentence the team acts on: a decision, a dead end, an open question.
Sessions are the evidence, Facts are the conclusions, and they are kept apart on purpose: evidence accumulates, conclusions change.
Few Facts, all worth trusting
A record nobody trusts is worse than none, because people still read it. So Facts are added carefully, and only when they earn it.
Less to read, nothing to second-guess: signal, not noise.
Work from what your team has actually established, not from what it half-remembers.
Get preview access
The hosted instance is a private preview, invite-only. Tell us who you are and what you'd like to try, and we'll set you up with a workspace.
Email us
sales@rovetech.org