Context and continuity
How to preserve decisions and organise long-running work with AI.
Articles
Architecture, context, evaluation, capability transfer and governance. Technical work explained through the decisions it helps you make.
Technical practice
How to preserve decisions and organise long-running work with AI.
How to check information and design a verification process.
Where rules belong, which mechanisms enforce them and how to test them.
Learning on the real case so people can direct the system.
Full archive
How much human-AI collaboration delivers depends on who directs it: what context the model gets, what is reviewed and who is accountable.
Read →Context engineering decides the quality of the answer: models perform measurably worse as the text in front of them grows, and continuity of work with AI is what makes it avoidable.
Read →AI training for employees that leaves capability, not diplomas — with practice and evidence to support the AI literacy of Article 4.
Read →AI Act compliance can live in a PDF or run inside the system. The difference shows on the day of the error. How a legal boundary that executes is built.
Read →Artificial intelligence hallucinations are not solved by trusting more: they are solved by demanding the source. How verification is built, with a real system open to inspection.
Read →Controlling artificial intelligence is not watching it: it is having its rules live in writing, apply to every response, and be provably enforced.
Read →Operating with artificial intelligence shows in the routine, not the demo: what the system does by Monday morning and how the manager checks the log.
Read →The reason to govern your AI is not the auditor: it is directing artificial intelligence as you direct a team. It helps with compliance, but that is not the motive.
Read →AESIA is the Spanish Agency for the Supervision of Artificial Intelligence: what it is, what it can ask of your company, the Spanish sandbox and the 16 guides it lists today.
Read →A roadmap to comply with the European AI Act without being an expert: what AI you have, what the law asks for, in what order and with which official guides.
Read →Your board signs off on an AI it cannot see without an interpreter. What AI transparency for decision-makers means —human oversight and traceability— and how to achieve it.
Read →The European AI Act sets fines of up to 35 million euros or 7% of worldwide turnover. What non-compliance with high-risk AI can cost, who is exposed and from what date, in plain language.
Read →An AI is only as good as the data it can read. Why the order of your data, as well as the model, decides whether an AI project ever gets used in the work. In plain language.
Read →Why an AI demo can stall before production: data, integrations, evaluation and operational responsibility.
Read →Before auditing anything, decision-makers must be able to see what their AI does, what risks it carries, and how it is sustained. Explained without jargon.
Read →What high-risk AI is under the EU AI Act and how to know whether yours qualifies: the Annex III list with examples and the documentation catch, in plain language.
Read →Tell us what you need to build or improve. Technical work starts with understanding your operations.