AI capability
Connect natural language and model output to product behavior.
Chat To Do · Todaktodak
I connect AI capabilities to product flows, then carry them through reliable operations and reusable knowledge.

AI Service Engineer
I go beyond model output, turning it into services that teams and users can depend on.
See the workConnect natural language and model output to product behavior.
Chat To Do · Todaktodak
Make frontend, backend, and AI work as one user journey.
PinLog · AlgoSu
Observe resources, failures, and logs; design safe delivery paths.
PinLog · AlgoSu
Preserve project decisions and outcomes as verifiable evidence.
Graph RAG Second Brain
SELECTED WORK
Five projects trace a path from natural-language features and generative AI to team operations, solo products, and reusable knowledge.
A place journal that preserves why a place mattered and retrieves it through natural language.
Single VM / 4 vCPU / 15 GiB
Team AI Platform
DELIVER
GitHub Actions · Argo CD
RUN
k3s · containerd
OBSERVE
Sentinel · Human decision
PinLog API → Atomic Queue → GPU Worker → Result
Problem
Frontend, backend, AI, and observability had to share one 4 vCPU / 15 GiB VM.
Contribution
Identified Docker and cri-dockerd as CPU bottlenecks, moved to containerd, and built Helm/ApplicationSet GitOps and observability.
Result
Standardized delivery, caught a real sync failure, and connected a separate GPU server through a safe asynchronous queue.
KEY IMPLEMENTATION
Optimize
Measured CPU throttling → containerd
Deliver
Immutable images, infra PRs, Argo CD
Observe
Sentinel summarizes evidence; people act
Async AI
Atomic claims, requeue, bounded failure
VERIFIED SIGNALS
AI search quality and keyword fusion were advisory work and are not claimed as direct implementation.
An AI review service that explains complexity, readability, and improvements beyond correctness.
SUBMISSION PIPELINE
Code in, actionable review out
ANALYZE
Complexity and approach
REVIEW
Role-based AI review
SYNTHESIZE
Grounded improvements
Problem
The challenge was not one AI response, but operating the whole review flow through failures and retries.
Contribution
Separated review stages, designed async jobs, retries, and state tracking, then deployed and operated it on OCI.
Result
Extended a solo AI project from build and deploy into ongoing, evidence-driven operations.
KEY IMPLEMENTATION
Review Pipeline
Role-based reviews and synthesis
Resilience
Async state, retries, visible failures
Operations
Prometheus, Grafana, Loki
OPERATING PRINCIPLE
Deployment is the beginning of operations, not the end.
A local knowledge system linking documents and conversations as claims and evidence, reusing only human-approved facts.
EVIDENCE GRAPH
Source → Claim → Evidence → Answer
Source
Claim
Evidence
Verified answer
When evidence is insufficient, the system abstains.
Problem
As documents grew, current facts mixed with stale claims and provenance became difficult to verify.
Contribution
Separated sources, entities, claims, and evidence while preserving review status and provenance paths.
Result
Generates portfolio and application material from verified evidence and abstains when support is insufficient.
KEY IMPLEMENTATION
Ground
Claims and evidence linked to sources
Review
Reuse only human-reviewed facts
Regress
Retrieval and answer regression checks
OPERATING PRINCIPLE
Choose a verifiable abstention over an unsupported answer.
AI SERVICE FOUNDATIONS
Chat To Do connected language to product actions; Todaktodak combined multiple generative models into one service flow.
Connected multiple generative AI models into one user journey.
An emotional support service generating a four-panel comic, music, and sentiment analysis from a journal entry.
MY ROLE
AI resources & pipeline contributor
WHAT IT TAUGHT ME
Learned that product flow and collaboration matter as much as individual models.
Turned natural language into executable product actions.
A conversational task service connecting user intent to concrete product functions.
MY ROLE
AI resources & pipeline contributor
WHAT IT TAUGHT ME
Moved beyond answer generation to systems where user language triggers real product behavior.
HOW I WORK
Across projects, the method stays the same: start from the user problem and preserve operational evidence.
Define where users get stuck before choosing technology.
Connect model output to concrete product behavior.
Observe failures, resources, and logs; improve from evidence.
Preserve decisions and outcomes as verifiable knowledge.
Automation handles repetition; people retain responsibility for operational decisions.
Documenting lessons learned from practice.
Open to hiring inquiries, tech discussions, and collaboration.