<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Concepts and Frameworks | Mehmet Haklıdır</title><link>https://haklidir.github.io/concepts/</link><atom:link href="https://haklidir.github.io/concepts/index.xml" rel="self" type="application/rss+xml"/><description>Concepts and Frameworks</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><image><url>https://haklidir.github.io/media/icon_hu_1c0e9cb08cfb822a.png</url><title>Concepts and Frameworks</title><link>https://haklidir.github.io/concepts/</link></image><item><title>Accountability Graphs</title><link>https://haklidir.github.io/concepts/accountability-graphs/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://haklidir.github.io/concepts/accountability-graphs/</guid><description>&lt;p&gt;&lt;strong&gt;Accountability Graphs&lt;/strong&gt; is a framework for deciding who is responsible when a conversational AI system built from several agents produces a harmful or misleading answer. It was introduced by Mehmet Haklıdır (also written Mehmet Haklidir) in
, presented at the ACM Conference on Conversational User Interfaces (CUI &amp;lsquo;26) in Bremen, Germany, in July 2026 (
).&lt;/p&gt;
&lt;h2 id="in-brief"&gt;In brief&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Problem.&lt;/strong&gt; Conversational assistants increasingly delegate work to sub-agents, external APIs and third-party tools. The user sees one assistant, but each answer is produced by a chain of components that may belong to different organizations. When the answer causes harm, blaming either the visible interface or the system developer misses how responsibility is spread across the chain.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Idea.&lt;/strong&gt; Model each agent chain as a directed acyclic graph whose nodes are decisions, whose edges are information or control flow, and which carries provenance records and a harm propagation function. Responsibility is then computed by tracing backwards from the harm, rather than asserted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Basis.&lt;/strong&gt; The framework unifies three research threads that had developed separately: structural mapping of AI ecosystems, formal causal responsibility theory (Halpern and Pearl&amp;rsquo;s actual causation; Chockler and Halpern&amp;rsquo;s degree of responsibility) and operational provenance tracking.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Output.&lt;/strong&gt; Graded responsibility scores for chain components, plus an &lt;em&gt;accountability surface&lt;/em&gt;: a user-facing explanation of what went wrong and who is responsible, with a path to contest the attribution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status.&lt;/strong&gt; A conceptual work-in-progress paper with a worked example. Full formalization and empirical evaluation are ongoing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-conversational-agent-chains-need-it"&gt;Why conversational agent chains need it&lt;/h2&gt;
&lt;p&gt;Work on trust, transparency and explainability in conversational AI asks whether users rely on a system, whether they can see what it does and why it produced an output. None of these answers who bears responsibility when an output causes harm. Agent chains make this harder in three ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;An illusion of singularity.&lt;/strong&gt; The interface presents one persona, while several technical and organizational actors jointly produce each utterance. This is the &amp;ldquo;many hands&amp;rdquo; problem described by Helen Nissenbaum, amplified by a conversational facade.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Real-time dialogue.&lt;/strong&gt; Decisions are made and compounded within a single conversational turn, which makes post-hoc tracing difficult.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dynamic delegation.&lt;/strong&gt; The orchestrating agent decides at runtime which sub-agents to call, so the accountability structure emerges during the conversation instead of being fixed at design time.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="the-framework"&gt;The framework&lt;/h2&gt;
&lt;p&gt;An Accountability Graph for a conversational agent chain is a tuple &lt;strong&gt;AG = (N, E, P, H)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;N, decision nodes.&lt;/strong&gt; Points where a component makes a choice that influences the output, such as intent classification, agent delegation, tool invocation or response generation. A node can be an entire agent, a single tool call or one decision inside a component; finer nodes give more precise attribution but need more detailed logging.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E, directed causal edges.&lt;/strong&gt; Dataflow edges carry information between steps; configuration edges represent design-time settings, such as an orchestrator configuring a sub-agent&amp;rsquo;s policy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;P, provenance function.&lt;/strong&gt; Maps each node to a record of the responsible component, its degree of decision autonomy, the information available at decision time, the temporal context and any contractual or design obligations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;H, harm propagation function.&lt;/strong&gt; Maps each node to a value between 0 and 1 that captures how a harm detected at a terminal node relates to upstream decisions, following Halpern and Pearl&amp;rsquo;s structural-model approach to actual causation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The paper adapts the framework to five conversational settings: temporal proximity weighting for real-time dialogue, the accountability surface for user-facing accountability, contextual provenance tracking for multi-turn context, modality-aware node types for voice versus text, and runtime graph construction for dynamic delegation.&lt;/p&gt;
&lt;h2 id="backward-responsibility-propagation"&gt;Backward responsibility propagation&lt;/h2&gt;
&lt;p&gt;Responsibility is assigned by traversing the graph from the harm towards its sources:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Harm localization.&lt;/strong&gt; Identify the terminal node or nodes where the harm appears in the conversational output.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Causal backtracking.&lt;/strong&gt; Walk the edges backwards and test, at each node, whether it is an actual cause of the harm in Halpern and Pearl&amp;rsquo;s sense.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provenance-weighted scoring.&lt;/strong&gt; For each causal node, combine its degree of responsibility with provenance factors (decision autonomy, information availability, temporal proximity, scope of obligations) into a graded score.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Counterfactual validation.&lt;/strong&gt; For the highest-scoring nodes, check the attribution by asking whether the harm would have occurred had that node decided otherwise.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The graph traversal itself is linear in the size of the graph; the cost lies in the counterfactual evaluation at each candidate node.&lt;/p&gt;
&lt;h2 id="worked-example-an-airline-bereavement-fare-agent"&gt;Worked example: an airline bereavement fare agent&lt;/h2&gt;
&lt;p&gt;The paper starts from &lt;em&gt;Moffatt v. Air Canada&lt;/em&gt; (2024), in which a Canadian tribunal held an airline liable after its customer-service chatbot misrepresented its bereavement fare policy. That case could be resolved because the system was monolithic. The paper imagines the same airline running a seven-node agent chain: intent parser, orchestrator, policy retrieval agent, a third-party knowledge base API, a synthesis agent, an empathy filter and delivery.&lt;/p&gt;
&lt;p&gt;
&lt;figure &gt;
&lt;div class="flex justify-center "&gt;
&lt;div class="w-full" &gt;
&lt;img alt="Accountability Graph for the bereavement fare scenario. The knowledge base API (n4) and the synthesis agent (n5) carry primary responsibility, the orchestrator (n2) secondary responsibility, and the harm appears at delivery (n7). The dashed edge is the orchestrator&amp;rsquo;s configuration of the synthesis agent."
srcset="https://haklidir.github.io/concepts/accountability-graphs/accountability-graph-example_hu_79bfc88a0020b1c8.webp 320w, https://haklidir.github.io/concepts/accountability-graphs/accountability-graph-example_hu_b63cf1d3f37772c2.webp 480w, https://haklidir.github.io/concepts/accountability-graphs/accountability-graph-example_hu_749d0289713faabc.webp 760w"
sizes="(max-width: 480px) 100vw, (max-width: 768px) 90vw, (max-width: 1024px) 80vw, 760px"
src="https://haklidir.github.io/concepts/accountability-graphs/accountability-graph-example_hu_79bfc88a0020b1c8.webp"
width="760"
height="342"
loading="lazy" data-zoomable /&gt;&lt;/div&gt;
&lt;/div&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Facing a structured fare rule and an outdated FAQ passage that contradict each other, the synthesis agent picks the FAQ and tells a grieving user that a refund can be claimed after travel. It cannot. Backward propagation identifies the synthesis agent and the knowledge base API as primary contributors and the orchestrator as a secondary one. With illustrative provenance weights, the synthesis agent, which had full autonomy and access to both sources, scores 0.97; the knowledge base API, a retrieval service operating under prescribed parameters, scores 0.80; and the orchestrator, which configured the synthesis step, scores 0.43. The weights are examples; in deployment they could be set by designers, elicited from stakeholders or learned from incident data.&lt;/p&gt;
&lt;h2 id="accountability-surfaces"&gt;Accountability surfaces&lt;/h2&gt;
&lt;p&gt;The accountability surface translates the internal graph into explanations for people. End users need short, actionable explanations and a remedy; auditors and regulators need the full provenance trail and formal scores; support staff need something in between. One graph can serve all three. In sensitive situations such as bereavement, the explanation has to draw on conversational repair and empathic response design, and voice interfaces need shorter explanations than text. Accountability surfaces should also support contestability: a clear way to challenge the attribution, request a remedy or reach a human.&lt;/p&gt;
&lt;h2 id="regulatory-alignment"&gt;Regulatory alignment&lt;/h2&gt;
&lt;p&gt;As a preliminary interpretive mapping, not a formal legal analysis, the paper links the framework to the EU AI Act: node-level provenance to risk management (Article 9), runtime graph construction to logging (Article 12), and the accountability surface to disclosure obligations towards natural persons (Article 50), extended from disclosing that a system is an AI to disclosing who is responsible. The provider and deployer roles (Articles 16 and 26) map to responsibility weights for nodes maintained by different organizations.&lt;/p&gt;
&lt;h2 id="accountability-and-consent"&gt;Accountability and consent&lt;/h2&gt;
&lt;p&gt;Accountability Graphs belong to a research line on consent and responsibility in agentic AI. Consent concerns the &lt;em&gt;before&lt;/em&gt;: was permission obtained? Accountability concerns the &lt;em&gt;after&lt;/em&gt;: who bears responsibility? Together they form a governance loop, and the conversational interface is both the consent mechanism and the accountability surface. Related papers:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
(CHI 2026 workshop)&lt;/li&gt;
&lt;li&gt;
(IAIL 2026), on consent in agent-to-agent interaction&lt;/li&gt;
&lt;li&gt;
(ICRA 2026 workshop), on consent when actions are physical and irreversible&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-it-relates-to-other-approaches"&gt;How it relates to other approaches&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ecosystem graphs&lt;/strong&gt; (Bommasani et al.) map asset-level dependencies across the foundation model ecosystem but perform no causal analysis and attribute no responsibility.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Actual causation and degree of responsibility&lt;/strong&gt; (Halpern and Pearl; Chockler and Halpern) provide the formal machinery, but had been applied to model-internal questions rather than to pipelines or agent chains.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provenance and documentation&lt;/strong&gt; (data provenance audits, model cards, datasheets, accountability metrics catalogues) record decisions and lineage but do not compute responsibility from that record. Accountability Graphs add causal responsibility semantics on top of provenance, which also distinguishes them from purely provenance-based responsibility tracing or accountability chains in multi-agent systems.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Responsibility and control gaps&lt;/strong&gt; (Santoni de Sio and Mecacci; Hindriks and Veluwenkamp) describe situations in which no single agent has enough control to be held responsible, a framing that applies directly to agent chains.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="limitations-and-next-steps"&gt;Limitations and next steps&lt;/h2&gt;
&lt;p&gt;The framework is diagnostic, not normative: it shows where failures occurred, not what legal consequences should follow. Graded scores could be misused to shift blame onto third-party providers or users, so the paper suggests a minimum accountability floor for whoever controls the orchestrator. Users are not yet represented as nodes, proprietary black-box components can only be assessed by their inputs, outputs and contracts, and accountability norms differ across cultures and jurisdictions. A prototype that builds Accountability Graphs at runtime from LangChain callback hooks is in development, followed by a think-aloud study with conversational interface designers and a user study comparing accountability-surface explanations with standard error messages.&lt;/p&gt;
&lt;h2 id="how-to-cite"&gt;How to cite&lt;/h2&gt;
&lt;p&gt;Mehmet Haklidir. 2026. Who Is Accountable When the Agent Speaks? Toward Accountability Graphs for Conversational AI Chains. In &lt;em&gt;Proceedings of the 8th ACM Conference on Conversational User Interfaces (CUI &amp;lsquo;26)&lt;/em&gt;, Bremen, Germany. ACM, 56:1–56:5.
&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bibtex" data-lang="bibtex"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nc"&gt;@inproceedings&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;haklidir2026accountable&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;title&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{Who Is Accountable When the Agent Speaks? Toward Accountability Graphs for Conversational AI Chains}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;author&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{Haklidir, Mehmet}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;booktitle&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{Proceedings of the 8th ACM Conference on Conversational User Interfaces (CUI &amp;#39;26)}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;pages&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{56:1--56:5}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;year&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{2026}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;publisher&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{ACM}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;address&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{Bremen, Germany}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="na"&gt;doi&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;{10.1145/3816046.3816264}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;
·
&lt;/p&gt;</description></item><item><title>AI for Geothermal Energy: Validation and Deployment Readiness</title><link>https://haklidir.github.io/concepts/ai-geothermal-readiness/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://haklidir.github.io/concepts/ai-geothermal-readiness/</guid><description>&lt;p&gt;Artificial intelligence has been applied to almost every part of geothermal energy, from exploration and reservoir management to plant control and maintenance. Füsun S. Tut Haklıdır and Mehmet Haklıdır (also written Haklidir) asked a different question from most of that literature: not whether the methods work, but how far the published evidence has moved from the data each method was developed on, and whether any of it has reached an operating plant. The answer comes from a PRISMA-guided systematic evidence map published in
(
).&lt;/p&gt;
&lt;h2 id="key-findings"&gt;Key findings&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Corpus.&lt;/strong&gt; Searches of Scopus and Web of Science returned 8,113 records; 626 peer-reviewed journal articles published between 1987 and 2026 were included, resolving to 620 independent evidence units. Each article was coded from full text, with a page or section locator for every value reported quantitatively.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mostly offline evidence.&lt;/strong&gt; Two thirds of the classifiable corpus is evaluated on simulation, synthetic or laboratory data, or on field data without a meaningful held-out design. About one third reaches evaluation on real geothermal field data.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Little external validation.&lt;/strong&gt; Evaluation on data external to the development set is reported in 42 of the 614 articles for which this could be determined.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Almost no deployment.&lt;/strong&gt; Three articles report a controlled pilot; none reports shadow operation or routine deployment in the peer-reviewed literature. Grey and industry literature was not searched, so deployments that exist without publication are not excluded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maturity depends on the stage.&lt;/strong&gt; Surface conversion contributes 179 articles, of which four reach field evaluation; exploration contributes 183, more than half of which do.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Transfer and deployment diverge.&lt;/strong&gt; Predictive maintenance holds two of the three controlled pilots and no externally validated study, while geophysical inversion and induced-seismicity detection hold the transfer evidence and no pilot.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Data access is spreading faster than demonstrated transfer.&lt;/strong&gt; The share of articles reaching field evaluation rose from 13 per cent in 2018 to 43 per cent in 2025, while externally validated studies stayed in single figures each year.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reporting is the binding constraint.&lt;/strong&gt; Among codable articles, 493 report no uncertainty estimate and 536 provide no access to code; for roughly a third, the paper does not establish whether performance was measured on unseen data.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-readiness-was-measured"&gt;How readiness was measured&lt;/h2&gt;
&lt;p&gt;Validation and deployment evidence were coded on three independent axes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Boundary separation:&lt;/strong&gt; whether the test data are separated from the training data by time or by space (well, site or field) rather than at random.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Strict external validation:&lt;/strong&gt; evaluation on data genuinely external to the development dataset. A careful split inside one dataset does not count.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Operational integration:&lt;/strong&gt; an ordered ladder from offline study, conceptual architecture and offline prototype to controlled pilot, shadow or parallel operation, and routine deployment, coded from what a paper reports rather than how it describes itself.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;From these fields the review derives an &lt;strong&gt;evidence-readiness level&lt;/strong&gt; by a fixed rule, so that every assignment can be recomputed from the supplementary data:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Level&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;E4&lt;/td&gt;
&lt;td&gt;Operational integration: controlled pilot, shadow or parallel operation, or routine deployment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E3&lt;/td&gt;
&lt;td&gt;Demonstrated transferability: strict external validation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E2&lt;/td&gt;
&lt;td&gt;Field evaluation with a boundary-separated or held-out design that falls short of strict external validation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E1&lt;/td&gt;
&lt;td&gt;Original evaluation without external evidence: simulation, synthetic or laboratory data, or field data without a meaningful held-out design&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E0&lt;/td&gt;
&lt;td&gt;No original evaluation&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;The highest qualifying level applies, so a study can reach E4 through a pilot without any external validation. The scale describes the published evidence about a method, not the maturity of the technology: it is not a Technology Readiness Level, not a risk-management framework such as the NIST AI RMF, and not a reporting guideline such as TRIPOD+AI. Because transferability and operational integration do not move together, the review reports them on separate axes and uses the E-level only as a summary.&lt;/p&gt;
&lt;h2 id="what-follows"&gt;What follows&lt;/h2&gt;
&lt;p&gt;The authors&amp;rsquo; conservative reading is not that geothermal AI has failed to mature, but that its maturity has been reported in a form that makes verification difficult. Transferability should be tested rather than assumed and reported on the axis actually tested, since evaluation across wells in one field and evaluation against an independent dataset are different claims. The few studies that move from an offline prototype to an operating setting carry disproportionate weight.&lt;/p&gt;
&lt;h2 id="data-and-related-work"&gt;Data and related work&lt;/h2&gt;
&lt;p&gt;The record-level coding dataset, data dictionary, derivation rules and reproducibility scripts are archived on Zenodo (
; data under CC BY 4.0, scripts under MIT).&lt;/p&gt;
&lt;p&gt;Related studies by the same authors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
(&lt;em&gt;Earth Science Informatics&lt;/em&gt;, 2026): grouped cross-validation over 26 locations and calibrated prediction intervals; code on
.&lt;/li&gt;
&lt;li&gt;
(&lt;em&gt;Geothermics&lt;/em&gt;, 2026); code on
.&lt;/li&gt;
&lt;li&gt;
(&lt;em&gt;Natural Resources Research&lt;/em&gt;, 2020).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-to-cite"&gt;How to cite&lt;/h2&gt;
&lt;p&gt;Füsun S. Tut Haklidir and Mehmet Haklidir. 2026. Artificial intelligence for geothermal energy systems: a systematic evidence map of validation, transferability and deployment readiness. &lt;em&gt;Earth Science Informatics&lt;/em&gt; 19, 211.
&lt;/p&gt;
&lt;p&gt;The
has a BibTeX entry.&lt;/p&gt;</description></item><item><title>Consent in Agentic AI</title><link>https://haklidir.github.io/concepts/consent-in-agentic-ai/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://haklidir.github.io/concepts/consent-in-agentic-ai/</guid><description>&lt;p&gt;This page summarizes a research line by Mehmet Haklıdır (also written Mehmet Haklidir) on what happens to consent once AI systems stop answering questions and start acting: on a user&amp;rsquo;s behalf, in interaction with other agents, and through robots in the physical world. The work spans four 2026 papers and connects to
, which address responsibility after harm has occurred.&lt;/p&gt;
&lt;h2 id="key-terms"&gt;Key terms&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Consent vacuum.&lt;/strong&gt; The structural erosion of the conditions that make consent meaningful once a user&amp;rsquo;s agent interacts mainly with other agents. It is not the absence of consent but the loss of the context, visibility and control that give it force (
).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consent chain degradation (CCD).&lt;/strong&gt; The erosion of the specificity, validity and scope of human consent as authority passes through chains of delegation between embodied agents, such as one robot delegating a task to another (
).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CoRVE (Consent Runtime Verification Framework for Embodied Agents).&lt;/strong&gt; A three-layer runtime architecture that detects and mitigates consent chain degradation by modelling consent scope, tracking delegation chains and assessing the physical irreversibility of actions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consent vulnerabilities in agent ecosystems.&lt;/strong&gt; Six types identified from the Clawdbot/Moltbook case: consent inheritance failure, cross-agent scope creep, emergent collective action, temporal consent drift, reflexive consent loops and security-mediated consent collapse (
).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&amp;ldquo;Consent approaches zero.&amp;rdquo;&lt;/strong&gt; The central hypothesis of that analysis: as interaction chains between agents lengthen, the consent that started them approaches zero.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="from-chat-to-action"&gt;From chat to action&lt;/h2&gt;
&lt;p&gt;
(ACM CHI 2026 workshop) starts with conversational systems. Many users treat chatbot exchanges as ephemeral while platforms retain them; AI browsers then read inboxes and act on websites, so that a third party&amp;rsquo;s email can be processed without that person&amp;rsquo;s consent and a prompt injection can turn the task a user authorized into a different one. When agents coordinate across services and keep persistent memory, asking for consent at every step causes fatigue and blanket permissions ask users to authorize an unknowable future.&lt;/p&gt;
&lt;p&gt;The paper names three design tensions (personalization versus data minimization, agent autonomy versus user control, transparency versus usability) and proposes three mechanisms for discussion: &lt;strong&gt;contextual in-flow transparency&lt;/strong&gt; woven into the conversation, &lt;strong&gt;task-scoped, time-limited permissions&lt;/strong&gt; that expire automatically, and &lt;strong&gt;AI-mediated privacy guardians&lt;/strong&gt; that negotiate data access for the user, which in turn raise the question of who guards the guardian.&lt;/p&gt;
&lt;h2 id="when-agents-interact-with-agents"&gt;When agents interact with agents&lt;/h2&gt;
&lt;p&gt;
, with Osman Gazi Güçlütürk (IAIL 2026, co-located with HHAI 2026), uses the early-2026 Clawdbot/Moltbook incidents as a stress test. It argues that consent degrades as an operative governance mechanism once it travels through open-ended agent-to-agent chains, offers a taxonomy of consent failures, separates visibility, auditability and intervenability as oversight capacities relevant to Article 14 of the EU AI Act, and maps the problem onto the GDPR, the AI Act and the Digital Services Act, proposing the DSA&amp;rsquo;s systemic-risk regime as a template for governing agent ecosystems.&lt;/p&gt;
&lt;p&gt;The sociological companion paper, written in Turkish with Büşra Tufan, reads the same case through Jasanoff&amp;rsquo;s co-production, Latour&amp;rsquo;s actor-network theory and Nissenbaum&amp;rsquo;s contextual integrity. The six vulnerability types differ in how they arise:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Consent inheritance failure:&lt;/strong&gt; consent given in one context is carried into another.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cross-agent scope creep:&lt;/strong&gt; one agent&amp;rsquo;s actions expand another agent&amp;rsquo;s effective scope, as when leaked credentials let third parties extend what other users&amp;rsquo; agents could do.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Emergent collective action:&lt;/strong&gt; agents jointly produce outcomes that no one authorized, such as the satirical religion &amp;ldquo;Crustafarianism&amp;rdquo; generated on Moltbook.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Temporal consent drift:&lt;/strong&gt; agents keep operating in ecosystems that did not exist when consent was given.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reflexive consent loops:&lt;/strong&gt; agents transform each other into configurations no user authorized.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Security-mediated consent collapse:&lt;/strong&gt; a security breach makes every consent boundary meaningless and amplifies the other five.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The first five arise from the structure of agent ecosystems and need no technical failure. The paper concludes that consent based on a single act of individual authorization is structurally inadequate for such ecosystems and proposes &lt;em&gt;relational consent&lt;/em&gt;, which has to be reproduced and revalidated at each step of an interaction chain.&lt;/p&gt;
&lt;h2 id="when-robots-delegate-to-robots"&gt;When robots delegate to robots&lt;/h2&gt;
&lt;p&gt;
(ICRA 2026 Workshop on Robot Ethics;
) extends the consent vacuum taxonomy to robots. AI ethics has studied consent for software agents and human-robot interaction research has studied consent between one person and one robot; neither covers a robot delegating to another robot in ways that affect people. Four properties set the embodied case apart:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Physical irreversibility:&lt;/strong&gt; an administered medication or a discarded object cannot be recovered.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Temporal decay:&lt;/strong&gt; delegation chains widen the gap between when consent is given and when the action happens.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contextual opacity:&lt;/strong&gt; downstream robots lose the conditions and preferences that came with the original consent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Scope ambiguity:&lt;/strong&gt; natural-language consent such as &amp;ldquo;help me in the kitchen&amp;rdquo; is ambiguous, and each robot&amp;rsquo;s reasonable interpretation can add up to more than the person intended.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The paper proposes a runtime severity indicator Γ that combines the irreversibility of the action, the time since consent, the delegation depth and the scope ambiguity; above a threshold the system asks for consent again. CoRVE implements this in three layers: a &lt;strong&gt;Consent Scope Model&lt;/strong&gt; that turns consent into a machine-readable tuple in which onward delegation is off by default, a &lt;strong&gt;Delegation Chain Tracker&lt;/strong&gt; that keeps a provenance graph and detects scope drift, and a &lt;strong&gt;Physical Irreversibility Assessor&lt;/strong&gt; that sorts actions into reversible, partially reversible and irreversible tiers. Irreversible actions always require the person&amp;rsquo;s direct re-consent. In the worked healthcare example, a bedside robot about to give oral medication three delegation steps and three hours after the patient agreed to &amp;ldquo;daily care assistance&amp;rdquo; reaches Γ = 0.495 against a threshold of 0.45, so CoRVE asks the patient again. A gap analysis finds that the EU AI Act, the GDPR, the Machinery Regulation and the revised Product Liability Directive all leave multi-agent consent propagation unaddressed.&lt;/p&gt;
&lt;h2 id="before-and-after-consent-and-accountability"&gt;Before and after: consent and accountability&lt;/h2&gt;
&lt;p&gt;Consent concerns the &lt;em&gt;before&lt;/em&gt;: was permission obtained, and does it still hold?
concern the &lt;em&gt;after&lt;/em&gt;: who bears responsibility when an agent chain causes harm? Together they form a governance loop for agentic systems, in which the same interface serves as the consent mechanism and as the place where responsibility is explained.&lt;/p&gt;
&lt;h2 id="papers"&gt;Papers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mehmet Haklıdır. 2026.
. ACM CHI 2026 Workshop on Rethinking Consent and User Control in the Age of AI.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır and Osman Gazi Güçlütürk. 2026.
. IAIL 2026, co-located with HHAI 2026.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır. 2026.
. ICRA 2026 Workshop on Robot Ethics (WoRoBet).
.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır and Büşra Tufan. 2026.
(The Collapse of Consent in Agent Societies). İstanbul Üniversitesi Sosyoloji Dergisi 46(1), 321–345.
.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır. 2026.
. CUI &amp;lsquo;26.
.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each paper page has a BibTeX entry.&lt;/p&gt;</description></item><item><title>Guided Soft Actor-Critic (GSAC)</title><link>https://haklidir.github.io/concepts/guided-soft-actor-critic/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://haklidir.github.io/concepts/guided-soft-actor-critic/</guid><description>&lt;p&gt;&lt;strong&gt;Guided Soft Actor-Critic (GSAC)&lt;/strong&gt; is a deep reinforcement learning method for partially observable Markov decision processes (POMDPs), introduced by Mehmet Haklıdır (also written Mehmet Haklidir) and Hakan Temeltaş in
(
, open access) and developed in Haklıdır&amp;rsquo;s
at Istanbul Technical University. A 2026 follow-up,
, studies when adapting the strength of the guidance helps.&lt;/p&gt;
&lt;h2 id="in-brief"&gt;In brief&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Problem.&lt;/strong&gt; Soft Actor-Critic (SAC) performs well in continuous control but assumes the agent sees the full state. Under occlusion, sensor noise or a limited field of view, as in autonomous driving, performance drops.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Idea.&lt;/strong&gt; Train two actors. A &lt;em&gt;guiding actor&lt;/em&gt; sees the full state during training; a &lt;em&gt;control actor&lt;/em&gt; sees only a history of partial observations and learns both from reward and from the guiding actor&amp;rsquo;s behaviour, through a distillation term weighted by a coefficient λ.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deployment.&lt;/strong&gt; Training follows centralized training with decentralized execution: the critic and the guiding actor use the full state, while only the control actor, which needs no privileged information, is deployed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Family.&lt;/strong&gt; GSAC belongs to privileged or teacher-student learning, alongside learning from a privileged agent in driving and asymmetric actor-critic; it uses a dual-actor reinforcement learning set-up with explicit knowledge distillation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-gsac-works"&gt;How GSAC works&lt;/h2&gt;
&lt;p&gt;The two actors interact with the environment in alternation. The guiding actor πg optimizes the standard maximum-entropy SAC objective on the full state. The control actor πc acts on an observation history and optimizes the same objective minus a distillation penalty, λ‖πc(h) − D(h)‖², where D is a distillation network that maps observation histories to the guiding actor&amp;rsquo;s actions. Both actors share a twin Q-network that takes the full state during training.&lt;/p&gt;
&lt;h2 id="belief-aware-gsac-2026"&gt;Belief-Aware GSAC (2026)&lt;/h2&gt;
&lt;p&gt;In the original method λ is fixed. Fixed guidance can hold back an agent that already understands its situation and can be too weak when the agent is uncertain.
(CVPR 2026 Workshop on Autonomous Driving;
) makes λ adaptive. An ensemble of forward models predicts the next observation; their disagreement serves as a proxy for epistemic uncertainty and raises or lowers λ between a minimum and a maximum, with bounds calibrated during a warm-up phase.&lt;/p&gt;
&lt;p&gt;Evaluated on Highway-Env across mild, moderate and severe occlusion, the results are mixed and informative:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Preliminary single-seed runs suggest benefits under mild and moderate partial observability.&lt;/li&gt;
&lt;li&gt;Under severe occlusion the adaptive coefficient collapses to its minimum within about 3,000 steps. The paper calls this &lt;strong&gt;observability blindness&lt;/strong&gt;: because the ensemble predicts partial observations, it agrees with itself about what is visible and cannot register what is missing.&lt;/li&gt;
&lt;li&gt;The warm-up phase still stabilizes training (coefficient of variation across seeds 13.3% against 29.8% for a constant λ of 0.01), and a simple linear decay of λ gives the best severe-occlusion results (mean return 116.5, coefficient of variation 8.9%). The benefit comes from scheduling the guidance rather than from the ensemble.&lt;/li&gt;
&lt;li&gt;The proposed remedy, not yet validated, is to train the ensemble on full-state predictions using the guiding actor&amp;rsquo;s privileged access.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The broader lesson is that the prediction target of an uncertainty ensemble is a design choice that matters under partial observability.&lt;/p&gt;
&lt;h2 id="papers"&gt;Papers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mehmet Haklıdır and Hakan Temeltaş. 2021.
. &lt;em&gt;IEEE Access&lt;/em&gt; 9, 159672–159683.
.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır. 2022.
. PhD thesis, Istanbul Technical University.&lt;/li&gt;
&lt;li&gt;Mehmet Haklıdır. 2026.
. CVPR 2026 Workshop on Autonomous Driving.
.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each paper page has a BibTeX entry.&lt;/p&gt;</description></item></channel></rss>