Short thoughts, half-formed ideas, and things worth noting.
Naming a phase is not the same as discovering one. "Graph engineering" is the
current label for wiring agents into explicit execution graphs. The essay
credited with coining it has no archived copy and no exact-phrase hits. The
term appears zero times in the survey literature, which calls it flow
engineering.
The techniques are older than the label: state machines, DAGs, workflow
orchestration. What changed is what sits inside the nodes. A probabilistic
component fails quietly, and that is what makes the old toolbox interesting
again.
"AI-native" sounds like a model choice. It is an ordering choice. When the
model produces the value, the screen is an output, not a spec, so it cannot
come first. You start with the problem, the model and its context, the tools,
and the evals. The interface comes last, and contextual.
UI still matters most. Everyone rents the same models, so the surface that
lets a person aim one and trust the result is the moat. The UI did not die.
It just stopped going first.
If you plan to keep Markdown as your source of truth and move to Strapi later,
model the body as a Rich text (Markdown) field, not the newer Blocks
field. Blocks stores a structured JSON tree, and there is no built-in
Markdown-to-Blocks conversion, so you would have to write your own transformer
at migration time.
Markdown round-trips as a plain string. One less thing to fight when the import
script runs.
Starting a notes section. The blog is for things I want to think through in full;
this is for the smaller stuff that never grows into an article but is still worth
writing down. Half-formed ideas, a snippet that saved me an hour, a sharp line
from something I read.
The rule I am giving myself: if it needs a title, it is a blog post. Everything
else lives here.