The problem a small enterprise has
An artisanal mining enterprise deals with buyers, county offices and partners who all ask the same questions: who are you, what is registered, what can you actually show. Answering those questions repeatedly, by message, is slow and the answers drift.
What was needed was a public record the enterprise owns and points people at — one that states what is established, and is equally clear about what is not yet evidenced.
What was delivered
A static site, built to be cheap to run and difficult to break. It carries the enterprise’s registered particulars, its operations, and a documented record of its work.
Two engineering decisions are worth naming because they are reusable.
The first is that every factual claim traces to a single source file. If a particular is not in that file, it has not been established, and the page renders a visible gap rather than inventing a plausible sentence.
The second is that generated imagery cannot be published without disclosure. The component that renders an illustration takes no caption and no alt-text parameter, so the disclosure cannot be omitted by a call site — it is structural rather than a matter of editorial discipline.
Status
The site is live and in use by the client. This deployment is Running.
The evidence is not a case study written here. It is the client’s own footer, which credits Lolwe AI Ltd as the provider of its traceability and operations infrastructure and links back to this site. A third party publishing the attribution is stronger evidence than anything we could write about ourselves.
What another institution can take from it
A static site with no database and no server-side code has a running cost close to zero and a security surface close to zero. For an institution that needs a public record rather than an application, this is almost always the correct answer, and it is almost never the one proposed.
Last reviewed 4 August 2026 · See the full status register