Engineering notes
Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: graph-engineering
Graph Engineering for AI Coding Agents: Context, Contracts and Repair
What a contract-driven agent graph taught one developer: scoped context, deterministic validation, targeted repair, and when the extra compute cost is justified.
11 min readGraph Engineering Explained: Nodes, Edges and LangGraph in Practice
Is graph engineering actually new? Prompt, context, harness and loop engineering compared, what makes something a graph, and an 11-node LangGraph agent.
4 min readFrom Loop Engineering to Graph Engineering: Building Reliable
From loop engineering to graph engineering: the agent loop as an engineering unit, where a single loop breaks down with state tangles, and why graphs help.
22 min read
FAQ
About these articles
Yes. Each piece is an original English rewrite prepared for this site. Structure and code examples follow the source material; prose is rewritten and checked for overlap before export.
English is the source. Another language is shown only when that translation body exists. A missing or empty translation stays in English, including on a localized URL.
New drafts land in the publish queue as they pass editorial checks. Running the site import picks up only new or changed slugs — nothing is duplicated.
Treat samples as illustrative. Validate against your stack and licences before production use. For delivery work, contact us with the brief.
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.