You remember the conversation. docenta finds the thread, the attachment and the exact line.
Ask a large mailbox by meaning, chronology, sender, date, numbers and what was agreed, even when you remember the promise and not the subject line. An export in an evening, the live mailbox from then on. Threads stay threads; attachments stay attached; the answer stays inspectable.
Acme first proposed September 8, moved it to September 15 in an August 21 email, and confirmed September 15 again in the revised schedule attached on August 22. No later message or attachment in the indexed mailbox changes that date. A September 10 email says the team is "still on track" and introduces no new date.
An illustration of the shape of an answer. The thread is made up; the behavior, both sides in order, the attachment read as evidence, the quiet message that changes nothing, is docenta's.
You remember the meaning, the date, the argument. Ask that.
Find it
Find the email I remember by meaning even though I forgot the sender and the subject.
Find the attachment sent around the time we discussed this.
Which messages mention the same reference number even when it is written differently?
Agreement
Find the thread where the landlord agreed to cover the repair and the invoice attached later.
Show the exact message where they approved this.
Was the final number in the attachment ever acknowledged in the thread?
Versions and dates
Who first proposed this price, date or term, and when was it changed?
Which attachment is the latest version, and which message sent it?
Did someone retract or qualify an earlier promise?
In order
Build the timeline of this thread, both sides and attachments included.
What was the last message on this topic before the project went quiet?
What did this person say about this across several threads over two years?
Evidence and gaps
Which open questions in this thread never received an answer?
What did the message say versus what the attached PDF said?
What cannot be established because part of the thread or the attachments is missing?
The export, then the live mailbox.
A Takeout or mbox in an evening, then the live account every hour: Sign in with Google for a Google account, one click on Allow; an app password elsewhere, kept in the OS credential store. Every folder the server lists, trash and spam included, so nothing is invisible.
Fields that answer.
From, to, subject, date, labels, thread: query fields that narrow like a database, and a "latest first" that never relaxes the question to fit an answer.
Attachments as members.
A PDF inside a message is a document of its own, still tied to the message that carried it, so the invoice and the promise are one chain.
The same four-part contract, every time.
Exact source.
The file, the page, the message, the span. Not "sources": the line you can open and read.
Order and version.
When it was said, which version it was, what replaced what. A three-event timeline beats another paragraph.
Conflicts.
Two sources that disagree are shown side by side, never smoothed into one confident sentence.
Gaps.
"Not established by this collection" is an answer, printed as one. It is how you know the rest is solid.
The evidence path.
What was searched, which lanes answered, what was dropped and why, how many tokens the agent was handed. Inspectable, every time.
Boundedness is the feature.
Most AI marketing hides uncertainty. docenta prints it. The lines below are not disclaimers; they are what a trustworthy answer looks like.
Meaning search is disclosed. When a term is not in your mailbox, docenta says which word it dropped or respelled to find the page; a relaxed answer is labelled as one.
Received is not read. A message at an address is a fact; that a person read it is not, unless a reply says so.
The quiet message is not a change. "Still on track" carries no date and is cited as carrying none.
Missing halves are named. A thread whose other side or attachment is not in the mailbox is reported as incomplete, with what is there.
Back to the collections · also for contractors, lawyers, insurance, home, mail, developers, researchers · public collections, live: Judaism, Christianity, Islam, faith, sleep · in preparation: diabetes · the handbook
Ask the sensitive question without first uploading the sensitive file.
Your mailbox, its attachments and its history stay on your machine: ingest, index, embeddings and answers all run there. Originals are never copied; only searchable derivatives are stored. Your agent gets a small evidence pack, a few kilobytes with the receipts, not your archive. Zero uploads, zero telemetry, and the token budget is printed on every answer.
It gets it over MCP, the connector standard Claude, ChatGPT and most coding assistants speak, from a server that runs on your own machine: the agent talks to a local process, not to a URL in someone's cloud. The only remote MCP addresses on this site are the public doors, sealed collections hosted on purpose; your own collection never has one. Deterministic layers, no learned model in the retrieval loop, bit-stable re-runs.
What is one question your files should be able to answer today?
docenta is a commercial product of SKY, LLC, now in private preview. Tell us the question; we will tell you when the door opens, and the questions we hear shape what we build.
No account and no newsletter: you confirm your address by mail, then we write back when the door opens. Prefer mail? email@docenta.ai