People first · Technology in context
See the experience. Then build the system.
I’m Nazar. I tend to see everything as a system. I explore how technology can shape those systems around a better experience for the people using them.
In tech since thirteen.
Still asking what we could make.
The part that stays human
Without your direction, the tool fills the gaps with what is familiar.
A collection of tools is not yet a system.
How I see it
Design the response before the workflow.
I start with the person. How should they feel? What would create that feeling? What should they understand or do next? Those answers shape the experience. Then I design the workflow and choose the tools that can make it happen.
Where this way of thinking comes fromWhy I am building Life OS
More calm. Less to carry.
I wanted to enjoy the work and slow down, even as information and tools kept speeding up. Life OS is the private agentic assistant system I am building to hold context, run the workflows I define, and surface what needs my attention.
Privacy, private backups, and the freedom to change AI providers are part of the design. Life OS keeps evolving as I learn what actually helps.
More about Life OSCalm. Joy. Room to think.
Capture context. Run workflows. Monitor signals. Trigger automations.
Private. Privately backed up. Provider agnostic.
How an idea becomes a system
Start with the person.
Then follow the flow.
Bring an idea of your own. Move from the experience you want to create to the behavior, workflow and tools that can support it.
Name the experience.
What should a person feel, understand, or be able to do when this works?
Choose one person. Write one feeling and one practical change you want for them.
Trace what creates it.
Which moments and behaviors could bring about that change? Where does information or a human decision matter?
Sketch the person's path. Mark the choices and handoffs that shape their experience.
Design the workflow.
What needs to happen behind those moments, and which choices should stay with a person?
Map one useful path. Give each tool a role, then test whether it creates the experience you intended.
Something to take with you
Think of one idea you want to build. Type what the person using it should be able to do in the highlighted field.
“When this works, the person using it will be able to .”
For example: find the answer without searching five different places.
This is just for you. Nothing you type is sent or saved.
The Journal
There’s a story behind the system.
Choose by the attention you have, not by what’s newest.
A few honest answers.
A set of decisions about what someone should be able to do, how they should feel along the way, and how the parts work together to make that possible. The tools matter, but they come after that picture is clear.
AI can help me explore, build and connect the pieces. It does not decide what experience is worth creating. That starts with understanding the person who will use it.
People who want to build useful things and think more clearly about how to do it. You do not need to know every tool or have the whole plan before you start.
It is the private system I’m building to connect my ideas, projects and everyday work. I share selected decisions and lessons from the build, while the system and personal information stay private.
You can build a system shaped around your own life or work. I’m sharing how I think through the decisions, not offering my private system as a template to copy.
The longer thinking behind the work: decisions, experiments, things that needed rethinking, and ideas you might take into your own projects.
Not right now. I’m sharing the work because I want people to feel curious about what they could build, even if they’ve assumed they couldn’t do it themselves. That does not mean doing every part alone. It means knowing what you want to create, understanding the choices behind it, and being able to judge whether what a person or an AI builds actually serves someone. That is the human part I want to keep in view as we build with AI.