Show me before saving.
Think it through together, then record.
The product · beta
Orient before work.
Capture as you go.
Let your agent check the context, capture the reason and reuse what your team knows—from the tools you already use.
Where it happens
Product Brain
Your usualagent
Product BrainShared decisions · reasons · roles
Read and write through CLI or MCP.Keep working in your connected agent.
Orient before work
Your agent finds
what applies.
What exists, what’s decided, what came before—and who can change it.
Your usual work request
“Can we include this extra workflow in the proposal?”
With the practice configured, your agent reads its role and relevant records. Partial orientation needs further lookups before acting.
Walkthrough · a customer request
An extra request. An existing agreement.
Current · accepted decision
Keep the pilot within the agreed scope.
Why · Deliver the first result before adding custom work.
Who can change it · Product Lead
DirectionProve value before adding complexity.
WorkPrepare a customer proposal.
What exists? What came before?
Already there · The current offer and pilot plan.
Earlier choice · A broader pilot. Its reason—exploring more possibilities—stays in history after the team narrows the scope.
Work & capture
Your agent keeps
the reason.
A new choice emerges during work. Your agent records its reason, scope and owning role.
As you work together
“Let’s test the extra workflow with one customer before offering it more widely.”
Your agent can capture and accept in its acting role. You remain accountable. Accepted isn’t delivered.
Walkthrough · a new choice during work
One customer. One scoped experiment.
01 · DraftRecord the choice.
Why: learn what it takes before adding it to the offer.
02 · AcceptedEstablish the agreement.
Product Lead—or their agent in that role—accepts.
03 · Work doneRecord delivery.
The experiment runs. Record what happened.
What must be in place to accept?
The agent’s session must act in the role that can decide. Holding another role does not add its authority to this session. Required fields and applicable direction links, limits and verification requirements must also be met.
Agents can accept any entry kind within those requirements. Acceptance is recorded for the person they act for. The person remains accountable and can confirm it themselves.
Your working preference
Choose how your agent captures.
Set this in its working instructions.
Both follow your team’s rules and role authority. You remain accountable.
Give your agent the working instructions →Reuse together
The next person
starts with the why.
Sales asks their agent to prepare the next proposal. It can consult the same decision and reason—even while the author is away.
Original context holder
Product Lead
Away from the workAccepted decisionOne customer.
One customer.
One scoped experiment.
Reason · Learn what it takes before adding it to the offer.
Owning role + reasons + historySales + agentSet expectations from the agreed offer
Delivery + agentPlan the agreed scope
Marketing + agentDescribe the actual offer
CaptureConnectReviewReuseRefine
Knowledge compounds when your team captures, maintains and reuses it. That’s our thesis.
Learn & refine
New learning.
Your agent brings it back.
New learning prompts review. The agreement stands until its owning role changes it.
Through your agent
“Customers want this workflow. Delivery needs more time. Let’s revisit the offer.”
Possible contradiction flags prompt review. The owning role—or its agent in that role—decides what changes.
01 · Current agreement
One customer. One scoped experiment.
Why · Learn before adding it to the offer.
02 · New learning
Useful for customers. More work to deliver.
Candidate: an optional add-on. Not yet accepted.
03 · Review
Does the add-on fit our direction and capacity?
Check the learning against the current agreement.
04 · If the owner agrees
Optional add-on. Separately scoped.
The owner records why. Earlier versions stay in history.
Across the team
Keep using
the agent you know.
Connect a supported CLI/MCP agent and teach it your practice. Day-to-day lookups, capture and authorised acceptance can stay there.
Claude
web + desktop
Hosted MCP connector. Look up your workspace’s decisions, reasons and related work.
Claude connection guide ↗Connector · betaChatGPT
Custom MCP connectors on supported plans. Check your plan and rollout.
Check the ChatGPT guide ↗Conditional connection · betaCoding agents
Claude Code: opening briefing. Cursor and Codex: CLI or MCP lookup. Copilot: instruction files.
Choose your agent guide ↗Claude Code · Cursor · Codex · Copilot · betaTeach your agent to consult the record as it works. Changes aren’t pushed to every active session.
Build on what
your team already knows.
Give your connected agent a real task. Let the next person build on the recorded reason.