Living memory

What your best people know, kept.

Most of what a company actually knows never makes it into a document. It lives in how your most experienced people work, and the calls they make without ever writing them down. When they leave, it leaves with them. Living Memory captures it from real work, not from an upload.

Talk to us about a pilot See what's built on top

The method

Captured from real work, on the person's own terms.

Seven steps, in order, from the moment someone decides a piece of work is worth keeping to the moment your company can trust the result.

The person presses record.

A staff member starts a recording on their own screen when they're doing a piece of work worth keeping. Nobody switches this on for them. There is no silent monitoring and no employer-initiated capture, ever: that is a principle here, not a setting anyone could change.

They think out loud.

While they work they talk through why they're doing what they're doing, or they type it afterwards. The reasoning is the valuable half. The steps alone are a checklist; the reasoning is the judgment call nobody had written down before.

Cleaned before it goes anywhere.

Everything is processed on the person's own computer first: finding the key steps, reading what's on screen, and automatically finding and blurring personal data, national IDs, account numbers, contact details, so nothing identifying survives past this step.

The person reviews it, not us.

They watch their own recording back, blur anything else they want gone, or delete the whole thing. Nothing proceeds until they press Export. Consent here is a moment they control, not a checkbox buried in a policy somewhere.

Speech becomes text, and nothing else survives that step.

A speech engine tuned for local Singapore speech, hosted in Singapore, converts what was said into text. It processes the audio to do that job, and retains none of it afterward.

Sealed with a key that isn't ours.

The result is a knowledge card: the steps, plus the reasoning behind them. It's sealed on the person's laptop with an encryption key that belongs to your company, then delivered. The raw recording never leaves the machine, and it's deleted automatically after a set period.

Trusted only after a person says so.

Every card arrives marked captured. It becomes trusted company knowledge only after someone at your company reviews and verifies it. Software never declares something true on its own here; a human promotes it.

The security model

We carry the box. You hold the key.

Every knowledge card is encrypted with a key that belongs to your company. We do not have it. There is no master key, and there is no support backdoor. Reading your company's knowledge without your company isn't something we refrain from. It's something we cannot do. We never receive your recordings, only what your company learned.

The honest trade-off

If your company loses every one of its recovery keys, the sealed content behind them becomes permanently unrecoverable. No procedure brings it back. That is the actual price of a promise that is real, and we would rather you hear it from us now than find it out the hard way later.

Four levels of control

The contract.

What we can and can't do with your data, in plain terms, on paper.

The workspace switch.

A setting your admin controls, off by default, that turns capture on for your company at all.

The key itself.

Owned by your company, not us, which makes your consent structural rather than a policy someone could quietly change.

Per-card verification.

Every card is checked by a person on your team before it's ever treated as trusted knowledge.

Consultant access is invited access.

You can grant a named consultant a seat, see exactly what that seat has viewed, and revoke it in one click. Access is always something your company grants. It is never something we take.

Data residency.

Singapore.

The whole pipeline

From a screen recording to a grounded agent.

Eight steps, one continuous system. The last one is what the agents layer is built on.

Capture

A staff member records their own work.

Distill

The reasoning is pulled out; the rest is left behind.

Seal

Sealed on the laptop with your company's own key.

Deliver

The sealed card arrives. Nothing else does.

Verify

A person on your team checks it before it's trusted.

Ask

Staff query it and get an answer, cited.

Audit

Every access and every answer is logged.

Agents

Verified memory becomes what an agent is grounded on.

Common questions

About Living Memory.

Can a manager or employer trigger a recording?

No. Recording starts only when the staff member presses record themselves. There is no employer-initiated or silent capture. That's a design decision, not a setting someone could turn on.

What happens to the raw recording afterward?

It stays on the person's own laptop, is used only to produce the sealed knowledge card, and is deleted automatically after a set period. We never receive it.

What if my company loses its recovery keys?

The sealed content behind those keys becomes permanently unrecoverable. No procedure brings it back. We would rather you know that plainly now than find it out later.

Does any of this leave the laptop?

The finished, blurred knowledge card does, sealed with your company's key. So does the audio, but only for transcription: a Singapore-hosted speech engine turns it into text and retains none of it afterward. We never receive your recordings, only what your company learned.

Built on this

See what the memory feeds.

Staff answers, staff training, and the agents layer all draw on the same verified memory. Nothing here is a separate product bolted on afterward.

See the agents layer See how staff use it