Drive and Project List

This is a snapshot of the projects I am choosing to make visible outside my internship work at CMA CGM Air Cargo. I keep this list because ideas are cheap when they stay private. The point is to expose what I am building, what I am postponing, and what kind of life I am trying to design around action.

One-minute version

I want to create my own opportunities instead of waiting for a hierarchy to validate them. The common thread is simple: proof of life, then proof of work, then proof of study.

Active Now

ProjectCurrent roleWhy it matters now
International job searchActive priorityI am looking for VIE and job opportunities abroad, with a particular focus on Argentina.
This public vaultActive priorityPublishing forces clarity. It turns a private collection of notes into a visible body of work.
OpenClaw workflow automationActive build trackI want to automate parts of my engineering and job-search workflows instead of manually repeating low-leverage tasks.

Paused, But Not Abandoned

ProjectStatusReason
FrandetourPaused conceptThe idea is aligned with my values, but it asks for time, field work, trust, and operational depth.
Data sovereignty platform AILong-term ideaThe direction still matters to me, but it needs more technical and strategic maturity before it should become a main focus.

The Common Thread

I am bored by systems where responsibility is constantly transferred upward, sideways, or into procedure. The projects that interest me are the opposite: they force ownership. They make me answer for what I claim to believe.

That is why the same pattern keeps appearing across very different subjects:

  • Work on things where I can be exposed to real consequences.
  • Build tools and notes that compound instead of disappearing after one use.
  • Use the public site as a forcing function for clarity.
  • Create optionality through skills, proof, and network rather than waiting for permission.

Next Concrete Actions

  • Keep turning this site into a coherent public portfolio of notes, projects, and thinking.
  • Build a VPS-based workflow that reduces the repetitive work in my job search.
  • Keep developing my network so that time is not consumed only by applications.
  • Revisit Frandetour only when I can give it the operational attention it deserves.

What Stays Private

Some material should not be published: internship details, raw vault fragments, and unfinished ideas that depend on people who did not choose to be part of this site.

The point of publishing is not to expose everything. It is to make the useful part legible.