One shared
record.

Connection is the second root.

A seat without a record still leaves the reason in a chat. The next agent starts without it.

The useful record is small. It names what was chosen, why, and which seat owns it.

A shared record is how the work remembers.

Three parts stay together.

1. The choiceKeep one live report.

   No separate PDF.

2. The reasonThe figures change every day.

   Another export is another version to maintain.

3. The ownerAsk the Product Lead.

   The seat owns the decision. A named person answers.

A hypothetical teaching scene, the same one on the homepage. Recording it here does not mean your agent has read your record.

Try it with one decision you already made.

1. Write the choice. One sentence a teammate can repeat.
2. Put the reason beside it. Why this, and what it rules out.
3. Name the seat. Which role owns a change, and which person answers.
4. Ask the agent to read it before the next related task. Check that the answer uses the reason, not a fresh guess.

If the agent cannot show the record it used, the connection is not in place yet. The first lesson’s start check ispb whoami.

What this does not prove.

A written record is not evidence the agent read it. The owner still judges a request to change it. Assigning the record to a seat does not, by itself, notify that person.

Product Brain is in early beta. Context has to be kept current. A connected agent still needs a result you can inspect.