<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Writing by Yash Sharma</title>
    <link>https://www.yashsharma.ai</link>
    <atom:link href="https://www.yashsharma.ai/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Yash Sharma leads 57+ engineers and researchers building enterprise AI at UnitedHealth Group, spanning strategy, architecture, delivery, governance and production.</description>
    <language>en</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Workflow Orchestration: Why Durable AI Needs an Effect Ledger</title>
      <link>https://www.yashsharma.ai/writing/workflow-orchestration-and-durable-execution-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/workflow-orchestration-and-durable-execution-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Durable execution replays a workflow's own history, not the actions it takes outside itself. The effect ledger framework, and what leaders should fund.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>workflow orchestration</category><category>reliability</category><category>enterprise architecture</category><category>agent runtime</category><category>tool use and integration</category>
    </item>
    <item>
      <title>Verification Engineering: How to Trust an AI System's Answer</title>
      <link>https://www.yashsharma.ai/writing/verification-testing-and-formal-assurance-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/verification-testing-and-formal-assurance-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A passed AI test proves one narrow property, not the whole task. The obligation ladder shows what to verify, test, prove and never assume.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>formal verification</category><category>evaluation and benchmarks</category><category>release gates</category><category>audit trails</category><category>risk management</category>
    </item>
    <item>
      <title>Why Confident AI Answers Still Need a Calibration Layer</title>
      <link>https://www.yashsharma.ai/writing/uncertainty-calibration-and-abstention-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/uncertainty-calibration-and-abstention-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI confidence scores are not probabilities. Calibrating them and building a cost-based rule for when to abstain is what makes an AI answer trustworthy.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>uncertainty and calibration</category><category>evaluation and benchmarks</category><category>risk management</category><category>reliability</category><category>human oversight</category>
    </item>
    <item>
      <title>The Time-to-Quality Ledger for Training System Spending</title>
      <link>https://www.yashsharma.ai/writing/training-systems-and-distributed-optimization-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/training-systems-and-distributed-optimization-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A faster training step is not a cheaper training run. The time-to-quality ledger shows what distributed optimization choices actually cost.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>training infrastructure</category><category>cost and unit economics</category><category>reliability</category><category>what to fund</category><category>model architecture</category>
    </item>
    <item>
      <title>The Four Gates Between a Tool Call and a Business Outcome</title>
      <link>https://www.yashsharma.ai/writing/tool-agent-computer-interface-and-protocol-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/tool-agent-computer-interface-and-protocol-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A tool call that returns success is not proof an action happened. The four-gate chain shows what AI agents must verify before it counts.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>tool use and integration</category><category>agent governance</category><category>security</category><category>reliability</category><category>prompt injection</category>
    </item>
    <item>
      <title>Tokenization and Embedding Choices That Decide AI Cost and Risk</title>
      <link>https://www.yashsharma.ai/writing/tokenization-embedding-and-representation-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/tokenization-embedding-and-representation-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Tokenizer, embedding and index choices decide what your AI can distinguish, what it costs, and how safely you can upgrade it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>tokenization and embeddings</category><category>retrieval and grounding</category><category>cost and unit economics</category><category>multilingual and localization</category><category>model architecture</category><category>deployment and release</category>
    </item>
    <item>
      <title>The Mechanism Ownership Map for AI Engineering Labels</title>
      <link>https://www.yashsharma.ai/writing/taxonomy-discovery-terminology-validation-and-coverage-architecture</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/taxonomy-discovery-terminology-validation-and-coverage-architecture</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A mechanism ownership map separates AI engineering labels like harness and loop from the work underneath, so spend and hiring track real mechanisms.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>enterprise architecture</category><category>what to fund</category><category>board-level questions</category><category>agent runtime</category><category>ROI and value measurement</category>
    </item>
    <item>
      <title>Synthetic Data and Curriculum Design: The Three-Gate Pipeline</title>
      <link>https://www.yashsharma.ai/writing/synthetic-data-curriculum-and-training-environment-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/synthetic-data-curriculum-and-training-environment-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Synthetic training data only builds real capability when generation, verification and a frozen holdout stay separate, never when it merely looks fluent.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>synthetic data</category><category>training data</category><category>reinforcement learning</category><category>reward design</category><category>simulation and world models</category><category>evaluation and benchmarks</category>
    </item>
    <item>
      <title>Structured Output and the Validity Ladder for AI</title>
      <link>https://www.yashsharma.ai/writing/structured-output-schema-and-constrained-generation-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/structured-output-schema-and-constrained-generation-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Valid JSON from an AI system is not proof the answer is true. The validity ladder separates format, type, domain and evidence checks before anything acts.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>structured outputs</category><category>tool use and integration</category><category>reliability</category><category>retrieval and grounding</category><category>agent governance</category>
    </item>
    <item>
      <title>The Sealed-Evidence Arbiter for Multi-Agent AI Risk</title>
      <link>https://www.yashsharma.ai/writing/strategic-multi-agent-mechanism-design-and-collective-risk-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/strategic-multi-agent-mechanism-design-and-collective-risk-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Multi-agent AI rarely beats one accountable decision process. The sealed-evidence arbiter shows when coordination earns its cost and where risk hides.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multi-agent systems</category><category>agent governance</category><category>risk management</category><category>cost and unit economics</category><category>human oversight</category>
    </item>
    <item>
      <title>State-Space and Recurrent Models: Audit What They Really Keep</title>
      <link>https://www.yashsharma.ai/writing/state-space-recurrent-and-hybrid-sequence-architectures</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/state-space-recurrent-and-hybrid-sequence-architectures</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>State-space and recurrent architectures cut memory only if every retained tensor is counted. The retained-byte audit shows what to trust before buying in.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>attention and sequence models</category><category>model architecture</category><category>long context</category><category>inference serving</category><category>what to fund</category>
    </item>
    <item>
      <title>Skill Engineering: The Three-Gate Contract for AI Agents</title>
      <link>https://www.yashsharma.ai/writing/skill-and-reusable-capability-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/skill-and-reusable-capability-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Agent skills are mixed evidence, not a proven lift. The three-gate skill contract separates discovery, execution and outcome so leaders fund what works.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent skills</category><category>agent governance</category><category>tool use and integration</category><category>evaluation and benchmarks</category><category>security</category><category>ROI and value measurement</category>
    </item>
    <item>
      <title>Why Semantic Caching Needs Authorization, Not Just Similarity</title>
      <link>https://www.yashsharma.ai/writing/semantic-caching-invalidation-and-authorization-equivalence-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/semantic-caching-invalidation-and-authorization-equivalence-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Semantic caching only pays off when authority, version, freshness and equivalence checks all pass, not when a similarity score alone approves a hit.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>caching</category><category>privacy and access control</category><category>retrieval and grounding</category><category>cost and unit economics</category><category>security</category>
    </item>
    <item>
      <title>How to Govern Self-Improving AI Agents Without Losing Control</title>
      <link>https://www.yashsharma.ai/writing/self-improving-agent-and-automated-system-optimization-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/self-improving-agent-and-automated-system-optimization-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Self-improving AI agents need a sealed acceptance loop that keeps the grader, the test data and rollback authority out of the proposer's reach.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>self improving systems</category><category>agent governance</category><category>automated grading</category><category>evaluation and benchmarks</category><category>human oversight</category><category>risk management</category>
    </item>
    <item>
      <title>The Four-Gate Boundary: Stopping AI Supply-Chain Attacks</title>
      <link>https://www.yashsharma.ai/writing/security-adversarial-defense-and-supply-chain-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/security-adversarial-defense-and-supply-chain-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI agents fail when untrusted content is treated as a command. The four-gate boundary sets the identity, capability, flow and execution checks that stop it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>security</category><category>prompt injection</category><category>safety and red teaming</category><category>agent governance</category><category>agent skills</category><category>risk management</category>
    </item>
    <item>
      <title>The Reconciliation Gate: How to Resume AI Agents Safely</title>
      <link>https://www.yashsharma.ai/writing/secure-resumption-semantic-transactions-and-external-effect-consistency</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/secure-resumption-semantic-transactions-and-external-effect-consistency</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A restarted AI agent recovers memory, not the world. The reconciliation gate checks identity, ledger status, approval and authority before it acts again.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>reliability</category><category>security</category><category>workflow orchestration</category><category>agent governance</category><category>tool use and integration</category>
    </item>
    <item>
      <title>The Residual-Risk Chain: How to Prove an AI System Is Safe</title>
      <link>https://www.yashsharma.ai/writing/safety-robustness-and-behavioral-assurance-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/safety-robustness-and-behavioral-assurance-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI safety is not a benchmark score. The residual-risk chain ties every hazard to a tested control, an evaluation and an owner who can roll it back.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>safety and red teaming</category><category>risk management</category><category>evaluation and benchmarks</category><category>release gates</category><category>human oversight</category>
    </item>
    <item>
      <title>AI Model Routing: How to Cut Cost Without Losing Quality</title>
      <link>https://www.yashsharma.ai/writing/routing-cascade-and-model-portfolio-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/routing-cascade-and-model-portfolio-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>How AI model routing cuts inference cost per task without losing quality: the eligibility ladder, what 2026 evidence supports, and what to fund first.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>model routing</category><category>cost and unit economics</category><category>small models and compression</category><category>inference serving</category><category>what to fund</category><category>vendor and build decisions</category>
    </item>
    <item>
      <title>Retrieval and RAG: How AI Systems Ground Answers in Evidence</title>
      <link>https://www.yashsharma.ai/writing/retrieval-search-rag-and-evidence-grounding-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/retrieval-search-rag-and-evidence-grounding-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Retrieval finds relevant material. It does not prove an answer is supported. The evidence chain shows the four checks that separate the two.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>retrieval and grounding</category><category>context engineering</category><category>data provenance</category><category>prompt injection</category><category>enterprise architecture</category><category>tokenization and embeddings</category><category>what to fund</category>
    </item>
    <item>
      <title>Requirements and Contracts: The Two-Gate Model for AI</title>
      <link>https://www.yashsharma.ai/writing/requirements-specification-and-contract-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/requirements-specification-and-contract-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI agents can pass every test and still miss the point. The two-gate model separates whether a spec means the right thing from whether code obeys it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>product and workflow design</category><category>formal verification</category><category>release gates</category><category>coding agents</category><category>agent governance</category>
    </item>
    <item>
      <title>Reliability Engineering for AI Agents: Contain Before You Recover</title>
      <link>https://www.yashsharma.ai/writing/reliability-resilience-and-failure-containment-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/reliability-resilience-and-failure-containment-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A retried AI action can leave a duplicate effect in the world. The three-ledger model shows what to contain before recovery even starts.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>reliability</category><category>observability and debugging</category><category>workflow orchestration</category><category>risk management</category><category>tool use and integration</category>
    </item>
    <item>
      <title>What Automatic Prompt Optimization Is Actually Worth</title>
      <link>https://www.yashsharma.ai/writing/prompt-engineering-and-automatic-prompt-optimization</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/prompt-engineering-and-automatic-prompt-optimization</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Automatic prompt optimization pays off only when you measure headroom first, isolate the prompt's parts, and confirm gains on a holdout.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>prompt design</category><category>context engineering</category><category>evaluation and benchmarks</category><category>cost and unit economics</category><category>what to fund</category>
    </item>
    <item>
      <title>How to Judge an AI Product by Its Outcome, Not Its Output</title>
      <link>https://www.yashsharma.ai/writing/product-workflow-and-outcome-value-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/product-workflow-and-outcome-value-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Judging AI products by end to end outcomes, not model output. The accountability chain shows what to pilot, fund, measure and stop first.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>product and workflow design</category><category>ROI and value measurement</category><category>what to fund</category><category>board-level questions</category><category>evaluation and benchmarks</category>
    </item>
    <item>
      <title>The Four-Boundary Check: Securing AI Access Across Tenants</title>
      <link>https://www.yashsharma.ai/writing/privacy-identity-authorization-and-tenant-isolation-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/privacy-identity-authorization-and-tenant-isolation-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI privacy fails when access is approved once and never rechecked. The four-boundary check enforces identity and authorization at every step.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>privacy and access control</category><category>security</category><category>regulatory compliance</category><category>agent governance</category><category>caching</category>
    </item>
    <item>
      <title>The Four-Layer Test Before Betting on Joint-Embedding Models</title>
      <link>https://www.yashsharma.ai/writing/predictive-contrastive-and-joint-embedding-objective-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/predictive-contrastive-and-joint-embedding-objective-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Predictive, contrastive and joint-embedding objectives need a four-layer test before any executive funds a language-replacement claim on them.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>model architecture</category><category>tokenization and embeddings</category><category>multimodal AI</category><category>simulation and world models</category><category>what to fund</category><category>research due diligence</category>
    </item>
    <item>
      <title>The Four-Bottleneck Model for AI Reasoning and Planning</title>
      <link>https://www.yashsharma.ai/writing/planning-reasoning-and-test-time-compute-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/planning-reasoning-and-test-time-compute-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>More reasoning tokens do not guarantee a better answer. The four-bottleneck model shows where to spend inference compute, and where to stop.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>planning and reasoning</category><category>cost and unit economics</category><category>inference serving</category><category>what to fund</category><category>automated grading</category>
    </item>
    <item>
      <title>The History Ledger: How to Evaluate AI Agents That Adapt</title>
      <link>https://www.yashsharma.ai/writing/path-dependent-adaptive-and-contamination-resistant-evaluation-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/path-dependent-adaptive-and-contamination-resistant-evaluation-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A benchmark score answers one of three different questions. The history ledger keeps reset, path-dependent and search-selected evaluation claims honest.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>evaluation and benchmarks</category><category>release gates</category><category>automated grading</category><category>risk management</category><category>self improving systems</category>
    </item>
    <item>
      <title>Open-Ended Curricula: Why More Environments Can Hurt Training</title>
      <link>https://www.yashsharma.ai/writing/open-ended-curricula-and-environment-distribution-design</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/open-ended-curricula-and-environment-distribution-design</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>More generated training environments do not guarantee a more capable agent. The anchored mixture model shows how to gate, allocate and measure them.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>synthetic data</category><category>simulation and world models</category><category>reinforcement learning</category><category>training data</category><category>training infrastructure</category>
    </item>
    <item>
      <title>Knowledge Graphs and Ontologies: What They Are Worth Funding</title>
      <link>https://www.yashsharma.ai/writing/ontology-knowledge-graph-and-neuro-symbolic-semantics-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/ontology-knowledge-graph-and-neuro-symbolic-semantics-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Knowledge graphs and ontologies improve auditability far more reliably than they improve correctness, so test the two separately before you fund one.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>retrieval and grounding</category><category>data provenance</category><category>enterprise architecture</category><category>audit trails</category><category>what to fund</category><category>structured outputs</category>
    </item>
    <item>
      <title>Why Most AI Failure Explanations Are Not Proof of Cause</title>
      <link>https://www.yashsharma.ai/writing/observability-debugging-and-causal-error-attribution-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/observability-debugging-and-causal-error-attribution-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A trace shows what happened, not what caused it. The causal proof ladder is the four checks that turn a plausible story into a demonstrated cause.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>observability and debugging</category><category>reliability</category><category>audit trails</category><category>evaluation and benchmarks</category><category>deployment and release</category>
    </item>
    <item>
      <title>Separate Structure From Tuning Before You Trust an AI Design</title>
      <link>https://www.yashsharma.ai/writing/nested-program-structure-and-numerical-optimization</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/nested-program-structure-and-numerical-optimization</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>When AI proposes a system, split the fixed design from its numeric tuning and compare candidates only at matched effort. Here is how.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>self improving systems</category><category>what to fund</category><category>enterprise architecture</category><category>cost and unit economics</category>
    </item>
    <item>
      <title>Multiscale Credit Assignment: The Credit Integrity Test</title>
      <link>https://www.yashsharma.ai/writing/multiscale-credit-assignment-and-process-reward-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/multiscale-credit-assignment-and-process-reward-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Process rewards can look precise while crediting the wrong step. The credit integrity test checks invariance, causation and provenance before trust.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>reward design</category><category>reinforcement learning</category><category>alignment</category><category>evaluation and benchmarks</category><category>automated grading</category>
    </item>
    <item>
      <title>Multimodal AI Needs an Evidence Ledger, Not Just Bigger Models</title>
      <link>https://www.yashsharma.ai/writing/multimodal-document-voice-and-real-time-interaction-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/multimodal-document-voice-and-real-time-interaction-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Multimodal AI succeeds by preserving where each fact came from. The evidence ledger framework for document, voice and video pipelines leaders can trust.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multimodal AI</category><category>retrieval and grounding</category><category>data provenance</category><category>structured outputs</category><category>product and workflow design</category><category>enterprise architecture</category>
    </item>
    <item>
      <title>The Language Routing Contract: Localization Beyond Fluency</title>
      <link>https://www.yashsharma.ai/writing/multilingual-cross-cultural-and-localization-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/multilingual-cross-cultural-and-localization-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Fluent translation does not prove native reasoning, cultural fit or stable permissions. The language routing contract tests all five before trusting a score.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multilingual and localization</category><category>evaluation and benchmarks</category><category>safety and red teaming</category><category>product and workflow design</category><category>model routing</category>
    </item>
    <item>
      <title>The Delegation Contract: When Multiple AI Agents Earn Their Cost</title>
      <link>https://www.yashsharma.ai/writing/multi-agent-delegation-and-coordination-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/multi-agent-delegation-and-coordination-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Multi-agent AI adds coordination cost and shared mistakes. The delegation contract shows when splitting work across agents actually pays off.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multi-agent systems</category><category>agent governance</category><category>cost and unit economics</category><category>security</category><category>enterprise architecture</category><category>ROI and value measurement</category>
    </item>
    <item>
      <title>The Three-Ledger Method for Model Architecture Decisions</title>
      <link>https://www.yashsharma.ai/writing/model-architecture-pretraining-objective-and-scaling-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/model-architecture-pretraining-objective-and-scaling-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Architecture, pretraining objective and scaling bets need a three-ledger test that separates measured runs from fitted curves and extrapolated projections.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>model architecture</category><category>training infrastructure</category><category>attention and sequence models</category><category>cost and unit economics</category><category>what to fund</category>
    </item>
    <item>
      <title>The Four-Clock Model for Mixture-of-Experts Costs</title>
      <link>https://www.yashsharma.ai/writing/mixture-of-experts-and-communication-aware-conditional-computation</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/mixture-of-experts-and-communication-aware-conditional-computation</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Mixture-of-experts savings are set by four clocks, router, dispatch, expert and combine, not by active parameter counts alone.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>model architecture</category><category>inference serving</category><category>cost and unit economics</category><category>training infrastructure</category>
    </item>
    <item>
      <title>Memory Engineering: How AI Systems Should Govern What They Remember</title>
      <link>https://www.yashsharma.ai/writing/memory-and-persistent-state-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/memory-and-persistent-state-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Persistent AI memory needs governed admission, authority, correction and deletion, not just bigger storage. The memory ledger framework and what to fund.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>memory and state</category><category>privacy and access control</category><category>security</category><category>prompt injection</category><category>agent governance</category><category>regulatory compliance</category>
    </item>
    <item>
      <title>Loop Engineering: How to Control When an AI Agent Stops</title>
      <link>https://www.yashsharma.ai/writing/loop-feedback-control-and-termination-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/loop-feedback-control-and-termination-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI agent loops need a controller that can accept, repair, wait, reconcile, escalate or stop, not one that runs until it claims success.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent runtime</category><category>agent governance</category><category>reliability</category><category>cost and unit economics</category><category>human oversight</category><category>planning and reasoning</category>
    </item>
    <item>
      <title>LLMOps and AgentOps: How to Release AI Agents Safely</title>
      <link>https://www.yashsharma.ai/writing/llmops-agentops-deployment-and-release-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/llmops-agentops-deployment-and-release-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>An AI release spans the model, prompt, tools, memory and policy together. The compound release chain names what to version, gate and recover.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>deployment and release</category><category>release gates</category><category>observability and debugging</category><category>reliability</category><category>agent governance</category>
    </item>
    <item>
      <title>Latent Reasoning and Recurrent Depth: What Hidden Loops Are Worth</title>
      <link>https://www.yashsharma.ai/writing/latent-reasoning-recurrent-depth-and-adaptive-halting</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/latent-reasoning-recurrent-depth-and-adaptive-halting</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Latent reasoning lets a model loop over hidden state instead of writing text. What the thin 2026 evidence supports, and the depth ledger to fund it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>planning and reasoning</category><category>model architecture</category><category>attention and sequence models</category><category>interpretability</category><category>cost and unit economics</category><category>what to fund</category>
    </item>
    <item>
      <title>The Transfer-Compatibility-Confidentiality Test for Agent Memory</title>
      <link>https://www.yashsharma.ai/writing/latent-multi-agent-communication-and-state-interoperability-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/latent-multi-agent-communication-and-state-interoperability-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Before AI agents share raw internal state, prove transfer survives a scrambled message, compatibility holds across models, and confidentiality is real.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multi-agent systems</category><category>memory and state</category><category>security</category><category>privacy and access control</category><category>caching</category>
    </item>
    <item>
      <title>Document-Mediated Policy Adaptation: The Bounded-Edit Ledger</title>
      <link>https://www.yashsharma.ai/writing/language-and-document-mediated-policy-adaptation</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/language-and-document-mediated-policy-adaptation</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Editing the document that governs a frozen AI system can change its behavior. The bounded-edit ledger keeps every promotion accountable.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent skills</category><category>prompt design</category><category>context engineering</category><category>deployment and release</category><category>agent governance</category>
    </item>
    <item>
      <title>The Co-Design Ledger: Proving a Joint Harness and Weight Gain</title>
      <link>https://www.yashsharma.ai/writing/joint-harness-weight-policy-co-design</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/joint-harness-weight-policy-co-design</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Joint harness and weight co-design pays off only when a sealed test, a factorial audit and an immutable safety core back the reported gain.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>self improving systems</category><category>agent runtime</category><category>reinforcement learning</category><category>fine-tuning and adaptation</category><category>evaluation and benchmarks</category><category>cost and unit economics</category>
    </item>
    <item>
      <title>The Four-Claim Model: What AI Interpretability Actually Proves</title>
      <link>https://www.yashsharma.ai/writing/interpretability-representation-steering-and-behavioral-analysis-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/interpretability-representation-steering-and-behavioral-analysis-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A readable AI explanation is not proof of a mechanism. The four-claim model shows what interpretability and steering evidence actually establishes.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>interpretability</category><category>safety and red teaming</category><category>evaluation and benchmarks</category><category>observability and debugging</category><category>risk management</category>
    </item>
    <item>
      <title>Why a Small AI Circuit Is Not Proof You Understand It</title>
      <link>https://www.yashsharma.ai/writing/interpretability-by-construction-and-circuit-concentrating-training</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/interpretability-by-construction-and-circuit-concentrating-training</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A concentrated AI circuit is not automatically an explanation of the model. Four checks separate a real interpretability claim from an engineered story.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>interpretability</category><category>evaluation and benchmarks</category><category>research due diligence</category><category>risk management</category>
    </item>
    <item>
      <title>Why AI Agents Need Separate Goals, Metrics and Permissions</title>
      <link>https://www.yashsharma.ai/writing/intent-objective-and-decision-policy-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/intent-objective-and-decision-policy-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI agents fail when goals, metrics and permissions blur together. Separate intent, objective and decision policy before delegating real authority.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent governance</category><category>reward design</category><category>product and workflow design</category><category>ROI and value measurement</category><category>alignment</category>
    </item>
    <item>
      <title>The Substrate Gate: Where AI Systems Should Store Information</title>
      <link>https://www.yashsharma.ai/writing/information-bottlenecks-across-context-memory-weights-and-harnesses</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/information-bottlenecks-across-context-memory-weights-and-harnesses</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI systems should route information through a gate that checks deletion and tenant isolation first, then let cost decide between context, memory and weights.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>memory and state</category><category>context engineering</category><category>long context</category><category>privacy and access control</category><category>enterprise architecture</category><category>fine-tuning and adaptation</category><category>what to fund</category>
    </item>
    <item>
      <title>Why Tokens Per Second Is the Wrong AI Speed Metric</title>
      <link>https://www.yashsharma.ai/writing/inference-serving-and-runtime-performance-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/inference-serving-and-runtime-performance-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI inference speed claims mean little without goodput: verified work finished inside its deadline on the real workload and hardware.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>inference serving</category><category>cost and unit economics</category><category>caching</category><category>model routing</category><category>small models and compression</category>
    </item>
    <item>
      <title>The Bounded Verdict Ledger for Auditing AI Research Claims</title>
      <link>https://www.yashsharma.ai/writing/independent-adversarial-audit-of-the-research-dossiers</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/independent-adversarial-audit-of-the-research-dossiers</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A passing research dossier is not proof. The bounded verdict ledger traces every claim to its source and states exactly where the checking stopped.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>research due diligence</category><category>audit trails</category><category>evaluation and benchmarks</category><category>risk management</category><category>board-level questions</category>
    </item>
    <item>
      <title>The Four-Condition Test for Real Human Oversight of AI Agents</title>
      <link>https://www.yashsharma.ai/writing/humanagent-collaboration-interaction-and-oversight-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/humanagent-collaboration-interaction-and-oversight-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Approval screens are not oversight. Real oversight passes four conditions: comprehension, detection, timely intervention and real authority to act.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>human oversight</category><category>agent governance</category><category>product and workflow design</category><category>risk management</category>
    </item>
    <item>
      <title>The Runtime Ladder: How Much AI Agent Infrastructure to Build</title>
      <link>https://www.yashsharma.ai/writing/harness-runtime-and-execution-environment-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/harness-runtime-and-execution-environment-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Most agent failures start with the wrong amount of runtime. The runtime ladder matches five levels of infrastructure to what each task needs.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent runtime</category><category>workflow orchestration</category><category>security</category><category>vendor and build decisions</category><category>enterprise architecture</category><category>reliability</category>
    </item>
    <item>
      <title>The Manifest Ledger: Proving AI Development Actually Compounds</title>
      <link>https://www.yashsharma.ai/writing/harness-of-harness-artifact-evolution-and-evidence-continuity</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/harness-of-harness-artifact-evolution-and-evidence-continuity</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A fixed AI coding harness inside a versioned artifact loop can make work cumulative, but hierarchy alone does not yet prove better quality.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>coding agents</category><category>agent runtime</category><category>self improving systems</category><category>evaluation and benchmarks</category><category>audit trails</category>
    </item>
    <item>
      <title>Governance Engineering: How to Prove an AI System Is Compliant</title>
      <link>https://www.yashsharma.ai/writing/governance-compliance-and-auditability-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/governance-compliance-and-auditability-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A written policy is not evidence. The assurance chain ties every AI requirement to an owner, a control and proof it still runs.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>regulatory compliance</category><category>audit trails</category><category>risk management</category><category>human oversight</category><category>board-level questions</category>
    </item>
    <item>
      <title>The Four-Gate Audit For Geometry-Aware Training Optimizers</title>
      <link>https://www.yashsharma.ai/writing/geometry-aware-optimization-and-training-dynamics-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/geometry-aware-optimization-and-training-dynamics-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A new optimizer can solve its geometry problem exactly and still not lower your model's loss. Here is the audit before you fund the swap.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>training infrastructure</category><category>model architecture</category><category>cost and unit economics</category><category>what to fund</category>
    </item>
    <item>
      <title>The Novelty Gate: Testing AI Research Claims Before You Fund Them</title>
      <link>https://www.yashsharma.ai/writing/frontier-hypothesis-laboratory-and-novelty-challenge</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/frontier-hypothesis-laboratory-and-novelty-challenge</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Most AI research claims reaching leadership are relabeled prior art. The novelty gate tests mechanism, evidence and ownership before a claim gets a budget.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>research due diligence</category><category>what to fund</category><category>board-level questions</category><category>evaluation and benchmarks</category>
    </item>
    <item>
      <title>The Adaptation Gate: When Fine-Tuning Earns Its Keep</title>
      <link>https://www.yashsharma.ai/writing/fine-tuning-adaptation-and-domain-transfer-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/fine-tuning-adaptation-and-domain-transfer-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Fine-tuning earns its cost only when behavior is stable and lifecycle math beats a cheaper prompt, retrieval or tool call, not on a benchmark score alone.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>fine-tuning and adaptation</category><category>cost and unit economics</category><category>retrieval and grounding</category><category>ROI and value measurement</category><category>what to fund</category>
    </item>
    <item>
      <title>Fast Weights and Test-Time Training: A Leader's Guide to Model Memory</title>
      <link>https://www.yashsharma.ai/writing/fast-weights-test-time-training-and-nested-learning</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/fast-weights-test-time-training-and-nested-learning</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Fast weights let a model update its own state mid-session. What test-time training actually proves in 2026, and the state contract leaders should require.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>memory and state</category><category>continual learning and unlearning</category><category>model architecture</category><category>fine-tuning and adaptation</category><category>what to fund</category>
    </item>
    <item>
      <title>Auditing an AI Program When Every Piece Passes Its Own Test</title>
      <link>https://www.yashsharma.ai/writing/expanded-coverage-audit-contradiction-resolution-and-cross-layer-synthesis</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/expanded-coverage-audit-contradiction-resolution-and-cross-layer-synthesis</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A cross-layer synthesis audit checks where AI components meet, not just each one alone, before a board funds the next phase of the program.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>board-level questions</category><category>enterprise architecture</category><category>research due diligence</category><category>audit trails</category><category>risk management</category><category>what to fund</category>
    </item>
    <item>
      <title>Training Environments Need a Reward Contract, Not a Guess</title>
      <link>https://www.yashsharma.ai/writing/executable-environment-compilation-and-reward-contract-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/executable-environment-compilation-and-reward-contract-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>An executable training environment that runs code is not proof it behaves like reality. Four gates decide when it is ready to train an agent.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>simulation and world models</category><category>reinforcement learning</category><category>reward design</category><category>training infrastructure</category><category>synthetic data</category>
    </item>
    <item>
      <title>The Evidence Contract Behind a Defensible AI Acceptance Decision</title>
      <link>https://www.yashsharma.ai/writing/evidence-carrying-artifacts-and-acceptance-contract-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/evidence-carrying-artifacts-and-acceptance-contract-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A passing test, a signature and a benchmark score are different evidence types. The evidence contract binds each to one artifact before it counts.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>release gates</category><category>audit trails</category><category>evaluation and benchmarks</category><category>data provenance</category><category>deployment and release</category>
    </item>
    <item>
      <title>Stop Trusting Agreement Scores From Your AI's Own Grader</title>
      <link>https://www.yashsharma.ai/writing/evaluator-reward-model-and-test-generator-co-evolution</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/evaluator-reward-model-and-test-generator-co-evolution</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A solver and its grader can reach perfect agreement while both fail the task. The protected confirmation core keeps acceptance outside that loop.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>automated grading</category><category>reward design</category><category>evaluation and benchmarks</category><category>alignment</category><category>release gates</category>
    </item>
    <item>
      <title>The Evaluation Chain of Custody for Trustworthy AI Claims</title>
      <link>https://www.yashsharma.ai/writing/evaluation-benchmark-and-statistical-measurement-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/evaluation-benchmark-and-statistical-measurement-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A passing benchmark score is not proof. The evaluation chain of custody defines, freezes, grades and gates the evidence behind an AI release decision.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>evaluation and benchmarks</category><category>automated grading</category><category>release gates</category><category>audit trails</category><category>uncertainty and calibration</category>
    </item>
    <item>
      <title>Epistemic Trust Engineering: Why AI Needs a Time-Aware Evidence Core</title>
      <link>https://www.yashsharma.ai/writing/epistemic-trust-contradiction-and-temporal-state-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/epistemic-trust-contradiction-and-temporal-state-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>AI agents need typed claims, four time clocks and a commit gate that separates belief from fact. The evidence core framework and what to build first.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>memory and state</category><category>retrieval and grounding</category><category>data provenance</category><category>uncertainty and calibration</category><category>context engineering</category>
    </item>
    <item>
      <title>The Four-Layer Envelope for Embodied AI and Robot Simulation</title>
      <link>https://www.yashsharma.ai/writing/embodied-world-model-and-simulation-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/embodied-world-model-and-simulation-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A realistic robot simulation is not proof a plan is safe. The four-layer envelope shows where independent verification has to sit.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>simulation and world models</category><category>multimodal AI</category><category>safety and red teaming</category><category>agent governance</category><category>risk management</category><category>planning and reasoning</category>
    </item>
    <item>
      <title>What AI Model Compression Actually Changes Before Release</title>
      <link>https://www.yashsharma.ai/writing/distillation-compression-and-quantization-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/distillation-compression-and-quantization-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Distillation and quantization change what an AI model does, not just its size, so test the deployed artifact before trusting any compression claim.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>small models and compression</category><category>inference serving</category><category>cost and unit economics</category><category>evaluation and benchmarks</category><category>deployment and release</category><category>release gates</category>
    </item>
    <item>
      <title>The Hidden-Sequence Audit For Diffusion Language Models</title>
      <link>https://www.yashsharma.ai/writing/diffusion-flow-matching-and-non-autoregressive-language-generation</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/diffusion-flow-matching-and-non-autoregressive-language-generation</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Diffusion and flow-matching language models are not simply parallel. A three-check audit finds what still runs in sequence before you fund it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>model architecture</category><category>attention and sequence models</category><category>inference serving</category><category>what to fund</category>
    </item>
    <item>
      <title>The Dataset Contract: Governing What a Model Learns</title>
      <link>https://www.yashsharma.ai/writing/data-curation-annotation-provenance-and-quality-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/data-curation-annotation-provenance-and-quality-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Data curation, annotation and provenance decide what a model learns and whether that decision can be audited later, not a single quality score.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>training data</category><category>data provenance</category><category>evaluation and benchmarks</category><category>regulatory compliance</category><category>audit trails</category>
    </item>
    <item>
      <title>The Boundary-First Decision Atlas for Enterprise AI Systems</title>
      <link>https://www.yashsharma.ai/writing/cross-engineering-synthesis-interfaces-and-decision-atlas</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/cross-engineering-synthesis-interfaces-and-decision-atlas</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Component wins in serving, routing or oversight do not make a better system. Judge every AI investment against a shared boundary-first decision atlas.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>enterprise architecture</category><category>what to fund</category><category>board-level questions</category><category>ROI and value measurement</category><category>risk management</category>
    </item>
    <item>
      <title>The Four-Denominator Ledger for Pricing AI Work Correctly</title>
      <link>https://www.yashsharma.ai/writing/cost-latency-energy-and-capacity-economics-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/cost-latency-energy-and-capacity-economics-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Token price is not total cost. The four-denominator ledger prices AI work by accepted, verified, resolved and sustained outcomes.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>cost and unit economics</category><category>inference serving</category><category>ROI and value measurement</category><category>vendor and build decisions</category><category>model routing</category><category>small models and compression</category><category>what to fund</category>
    </item>
    <item>
      <title>The Reacquisition Clock: Testing Whether a Model Can Relearn</title>
      <link>https://www.yashsharma.ai/writing/continual-reinforcement-learning-plasticity-and-path-dependence</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/continual-reinforcement-learning-plasticity-and-path-dependence</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Low forgetting does not prove a model can still learn. The reacquisition clock times relearning speed and checks full state before an update ships.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>continual learning and unlearning</category><category>reinforcement learning</category><category>evaluation and benchmarks</category><category>fine-tuning and adaptation</category><category>release gates</category>
    </item>
    <item>
      <title>The Update Ledger: Deciding How a Model Should Change</title>
      <link>https://www.yashsharma.ai/writing/continual-learning-model-editing-and-unlearning-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/continual-learning-model-editing-and-unlearning-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Continual learning, editing and unlearning are three different decisions, and the update ledger decides which one a change actually requires.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>continual learning and unlearning</category><category>regulatory compliance</category><category>privacy and access control</category><category>deployment and release</category><category>fine-tuning and adaptation</category><category>risk management</category>
    </item>
    <item>
      <title>Context Engineering: How AI Systems Decide What They See</title>
      <link>https://www.yashsharma.ai/writing/context-engineering-and-context-compilation</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/context-engineering-and-context-compilation</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Context engineering decides what a model sees before it answers. The context compiler framework, why bigger windows are not the fix, and what to fund.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>context engineering</category><category>retrieval and grounding</category><category>long context</category><category>prompt design</category><category>memory and state</category>
    </item>
    <item>
      <title>Computational Provenance: How to Trust What an AI System Claims</title>
      <link>https://www.yashsharma.ai/writing/computational-provenance-and-causal-state-attestation</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/computational-provenance-and-causal-state-attestation</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A signature proves who signed an AI system output, not that it is true. See what computational provenance and causal-state attestation can prove.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>data provenance</category><category>audit trails</category><category>security</category><category>regulatory compliance</category><category>risk management</category>
    </item>
    <item>
      <title>The Core-and-Edge Model for Trustworthy Compound AI Systems</title>
      <link>https://www.yashsharma.ai/writing/compound-hybrid-system-architecture-and-integration-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/compound-hybrid-system-architecture-and-integration-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A defensible compound AI system keeps arithmetic, permissions and state deterministic and treats every model as a replaceable adapter at the edge.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>enterprise architecture</category><category>structured outputs</category><category>vendor and build decisions</category><category>tool use and integration</category><category>reliability</category><category>what to fund</category>
    </item>
    <item>
      <title>The Intervention Test Behind Every AI Causal Claim</title>
      <link>https://www.yashsharma.ai/writing/causal-abstraction-and-compositional-generalization-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/causal-abstraction-and-compositional-generalization-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A fluent explanation or a strong benchmark score is not proof an AI system understands cause and effect. Here is the test that separates the two.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>evaluation and benchmarks</category><category>interpretability</category><category>research due diligence</category><category>risk management</category>
    </item>
    <item>
      <title>Byte-Level and Hierarchical Models: A Leader's Guide to Text Units</title>
      <link>https://www.yashsharma.ai/writing/byte-level-hierarchical-and-multi-unit-language-representations</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/byte-level-hierarchical-and-multi-unit-language-representations</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Byte-level and hierarchical language models change sequence length and interface risk. The four-unit ledger for what to fund, measure and test first.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>tokenization and embeddings</category><category>model architecture</category><category>multilingual and localization</category><category>vendor and build decisions</category><category>what to fund</category><category>enterprise architecture</category>
    </item>
    <item>
      <title>Browser Agents That Prove an Action Actually Happened</title>
      <link>https://www.yashsharma.ai/writing/browser-computer-use-and-digital-action-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/browser-computer-use-and-digital-action-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Browser and computer-use agents need proof, not a success toast. The three-proof model for grounding, authority and verified effect.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>agent governance</category><category>tool use and integration</category><category>security</category><category>reliability</category><category>product and workflow design</category>
    </item>
    <item>
      <title>Why a Formally Checked Proof May Not Prove What You Meant</title>
      <link>https://www.yashsharma.ai/writing/autonomous-mathematical-formalization-and-statement-faithfulness-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/autonomous-mathematical-formalization-and-statement-faithfulness-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A proof can compile and check while proving the wrong statement. The three-gate model shows what a formalization must clear before it is trusted.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>formal verification</category><category>evaluation and benchmarks</category><category>research due diligence</category><category>audit trails</category>
    </item>
    <item>
      <title>Automated Alignment Research: Five Gates Before You Trust It</title>
      <link>https://www.yashsharma.ai/writing/automated-alignment-research-and-research-process-monitorability</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/automated-alignment-research-and-research-process-monitorability</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>A passed benchmark is not proof of safety. The five-gate model checks research integrity, capability and deployment authority apart.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>alignment</category><category>safety and red teaming</category><category>human oversight</category><category>research due diligence</category><category>agent governance</category><category>risk management</category>
    </item>
    <item>
      <title>The Reach-Record-Prove Method for Attention Architecture Decisions</title>
      <link>https://www.yashsharma.ai/writing/attention-topology-locality-and-positional-state-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/attention-topology-locality-and-positional-state-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Attention topology and position tracking decide whether long-context AI reliably retrieves facts or only looks like it does on average.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>attention and sequence models</category><category>long context</category><category>model architecture</category><category>caching</category><category>inference serving</category>
    </item>
    <item>
      <title>Reinforcement Learning Alignment: The Three-Signal Ledger</title>
      <link>https://www.yashsharma.ai/writing/alignment-reward-preference-and-reinforcement-learning-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/alignment-reward-preference-and-reinforcement-learning-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Reward scores can rise while real outcomes do not. The three-signal ledger tracks reward, process consistency and independent outcome separately to catch it.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>alignment</category><category>reinforcement learning</category><category>reward design</category><category>evaluation and benchmarks</category><category>fine-tuning and adaptation</category>
    </item>
    <item>
      <title>The Four-Gate Proof Loop for Governing AI Coding Agents</title>
      <link>https://www.yashsharma.ai/writing/agentic-software-repository-and-code-intelligence-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/agentic-software-repository-and-code-intelligence-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Passing tests and large diffs are not proof of good code. The four-gate proof loop shows what to fund, measure and protect when agents patch repositories.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>coding agents</category><category>agent governance</category><category>security</category><category>evaluation and benchmarks</category><category>release gates</category><category>ROI and value measurement</category>
    </item>
    <item>
      <title>What It Takes to Trust an AI Research Agent's Findings</title>
      <link>https://www.yashsharma.ai/writing/agentic-research-scientific-computing-and-discovery-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/agentic-research-scientific-computing-and-discovery-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Agentic research agents can find sources and rerun code well. Only external checks turn a claim into validated science. The claim ladder makes that decision.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>research due diligence</category><category>evaluation and benchmarks</category><category>formal verification</category><category>audit trails</category><category>agent governance</category>
    </item>
    <item>
      <title>Stop Paying for Information That Cannot Change a Decision</title>
      <link>https://www.yashsharma.ai/writing/active-learning-and-value-of-information-acquisition-engineering</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/active-learning-and-value-of-information-acquisition-engineering</guid>
      <pubDate>Tue, 15 Sep 2026 03:30:00 GMT</pubDate>
      <description>Active learning only pays off when a query changes a decision, not when it reduces uncertainty. The net-value gate prices every query against its full cost.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>training data</category><category>uncertainty and calibration</category><category>cost and unit economics</category><category>what to fund</category><category>ROI and value measurement</category>
    </item>
    <item>
      <title>The Future of Agentic AI: Beyond Traditional Automation</title>
      <link>https://www.yashsharma.ai/writing/future-of-agentic-ai</link>
      <guid isPermaLink="true">https://www.yashsharma.ai/writing/future-of-agentic-ai</guid>
      <pubDate>Sun, 12 Oct 2025 03:30:00 GMT</pubDate>
      <description>Rule-based RPA breaks. Agents reason, plan and adapt. How we replaced an eight-figure RPA contract with 3,200 in-house bots at 99.7% uptime.</description>
      <author>connect@yashsharma.ai (Yash Sharma)</author>
      <category>multi-agent systems</category><category>vendor and build decisions</category><category>ROI and value measurement</category><category>product and workflow design</category><category>agent governance</category><category>what to fund</category>
    </item>
  </channel>
</rss>