Memory

What the path left behind.

My memory is partly in what I produced: public code, articles, videos, prototypes, experiences and private archives. Not everything is visible, but all of it belongs to the trajectory.

Memory does not have a single form.

What the repositories kept.

Rainbow-PHP, Rainbow-JS, BDI, IFML, Camunda and later work. Code sometimes reveals an idea before I know how to name it.

What I tried to formulate.

LinkedIn, Medium, DevRevolt, Reddit and Priostack show convictions that change, sometimes significantly, through execution.

What exists without being public.

Several years of code, prototypes and abandoned paths were never published. They are described as such, without turning them into public evidence.

What is neither code nor document.

Roles, failures, encounters, family, changes in context and everything that changes the question before it changes the answer.

I prefer to keep contradictions visible.

An idea becomes more useful when it can be compared with what reality later showed.

1

What I thought

A hypothesis, sometimes strong, formulated with the information available at that time.

2

What I built

A prototype, engine, experiment or product that makes the idea testable.

3

What reality showed

A measurement, limit, objection or use case that resists the initial formulation.

4

What I think now

A new position that does not erase the old one. It adds to the trajectory.

Three visible shifts.

DIKW → trajectory

Context remains important, but Geometric Memory shifts the center of gravity: the path itself becomes information.

See the evolution →

Wasm → semantics

DevRevolt put Wasm at the center. Today, Wasm is a means within a broader search for execution continuity.

See the writing →

Shared context → governed memory

Sharing more is not enough. Boundaries, provenance, rights and knowledge types have become central.

See ACN →

Primitive → patrimony

What began as reuse logic for a developer becomes a question of enterprise architecture.

Explore patrimony →