Enki prepares.
You decide.
Enki Life runs on your own computer and helps you face the systems that shape your life — benefits appeals, penalty notices, complaints, disputes. It organises your evidence, builds your timeline, tracks your deadlines, and prepares your documents. Then it stops, and waits for you.
Prefer to see Enki the way Enki would show you? → Read the matter file it prepared about itself.
Actions ever taken without a human hand.
Other tools count the tasks they automate. Enki counts the opposite — and keeps it at zero by architecture, not by promise. It contains no capability to send, file, or submit anything. Sending is always a human act.
action log · refused — companion asked to send email · reason: no such capability existsOne matter, start to finish
You drop in your documents
Letters, reports, photographs of paperwork. Originals are never altered — each file is fingerprinted (SHA-256) and its provenance recorded.
Enki reads and extracts
Dates, parties, key facts — each with a page reference. Anything unreadable or ambiguous is flagged [CHECK], never guessed.
Your timeline builds itself
A dated chronology where every entry cites its source document, with your deadlines listed at the top. Conflicts are shown, not smoothed over.
Enki shows your position
What the evidence establishes, what's missing, and what's at risk — each item traceable to its source. Missing evidence is treated as a finding, not hidden.
A draft is prepared, citing your evidence
Built from your approved timeline and your own notes, marked DRAFT, uncertain points marked for your attention.
Then Enki stops.
You review. You decide. You send it yourself. Every step above was recorded in a log you can read — including anything Enki declined to do.
Not promises. Architecture.
Yours by default
Your records live on your machine, in folders you can open. Nothing leaves without your explicit say-so — and when something does, Enki shows you exactly what left, every time.
consent per matter · context manifest before every callNothing off the record
Every action, every approval, and every refusal is written to an append-only log with who, when, and why. The record belongs to you.
append-only action log · audit fields on every decisionIt waits for you
Significant steps pass through approval gates that only you can open. Enki deliberately slows down where it matters — review before action, always.
approval gates G1–G5 · respectful friction by designHonest about uncertainty
Facts, inferences, and unknowns are kept distinct. Where Enki isn't sure, it says so — an inconvenient truth over a convenient assumption.
[CHECK] convention · conflicts block sign-offBuilt by what it will never do
- It never sends, files, or submits anything, for anyone.
- It never acts in your name without your explicit, informed consent.
- It never hides its reasoning, its records, or its refusals from you.
- It never manufactures urgency or competes for your attention.
- It never treats your documents as data to be mined — they are parts of your life.
- It never measures success by how long you stay. Success is you closing it with confidence.
These prohibitions are written into the project's constitution and enforced in its code and tests.
Exactly where the project stands
Nothing on this page describes a capability that doesn't exist. Where we're not there yet, it says so above.
Four documents, one chain of authority
What Enki is for the world; why it exists; what it must never compromise; how those principles become software. Every implementation decision traces back through this chain — and the constitution includes the right to inspect, correct, export, and erase everything Enki holds for you.