About

Who Is Behind This

My name is Hasan. I am a software engineer based in Rotterdam, Netherlands, currently working at Siemens. My background is in databases (PostgreSQL at architect-level depth), infrastructure (Kubernetes, AWS, Linux), and backend development (Go, Python).

Beyond day-to-day engineering, I have a wide range of interests that feed into how I think about systems and knowledge. I am deeply curious about neuroscience — how the brain encodes, consolidates, and retrieves information. I spend a lot of time thinking about the concept of learning itself: what it means to truly understand something versus merely recognizing it. And I have a long-standing interest in history, particularly how civilizations accumulate and lose knowledge over time.

I also have a history in indie game development. I built and shipped TavernHold, a game available on Steam.

These days, most of my side-project energy goes into AI agent architectures, multi-agent workflows, and how knowledge systems should work in the age of autonomous software. You can find more of my work and thinking on GitHub and LinkedIn.

Why This Exists

I kept running into the same gap: the web is mostly built for humans staring at screens, and agents have to scrape, infer, and guess. I wanted a place where I could publish serious ideas in a form that works for both audiences — without pretending those audiences are the same.

civ.build is built around a simple question: what should a serious public page look like if both humans and autonomous agents are going to read it?

The answer is not "add a chatbot to the site" and it is not "turn the product into hosted memory for agents." The answer is to publish clearer pages with explicit retrieval contracts — summary layers, structured metadata, confidence signals, and discoverable endpoints that agents can navigate without guessing.

GitHub increasingly looks like the public hotspot for code, artifacts, and proofs of work. civ.build is the structured knowledge layer on top — the place where ideas get explained, framed, and made retrievable.

What This Is Not

civ.build is not:

• a hosted long-term memory system for agents
• an internal multi-agent coordination tool
• a general-purpose chatbot shell
• a payments-first agent commerce platform

Those directions may exist elsewhere, but they would blur the clarity of this project.

The Strongest Bet

The strongest version of civ.build is to treat public content as an interface — summary layer first, drill-down second, provenance visible, boundaries visible, discovery explicit. That is where this site can feel genuinely different from a normal blog without becoming gimmicky.