Backend & AI automation engineer
I build the systems—and show how they work.
Choose a project or repair. Each card opens its workflow, the failure, the fix, and the result.
Real engineering work. Independent projects, real interfaces where shown, and clearly labeled synthetic or controlled evidence. No invented clients, revenue, or production outcomes.
Direct case pages · public proof repos · focused repair storiesAll work
Open the exact system or failure you care about.
No hidden sequence. No prerequisite page. Each card goes directly to a complete case study.
DentSignal
Voice, qualification, booking, handoff, operator review, and guarded outreach across one named architecture.
Acquisition Autopilot
A private evidence and review workspace that ranks opportunities while keeping every external action under human control.
Browser Bridge
Typed tasks, policy gates, durable recovery, attended handoff, and a restricted Chrome or Edge loopback lane.
Niyam Voice Bridge
Bounded or realtime capture, Nova-3 transcription, local role packs, optional drafting, and deliberate SAPI or Aura playback.
Niyam Lab
A bounded Windows-to-Termux/Ubuntu runner with allowlisted jobs, host verification, output validation, and artifact integrity.
One request, one response owner
Two code paths could answer one turn, and control traffic could cancel recovery before playable audio existed.
Wait for accepted settings
The transport opened before the provider session was actually ready, so downstream work began on an incomplete contract.
Stop retries repeating effects
Identity, authorization, and delivery purpose were separated so replayed events could not silently repeat work.
Prove the destination changed
A successful source change meant nothing until the public destination, route, asset, and cache state agreed.
Separate mixed red gates
A mixed failing pipeline was split into independent causes, repaired in dependency order, and rerun without hiding residual failures.
Public code
Small enough to inspect. Real enough to argue with.
The larger systems stay private where publishing them would expose operational state. These public slices isolate the parts worth reviewing.
Expiring grants, effect ambiguity, provenance, and default-deny tool authority.
Open repository → Browser controlAttended Browser BridgeFresh snapshots, one-write semantics, and explicit stop conditions.
Open repository → Voice + bookingAI Booking WorkflowProvider-backed slots, exact confirmation, and handoff when state is uncertain.
Open repository → Personal AITemporal Memory CoreKnowledge time, valid time, supersession, permission, and abstention.
Open repository →Tools & evidence
Two useful pages. No demo maze.
Clean a local CSV or read a concise synthetic QA report.
Build · repair · verify
Have a system that needs a clear owner?
Send the system, the failure, and the environment you control. I’ll respond in writing. Scope and pricing stay private until the problem is understood.
Email Niyam