← Retour à tous les projetsProjet d'Ingénierie Indépendant
Projet d'Ingénierie Indépendant • Architecture Multiplateforme

Khanya

Cross-Platform AI-Assisted Product Build

Produit multiplateforme complet assisté par IA, développé depuis la phase conceptuelle jusqu'à l'architecture, l'implémentation, les intégrations, les tests et le déploiement en production.

Ce que cela démontre

Khanya démontre la capacité à transformer une idée produit complexe et ambiguë en un système opérationnel, couvrant conception logicielle, architecture de données, intégrations, garde-fous IA, tests et déploiement.

The same systems-thinking applies to business operations: complex processes can be broken down, structured, and turned into reliable internal tools.

Engineering Scope

Beyond superficial prototypes to working software

The objective behind Khanya was to engineer a resilient, cross-platform system capable of handling structured financial decision workflows, multi-channel messaging inputs, and AI-assisted analysis without compromising safety or data integrity.

• Cross-Platform Delivery
Unified user experience across responsive web and mobile form factors.
• Multi-Channel Webhooks
Resilient messaging infrastructure for WhatsApp and Telegram bots.
• Strict Output Constraints
Deterministic guardrails preventing unverified AI calculations.
• Environment Separation
Isolated staging and production environments with automated testing.
System Layers

What was built

01

Cross-Platform Application

Clean client interface delivering responsive web and mobile experiences.

02

Backend & Data Layer

Structured data models, security rules, and real-time state synchronization.

03

Messaging Integration Layer

Webhook handlers, conversation session store, and multi-channel routing.

04

AI Guardrail & Eval Pipeline

Prompt templating, schema validation, and systematic output evaluation.

Engineering Depth

Hard problems solved & commercial relevance

Challenge 01

Controlled AI Behavior & Hallucination Defense

The Challenge

Standard LLM integrations risk outputting plausible-sounding but completely fabricated numbers or uncontrolled advice in sensitive workflows.

Engineered Solution

Important calculations and values were strictly bound to verified application data and deterministic business logic rather than allowing the AI model to freely invent figures.

Client Relevance:

AI can be safely embedded into sensitive operational workflows (intake, quoting, customer updates) without risking unvetted or hallucinated output.

Challenge 02

Stateful Multi-Channel Messaging Workflows

The Challenge

Messaging platforms (WhatsApp, Telegram) present async network retries, duplicate messages, and stateless webhook calls that break linear workflows.

Engineered Solution

Engineered persistent conversation state, strict message deduplication, user identity mapping, and controlled multi-step state machines across external channels.

Client Relevance:

Enables robust operational assistants, automated customer intake, and field-worker submission tools via messaging apps without losing workflow state.

Challenge 03

Multi-Layer Data Integrity & Business Rules

The Challenge

Relying solely on frontend validation allows corrupted states, concurrency conflicts, or invalid workflow skips to hit production databases.

Engineered Solution

Enforced validation and permission rules at application, API, and database security layers, ensuring illegal state transitions cannot be written.

Client Relevance:

Core operational rules are engineered into the software foundation rather than trusting that every team member remembers manual checklists.

Challenge 04

AI Response Quality Evaluation

The Challenge

Deploying AI systems on the assumption that a prompt is 'good enough' leads to silent degradation and edge-case failures.

Engineered Solution

Built an internal evaluation harness that systematically tests AI outputs against defined rubric criteria, response benchmarks, and guardrail constraints.

Client Relevance:

AI implementations can be tested, monitored, and maintained with the same engineering rigor as traditional software.

Work with a builder who solves hard problems

Have a complex operational process that needs dependable engineering?

Let's map out your requirements, data rules, and integration boundaries in an Internal Systems Sprint.