papers, notes, public artefacts. signed under the khwarizmi imprint. every paper is footnoted to source; the canonical copy is held by the client where the work was commissioned. grouped by topic.
the runbook is the deliverable; the platform is the by-product. what a runbook must contain for the next reader to operate the system without the author in the room.
what a technical due-diligence read covers in four weeks: what to read, in what order, and what a diligent reviewer declines to put their name to.
how to scope a technology engagement to avoid riba while remaining commercially legible. four contract shapes, worked through.
the canonical statement of the firm’s method. three months to complete, three weeks to hand over, then we leave. with the eight failure modes we have actually observed.
a short field note. the difference between a slide deck and a working paper, and why we will only ship the latter — even when the board would prefer the former.
what ifrs s2 actually demands of a south african data estate. the disclosure requirements, the local adoption trajectory, the assurance that follows — and why the binding constraint is lineage, not reporting.
a survey of available residency postures: afrihost, xneelo, oracle joburg, hyperscaler sa regions, in-house. cost, latency, audit posture. tabled by sector.
would the team notice if you took the tool away on a tuesday morning? a test for whether ai enablement landed — and the design choices that decide it in advance.
how far does a halal certification actually travel from feedlot to retail, and where does it break? a research design for tracing certification claims across three provinces.