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.
WeddingTalkDruruk KidsMCP 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 · Druruk Kids
A child's records
stay inside the family space.
Druruk Kids keeps the conversations a child has in a space separated per family. In a family service, not mixing memories comes first.
Structure: per-family spaces, per-child deletion, fixed speakers and a language field, all managed to fit the product flow. Searching from one family must never surface another family's memories.
Family isolation
Only our family's memories.
Each family gets its own authenticated space and key, and search is designed to open only within that space.
Per-child deletion
One child's records can be erased on their own.
A single child's memories can be cleared without deleting the whole family.
Source of each line
Who said it is never blurred.
The product's fixed speakers and the service making the call are recorded, so a child's words never mix with the system's prompts.
More languages
The same rules in any language.
Every memory has a language field, so the source and scope of a memory hold as the product expands beyond Korean.
39Family spaces
internal count, 2026-09-07
internal count, 2026-09-07
3,037Active memories
same date
same date
0Cross-family search leaks
isolation test result
isolation test result
Figures come from the internal production database and isolation tests as of 2026-09-07. Live data changes over time; what we prioritise is the structure that keeps family boundaries intact, not the numbers.
03 · 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 and Druruk Kids, 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, family conversations and shared projects each stay within their own boundaries — and are ready to use again for the next task.