Story map
ckik.dev is becoming the public map of my founder/operator story: AI commentary, startup life, DHC, KAi, persistent memory, old technical scars, and the decisions that happen while building for real.
The story can be personal, but claims need clean sourcing.
I treat public proof, owned company narrative, and private memory as different materials. They can support each other, but they are not interchangeable.
The DHC Architect page is the company-side story map. Independent or official sources carry the heavier proof load when a claim needs to stand on its own.
Open
The earliest thread is self-taught engineering under pressure, then a life of building systems that adapt to people.
Why it matters now: It explains why DHC and KAi are not a sudden pivot. They sit on top of a much older pattern.
Proof: DHC Architect timeline, public identity page
Open question: Which origin story can be told first without flattening it into generic founder mythology?
Read the About pagePublic proof available
Before AI companionship, the work was performance, schedulers, Android, Linux, and making phones feel better without users needing to understand why.
Why it matters now: This is the technical bridge between optimization, adaptation, and persistent AI systems.
Proof: CompassList, IONIC AI public record
Open question: Which technical lesson from those years still applies to agents and memory today?
Read the CompassList coveragePublic proof available
Korea became the operating base because the market, institutions, and timing made the AI companion bet feel executable.
Why it matters now: This arc connects the visa, Seoul, DHC, KAi, and the founder reality behind moving a company across borders.
Proof: MSS, Platum, DHC
Open question: What did the move force Carlos to become that would not have happened from comfort?
Read the MSS materialActive
The central bet is that serious AI companions need continuity, privacy, and memory that serves the person instead of farming attention.
Why it matters now: Every major AI platform is moving toward agents, personal context, and persistent workflows. The memory layer is becoming the product.
Proof: DHC, ckik.dev analysis, future founder essays
Open question: How much of the product philosophy can be public without exposing implementation strategy too early?
Read the current thesisActive
The daily follow loop is not perfection. It is pressure, decisions, exhaustion, small wins, mistakes, and the discipline to keep moving.
Why it matters now: This is where ckik.dev can become more than AI commentary: a live operator log with useful lessons from inside the build.
Proof: daily posts, future field notes
Open question: Which real constraint from today can be turned into a useful public field note?
Read recent postsStarting
Public decisions create trust when they record context, tradeoffs, expected outcomes, and later review.
Why it matters now: AI moves fast enough that judgment matters as much as prediction. A dated decision trail makes that judgment visible.
Proof: future decision memos
Open question: Which current choice is safe and meaningful enough to log publicly first?
Start with the current mapInterview needed
The painful material only works if it becomes principle, not score-settling.
Why it matters now: Carlos has uncommon lived material, but the public version needs timing, filtering, and a clear lesson.
Proof: interview-first, verify before naming
Open question: Which almost-won moment can be told without harming people, deals, or future options?
Read the public baseline