Approval limits are revised as follows, effective 1 July 2025.
§1 Directors may approve spend up to $75,000.
Limits set in earlier policies are superseded.
§1 · limit in forceAsk a question and Chunkless finds the clause in one file, the exception in another and the memo that quietly overrode both. It answers with the exact section and page, checks every statement against its source, and says plainly when your documents disagree or don't say.
Your seat in Chunkless is ready - welcome. Your invite code is already in this link: set a password and your workspace is ready.
1 On 34 questions that each need several documents, half held out from tuning: 0.79 of the required facts, against 0.59 for standard chunk search. Paper, §5
Approval limits are revised as follows, effective 1 July 2025.
§1 Directors may approve spend up to $75,000.
Limits set in earlier policies are superseded.
§1 · limit in forceCapitalEquipment, vehicles
Operating · software subscriptions
LeasesPremises
definition§4.3 Capital items need CFO approval.
§5.1 Over $25,000: three written quotes.
§5.2 Approved vendors only.
§5.1–5.2 · requiredYes, with two conditions. It is within a director's $75,000 limit, and software is operating spend, so the CFO rule for capital items does not apply. It still needs three written quotes from an approved vendor.
Most AI search cuts your documents into chunks and grabs the few that sound like your question. But your answer lives across three documents. Chunkless keeps every document whole and follows what it points to, the way the person who wrote it would.
It learns your documents' vocabulary: the same thing under three names, what refers to what, which version replaced which, who cites whom. Then it connects volume 1 to volume 20 on its own.
versions · citations · continuationsEvery part of the answer traces to its section and page. Open the source, see the passage, check it yourself.
section · page · figureEach answer says whether the documents settle it, settle it only under a condition, point elsewhere, or contradict each other.
four verdicts, belowAsk "why does this keep failing?" and it follows the chain through runbooks, configs and procedures to the step that causes it.
root causeFigures and screenshots are described at upload, tables keep their rows and columns, scans are OCR'd. A manual answers with each step's picture.
figures · tables · scansGive it the papers or specs and ask for a design, a theory or a plan. It builds the answer from what the documents prove and marks what is still open.
research modeEach organization is isolated at the database's row level. Connector keys are encrypted at rest. Organize by department, folder and case, and bring your own model key if you like.
isolation · encryptionA good expert tells you how sure they are and why. Chunkless works the verdict out from your documents instead of guessing it.
Everything the answer needs is in what you uploaded, and each piece is cited.
"Leave carries over 5 days." HR Handbook §6.2
The answer depends on something your question didn't say, and it tells you exactly what.
Yes, if the vendor is already on the approved list (§2.4).
The rule refers to a schedule, form or policy that isn't in the library yet, and it names it.
§9 depends on "Schedule B", which isn't uploaded.
Both are in force and can't both be right. It shows you both, and who decides.
Memo 2025-07 vs Policy §4.2: the stricter applies until Finance rules.
It reads everything carefully up front, remembers how it all fits together, and when you ask, it goes back to the sources and checks before it speaks.
Upload files or point it at a bucket. Group them in departments and cases.
PDF, Word, slides, sheets, scans · up to 1 GBSections, tables and figures stay in place, with every rule, limit, definition and cross-reference noted.
every figure described · what overrides whatA quick lookup, a "can I…?", a "why does this keep breaking?", or a design built from thirty papers.
one department or all · follow-ups keep contextIt opens the sources, looks for evidence against its first answer and checks every statement before you see it.
section and page · the trail, on requestMatch the effort to the question. You pick, or it picks for you.
A fact, a number, a definition, in seconds.
Reads until each part is found or shown absent, then checks every statement.
Quick for a one-fact lookup, full for everything else.
Long-running reasoning: designs, theories, plans.
Can I approve this, and who says so?
A new hire gets the answer a ten-year veteran would give, with the policy, the memo that changed it and the exception that applies.
Why does the export fail every Monday?
It follows the chain through runbooks, configs and procedures to the step that's actually causing it, and shows the chain.
From these papers, what should we build?
It pieces a design together from what each source proves, says where they conflict and marks what's still open.
We publish how it works and how it scores, including what didn't help and where we corrected our own numbers.
Read the paper →This is a working build, not a demo video. Make an account and you're in: sample client files and their libraries in tax, insurance, banking and medical are already loaded, so you can ask your first question in a minute. Then bring your own documents. You get a direct line to the people building it.
If a seat is open, your personal invite is on its way now: one click and you set a password. It only works with the address you gave us. If every seat is taken, you're on the list and we'll email you when one opens.
Nothing arrived after a few minutes? Check your spam folder for mail from Chunkless.
Those tools read a handful of passages that sound like your question. Chunkless reads your whole library up front and learns what refers to what, which rule overrides which and where each figure belongs. When you ask, it investigates and checks every statement against its source. So it can say "these two documents disagree" or "the answer depends on a schedule you haven't uploaded" instead of writing something that merely sounds right.
Your name, your email and a password, and you're in: the shared sample libraries (fictional client files with the tax, insurance, banking and medical reference texts) are already loaded, read-only, beside an empty workspace of your own for 7 days. While seats last; when every seat is taken, you're on the list and we email you when one opens. The Feedback button at the top of the app reaches us directly, and genuine feedback earns extra days.
Yes, two ways. "Try it on your own documents" opens a private workspace with no account: drop in up to 3 files and ask 5 questions. Only you can see it, and everything in it (the files, what was read from them and your questions) is deleted after 24 hours. Or "try a sample library": eleven documents from a fictional medical-device company that you can browse and ask about.
They're stored encrypted on AWS in the US. Each organization is isolated at the database's row level, so no other tester can see your documents. To answer questions, the engine sends the relevant passages to a language model (OpenAI by default), or you can bring your own model key. During early access, please only upload documents you're allowed to share with a test system.
Collections where the answer is spread out: policies and their amendments, SOPs and manuals, contracts and schedules, research papers, clinical protocols, engineering runbooks. It handles PDFs (including scans), Word, PowerPoint and Excel.
Reading documents deeply takes real compute. We'd rather give a small group a fast, dependable engine than give everyone a slow one. We open it to more people as we scale.