How it works

How your engram gets built, and how it keeps learning.

From your own record to a helper that works like you: what we read, what we keep, what we throw away, how it acts, and how we check it against you.

Three layers, one helper.

  • A library

    Search, or retrieval: the documents that match the words of a question. Fast and literal. It finds what was written, not what you would do.

  • A map

    A knowledge graph: what relates to what. The buyer, the account, the orders, the terms. It connects the facts. It does not choose between them.

  • You

    Your engram: your decisions, your rules, your preferences and your way of saying things, each traced to where you said it. The layer that turns facts into what you would do next.

What we build from

What we build from.

Only your own words. Each source is one you choose, in writing, and can disconnect.

  • Mail you sent

    Your replies and the threads they answer. The reply is the source. The thread you answered is context, read only to understand the reply.

  • Code review comments

    What you asked for, what you blocked, and why. The clearest record of an engineer's rules that exists.

  • Decisions and corrections you recorded

    Notes, decision logs, the edits you made to drafts. A correction is the most valuable sentence you write.

  • Transcripts and chat you wrote

    Your side of meetings and chat, where you connect them. The hardest register to learn, and the one you use most.

Not read: mail you received, notifications, newsletters, anything automated, and anything you did not connect.

What we keep and what we don't

Names become roles. Bodies are not kept.

Step through one thread. The buyer's name never reaches the engram; the rule in Sam's reply does, citing the reply.

  1. 01The thread, as receivedA buyer's email and Sam's reply. The reply is the source; the buyer's email is only the context it answers.
  2. 02Names become rolesBefore anything is stored, every person and company in the thread becomes a role type. The names never reach the engram.
  3. 03Bodies are not keptNo message body is stored. What is kept is a claim, and where in the source it was said.
  4. 04One node remainsA rule, in Sam's words, citing the message it came from and the span of characters that said it. Sam can read it, and delete it.

From Priya Natarajana buyer at a restaurant group, Harborline Foodsthe restaurant group

Subject Reorder and pricing

Hi Sam, we'd like to reorder 40 cases for the three Harborlinethe restaurant group locations. Can you do 15% given the volume? Marcus at Lakeside Supplya contact at a distributor mentioned you offer 60-day terms to some accounts.

Context only. Not stored.

From Sam

Thanks Priyathe buyer. I never go past 10% on reorders, volume earns terms rather than margin. I can do 8% and move Harborlinethe restaurant group to 60-day terms. Shall I confirm the 40 cases?

The source. Its body is not stored either; only the span the node cites.

rule

Never past 10% on reorders. Volume earns terms, not margin.

Source: Sam's reply, 12 March last year · characters 13 to 86

Valid from 12 March last year

Readable by Sam. Deletable by Sam. The only thing kept.

How it keeps learning

One correction, next time right.

It learns from the sources you connect and from every correction you make. Nothing ambient. Nothing you did not switch on. Step through one correction, then keep or discard what it learned.

  1. 01 · It drafts

    A buyer asks for 15% off a reorder.

    Happy to offer 15% on this reorder.

  2. 02 · Sam edits

    15% 8% on 60-day terms

    Never past 10% on reorders.

  3. 03 · It proposes a node

    Learned from Sam's edit on 3 October

    Never past 10% on reorders.

  4. 04 · Next time

    Two weeks later, another buyer asks for 12% off a reorder.

    I can do 8% on 60-day terms, which is what I offer on reorders.

    Cites Sam's edit of 3 October.

    No precedent for this. Asking Sam.

    Nothing to cite: Sam discarded the node.

    Drafted by Sam's AI. Sam approves before it sends.

Between sessions it consolidates what it learned, and you review the list each week: what it proposes to keep, with the source of each.

How it acts

It drafts. You approve.

  • Drafts

    Replies, summaries and notes in your voice, each labelled as drafted by your AI, waiting for you.

  • Decision cards

    The situation in one line, the recommended action, one or two alternatives, the cited rule or precedent, and Approve, Edit or Decline. Answered in seconds.

  • Approvals

    Nothing goes out, gets paid or gets promised without your OK, unless you set a rule that allows it, inside limits you set.

  • The label your contacts see

    Every message it sends says it was drafted by your AI, and carries a machine-readable marker. Disclosure is built in, not optional.

How we measure it

Graded against you, not a leaderboard.

We hold back decisions you already made, replay each one, and count agreement, reported as a fraction of your own consistency, with its margin. The method is on its own page; the number comes when the test has run.

Side by side

Three places an AI can learn you.

DimensionMemory built into assistantsClone platformsYour engram, with Duplikate
What it learns fromYour chats with that assistantDocuments and recordings you uploadYour own record: sent mail, reviews, notes, corrections, and only the sources you choose
What it keepsFacts about you, as it summarises themYour content, for retrievalDecisions, rules, preferences and voice, each citing where you said it
Who else is in itWhoever you mentioned, as saidWhoever is in your uploadsNobody by name: people and companies become role types at the door
Is it measured against you?No published scoreNo published scoreYes: held-out decisions, replayed, reported as a fraction of your own consistency
What it doesAnswers youAnswers your audienceDrafts, triages and prepares decisions you approve
LeavingExport, in someVariesExport everything with its sources, any time; 90 days' notice if we ever close

Based on the public pages of products in each group, read on 24 October 2026. A sourced, product-by-product comparison follows in Learn.

When the answer is not this

When the answer is not this.

  • You want an assistant that acts with no review. Ours asks first, by design, until it has earned a standing rule inside a limit you set.

  • You want a video or voice double. Duplikate writes. It does not imitate your voice or your face.

  • You won't share your own writing. There is nothing to build from without it, and we never build from someone else's.

Questions

What people ask first.

How much of my record does it need?
Enough of your own decisions to measure against. Sent mail, review comments and recorded decisions are the richest sources; a few hundred of your own messages already carry rules, preferences and voice. We tell you before the build what the sample supports, and the fidelity test tells you after it.
Does it read everything in my inbox?
No. It reads what you connect, and of that it keeps only what you wrote. Mail you received is read as the context of your replies, never as a source, and no message body is stored. Notifications and automated mail are left out.
What happens when I change my mind about a rule?
The old node is superseded, not deleted: it keeps the date it stopped applying, and the new one carries the date it began. The next answer follows the new rule, and you can see both, with their sources.
Can it work for my personal life too?
Yes, in a separate space. Work and Home each have their own sources and permissions, and you decide what each can see. Most people start with work, because that is where the same questions reach them most.
Who builds and runs it?
Traide, the consultancy behind Duplikate. A senior engineer scopes the sources with you, builds the engram, measures it against you, and maintains it as you keep correcting it. The same pipeline runs on our own founder's record.
Talk to us

Want to see what yours would be built from?

You'll talk to a senior engineer, not a sales rep, and leave knowing what your engram would be built from and how it would be measured.