Shared space
Bride, groom and planner are kept distinct.
Within one workspace, the bride, groom, planner and shared speakers are recorded, so it is clear who said what and who it is open to.
Use cases
Each product keeps
the memory it needs.
ASR is the same everywhere, but the memories each product needs — and who may reach them — differ by user and by product. Here is how it is used in practice, in AI tools and in products.
WeddingTalkMCP clientsDirect product calls
01 · WeddingTalk
Wedding-planning decisions,
still there in the next conversation.
WeddingTalk is a service where a couple and their planner follow the preparations together. Private conversations and decisions the team shares are kept apart.
How we describe it today: WeddingTalk is presented through its product-specific ASR integration and the way it separates memories. Production data and publishable usage figures are not stated until separately verified.
Five kinds of record
Decisions and feelings are saved separately.
Decisions, preferences, open questions, friction and promises are stored apart, so “what did we decide?” and “what is still open?” are found differently later.
Correctable records
Mistakes are corrected with a history.
The original is kept and the correction is saved as a new record. A deleted memory drops out of search, but the fact that something changed is never quietly covered up.
Consent and scope
What is shared and what stays private are kept apart.
The couple's default shared space is separated from what should stay personal, and sensitive records assume explicit consent and a defined scope of access.
02 · AI tools and products
Memories people look up,
and memories products call — managed together.
In clients such as Cursor, Claude Desktop, Codex and Trae, people search their memories over MCP. In products such as WeddingTalk, the server calls ASR at the moment it's needed.
01
The product's question
The user's current screen and conversation create context that needs to carry on.
02
An authorised call
The product server sends an MCP request with its own space and key.
03
Recall from ASR
Only the needed memories are found, respecting scope, speaker, language and deletion state.
Same ASR, different memory scopes.
Each service calls ASR only within its permitted space and users. Being connected does not mean sharing every memory — only the records that are needed, within a defined scope.
Different scopes of memory,
the same work carried on.
Personal work, plans two people make together and shared projects each stay within their own boundaries — and are ready to use again for the next task.