Appearance
Employee Knowledge Compensation
Employee Knowledge Compensation is DutyGraph's model for paying employees for the operational knowledge they contribute. A share of each implementation fee goes to the employees who write accepted Task Cards and who improve that work.
WARNING
Mostly Planned. This page describes how the program is designed to work. Parts of the payment rules exist in the Earn code today; the rest is a proposal. The Status box at the end says which part is which. All numbers on this page are examples, not results.
Why pay for knowledge
Most of how a company works lives in people's heads. A new hire, an AI assistant or an agent cannot use knowledge that nobody wrote down.
Employees have a sensible reason not to write it down. Knowledge that only one person has gives that person leverage. Writing down a job can feel like training a replacement. A program that asks for knowledge must make sharing worth more than keeping it.
The program works on three ideas:
- Pay for what is used. Pay when a Task Card is accepted, and again when it proves useful.
- Let the employee own the improvement. When a task is improved or turned into an agent, the person who wrote the card owns that agent and shares in what it saves.
- Make the company's promises visible. Employees see the rules, the pool and the company's protection choice before they write a card.
The three parties
| Party | What it wants | What it fears | What the program gives it |
|---|---|---|---|
| Employee | Fair pay, job safety, recognition, less repetitive work | Being automated away, not being paid, being watched | Payment rules shown first, ownership of the agents built from their cards, a protection tier shown up front, no surveillance metrics |
| Company | Less dependence on single people, faster onboarding, work that AI can help with | Paying for weak or padded cards | Payment only after a manager accepts a card and after a check period, measured value, checks against padding |
| DutyGraph | Complete, accurate Task Cards and a fair program that companies renew | Being seen as a tool for cutting jobs | Acts as the neutral scorekeeper: computes the numbers from records, not from opinion |
DutyGraph keeps score. It does not set the company's pay policy and it does not hold the money. The company pays its people through its own payroll, under its own pay rules.
KAR: Knowledge Above Replacement
KAR (Knowledge Above Replacement) is the proposed measure of the value an employee has put into the company's map. It borrows the idea of "wins above replacement" from baseball statistics.
The baseline, called replacement level, is a competent new hire in the same role. That person has the job description and a general AI assistant. They have no Task Cards and nobody to ask.
KAR is the yearly value the company would lose, or have to rebuild, without this person's captured knowledge, plus the measured value of their improvements.
What goes into KAR
| Part | What it measures | Evidence it uses |
|---|---|---|
| Capture | Accepted Task Cards, weighted by how often the task runs, how important it is, and how few other people can do it | Accepted cards, completeness check, run records |
| Response | How quickly the person answers requests for information | Request and answer times |
| Protection | Errors prevented, compliance steps written down, governance flags raised | Governance flags, recorded issues |
| Constraint weight | Extra weight for work on the step where work piles up (Theory of Constraints, a method that improves the slowest step first) | The Work Map and possible constraints |
| Leverage | Other people's cards built from this person's cards, and shorter onboarding for new hires | Card lineage, reuse counts |
| Improvement | Hours saved or errors cut after the person improved a task or built AI into it | A baseline recorded at capture, then a check period |
Example calculation
KAR per year = sum over the person's cards of
(task value per year × uniqueness × constraint weight)
+ measured improvement value
+ reuse credit
task value per year = runs per year × hours per run × loaded hourly rate
+ errors prevented
+ chance the holder leaves × cost to rebuild the knowledge
uniqueness = 1 ÷ number of people who can already do the task without the cardHow KAR is shown
- From day one, as a range. Early numbers have little evidence. The range narrows as run records come in. The page says how much evidence the number uses.
- Only within a role family. A warehouse role and a finance role are not compared.
- Credit only. KAR starts at zero and only goes up. Nobody has a negative KAR.
- No ranking of who can be replaced. DutyGraph does not show a "replaceable" score, a company leaderboard, activity time or keystrokes.
- Who sees it. The person sees their own KAR. Their manager sees the KAR of their direct reports. Peers see counts only.
Employees own the agents built from their cards
The program changes the usual story. The old story is "write down your task, then a machine does it." The new story is "write down your task, then turn it into an agent that you own."
The planned flow for an employee who is not a developer:
Step 1
Ask your own AI
In Claude or ChatGPT, connected to DutyGraph through MCP (Model Context Protocol), the employee asks: "Open my Task Cards and help me make these faster."
Step 2
DutyGraph looks for parts that fit
DutyGraph reads the person's cards. It searches the company's library of skills, plugins, connectors and workflows for parts that fit each task.
Step 3
DutyGraph proposes a change or names the gap
It proposes a change, for example: "This card can use the existing email connector and the scheduling skill." If nothing fits, it records the gap.
Step 4
A builder makes the agent from the card
DutyGraph writes an agent specification from the Task Card. A coding agent or the advisor builds it.
Step 5
The employee owns the agent
The agent is tied to its duty and to the employee as its owner. The employee approves changes, watches its runs and reports problems. Governance rules apply as for any agent. See Govern agents.
The employee moves from "the person the agent replaces" to "the person who runs the agent." Their value to the company goes up when the agent ships.
How payments work
The program has four payment levels. The first is paid once. The others continue while the work keeps paying off.
| Level | What it pays for | Example rule | When it is paid |
|---|---|---|---|
| 1. Capture | An accepted Task Card | A set amount per card, chosen by the company | Half when a manager accepts the card. Half after a check period, if the card is still used and correct |
| 2. Improvement | Measured savings from a change the employee made | A share of hours saved per week × loaded hourly rate × working weeks, with a cap per change | After the check period, measured against the baseline |
| 3. Agent ownership | An agent built from the employee's card, which they own and keep working | A share of the agent's measured savings | Each quarter, while the employee owns the agent |
| 4. Reuse | Other people's cards built from this card | Credit and reuse counts first, payment later | Over time |
Knowledge that people will not write down
Some people will not write down their deepest knowledge for any payment. DutyGraph can record that the knowledge exists without its content: the area, the person who holds it, the work that depends on it, and its value. The company can then pay the named holder a retention amount. This lowers the risk of losing the knowledge without forcing anyone to give it up.
Where the money comes from
- The company pays the implementation fee.
- The contract sets an employee pool from that fee and DutyGraph's share.
- Employees see the pool, the rules and the amount left.
- DutyGraph records each accepted card, each check and each amount due.
- The company pays its people through its own payroll.
Example (fictional numbers)
One employee in one year:
| Item | Calculation | Amount |
|---|---|---|
| Capture | 12 accepted cards × $100 | $1,200 |
| Improvement | 6 hours saved per week × $40 per hour × 48 weeks = $11,520 a year; 10% share | $1,152 |
| Agent ownership | 7.5% of $11,520 for the agent they own | $864 |
| Total paid | $3,216 |
The company keeps about $10,000 of that year's savings from the one change, and keeps the 12 cards for onboarding.
Protection when work is automated
The biggest fear is "they will take my knowledge and let me go." Most company leaders will not promise that no job changes. So the program offers a choice. The company chooses a protection tier, and every employee sees that choice before writing a card.
| Tier | What the company promises | What employees see |
|---|---|---|
| Pledge | No one is let go because a task they documented was automated, for 12 months | A "knowledge-safe employer" badge |
| Buyout (default) | If a role or task ends because of a card the person wrote, the person gets a knowledge buyout on top of normal severance | Their buyout value on their profile, updated as the card's value is measured |
| None | Capture payments only | A plain notice that there is no protection |
With a buyout, the company does not promise never to cut. It promises a price if it does. A company can plan for a price.
How DutyGraph measures the value of a card
- Baseline at capture. When a manager accepts a card, DutyGraph records the starting numbers: runs per month, hours per run, people involved, error or rework rate and loaded cost. The employee and the manager confirm them.
- After the change. When the task is improved or an agent runs it, DutyGraph measures the same numbers from run records.
- Card value. The yearly cost before, minus the yearly cost after, plus errors prevented and onboarding time saved.
The improvement payment, the agent ownership payment and the buyout all use this one card value.
Example buyout rule
- Buyout = the higher of (a) 50% of the first-year measured value of the cards that caused the change, or (b) 24 months of the agent ownership payment. The company sets a cap.
- Example: an agent built from a person's card saves $40,000 a year, and the role ends. The buyout is 50% × $40,000 = $20,000, on top of normal severance.
When ongoing payments stop
| Situation | What happens |
|---|---|
| The person stays and owns the agent | Payments continue |
| The role ends because of the person's card | Buyout, or 12 more months of payments. The company chooses which when it sets up the program |
| The person leaves by choice | Payments stop, after a minimum period of ownership |
| The person is dismissed for cause | Payments stop |
Severance and bonus rules differ by state and country. A company should have an employment lawyer review its program before launch.
Company secrets and proprietary knowledge
Two different problems are often mixed up:
- Secrets must never be in any card: passwords, API keys, account numbers, and patient or customer personal data.
- Proprietary knowledge belongs to the company: customer names, prices, supplier terms and the way the company does the work better. Inside the company's own workspace this knowledge is the point of the card. It must not leave that workspace.
Four labels
Every item in a card gets one of four labels:
| Label | Examples | Where it can be stored |
|---|---|---|
| Secret | Passwords, keys, card numbers, personal data | Nowhere. Replaced with [removed] before the card is saved. The card says where to get the login, for example "the company password vault", never the login itself |
| Confidential | Customer and supplier names, prices, contract terms, internal system names | The company workspace only. Replaced with a placeholder, such as {customer}, in anything that leaves the workspace |
| Proprietary method | The company's special way of doing the task | The company workspace, open only to named roles. It increases KAR because few people know it, but the content stays restricted |
| General method | Steps any company in the field would use | Can leave the workspace only after a manager or admin releases it |
How a card is cleaned before it is sent
- The AI checks the draft and flags items that look like secrets or confidential details.
- It suggests a placeholder for each item. The employee accepts or edits each one. Nothing changes without the employee seeing it.
- The manager confirms the card when they accept it.
- DutyGraph keeps two versions: the full card for the company workspace and a cleaned card for anything that leaves it.
- Agents built from cards get their logins from the company's own secret store when they run, never from card text.
How people could misuse the program, and the checks
| Misuse | Check |
|---|---|
| Split one task into many cards | Pay by task value, not by count. A duplicate check runs. The manager confirms |
| Overstate time spent | Use run records where they exist. Apply the check period. Compare with others in the same role |
| Leave out the last steps so the writer stays needed | The replacement test: a card is paid in full only when someone else, or an agent, can do the task from the card alone |
| Make a process worse, then "fix" it | The baseline is recorded at capture time and cannot be changed later |
| A manager and an employee agree to approve weak cards | Budget caps, spot checks by the advisor, random samples |
| Copy a colleague's card | Card lineage gives credit to the original writer |
| Work for the score instead of the work | KAR is one input to pay. It is not the only input to a performance review |
Rollout order
- Points and records first. Record accepted cards, completeness and runs, so the first payment rests on evidence. Payment can stay off.
- Capture payments, with company settings for the amount per card, the pool and the check period.
- Improvement payments, with recorded baselines.
- Agent ownership: the "improve my cards" conversation, matching cards to the company's skills and connectors, agent specifications and ownership payments.
- Reuse credit and a portable profile the employee can keep, holding only released general methods.
INFO
Status. Built (Partial): the Earn code on matt/dev lets a company set an amount per accepted card, a pool, a check period and a time-saved bonus rate with a cap; it checks drafts for duplicates and general chores, removes common secrets (API keys, tokens, passwords, card numbers) from cards, and pays only through a payroll CSV the company runs itself. Live payouts are not connected; a test payout path exists. Planned: KAR and its range, the protection tiers and buyout, agent ownership and its payments, reuse credit, the four labels with two versions of each card, the retention amount for held knowledge, and the "improve my cards" conversation. The agent specification from a Task Card is in review, not merged.
Source: gitbook/product/roadmap/employee-knowledge-compensation.md in the DutyGraph repository.