Kept for Engineering.
Every system has one person who knows why it is built the way it is. These films are about what happens when that stops being a risk.
All industriesFor executives
The architecture is in their heads. Keep it anyway.
Bus factor is not a joke metric. It is the list of systems you cannot change because the person who understood them left.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The reason the retry limit is three isn’t in the code. It left with someone in March.
Architecture decisions and incident lessons fragment across repos and people, and the next outage repeats the last one.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new engineer opens the config and asks why it’s three. Kept answers from the March backfill and shows the exact words from the call.
Incident lessons and design reasoning stay with the system, not the person. Kept. Keep the knowledge behind the work.
Every engineering org carries systems that one person can safely touch. The diagrams are stale, the runbooks describe the previous version, and the real documentation is whatever the senior engineer says in the meeting. When they resign, you do not lose a seat. You lose the reasons.
Kept interviews your engineers about the work they actually do, in their own words, and turns it into memory with receipts. Ask why the queue drains that way and the answer cites the person who built it, on the day they said it. The workspace owns the knowledge. Nobody inherits a mystery.
For managers
Your team already wrote the onboarding doc. Out loud.
The knowledge exists. It is just distributed across six people, two of whom are on call and one of whom is leaving.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The reason the retry limit is three isn’t in the code. It left with someone in March.
Your best engineer’s context leaves in a two-week notice period, and the runbook doesn’t cover it.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new engineer opens the config and asks why it’s three. Kept answers from the March backfill and shows the exact words from the call.
The context survives the notice period. Kept. Keep the knowledge behind the work.
A new engineer's first month is spent finding out who to ask. The deploy quirks, the service that lies in its dashboards, the incident from last spring that explains three weird defaults. None of it is written down, because writing it down has never survived a sprint plan.
Kept captures it in conversation, the way your engineers already explain things, and links captured knowledge to available sources. You see what your department has covered and where it is thin. You never see a score of a person, because Kept does not make one. Coverage, not surveillance.
For partners
You are the documentation. That should worry you less than it does.
Being the only person who understands the payment retry logic is job security right up until it is a pager duty sentence.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The reason the retry limit is three isn’t in the code. It left with someone in March.
You’re about to change a number someone set for a reason nobody can tell you.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new engineer opens the config and asks why it’s three. Kept answers from the March backfill and shows the exact words from the call.
You change the number knowing what happened last time. Kept. Keep the knowledge behind the work.
Kept talks with you about the work you actually do, like a colleague who wants to understand it, not a form that wants fields filled. It keeps what you say in your own words, and when someone asks a question your answer covers, they get your explanation with your name on it, instead of paging you.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in engineering.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a engineering team:
- Knowledge kept from the outgoing expert before the handoff date, by topic
- Questions the successor asks that are answered with a source, against honest unknowns
- Time from a new colleague's first day to their first cited answer
- Questions answered by Kept in the first 30 days instead of by a teammate
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance