Work in the open, work in progress

Work you can check.

Note

We publish what can be verified and label the rest by its real state. Nothing here is a promise.

How we build

Deterministic where correctness is knowable. Bounded where it is not.

Deterministic code decides what can be known. A model handles only genuine ambiguity, on the smallest evidence packet, and may abstain. A person keeps authority over consequential decisions. Every answer traces back to its source. The same doctrine applies to every entry below, open or in build.

Local-first
Runs on the customer's hardware; the cloud is optional and delayed.
Evidence before assertion
Every figure and decision traces to its source record.
Human authority
Consequential decisions are prepared by the system and made by a person.
Record linkage
Open source

Joinless.

Link records that share no key, and know what it costs to do it on a phone.

Two systems hold records about the same business and agree on nothing that can be joined on. Joinless links them anyway, on the strings themselves, and reports what that costs.

It ships with a benchmark rather than a claim. On Arm64, matching names on device, the classical matcher beat both embedding arms on F1 while using a fraction of the memory and latency. The benchmark is in the repository so the result can be disputed with evidence.

MIT licensed, on GitHub.

What it can do
  • Match business names across registers, statements and invoices with no shared identifier
  • Choose the matcher by measured F1, memory and latency, not by fashion
  • Run on CPU, offline, inside your own environment
github.com/raheebwa/joinless ↗
Business identity
Public, v0.1.0

TrustScore Atlas.

One source-cited view of who a business is, across the public registers that never agreed.

Public business registers in Uganda and Kenya describe the same companies in different words, at different times, with different identifiers. Atlas harmonises them into one view and keeps the disagreement visible rather than averaging it away.

Every attribute carries the register it came from and the date it was read, so an answer can be checked rather than trusted. Agents query it through typed, read-only tools.

v0.1.0 is public.

What it can do
  • Look up a business across registers and see where the sources disagree
  • Every attribute carries the register and date it came from
  • Query it from an agent through typed, read-only tools
github.com/raheebwa/trustscore-atlas ↗
Financial evidence
Architecture case study

Consylr.

Reconstruct what happened from the records you actually have.

A finance team’s real evidence is a bank statement, a spreadsheet somebody maintains by hand, and a folder of receipts. None of them share a key.

Consylr links them without one. Deterministic rules do the matching wherever correctness is knowable; a model is called only where the records are genuinely ambiguous, on the smallest packet of evidence, and it is allowed to abstain. Every reconciled item keeps the source lines that justify it, so the result is an audit trail rather than a number.

It runs on the customer’s own machine. Nothing leaves the building by default.

What it can do
  • Ingest the files a finance team already has; integrations come later
  • Deterministic matching first; a model only where the records are ambiguous, and it may abstain
  • Every reconciled item traces to the source lines that justify it
  • Runs on the customer's own machine; nothing leaves the building by default
Commerce OS
In development

Stoowa.

One system to run the whole shop, the counter and the online store, on one inventory.

Stoowa is an offline-first point of sale for Ugandan shops: the counter and the online store on one inventory, working with or without a signal. In development.

stoowapos.com ↗
Credit passport
In build

TrustScore.

A credit reputation the trader owns and carries — trusted by any lender, built without paperwork.

A trader can move goods reliably for ten years and still not be able to borrow a hundred dollars to restock — not because they are not creditworthy, but because nothing has ever recorded that they are.

TrustScore turns the proof that already exists into a score a lender trusts. The trader owns it, decides who may see it, and carries it from one lender to the next. No bank statement, no salary slip, no starting over each time.

For the lender, it is a decision made in seconds. For the trader, it is the first time their reputation counts as collateral.

What it can do
  • Gives traders with no bank record a credit standing lenders can actually trust
  • Nothing happens without the borrower's approval — every check is theirs to allow
  • One reputation that travels with the trader, from one lender to the next
  • Turns a phone number into a lending decision in seconds — no forms, no branch visit
trustscorehq.com ↗
Study companion
In closed testing

Somedser.

Notes in, study set out — summary, flashcards, and a quiz drawn from the same upload.

Most people turn a long document into a study session by hand — re-reading the same pages, scribbling cards, writing their own practice questions, and hoping the questions cover what they actually need to know.

Somedser does that work in one go. A learner uploads their notes — a chapter, a course PDF, a Word document — and a few seconds later has a summary, a deck of flashcards, and a practice quiz drawn from the same source.

The study set stays on the device after that, ready offline. Nothing leaves the device without an explicit ask. The learner does the studying; the busywork is done.

What it can do
  • Turn a chapter of notes into a study session in under a minute
  • Flashcards, summary, and a quiz built from the same upload — no second pass
  • Study sets stay on the device, ready offline once the work is done
  • Asks before anything leaves the device — every send is the learner's to allow
somedser.com ↗
Rentals OS
In build

Let & Rent.

One system for the whole tenancy — rent, leases, and repairs, with landlord and tenant on the same record.

Renting a home in East Africa still runs on spreadsheets, WhatsApp threads, and paper receipts. A landlord keeps rent in one place, repairs in another, and the tax owed in a third — and the tenant has nowhere to see a balance, pay what is due, or keep a signed lease on file.

Let & Rent makes it one system. Rent, leases, maintenance, and tax sit on a single record the landlord and the tenant both read from. Rent collected is rent invoiced. A repair logged is a repair tracked through to the person who fixed it and was paid. Nothing lives in a side conversation that no one can audit later.

It is built for how renting actually works here — UGX and USD, property and rental-income tax treated as first-class parts of the ledger rather than a year-end scramble, and a tenant experience that, for once, has moved in twenty years.

What it can do
  • Collect rent and reconcile every payment without a spreadsheet or a paper receipt
  • Give tenants a place to pay, see their balance, and keep a signed lease on file
  • Log a repair and track it through to a provider who did the work and was paid
  • File property and rental-income tax from the same ledger the rent runs on
letandrent.com ↗

Records that do not reconcile? That is the work we take.

Get in touch