Trajectory
How I moved from self-taught developer to software architecture, technical and solution architecture, and BPM. How code, systems and models changed at the same time as I did.
Follow the path →
Ousmane Sene · personal and technology notebook
I build to understand.
My personal, professional and technological trajectories are not three separate stories. They describe the same path, from my first lines of code in 2010 to Qubit, Priostack and a broader view of enterprise patrimony.
Flow of Meaning.
Current position · 22 October 2026Today I am trying to understand how an organization can preserve what it knows how to do, execute it, observe it and transmit it without losing meaning along the way.
Three doors
Trajectory. Memory. Patrimony.
Three words that describe my life, my work and my systems.
Memory
What the path left behind: public code, articles, prototypes, experiments, mistakes, corrections and periods of work that remained private.
Explore the traces →Patrimony
What I want to preserve and transmit: my family, my intellectual work, Qubit, Priostack and, at organizational scale, what an enterprise already knows how to do.
Explore patrimony →Flow of Meaning
Meaning does not live in a single layer.
It emerges from the relationship between what motivates, what is modeled, what executes, what is observed and what is retained.
Trajectory
The path explains how an intention, a person or a system arrived at its current state.
→
Memory
Traces from the path become precedents, evidence and sometimes counterexamples.
→
Patrimony
What deserves to last returns to the system in reusable and transmissible form.
Flow of MeaningFrom intention to execution, then from experience to what we preserve.
What I build today
Several objects, one research path.
Technical depth now lives on dedicated pages. The home remains a map.
Qubit
A deterministic, notation-agnostic execution foundation designed to preserve continuity between model and execution without exposing proprietary internal mechanisms.
Understand Qubit →Priostack
Where architecture, processes, decisions, agents, context and execution come together as reusable enterprise patrimony.
See current work →Geometric Memory
A way to shift attention from the current state to trajectory, precedents and what execution history can contribute to reasoning.
Explore Geometric Memory →Living patrimony
Moving from reusable technical primitives to capabilities, models, decisions and experiences that an enterprise can actually capitalize.
Explore the vision →Journal
The current endpoint remains provisional.
The journal lets the site evolve without rewriting the past.
Personal patrimony
Not everything that matters lives in Git.
My patrimony is not limited to what I have written or built. It also includes what I want to protect, share and transmit in my personal life.
Family belongs to this story, even if not everything is meant to become public.