I design the systems that turn operational chaos into predictable intelligence. Where behavioural psychology meets workflow architecture, and raw data stops being a liability.
Current Focus: Process Architecture
Location: Pretoria, SA · Open to remote contracts
02 // Root Access
The Architecture of the Problem
Most organisations deploying AI are solving the wrong problem. They treat it as a capability gap, when the actual gap is architectural. The model is not broken. The system feeding it is.
I came to this through a specific obsession: understanding not just how systems process information, but how humans produce it, distort it, and act on it. That intersection — between machine logic and human behaviour — is where most AI implementations quietly fail, and where I work.
Before AI, closing that gap required a team. Today it requires the right architecture. That is what I build.
03 // The Logic
Where the System Actually Breaks
An AI model is only as competent as the workflow it enforces.
My work sits at the intersection of three disciplines most people treat as separate.
1.The Structure — Information architecture that imposes order on fragmented operational data
2. The User — Behavioural psychology that accounts for how humans actually produce and distort information
3. he Tool — Workflow automation and generative AI that amplifies the output of both
The result is not an AI deployment. It is a system that knows when to trust its own outputs — and when to suppress them.
I act as a translator between the rigid logic of machine code and the fluid nuance of human psychology.
04 // Output
Deployed Work
[CORE_PROTOCOL :: RUNNING]
Continuum: AI Progress Intelligence & The Hallucination Brake
The Business Problem: Stakeholders at Continuum, an early-stage development startup, were drowning in data but starving for the truth. Standard project updates showed activity but failed to prove progress, leaving leadership unable to distinguish between a workflow that was moving and one that was simply busy. The AI reporting layer running on top of this environment had no way to know the difference either — so it didn't flag it. It reported confidently on a foundation no one had verified.
The Architectural Solution: A state-aware system designed to manage data entropy from the source. Rather than filtering bad data out after the fact, the architecture intercepted it at the point of entry and structured it into verifiable truth anchors before any model consumed it.
01
Input Variables
Normalises raw administrative and structural system data — commits, state changes, logged hours — into a set of verifiable truth anchors the system can reason against.
02
The Ghost Filter
Identifies tasks that simulate work without producing measurable output. Ephemeral activity that inflates velocity metrics without moving anything forward gets flagged before it enters the reporting layer.
03
Efficiency Monitor
Tracks resource expenditure against concrete deliverables in real time. When time spent diverges from estimated hours, the system flags it immediately rather than surfacing it in a retrospective review.
04
Heartbeat Monitor
Detects task stagnation disguised as active progress. Work that has stopped moving but remains marked as in-progress gets surfaced to management automatically, regardless of task size or priority level.
05
The Hallucination Brake
The system's trust mechanism. A Global Confidence Score continuously evaluates the integrity of the underlying data and actively suppresses AI-generated summaries and projections when that data is weak, conflicting, or performative. The system does not just report on what is happening. It tells you how much to trust what it is reporting.
Currently mapping organizational bottlenecks and designing new human-AI workflows. Next system iteration pending deployment.
In Development
05 // System Diagnostics
Workflow Optimizer
Most workflow problems follow a pattern even when they feel unique. The symptoms vary — missed deadlines, unreliable reporting, AI outputs no one trusts — but the structural failure underneath is usually identifiable.
Describe your bottleneck below in plain language, as specifically as you can. The system will return a structured diagnosis of the failure point and a recommended architectural fix.
This is not a chatbot. It is a diagnostic.
audit_protocol.exe
>
06 // Handshake
Let's Build Something
If your team is moving faster than its processes, or you have deployed AI and cannot verify what it is telling you — that is the problem I am built for.
Let's look at the architecture.
