Frame the real problem
Start from the repeated friction, the existing workflow and the evidence that software should exist at all.
AI agents, automation, developer tools and focused software systems — designed, built and documented by one independent builder.

Current experiments focus on long-running agent workflows, durable project state and practical automation that turns repetitive development work into reusable systems.
Explore DeepLoopMinder

An AI-native multi-agent software development runtime focused on project control, durable state and external coding workers.

A local-first context packaging tool that turns messy customer chats, screenshots and attachments into traceable issue packages for coding agents.

An experimental Android agent that turns natural-language goals into screen actions through accessibility APIs and LLM tool calling.
The goal is not to add AI everywhere. It is to identify where software can remove repeated effort, then make that software explicit, observable and maintainable.
Start from the repeated friction, the existing workflow and the evidence that software should exist at all.
Prove the workflow with the fewest moving parts before adding orchestration, persistence or model complexity.
Keep context, decisions and progress observable so long-running software can be resumed, inspected and trusted.
Turn the useful prototype into maintainable software with clear boundaries, tests, documentation and automation.
Design and implementation of practical agent workflows, tool use, task routing and durable project state.
Replace repetitive operational work with focused automations, data pipelines and small tools that remain understandable.
Fast, maintainable websites and focused web applications with clean information architecture and strong technical foundations.
Most current experiments sit one layer below the chatbot interface: orchestration, context, durable state and the operational tooling that makes model-driven work dependable.
Long-running agent workflows, delegation and durable execution without losing project state.
Reusable issue packages, structured evidence and compact context that survives across tools and sessions.
Replacing repetitive software work with observable systems that remain understandable to a human operator.

The public Yachenyi site treats crawlability, speed and machine-readable structure as architecture constraints rather than launch-time polish.

Long-running software work becomes more reliable when agents operate on explicit projects, tasks and artifacts instead of a single disappearing chat context.