Decisions and memory

Company memory keeps decisions in context so a later conversation can use what was agreed and understand where it applies. The reason, owner, source and time limit can matter as much as the decision itself.

A remembered exception should remain an exception with defined boundaries.

Describe a decision completely

Detail	Why it matters
Agreement	States what the team decided.
Owner	Identifies who made or owns the decision.
Reason	Explains the circumstances behind it.
Scope and duration	Shows where it applies and when it ends.
Source	Lets another person verify the agreement.

For example, a customer may have a temporary billing exception for the first contract year. A handoff should preserve both the exception and the requirement for new approval before extending it.

Ask what still applies

Summarize the customer's approved exception, who approved it and when it ends. Explain what happens at renewal, with links to the approval and signed terms.

Review the original evidence before making a new commitment. A past approval does not automatically authorize an extension.

Handle a changed decision

When circumstances change, identify the new decision and the earlier agreement it replaces. Ask Milo to make any unresolved conflict visible rather than treating both versions as simultaneously current.

Memory supports continuity across work and handoffs. Its availability and sources depend on the enterprise configuration. For questions about correcting or deleting stored information, use the applicable account and privacy support process.