<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Approach on Tech Foundations</title><link>https://valery.tech/ai-engineering/approach/</link><description>Recent content in Approach on Tech Foundations</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2014-2023</copyright><atom:link href="https://valery.tech/ai-engineering/approach/index.xml" rel="self" type="application/rss+xml"/><item><title>Combined Approach</title><link>https://valery.tech/ai-engineering/approach/combined-approach/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/combined-approach/</guid><description>&lt;p&gt;Structured AI development approach:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Causal stack framework: the causal-stack set of notes under &lt;code&gt;ai-engineering/evaluation/causal-stack&lt;/code&gt;, with &lt;a href="https://valery.tech/ai-engineering/causal-stack/causal-stack-operating-model/"&gt;Causal Stack Operating Model&lt;/a&gt; as the top-level map. It links language and system-level causal properties to fault families, evaluation methods, and operational controls, so it shows where the harness, platform, and methodology fit.&lt;/li&gt;
&lt;li&gt;Evaluation harness and platform&lt;/li&gt;
&lt;li&gt;Methodology and operating model&lt;/li&gt;
&lt;li&gt;Observability and test pyramid&lt;/li&gt;
&lt;li&gt;Experimentation and scientific foundation as well as &lt;a href="https://valery.tech/ai-engineering/approach/experimentation/"&gt;Experimentation&lt;/a&gt; approach to delivery&lt;/li&gt;
&lt;li&gt;Architecture and engineering principles&lt;/li&gt;
&lt;li&gt;Cross-functional alignment with shared taxonomies and tools (frameworks, patterns, delivery)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;and approach of design: &lt;a href="https://valery.tech/engineering/eng-exp/exploratory-design/"&gt;Exploratory Design&lt;/a&gt;:&lt;/p&gt;</description></item><item><title>Cross Domain Mindset</title><link>https://valery.tech/ai-engineering/approach/cross-domain-mindset/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/cross-domain-mindset/</guid><description>&lt;p&gt;Short answer: yes, they absolutely apply in ML, but some of them show up in slightly different ways and are even more important because of uncertainty around data and models.&lt;/p&gt;</description></item><item><title>Edd</title><link>https://valery.tech/ai-engineering/approach/edd/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/edd/</guid><description>&lt;p&gt;resources&lt;/p&gt;
&lt;p&gt;https://cookbook.openai.com/examples/partners/eval_driven_system_design/receipt_inspection&lt;/p&gt;
&lt;p&gt;and also evaluation-driven system design / system delivery&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Eval-Driven Development (EDD)&lt;/strong&gt; is the architectural answer to the non-deterministic nature of AI.&lt;/p&gt;</description></item><item><title>Empirical Nature</title><link>https://valery.tech/ai-engineering/approach/empirical-nature/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/empirical-nature/</guid><description>&lt;h1 id="ai-systems-require-behavioral-evidence"&gt;AI Systems Require Behavioral Evidence&lt;/h1&gt;
&lt;p&gt;This note defines a working principle for designing, evaluating, and operating AI systems.&lt;/p&gt;
&lt;h2 id="short"&gt;Short&lt;/h2&gt;
&lt;p&gt;An AI system’s behavior is implemented by its complete runtime composition, including model weights, prompts, code, data, tools, policies, and state.&lt;/p&gt;</description></item><item><title>Experimentation</title><link>https://valery.tech/ai-engineering/approach/experimentation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/experimentation/</guid><description>&lt;h1 id="disciplined-ai-experimentation"&gt;Disciplined AI Experimentation&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Objective:&lt;/strong&gt; Define the systemic framework for transitioning AI development workflows from uncontrolled, intuition-based iterations to evidence-driven, decision-grade engineering.&lt;/p&gt;</description></item><item><title>Experiments Vs Features</title><link>https://valery.tech/ai-engineering/approach/experiments-vs-features/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/experiments-vs-features/</guid><description>&lt;h1 id="resources"&gt;Resources&lt;/h1&gt;
&lt;h1 id="input"&gt;Input&lt;/h1&gt;
&lt;p&gt;downloaded video &amp;ldquo;Stop Managing AI Projects Like Traditional Software&amp;rdquo; and https://www.youtube.com/watch?v=R_HnI9oTv3c&lt;/p&gt;
&lt;p&gt;https://www.youtube.com/watch?v=k98gDjYbSaU Failure is a funnel, also downloaded&lt;/p&gt;</description></item><item><title>Workflow Design</title><link>https://valery.tech/ai-engineering/approach/workflow-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/approach/workflow-design/</guid><description>&lt;p&gt;Designing workflows:&lt;/p&gt;
&lt;p&gt;Interaction-point design approach for AI workflows. The idea was to expose uncertain pipeline decisions &amp;ndash; retrieval candidates, context assembly, validation, review judgments, and failure labels &amp;ndash; as inspectable artifacts before automating them. That gave us a way to compare variants, capture domain feedback as traces, and turn stable patterns into evaluation criteria, operational controls, or automated policies.&lt;/p&gt;</description></item></channel></rss>