Every answer carries the page it came from.
ContractManager reads a project's whole folder — the contract, the monthlies, the certificates, the site photographs — and answers in plain words, citing the document and page. Where the record is silent it says so. Nothing is invented, and no document is processed off this machine.
Has the retention on the third payment certificate been released?
No release is evidenced. The certificate records KES 5,000,000 gross with 10% retention held; the payment advice in the folder covers the net sum only. The release certificate required under the retention clause is not in this project's record.
Illustrative example. Every project shown in public material is invented.
First three counted from the live register, 17 September 2026. The fourth is policy, not a count: the app refuses any model that is not installed locally.
Three jobs, done the way the office already works.
Not a chatbot bolted to a drive. The tool files the day's work, reads the record, and writes the documents that go to the ministry.
The clerk files from the site
The day's report goes in from a phone with a signal that comes and goes: weather, crew, plant, work done, photographs. It becomes a document in the record the moment it sends, and the week and the month compile themselves.
Offline draft · one tap files · IOW layout PDF
Ask, and get the page
Questions in plain words, answered from that project's own documents with the file name and page beside each fact. A clause is quoted only when this contract's own conditions carry it; anything else is marked unverified rather than guessed.
Citations · clause check · [NOT EVIDENCED] where silent
The heavy documents, in hours
The contractual fault report that takes a week by hand, on official format with the ministry's own report format, the project details table and a contents page. A presentation gate reads it before you can: ready, or draft with the reasons listed.
Word and PDF · sources listed · gate before handover
The record is the authority, and it never leaves the country.
Every model runs on hardware in Kenya, in the office's own possession. No document, name or photograph is sent to a foreign AI service — which is also the shortest answer a data-protection regulator can be given under section 48.
Progress, time elapsed and the contract sum are computed from the monthly reports themselves, one standing figure per month, and handed to the writer as authoritative. Where two documents disagree, the report states both and says they conflict.
A clerk of works sees the one project they answer for. Every deletion, download and sign-in lands in a hash-chained audit trail that shows any later edit.
A daily written on site survives a closed tab and a dropped connection; a second tap never files twice. Reports are written by a separate service wherever it is running, and by the app itself when it is not, so a restart never loses one in flight.
Bring the programme, we will read it.
Tell us how many projects, and what nobody currently has the hours to read. A walkthrough runs on your own folder, not a demo set.
- General and new work
- [email protected]
- Data protection · the DPO
- [email protected]
- Built by
- Exo AI · Mombasa, Kenya