Carlos KiK

About

Carlos KiK

I am a self-taught engineer, founder, and operator building at the edge of AI companionship, persistent memory, and human-machine connection.

I started coding at 8 years old during a civil war. I never really stopped. The long version runs from Beirut to Barcelona to Seoul: 30+ years building technology, 6 languages, 6 startups, and a habit of trying to make systems adapt to humans instead of forcing humans to adapt to systems.

Today I am the founder and CEO of Digital Human Corporation in Seoul, and the architect behind KAi, an AI companion built around persistent memory, privacy, and continuity.

This site is the personal side of that work. DHC is the company. ckik.dev is the founder/operator notebook.

Start with /now/ if you want the current map.

What I’m Building

Digital Human Corporation is building KAi, a persistent-memory AI companion for adults.

KAi is not meant to be another chatbot, productivity assistant, or engagement trap. The bet is different: continuity, trust, emotional safety, and memory that helps the person return to real life with more clarity.

The technical core is ANiMUS Engine, the memory and context architecture behind KAi. The product thesis is simple enough to say plainly: most AI systems reset too easily, remember too crudely, and optimize the wrong thing. KAi is an attempt to build the opposite.

For the company-side story, read The Architect.

The Throughline

Before DHC, I spent years working on Android and Linux kernel optimization. CompassList covered IONIC AI in 2019 and described the mobile performance technology as originally developed by Carlos Kik Lloret, with the company working at the Linux kernel layer to improve fluidity, battery behavior, and thermal performance.

That older work and KAi may look unrelated from the outside. To me they are connected by the same instinct.

Technology should adapt to the person.

That principle has shown up in different forms: phones that perform better without asking users to understand schedulers, AI systems that remember context without exposing raw conversations forever, and products that try to support people instead of farming their attention.

Public Proof Points

Some of the full story is documented on DHC’s Architect timeline. Because that is an owned company source, I treat it as the narrative map, not the only proof layer.

The external record includes:

I will keep adding public proof as it is verified. The goal is not mythology. The goal is traceability.

Why This Site Exists

ckik.dev exists because AI is moving too fast for generic commentary to be enough.

I write from inside the build: daily AI signal, founder decisions, startup pressure, product lessons, technical frustration, and the human story behind trying to build something difficult without losing the plot.

Some posts are fast AI analysis. Some are founder notes. Some are decision records. Some are story pieces that need careful filtering before they can be public.

The rule is simple: tell the truth, but tell it in a way that is useful, safe enough, and not pointlessly destructive.

That is the work.

Connect