<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xml:lang="en" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CMC</journal-id>
<journal-id journal-id-type="nlm-ta">CMC</journal-id>
<journal-id journal-id-type="publisher-id">CMC</journal-id>
<journal-title-group>
<journal-title>Computers, Materials &#x0026; Continua</journal-title>
</journal-title-group>
<issn pub-type="epub">1546-2226</issn>
<issn pub-type="ppub">1546-2218</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">74520</article-id>
<article-id pub-id-type="doi">10.32604/cmc.2025.074520</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Lexical-Prior-Free Planning: A Symbol-Agnostic Pipeline that Enables LLMs and LRMs to Plan under Obfuscated Interfaces</article-title>
<alt-title alt-title-type="left-running-head">Lexical-Prior-Free Planning: A Symbol-Agnostic Pipeline that Enables LLMs and LRMs to Plan under Obfuscated Interfaces</alt-title>
<alt-title alt-title-type="right-running-head">Lexical-Prior-Free Planning: A Symbol-Agnostic Pipeline that Enables LLMs and LRMs to Plan under Obfuscated Interfaces</alt-title>
</title-group>
<contrib-group>
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Du</surname><given-names>Zhendong</given-names></name><email>zhendong@fuji.waseda.jp</email></contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western"><surname>Wang</surname><given-names>Hanliu</given-names></name></contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western"><surname>Hashimoto</surname><given-names>Kenji</given-names></name></contrib>
<aff id="aff-1"><institution>Graduate School of Information, Production and Systems, Waseda University</institution>, <addr-line>Kitakyushu, 808-0135</addr-line>, <country>Japan</country></aff>
</contrib-group>
<author-notes>
<corresp id="cor1"><label>&#x002A;</label>Corresponding Author: Zhendong Du. Email: <email>zhendong@fuji.waseda.jp</email></corresp>
</author-notes>
<pub-date date-type="collection" publication-format="electronic">
<year>2026</year>
</pub-date>
<pub-date date-type="pub" publication-format="electronic">
<day>10</day><month>2</month><year>2026</year>
</pub-date>
<volume>87</volume>
<issue>1</issue>
<elocation-id>12</elocation-id>
<history>
<date date-type="received">
<day>13</day>
<month>10</month>
<year>2025</year>
</date>
<date date-type="accepted">
<day>16</day>
<month>12</month>
<year>2025</year>
</date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2026 The Authors.</copyright-statement>
<copyright-year>2026</copyright-year>
<copyright-holder>Published by Tech Science Press.</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CMC_74520.pdf"></self-uri>
<abstract>
<p>Planning in lexical-prior-free environments presents a fundamental challenge for evaluating whether large language models (LLMs) possess genuine structural reasoning capabilities beyond lexical memorization. When predicates and action names are replaced with semantically irrelevant random symbols while preserving logical structures, existing direct generation approaches exhibit severe performance degradation. This paper proposes a symbol-agnostic closed-loop planning pipeline that enables models to construct executable plans through systematic validation and iterative refinement. The system implements a complete generate-verify-repair cycle through six core processing components: semantic comprehension extracts structural constraints, language planner generates text plans, symbol translator performs structure-preserving mapping, consistency checker conducts static screening, Stanford Research Institute Problem Solver (STRIPS) simulator executes step-by-step validation, and VAL (Validator) provides semantic verification. A repair controller orchestrates four targeted strategies addressing typical failure patterns including first-step precondition errors and mid-segment state maintenance issues. Comprehensive evaluation on PlanBench Mystery Blocksworld demonstrates substantial improvements over baseline approaches across both language models and reasoning models. Ablation studies confirm that each architectural component contributes non-redundantly to overall effectiveness, with targeted repair providing the largest impact, followed by deep constraint extraction and step-wise validation, demonstrating that superior performance emerges from synergistic integration of these mechanisms rather than any single dominant factor. Analysis reveals distinct failure patterns between model types&#x2014;language models struggle with local precondition satisfaction while reasoning models face global goal achievement challenges&#x2014;yet the validation-driven mechanism successfully addresses these diverse weaknesses. A particularly noteworthy finding is the convergence of final success rates across models with varying intrinsic capabilities, suggesting that systematic validation and repair mechanisms play a more decisive role than raw model capacity in lexical-prior-free scenarios. This work establishes a rigorous evaluation framework incorporating statistical significance testing and mechanistic failure analysis, providing methodological contributions for fair assessment and practical insights into building reliable planning systems under extreme constraint conditions.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>LLM planning</kwd>
<kwd>PDDL</kwd>
<kwd>symbol obfuscation</kwd>
<kwd>lexical-prior-free evaluation</kwd>
<kwd>closed-loop verification</kwd>
<kwd>validation-driven repair</kwd>
<kwd>structural reasoning</kwd>
<kwd>mystery domain</kwd>
</kwd-group>
<funding-group>
<award-group id="awg1">
<funding-source>Waseda University</funding-source>
<award-id>2024C-518</award-id>
<award-id>2025E-027</award-id>
</award-group>
</funding-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>Planning serves as a crucial capability that bridges high-level intentions with low-level execution. Traditional symbolic planning systems rely on explicitly defined predicates and action models, employing heuristic search, hierarchical task networks (HTN), or satisfiability solving (SAT/SMT) to identify action sequences in state spaces that satisfy goal constraints. STRIPS/ADL established standard semantics, Planning Domain Definition Language (PDDL) provided unified representations for domains and problems, Graphplan and the FF/FD series laid solid foundations for heuristic construction and holistic solving frameworks, while SAT/SMT-based approaches demonstrated excellence in complex constraint and optimization scenarios. Validators such as VAL provide formal guarantees for plan correctness. This classical paradigm of &#x201C;explicit models &#x002B; systematic search&#x201D; emphasizes structural interpretability and verifiability.</p>
<p>In recent years, LLMs have demonstrated the potential of &#x201C;language as model&#x201D;: through prompt engineering, chain-of-thought (CoT), tool usage, or program sketch generation, models can directly generate plans or intermediate subgoals within natural language space. Text-to-PDDL efforts attempt to translate natural language into formalized descriptions usable by classical planners. However, recent investigations have exposed fundamental limitations: when symbolic interfaces (predicate/action names) are decoupled from natural semantics through obfuscation&#x2014;retaining only their structural roles&#x2014;existing LLMs or Large Reasoning Models (LRMs) exhibit severe performance degradation [<xref ref-type="bibr" rid="ref-1">1</xref>,<xref ref-type="bibr" rid="ref-2">2</xref>]. This phenomenon reveals a critical research gap: models&#x2019; apparent planning success largely depends on lexical priors and script-like co-occurrences in training data rather than genuine structural reasoning about preconditions, effects, and state transitions.</p>
<p><bold>Research Gap and Motivation.</bold> While prior work has extensively documented this lexical dependency problem, three fundamental questions remain unaddressed: First, <italic>can models achieve reliable planning performance when lexical priors are completely removed?</italic> Existing baseline approaches show near-zero success rates in Mystery domains, but it remains unclear whether systematic methods can overcome this barrier. Second, <italic>what mechanisms enable structural reasoning without semantic cues?</italic> The field lacks concrete solutions that operate purely on logical consistency rather than lexical matching. Third, <italic>how do validation-driven approaches compare to raw model capabilities</italic> in such extreme conditions? Understanding whether systematic verification matters more than intrinsic model capacity has important implications for building reliable AI systems.</p>
<p>Addressing these gaps is critical for several reasons:
<list list-type="bullet">
<list-item>
<p><bold>Theoretical necessity:</bold> Genuine planning capabilities must be independent of surface lexical forms&#x2014;a system that only works with familiar vocabulary cannot claim true structural reasoning.</p></list-item>
<list-item>
<p><bold>Practical robustness:</bold> Real-world applications often encounter novel domains where training-time vocabulary associations are unavailable or misleading.</p></list-item>
<list-item>
<p><bold>Evaluation rigor:</bold> Without lexical-prior-free testing, we cannot distinguish memorization from reasoning, leading to overestimated capabilities.</p></list-item>
<list-item>
<p><bold>System reliability:</bold> As AI systems assume critical decision-making roles, verification mechanisms become essential safety infrastructure.</p></list-item>
</list></p>
<p><bold>Our Approach and Contributions.</bold> This paper addresses the question: <italic>under lexical-prior-free symbolic interfaces, how can models construct executable plans that achieve specified goals?</italic> We propose a symbol-agnostic closed-loop planning pipeline that enables structured reasoning through systematic validation and iterative refinement. Our approach implements a complete generate-verify-repair cycle comprising six processing components (semantic comprehension, language planner, symbol translator, consistency checker, STRIPS simulator, VAL validator) and two control components (repair controller, signal aggregator). The system operates entirely on structural relationships&#x2014;preconditions, effects, state dependencies&#x2014;without any name-based semantic inference.</p>
<p>Comprehensive evaluation on PlanBench Mystery Blocksworld demonstrates that our method achieves 46.2%&#x2013;48.0% success rates across GPT-4 (Generative Pre-trained Transformer 4) [<xref ref-type="bibr" rid="ref-3">3</xref>], GPT-4o (Generative Pre-trained Transformer 4 Omni) [<xref ref-type="bibr" rid="ref-3">3</xref>], and o1-mini [<xref ref-type="bibr" rid="ref-4">4</xref>], representing more than 10-fold improvements over baseline direct generation (0%&#x2013;19.1%). A particularly noteworthy finding is the convergence of final success rates across models with vastly different intrinsic capabilities, suggesting that systematic validation and repair mechanisms play a more decisive role than raw model capacity in lexical-prior-free scenarios. We adhere to fair evaluation standards consistent with existing benchmarks (LLMs: GPT-4/4o; LRMs: o1-mini; index boundary filtering), providing systematic evidence from holistic to mechanistic levels through rigorous statistical protocols (Wilson CI, two-proportion z-tests, effect size <inline-formula id="ieqn-1"><mml:math id="mml-ieqn-1"><mml:mi>h</mml:mi></mml:math></inline-formula>, temporal robustness, retry benefit curves, hazard risk profiles, normalized pointwise mutual information (NPMI) association strength).</p>
<p><bold>Novelty and Contributions.</bold> This work makes four distinct contributions to the field:
<list list-type="bullet">
<list-item>
<p><bold>Methodological novelty:</bold> We propose the first complete symbol-agnostic closed-loop planning pipeline specifically designed for lexical-prior-free environments, introducing targeted repair strategies (First-Step Constraint, Precondition Probing, Parameter Swap &#x0026; Landmarks, Budget-Adaptive Retry) that address empirically identified failure patterns.</p></list-item>
<list-item>
<p><bold>Evaluation rigor:</bold> We establish comprehensive evaluation protocols incorporating Wilson confidence intervals, two-proportion z-tests, effect size measures, temporal robustness analysis, retry benefit curves, hazard risk profiles, and NPMI association analysis&#x2014;providing reproducible evidence that withstands statistical scrutiny beyond existing benchmarks.</p></list-item>
<list-item>
<p><bold>Mechanistic insights:</bold> We reveal distinct failure patterns between model types (LLMs struggle with local precondition satisfaction; reasoning models face global goal achievement challenges) and demonstrate how validation-driven mechanisms enable performance convergence across heterogeneous models, advancing understanding of when and why systematic verification matters.</p></list-item>
<list-item>
<p><bold>Practical contribution:</bold> We provide fairness-aware data specifications (index boundary filtering), chart-to-script mappings for reproducibility, and empirical evidence that <inline-formula id="ieqn-2"><mml:math id="mml-ieqn-2"><mml:mi>b</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula> attempts achieve optimal cost-effectiveness&#x2014;offering actionable guidance for deploying planning systems under extreme constraints.</p></list-item>
</list></p>
<p>These contributions establish that structural reasoning without lexical priors is achievable through systematic validation-driven approaches, with implications extending to program synthesis, theorem proving, and other multi-step reasoning tasks requiring verifiable correctness guarantees. To facilitate comprehension of specialized terminology for readers less familiar with planning formalisms and statistical methodologies, <xref ref-type="fig" rid="fig-1">Fig. 1</xref> provides visual explanations and plain-language descriptions of key technical concepts used throughout this work.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>Comprehensive glossary of technical terminology used in this paper. <bold>Left column:</bold> Planning and formal methods concepts. <bold>Right column:</bold> Statistical and evaluation metrics</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-1.tif"/>
</fig>
</sec>
<sec id="s2">
<label>2</label>
<title>Related Work</title>
<p>This chapter systematically reviews research progress related to lexical-prior-free planning. We first review the development of symbolic planning, analyzing the capabilities and limitations of existing planning systems. We then survey research on LLMs applications in planning tasks, focusing on their performance and dependency patterns. Next, we examine verification-driven and repair-based approaches, highlighting critical distinctions from our symbol-agnostic pipeline. We then analyze related work on symbol obfuscation and lexical-prior-free evaluation. Finally, we review research progress in planning evaluation methodologies.</p>
<sec id="s2_1">
<label>2.1</label>
<title>PDDL Planning Language and Symbolic Planning Research</title>
<sec id="s2_1_1">
<label>2.1.1</label>
<title>PDDL&#x2019;s Formalization Framework</title>
<p>The PDDL was proposed by [<xref ref-type="bibr" rid="ref-5">5</xref>] and has become the standard language for symbolic planning. Understanding the structural nature of PDDL is crucial for analyzing the feasibility of lexical-prior-free approaches, as the core assumption of obfuscation techniques is that the logical dependencies of planning reasoning are independent of specific lexical choices.</p>
<p>PDDL employs a modular design where domain definitions <inline-formula id="ieqn-3"><mml:math id="mml-ieqn-3"><mml:mrow><mml:mi>&#x1D49F;</mml:mi></mml:mrow><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">&#x27E8;</mml:mo><mml:mrow><mml:mi>&#x1D4AF;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mi>&#x1D4AB;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mi>&#x1D49C;</mml:mi></mml:mrow><mml:mo fence="false" stretchy="false">&#x27E9;</mml:mo></mml:math></inline-formula> include:
<list list-type="bullet">
<list-item>
<p><bold>Type system <inline-formula id="ieqn-4"><mml:math id="mml-ieqn-4"><mml:mrow><mml:mi>&#x1D4AF;</mml:mi></mml:mrow></mml:math></inline-formula>:</bold> Defines object type hierarchies, forming a partial order structure <inline-formula id="ieqn-5"><mml:math id="mml-ieqn-5"><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>&#x1D4AF;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mo>&#x2AAF;</mml:mo><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula></p></list-item>
<list-item>
<p><bold>Predicate signatures <inline-formula id="ieqn-6"><mml:math id="mml-ieqn-6"><mml:mrow><mml:mi>&#x1D4AB;</mml:mi></mml:mrow></mml:math></inline-formula>:</bold> Each predicate <inline-formula id="ieqn-7"><mml:math id="mml-ieqn-7"><mml:mi>p</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>&#x1D4AB;</mml:mi></mml:mrow></mml:math></inline-formula> is defined as <inline-formula id="ieqn-8"><mml:math id="mml-ieqn-8"><mml:mi>p</mml:mi><mml:mo>:</mml:mo><mml:msup><mml:mrow><mml:mi>&#x1D4AF;</mml:mi></mml:mrow><mml:mrow><mml:mi>k</mml:mi></mml:mrow></mml:msup><mml:mo stretchy="false">&#x2192;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mi>t</mml:mi><mml:mi>r</mml:mi><mml:mi>u</mml:mi><mml:mi>e</mml:mi><mml:mo>,</mml:mo><mml:mi>f</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></inline-formula></p></list-item>
<list-item>
<p><bold>Action schemas <inline-formula id="ieqn-9"><mml:math id="mml-ieqn-9"><mml:mrow><mml:mi>&#x1D49C;</mml:mi></mml:mrow></mml:math></inline-formula>:</bold> Action <inline-formula id="ieqn-10"><mml:math id="mml-ieqn-10"><mml:mi>a</mml:mi></mml:math></inline-formula> is defined by parameters params<inline-formula id="ieqn-11"><mml:math id="mml-ieqn-11"><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>, preconditions pre<inline-formula id="ieqn-12"><mml:math id="mml-ieqn-12"><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>, and effects eff<inline-formula id="ieqn-13"><mml:math id="mml-ieqn-13"><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula></p></list-item>
</list></p>
<p>PDDL supports multiple semantic models, with STRIPS semantics [<xref ref-type="bibr" rid="ref-6">6</xref>] being the most fundamental and widely used. In the STRIPS model, states are represented as sets of atomic predicates, and action effects are divided into add effects add<inline-formula id="ieqn-14"><mml:math id="mml-ieqn-14"><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> and delete effects del<inline-formula id="ieqn-15"><mml:math id="mml-ieqn-15"><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>. The state transition function is defined as:
<disp-formula id="eqn-1"><label>(1)</label><mml:math id="mml-eqn-1" display="block"><mml:mi>&#x03B3;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mtable columnalign="left left" rowspacing=".2em" columnspacing="1em" displaystyle="false"><mml:mtr><mml:mtd><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>&#x222A;</mml:mo><mml:mrow><mml:mtext>add</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2216;</mml:mo><mml:mrow><mml:mtext>del</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mtd><mml:mtd><mml:mrow><mml:mtext>if&#xA0;</mml:mtext></mml:mrow><mml:mi>s</mml:mi><mml:mo>&#x22A8;</mml:mo><mml:mrow><mml:mtext>pre</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mi mathvariant="normal">&#x22A5;</mml:mi></mml:mtd><mml:mtd><mml:mrow><mml:mtext>otherwise</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable><mml:mo fence="true" stretchy="true" symmetric="true"></mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>Given initial state <inline-formula id="ieqn-16"><mml:math id="mml-ieqn-16"><mml:msub><mml:mi>s</mml:mi><mml:mn>0</mml:mn></mml:msub></mml:math></inline-formula> and goal condition <italic>G</italic>, a plan <inline-formula id="ieqn-17"><mml:math id="mml-ieqn-17"><mml:mi>&#x03C0;</mml:mi><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">&#x27E8;</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo fence="false" stretchy="false">&#x27E9;</mml:mo></mml:math></inline-formula> is valid if and only if there exists a state sequence <inline-formula id="ieqn-18"><mml:math id="mml-ieqn-18"><mml:msub><mml:mi>s</mml:mi><mml:mn>0</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>s</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mi>s</mml:mi><mml:mi>n</mml:mi></mml:msub></mml:math></inline-formula> such that:
<list list-type="simple">
<list-item><label>1.</label><p>For all <inline-formula id="ieqn-19"><mml:math id="mml-ieqn-19"><mml:mi>i</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mi>n</mml:mi><mml:mo stretchy="false">]</mml:mo></mml:math></inline-formula>: <inline-formula id="ieqn-20"><mml:math id="mml-ieqn-20"><mml:msub><mml:mi>s</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mi>&#x03B3;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>s</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula></p></list-item>
<list-item><label>2.</label><p><inline-formula id="ieqn-21"><mml:math id="mml-ieqn-21"><mml:msub><mml:mi>s</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>&#x22A8;</mml:mo><mml:mi>G</mml:mi></mml:math></inline-formula></p></list-item>
</list></p>
<p>The key insight of this formalization framework is that plan executability and correctness are entirely determined by structural relationships (precondition satisfaction, state transition logic) rather than the specific meanings of symbols.</p>
</sec>
<sec id="s2_1_2">
<label>2.1.2</label>
<title>Development of Classical Planning Algorithms</title>
<p>Based on the PDDL framework, the development of symbolic planning algorithms provides important insights for understanding structured reasoning. The FF planner proposed by [<xref ref-type="bibr" rid="ref-7">7</xref>] demonstrated how to utilize structural information for efficient reasoning through heuristic search and the concept of helpful actions. FF&#x2019;s success indicates that effective planning reasoning depends on accurate modeling of precondition and effect relationships, providing an important reference framework for analyzing LLM planning capabilities.</p>
<p>The Fast Downward system developed by [<xref ref-type="bibr" rid="ref-8">8</xref>] further demonstrated the importance of structured representation. The system achieved performance breakthroughs through multi-level abstraction and precise state transition modeling. More importantly, Fast Downward provided a standardized experimental platform for planning research, and its rigorous correctness verification mechanisms laid the technical foundation for subsequent LLM planning evaluation.</p>
</sec>
<sec id="s2_1_3">
<label>2.1.3</label>
<title>Theoretical Analysis of Computational Complexity and Reasoning Capabilities</title>
<p>Theoretical analysis proposed by [<xref ref-type="bibr" rid="ref-9">9</xref>] provides important insights for understanding the nature of planning reasoning. They proved the PSPACE-completeness of STRIPS planning, indicating that even under the most simplified STRIPS framework, planning remains a computationally hard problem requiring structured reasoning rather than simple pattern matching. This theoretical result has important implications for analyzing LLM planning capabilities: if models truly master planning reasoning abilities, they should be able to handle such computational complexity rather than relying solely on lexical patterns.</p>
<p>HTN planning proposed by [<xref ref-type="bibr" rid="ref-10">10</xref>] reduces search complexity by introducing domain knowledge, but the success of this approach precisely illustrates the important impact of domain knowledge on planning performance. Recent work has explored alternative complexity management strategies through collaborative approaches where multiple language model instances coordinate to solve planning problems, demonstrating effectiveness in related reasoning tasks such as machine translation, sentiment analysis, and text summarization [<xref ref-type="bibr" rid="ref-11">11</xref>]. However, these multi-model approaches typically rely on semantic information exchange and domain-specific coordination mechanisms. This observation provides theoretical support for lexical-prior-free evaluation: by removing domain-specific lexical cues, the pure reasoning capabilities of models can be assessed more accurately, independent of coordination strategies or semantic priors.</p>
</sec>
</sec>
<sec id="s2_2">
<label>2.2</label>
<title>Research on LLMs Applications in Planning Tasks</title>
<sec id="s2_2_1">
<label>2.2.1</label>
<title>Exploration of Early Direct Generation Methods</title>
<p>The application of LLMs in planning tasks began with attempts at direct sequence generation. Reference [<xref ref-type="bibr" rid="ref-12">12</xref>] first systematically studied the potential of language models in planning tasks by fine-tuning GPT-2 [<xref ref-type="bibr" rid="ref-13">13</xref>] models to generate simple action sequences. The important finding of this research was that models performed well in controlled environments but had significant limitations when handling complex causal relationships, particularly in tasks requiring precise state tracking.</p>
<p>The introduction of chain-of-thought techniques brought new possibilities to planning tasks. Reference [<xref ref-type="bibr" rid="ref-14">14</xref>] proposed chain-of-thought reasoning that significantly improved performance on complex reasoning tasks by guiding models through structured reasoning (state analysis <inline-formula id="ieqn-22"><mml:math id="mml-ieqn-22"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula> goal decomposition <inline-formula id="ieqn-23"><mml:math id="mml-ieqn-23"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula> action selection <inline-formula id="ieqn-24"><mml:math id="mml-ieqn-24"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula> effect prediction). However, the success of this approach largely depends on the match between reasoning steps and domain knowledge, raising important questions for subsequent lexical-prior-free research.</p>
</sec>
<sec id="s2_2_2">
<label>2.2.2</label>
<title>Research on Structured Approaches and Tool Enhancement</title>
<p>Recognizing the limitations of direct generation methods, researchers began exploring more structured approaches. Reference [<xref ref-type="bibr" rid="ref-15">15</xref>] proposed template-based planning methods that significantly reduced the proportion of invalid plans by constraining the generation process through predefined action templates. The key insight of this work is that structured constraints can improve plan executability, but template design still relies on domain-specific knowledge.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-16">16</xref>] systematically analyzed the possibilities of combining LLMs with symbolic planners. Their research showed that LLMs have advantages in understanding natural language descriptions but still need to rely on traditional planners&#x2019; verification mechanisms to ensure logical consistency. This finding directly supports the necessity of adopting validation-driven methods in this paper.</p>
</sec>
<sec id="s2_2_3">
<label>2.2.3</label>
<title>Discovery and Analysis of Performance Limitations</title>
<p>The groundbreaking research by [<xref ref-type="bibr" rid="ref-1">1</xref>] first systematically exposed the fundamental limitations of LLMs in planning tasks. Through comprehensive evaluation on standard planning benchmarks, they found that even the most advanced models performed poorly on tasks requiring precise logical reasoning. More importantly, they identified models&#x2019; strong dependence on domain knowledge in training data.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-17">17</xref>] further analyzed the nature of LLM planning capabilities. Through controlled experiments, they found that model success largely depends on memory of common scenarios rather than genuine causal reasoning abilities. This finding has important implications for understanding the cognitive capability boundaries of LLMs.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-18">18</xref>] specifically studied GPT-4&#x2019;s performance on classical planning tasks, finding that even the latest models still have significant defects in tasks requiring multi-step reasoning. Their analysis showed that models tend to generate plans that &#x201C;look reasonable&#x201D; but are logically incorrect. Reference [<xref ref-type="bibr" rid="ref-19">19</xref>] extended this evaluation to reasoning-enhanced models, specifically assessing OpenAI&#x2019;s o1-mini on PlanBench, and confirmed that even with enhanced reasoning capabilities, models still cannot reliably plan without systematic validation when lexical priors are removed.</p>
</sec>
</sec>
<sec id="s2_3">
<label>2.3</label>
<title>Verification-Driven and Repair-Based Approaches</title>
<p>Recent advances in LLM reasoning have increasingly emphasized iterative refinement through external feedback mechanisms. Representative approaches include ReAct [<xref ref-type="bibr" rid="ref-20">20</xref>], which interleaves reasoning traces with environment actions, and Reflexion [<xref ref-type="bibr" rid="ref-21">21</xref>], which employs verbal self-reflection to learn from task failures. While these verification-driven paradigms demonstrate substantial improvements on complex reasoning tasks, they operate under fundamentally different constraints than our symbol-agnostic pipeline.</p>
<p><italic>Critical Distinctions from Our Approach</italic></p>
<p>ReAct generates reasoning traces (&#x201C;thoughts&#x201D;) alongside actions, leveraging environmental observations to guide dynamic replanning in tasks like question answering and web navigation. Reflexion extends this through episodic memory and verbal self-reflection, where models generate natural language summaries of failures to improve subsequent attempts. Both approaches achieve strong performance in semantically rich environments but rely fundamentally on interpretable symbolic interfaces.</p>
<p>Our approach differs across four critical dimensions:</p>
<p><bold>Lexical Prior Dependency.</bold> ReAct and Reflexion operate where action names and feedback maintain natural semantics, enabling models to leverage training-time associations. Our pipeline addresses complete lexical obfuscation where symbols like &#x201C;overcome&#x201D; or &#x201C;province&#x201D; bear no relationship to planning concepts. This qualitative distinction renders language-based reflection ineffective (baseline: 0%&#x2013;19.1% success), while our formal verification mechanisms achieve 46.2%&#x2013;48.0% success rates.</p>
<p><bold>Verification Mechanisms.</bold> Existing approaches use language-based feedback&#x2014;environmental observations in ReAct, verbal critiques in Reflexion&#x2014;requiring semantic understanding. We employ formal verification through STRIPS simulation and VAL validation, operating purely on structural logic (precondition satisfaction, state transitions) without symbol semantics, providing rigorous correctness guarantees.</p>
<p><bold>Repair Strategy Specificity.</bold> ReAct and Reflexion adopt general-purpose refinement strategies: regenerating reasoning traces or adjusting high-level plans based on verbal feedback. Our repair controller implements four specialized strategies (First-Step Constraint, Precondition Probing, Parameter Swap &#x0026; Landmarks, Budget-Adaptive Retry) targeting distinct structural failure modes identified through empirical analysis&#x2014;interventions impossible without formal state tracking.</p>
<p><bold>Evaluation Scope.</bold> ReAct and Reflexion are evaluated on tasks where semantic priors aid reasoning (web navigation, household tasks with meaningful action names). Our evaluation protocols target the lexical-prior-free regime with rigorous statistical testing (Wilson CI, effect sizes, hazard profiles), assessing genuine structural reasoning independent of lexical memorization.</p>
<p>These distinctions align with cognitive science perspectives on abstraction [<xref ref-type="bibr" rid="ref-22">22</xref>,<xref ref-type="bibr" rid="ref-23">23</xref>]: while ReAct and Reflexion advance iterative refinement in semantically grounded environments, they do not address reasoning when semantic scaffolding is removed. Our work demonstrates that systematic validation and repair, when designed for symbol-agnostic operation through formal verification, can achieve reliable performance where lexical priors are completely absent&#x2014;establishing a complementary paradigm for systems facing novel domains or adversarial settings where training-time associations are unavailable.</p>
<p>Recent work has further emphasized the necessity of external verification for reliable planning. Reference [<xref ref-type="bibr" rid="ref-24">24</xref>] provided a systematic analysis categorizing LLM contributions to planning into three roles: solver, verifier, and heuristic provider, demonstrating that verification-driven workflows significantly outperform direct generation across multiple benchmarks. These developments reinforce our core thesis that validation-driven closed-loop mechanisms are not merely beneficial but essential for achieving reliable planning under symbol-agnostic conditions.</p>
</sec>
<sec id="s2_4">
<label>2.4</label>
<title>Symbol Obfuscation and Lexical Prior Removal Research</title>
<sec id="s2_4_1">
<label>2.4.1</label>
<title>Identification of the Lexical Prior Problem</title>
<p>The impact of lexical priors on AI system performance was first identified in the knowledge representation field. Reference [<xref ref-type="bibr" rid="ref-25">25</xref>] pointed out that many seemingly intelligent behaviors are actually memory of patterns in training data rather than genuine reasoning capabilities. This observation provided a theoretical foundation for subsequent lexical-prior-free research.</p>
<p>In the planning field, reference [<xref ref-type="bibr" rid="ref-2">2</xref>] first explicitly proposed the concept of lexical priors. Through comparative experiments, they found that when using familiar domain vocabulary (such as &#x201C;pick-up,&#x201D; &#x201C;put-down&#x201D;), LLMs performed well, but this performance mainly came from memory of common patterns in training corpora.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-26">26</xref>] further deepened this understanding by proposing the &#x201C;System 1&#x201D; vs. &#x201C;System 2&#x201D; analytical framework. They argued that LLMs primarily rely on fast pattern recognition (System 1) while lacking deep logical reasoning capabilities (System 2). This analysis provides important insights for understanding the nature of LLM planning capabilities.</p>
</sec>
<sec id="s2_4_2">
<label>2.4.2</label>
<title>Design and Implementation of PlanBench Mystery Domains</title>
<p>The core contribution of PlanBench [<xref ref-type="bibr" rid="ref-27">27</xref>] is the systematic construction of &#x201C;Mystery&#x201D; domains, which provides a standardized technical framework for lexical-prior-free evaluation. Mystery domains use symbol obfuscation techniques to replace all predicate and action names in classical planning domains with semantically neutral random vocabulary, thereby cutting off lexical cues that models might depend on.</p>
<p><bold><italic>Formal Definition of Obfuscation Mapping</italic></bold></p>
<p>The construction of Mystery domains is based on bijective mapping <inline-formula id="ieqn-25"><mml:math id="mml-ieqn-25"><mml:mrow><mml:mi>&#x02133;</mml:mi></mml:mrow><mml:mo>:</mml:mo><mml:mi mathvariant="normal">&#x03A3;</mml:mi><mml:mo stretchy="false">&#x2192;</mml:mo><mml:msup><mml:mi mathvariant="normal">&#x03A3;</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:math></inline-formula>, where <inline-formula id="ieqn-26"><mml:math id="mml-ieqn-26"><mml:mi mathvariant="normal">&#x03A3;</mml:mi></mml:math></inline-formula> is the original symbol set (predicate and action names) and <inline-formula id="ieqn-27"><mml:math id="mml-ieqn-27"><mml:msup><mml:mi mathvariant="normal">&#x03A3;</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:math></inline-formula> is random symbols selected from a predefined vocabulary. The mapping must satisfy strict structure-preserving constraints:
<list list-type="bullet">
<list-item>
<p><bold>Arity preservation:</bold> <inline-formula id="ieqn-28"><mml:math id="mml-ieqn-28"><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mi>p</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>&#x1D4AB;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mrow><mml:mtext>args</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mrow><mml:mtext>args</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>&#x02133;</mml:mi></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow></mml:math></inline-formula></p></list-item>
<list-item>
<p><bold>Type consistency:</bold> Type hierarchy structure <inline-formula id="ieqn-29"><mml:math id="mml-ieqn-29"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>&#x2AAF;</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">&#x21D4;</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>&#x02133;</mml:mi></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2AAF;</mml:mo><mml:mrow><mml:mi>&#x02133;</mml:mi></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula></p></list-item>
<list-item>
<p><bold>Structural isomorphism:</bold> Logical structure of preconditions and effects is completely preserved</p></list-item>
</list></p>
<p><bold><italic>Concrete Example: Blocks World Obfuscation</italic></bold></p>
<p>Taking the classical Blocks World domain as an example, the original domain (Listing 1) includes the following core elements:</p>
<p><boxed-text position="anchor" id="box1">
<label>Listing 1:</label>
<caption>
<title>Original Blocks World Domain</title>
</caption>
<p><monospace>(:predicates</monospace></p>
<p><monospace>&#x2002;&#x2002;(clear ?x - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;(holding ?x - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;(on ?x ?y - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;(ontable ?x - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;(handempty))</monospace></p>
<p><monospace>(:action pick-up</monospace></p>
<p><monospace>&#x2002;&#x2002;:parameters (?x - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;:precondition (and (clear ?x) (ontable ?x) (handempty))</monospace></p>
<p><monospace>&#x2002;&#x2002;:effect (and (not (ontable ?x)) (not (clear ?x))</monospace></p>
<p><monospace>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;(not (handempty)) (holding ?x)))</monospace></p>
</boxed-text></p>
<p>After obfuscation, the Mystery domain (Listing 2) might become:</p>
<p><boxed-text position="anchor" id="box2">
<label>Listing 2:</label>
<caption>
<title>Obfuscated Mystery Domain</title>
</caption>
<p><monospace>(:predicates</monospace></p>
<p><monospace>&#x2002;&#x2002;(province ?x - block) &#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;<italic>; originally clear</italic></monospace></p>
<p><monospace>&#x2002;&#x2002;(pain ?x - block) &#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;<italic>; originally holding</italic></monospace></p>
<p><monospace>&#x2002;&#x2002;(planet ?x ?y - block) &#x2002;&#x2002;&#x2002;&#x2002;&#x2002;<italic>; originally on</italic></monospace></p>
<p><monospace>&#x2002;&#x2002;(harmony ?x - block) &#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;<italic>; originally ontable</italic></monospace></p>
<p><monospace>&#x2002;&#x2002;(craves)) &#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;<italic>; originally handempty</italic></monospace></p>
<p><monospace>(:action overcome</monospace></p>
<p><monospace>&#x2002;&#x2002;:parameters (?x - block)</monospace></p>
<p><monospace>&#x2002;&#x2002;:precondition (and (province ?x) (harmony ?x) (craves))</monospace></p>
<p><monospace>&#x2002;&#x2002;:effect (and (not (harmony ?x)) (not (province ?x))</monospace></p>
<p><monospace>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;(not (craves)) (pain ?x)))</monospace></p>
</boxed-text></p>
<p><bold><italic>Mapping Consistency and Verification</italic></bold></p>
<p>The obfuscation process ensures consistency: within a single evaluation, the mapping remains fixed to avoid &#x201C;same word, different meaning&#x201D; interference. The obfuscated domain is verified through the VAL validator to confirm logical equivalence with the original domain. For example, whether it&#x2019;s &#x2018;(clear a)&#x2019; or &#x2018;(province a)&#x2019;, their roles in state transitions are identical.</p>
<p><bold><italic>Semantically Neutral Random Replacement</italic></bold></p>
<p>The construction of Mystery domains employs a strict random replacement strategy, randomly selecting replacement vocabulary from a predefined semantically neutral vocabulary. Key characteristics include:
<list list-type="bullet">
<list-item>
<p><bold>Complete semantic irrelevance:</bold> Replacement vocabulary (such as planet, province, pain, harmony, craves, etc.) is completely unrelated to original planning concepts, avoiding any semantic cues.</p></list-item>
<list-item>
<p><bold>Randomness guarantee:</bold> The vocabulary selection process is random, not based on semantic similarity or any meaningful associations. For example, the &#x2018;clear&#x2019; predicate representing the &#x201C;clear&#x201D; concept might be replaced by &#x2018;province&#x2019;, having no connection to spatial or political concepts.</p></list-item>
<list-item>
<p><bold>Consistency constraints:</bold> Although selection is random, mappings remain fixed within a single evaluation, ensuring &#x2018;clear&#x2019; always corresponds to &#x2018;province&#x2019;, avoiding &#x201C;same word, different meaning&#x201D; confusion.</p></list-item>
</list></p>
</sec>
<sec id="s2_4_3">
<label>2.4.3</label>
<title>Development of Symbol Obfuscation Techniques</title>
<p>The proposal of PlanBench marks the formal establishment of lexical-prior-free evaluation methods. Reference [<xref ref-type="bibr" rid="ref-27">27</xref>] designed a systematic symbol obfuscation framework that cuts off lexical cues models might depend on by replacing predicate and action names with semantically neutral random vocabulary.</p>
<p>Building on these foundations, recent work has continued to explore LLM robustness under obfuscation. Reference [<xref ref-type="bibr" rid="ref-28">28</xref>] evaluated frontier models (GPT-5, Gemini 2.5 Pro) on both standard and obfuscated PDDL tasks, finding that while performance on standard tasks now competes with classical planners like LAMA, obfuscation still causes significant degradation&#x2014;confirming persistent reliance on token semantics despite architectural improvements. Notably, their work identifies Gemini 2.5 Pro as exhibiting reduced sensitivity to obfuscation compared to earlier models, suggesting incremental progress in symbolic reasoning capabilities. Reference [<xref ref-type="bibr" rid="ref-29">29</xref>] introduced PLANET, a comprehensive benchmark collection specifically designed to evaluate LLM planning capabilities across diverse obfuscation strategies, providing standardized evaluation protocols that complement PlanBench&#x2019;s Mystery domains.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-30">30</xref>] built upon this by studying the effectiveness of different obfuscation strategies. They compared the effects of random obfuscation, adversarial obfuscation, and structured obfuscation, finding that adversarial obfuscation (using semantically opposite vocabulary) was most effective at exposing models&#x2019; lexical dependencies.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-31">31</xref>] proposed more refined obfuscation techniques by maintaining consistency in certain semantic categories to study the role of different levels of lexical knowledge. Their research showed that even abstract semantic category information affects model performance.</p>
<p>These recent advancements validate the continued relevance of symbol-agnostic evaluation while highlighting that raw model improvements alone remain insufficient without systematic validation mechanisms.</p>
</sec>
<sec id="s2_4_4">
<label>2.4.4</label>
<title>Theoretical Analysis of Lexical-Prior-Free Evaluation</title>
<p>Reference [<xref ref-type="bibr" rid="ref-23">23</xref>] analyzed the theoretical foundation of symbol obfuscation from a cognitive science perspective. They argued that genuine intelligence should be able to handle arbitrary symbol systems without depending on specific lexical conventions. This viewpoint provides cognitive science support for lexical-prior-free evaluation.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-22">22</xref>] further discussed the relationship between abstraction capabilities and lexical independence. She pointed out that an important characteristic of higher-level cognitive abilities is the capacity to abstract and transfer between different symbol systems, an area where current AI systems still show significant deficiencies.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-32">32</xref>] proposed similar views in ARC (Abstraction and Reasoning Corpus) research, emphasizing the importance of evaluating systems&#x2019; genuine reasoning capabilities rather than memory abilities. Although ARC focuses on visual reasoning, its design philosophy is highly consistent with lexical-prior-free evaluation.</p>
</sec>
</sec>
<sec id="s2_5">
<label>2.5</label>
<title>Research Development in Planning Evaluation Methods</title>
<sec id="s2_5_1">
<label>2.5.1</label>
<title>Development of Planning Evaluation Frameworks</title>
<p>The development of planning evaluation methods is closely related to understanding the nature of planning capabilities. Reference [<xref ref-type="bibr" rid="ref-33">33</xref>] emphasized the importance of standardized evaluation at the AIPS-2000 conference, particularly noting that the lack of unified correctness standards was an important factor hindering progress in planning research. This viewpoint provided important impetus for subsequently establishing rigorous verification mechanisms.</p>
<p>The establishment of the International Planning Competition (IPC) [<xref ref-type="bibr" rid="ref-34">34</xref>] confirmed a multi-dimensional evaluation framework whose core principle is that planning algorithm evaluation must be based on rigorous correctness verification, not merely surface performance metrics. This principle has important guiding significance for understanding LLM planning capabilities as it emphasizes the importance of structured verification relative to heuristic evaluation.</p>
</sec>
<sec id="s2_5_2">
<label>2.5.2</label>
<title>Development of Validation Tools</title>
<p>The development of VAL represents an important advance in planning evaluation technology. Reference [<xref ref-type="bibr" rid="ref-35">35</xref>] designed a complete PDDL validation framework, providing authoritative correctness checking tools for the entire planning community. VAL&#x2019;s importance lies not only in its technical implementation but also in establishing unified validation standards.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-36">36</xref>] further extended validation technology in their PDDL&#x002B; research, addressing validation problems for continuous time and hybrid systems. Their work showed that as planning language expressiveness increases, validation technology must develop accordingly.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-37">37</xref>] developed comparative frameworks for various validation tools, systematically analyzing the advantages and disadvantages of different validation methods. Their research provided guidance for selecting appropriate validation tools.</p>
<p>Recent developments have further advanced planning evaluation methodologies. Reference [<xref ref-type="bibr" rid="ref-38">38</xref>] conducted comprehensive studies on error detection and correction in PDDL domain models, revealing that LLMs demonstrate stronger capabilities in translation tasks than in direct planning, supporting our design decision to separate semantic comprehension from plan generation. This finding emphasizes the importance of rigorous validation mechanisms when employing LLMs in planning workflows&#x2014;a principle we adopt throughout our evaluation protocol by using VAL for sound plan verification.</p>
<p>We can see that: the symbolic planning field has developed mature theoretical foundations and technical frameworks; applications of LLMs in planning tasks have made progress but still face fundamental limitations; verification-driven approaches like ReAct and Reflexion have advanced iterative refinement in semantically rich environments through language-based feedback, yet the lexical-prior-free regime remains unaddressed; symbol obfuscation techniques provide effective means for rigorous evaluation of structural reasoning capabilities; and the continuous development of evaluation methods provides important support for research progress. These research achievements collectively lay a solid foundation for the work in this paper.</p>
</sec>
</sec>
</sec>
<sec id="s3">
<label>3</label>
<title>Methodology</title>
<p>This chapter proposes a Symbol-Agnostic Planning Pipeline that aims to construct a verifiable and repairable end-to-end planning system under lexical-prior-free constraints. Through modular design, this method achieves structured reasoning that relies entirely on the logical consistency of preconditions, effect relationships, and state dependencies, rather than lexical semantic cues.</p>
<sec id="s3_1">
<label>3.1</label>
<title>Problem Formulation and Design Objectives</title>
<sec id="s3_1_1">
<label>3.1.1</label>
<title>Core Challenges and Problem Setting</title>
<p>Based on the analysis of related work in <xref ref-type="sec" rid="s2">Section 2</xref>, existing LLMs exhibit significant deficiencies in planning capabilities under lexical-prior-free conditions. Specifically:
<list list-type="bullet">
<list-item>
<p><bold>Insufficient structural reasoning capabilities:</bold> As demonstrated by [<xref ref-type="bibr" rid="ref-1">1</xref>], model failures in Mystery domains are primarily dominated by unsatisfied preconditions and state transition errors, reflecting a lack of understanding of PDDL structural semantics.</p></list-item>
<list-item>
<p><bold>Over-reliance on lexical dependencies:</bold> Related work shows that traditional methods based on lexical matching or templates completely fail in symbol obfuscation environments, exposing excessive dependence on surface semantic cues.</p></list-item>
<list-item>
<p><bold>Lack of systematic repair strategies:</bold> Existing methods lack structured repair mechanisms based on validation feedback, failing to effectively utilize failure information provided by validation tools like VAL for iterative improvement.</p></list-item>
</list></p>
</sec>
<sec id="s3_1_2">
<label>3.1.2</label>
<title>Design Principles and Symbol-Agnostic Mechanisms</title>
<p>Based on the above challenge analysis, this paper&#x2019;s method follows the following core design principles:
<list list-type="bullet">
<list-item>
<p><bold>Structure-first principle:</bold> Rely solely on the logical consistency of preconditions, effect relationships, and state dependencies, completely avoiding dictionary matching or semantic inference based on names.</p></list-item>
<list-item>
<p><bold>Validation-driven principle:</bold> Establish a &#x201C;generate<inline-formula id="ieqn-30"><mml:math id="mml-ieqn-30"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>verify<inline-formula id="ieqn-31"><mml:math id="mml-ieqn-31"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>repair&#x201D; closed-loop mechanism, providing authoritative correctness determination and structured failure diagnosis through STRIPS simulation and VAL validation.</p></list-item>
<list-item>
<p><bold>Budget-aware principle:</bold> Maximize success rate within limited attempt budgets, with particular focus on marginal gains in small budget scenarios.</p></list-item>
</list></p>
<p><bold><italic>What Makes the System Symbol-Agnostic</italic></bold></p>
<p>Beyond merely processing obfuscated symbols, our system achieves genuine symbol-agnosticism through architectural design where every component operates on structural relationships rather than semantic interpretations. This distinguishes our approach from systems that tolerate random symbols but still rely on semantic reasoning internally:
<list list-type="bullet">
<list-item>
<p><bold>Structural constraint extraction:</bold> The SC module extracts constraints not through lexical matching (e.g., recognizing &#x201C;pick-up&#x201D; patterns) but by parsing PDDL structural relationships directly from domain specifications: which predicates appear in which action preconditions (<inline-formula id="ieqn-32"><mml:math id="mml-ieqn-32"><mml:mi>p</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mtext>pre</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>), which parameters share type constraints (<inline-formula id="ieqn-33"><mml:math id="mml-ieqn-33"><mml:mrow><mml:mtext>type</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03B8;</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2AAF;</mml:mo><mml:mrow><mml:mtext>type</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03B8;</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>), which effects delete which predicates (<inline-formula id="ieqn-34"><mml:math id="mml-ieqn-34"><mml:mi>p</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mtext>del</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>). The constraint set <italic>C</italic> encodes purely structural dependencies&#x2014;arity preservation, type consistency, precondition-effect chains&#x2014;independent of whether symbols are &#x201C;clear&#x201D;, &#x201C;province&#x201D;, or arbitrary tokens.</p></list-item>
<list-item>
<p><bold>Formal set-theoretic verification:</bold> STRIPS simulation operates through set membership checking (<inline-formula id="ieqn-35"><mml:math id="mml-ieqn-35"><mml:mrow><mml:mtext>pre</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo><mml:mi>s</mml:mi></mml:math></inline-formula>) and set operations (<inline-formula id="ieqn-36"><mml:math id="mml-ieqn-36"><mml:msup><mml:mi>s</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:mo>=</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>&#x222A;</mml:mo><mml:mrow><mml:mtext>add</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2216;</mml:mo><mml:mrow><mml:mtext>del</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula>), treating symbols as atomic identifiers in Boolean predicates. VAL validation verifies logical entailment (<inline-formula id="ieqn-37"><mml:math id="mml-ieqn-37"><mml:msub><mml:mi>s</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>&#x22A8;</mml:mo><mml:mi>G</mml:mi></mml:math></inline-formula>) through syntactic pattern matching against PDDL specifications, never interpreting what &#x201C;province(?x)&#x201D; or &#x201C;overcome(?x)&#x201D; &#x201C;mean&#x201D; beyond their roles in state transitions. This formal approach provides correctness guarantees independent of symbol semantics.</p></list-item>
<list-item>
<p><bold>Structure-preserving translation:</bold> The ST module performs bijective mapping based solely on structural signatures extracted from domain specification <inline-formula id="ieqn-38"><mml:math id="mml-ieqn-38"><mml:msub><mml:mrow><mml:mi>&#x1D49F;</mml:mi></mml:mrow><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>: matching parameter counts (<inline-formula id="ieqn-39"><mml:math id="mml-ieqn-39"><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mrow><mml:mtext>args</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow><mml:mrow><mml:mtext>args</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:mo stretchy="false">|</mml:mo></mml:mrow></mml:math></inline-formula>), preserving type hierarchies, and maintaining precondition-effect correspondence. Translation correctness depends on structural alignment rather than semantic similarity&#x2014;the system would function identically whether translating &#x201C;pick-up&#x201D; to &#x201C;overcome&#x201D;, &#x201C;X7&#x201D;, or any arbitrary symbol satisfying arity constraints.</p></list-item>
<list-item>
<p><bold>Failure-pattern-driven repair:</bold> RC&#x2019;s four strategies target structural failure modes identified through position-based analysis (step <inline-formula id="ieqn-40"><mml:math id="mml-ieqn-40"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula> vs. <inline-formula id="ieqn-41"><mml:math id="mml-ieqn-41"><mml:mi>s</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>3</mml:mn></mml:math></inline-formula>), set-based diagnosis (which predicates <inline-formula id="ieqn-42"><mml:math id="mml-ieqn-42"><mml:mi>p</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mtext>pre</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> are missing from current state <inline-formula id="ieqn-43"><mml:math id="mml-ieqn-43"><mml:mi>s</mml:mi></mml:math></inline-formula>), and graph-based dependency tracking (which action sequences satisfy landmark orderings). These interventions operate on formal failure signals&#x2014;&#x201C;precondition <inline-formula id="ieqn-44"><mml:math id="mml-ieqn-44"><mml:mi>p</mml:mi></mml:math></inline-formula> unsatisfied at step <inline-formula id="ieqn-45"><mml:math id="mml-ieqn-45"><mml:mi>s</mml:mi></mml:math></inline-formula>&#x201D;, &#x201C;state <inline-formula id="ieqn-46"><mml:math id="mml-ieqn-46"><mml:msub><mml:mi>s</mml:mi><mml:mn>4</mml:mn></mml:msub></mml:math></inline-formula> lacks predicate <inline-formula id="ieqn-47"><mml:math id="mml-ieqn-47"><mml:mi>q</mml:mi></mml:math></inline-formula>&#x201D;&#x2014;without accessing or requiring semantic knowledge of what <inline-formula id="ieqn-48"><mml:math id="mml-ieqn-48"><mml:mi>p</mml:mi></mml:math></inline-formula> or <inline-formula id="ieqn-49"><mml:math id="mml-ieqn-49"><mml:mi>q</mml:mi></mml:math></inline-formula> represent in the planning domain.</p></list-item>
<list-item>
<p><bold>Constraint propagation without semantics:</bold> When RC updates constraint set <italic>C</italic> or modifies text plan <inline-formula id="ieqn-50"><mml:math id="mml-ieqn-50"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>, modifications propagate through structural consistency rules encoded in PDDL: &#x201C;if action <inline-formula id="ieqn-51"><mml:math id="mml-ieqn-51"><mml:mi>a</mml:mi></mml:math></inline-formula> requires predicate <inline-formula id="ieqn-52"><mml:math id="mml-ieqn-52"><mml:mi>p</mml:mi></mml:math></inline-formula> in preconditions, ensure some prior action <inline-formula id="ieqn-53"><mml:math id="mml-ieqn-53"><mml:msup><mml:mi>a</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:math></inline-formula> has <inline-formula id="ieqn-54"><mml:math id="mml-ieqn-54"><mml:mi>p</mml:mi></mml:math></inline-formula> in add-effects&#x201D;, &#x201C;if predicates <inline-formula id="ieqn-55"><mml:math id="mml-ieqn-55"><mml:msub><mml:mi>p</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:math></inline-formula> are mutex, no state can satisfy both simultaneously&#x201D;. These propagation rules reference only structural relationships (<inline-formula id="ieqn-56"><mml:math id="mml-ieqn-56"><mml:mrow><mml:mtext>pre</mml:mtext></mml:mrow></mml:math></inline-formula>, <inline-formula id="ieqn-57"><mml:math id="mml-ieqn-57"><mml:mrow><mml:mtext>add</mml:mtext></mml:mrow></mml:math></inline-formula>, <inline-formula id="ieqn-58"><mml:math id="mml-ieqn-58"><mml:mrow><mml:mtext>del</mml:mtext></mml:mrow></mml:math></inline-formula> sets; type hierarchies; mutex constraints) defined in domain <inline-formula id="ieqn-59"><mml:math id="mml-ieqn-59"><mml:msub><mml:mrow><mml:mi>&#x1D49F;</mml:mi></mml:mrow><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, remaining valid regardless of symbol obfuscation mapping.</p></list-item>
</list></p>
<p>This architectural symbol-agnosticism is verifiable: the same pipeline, without modification or recalibration, achieves consistent performance across different obfuscation mappings <inline-formula id="ieqn-60"><mml:math id="mml-ieqn-60"><mml:msub><mml:mi>&#x03D5;</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>&#x03D5;</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo></mml:math></inline-formula> applied to the same underlying domain structure. The system does not &#x201C;learn&#x201D; that &#x201C;overcome&#x201D; means &#x201C;pick-up&#x201D;; instead, it reasons that &#x201C;action <inline-formula id="ieqn-61"><mml:math id="mml-ieqn-61"><mml:mi>a</mml:mi></mml:math></inline-formula> with parameters <inline-formula id="ieqn-62"><mml:math id="mml-ieqn-62"><mml:mo fence="false" stretchy="false">&#x27E8;</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo fence="false" stretchy="false">&#x27E9;</mml:mo></mml:math></inline-formula> requires predicates <inline-formula id="ieqn-63"><mml:math id="mml-ieqn-63"><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mn>3</mml:mn></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></inline-formula> and produces effects <inline-formula id="ieqn-64"><mml:math id="mml-ieqn-64"><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mi mathvariant="normal">&#x00AC;</mml:mi><mml:msub><mml:mi>p</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>,</mml:mo><mml:mi mathvariant="normal">&#x00AC;</mml:mi><mml:msub><mml:mi>p</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>,</mml:mo><mml:mi mathvariant="normal">&#x00AC;</mml:mi><mml:msub><mml:mi>p</mml:mi><mml:mn>3</mml:mn></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mn>4</mml:mn></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mo>?</mml:mo><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></inline-formula>&#x201D;&#x2014;structural facts that hold invariant under symbol substitution. This contrasts fundamentally with approaches where obfuscated symbols merely serve as opaque inputs to semantic reasoning processes that would fail if symbols lacked training-time associations.</p>
</sec>
<sec id="s3_1_3">
<label>3.1.3</label>
<title>Formalized Objectives</title>
<p>Let the set of feasible plans in the obfuscated symbol space be:
<disp-formula id="eqn-2"><label>(2)</label><mml:math id="mml-eqn-2" display="block"><mml:mi mathvariant="normal">&#x03A0;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mi>&#x03C0;</mml:mi><mml:mo>&#x2223;</mml:mo><mml:mrow><mml:mtext>VAL</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mi>&#x03C0;</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mrow><mml:mtext>true</mml:mtext></mml:mrow><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></disp-formula>where <inline-formula id="ieqn-65"><mml:math id="mml-ieqn-65"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula> represent the domain, initial state, and goal condition processed through PlanBench obfuscation mapping <inline-formula id="ieqn-66"><mml:math id="mml-ieqn-66"><mml:mi>&#x03D5;</mml:mi></mml:math></inline-formula>, respectively. As described in <xref ref-type="sec" rid="s2">Section 2</xref>, obfuscation mapping <inline-formula id="ieqn-67"><mml:math id="mml-ieqn-67"><mml:mi>&#x03D5;</mml:mi></mml:math></inline-formula> replaces original predicate and action names with semantically irrelevant random vocabulary while strictly preserving structural relationships.</p>
<p>Given attempt budget <inline-formula id="ieqn-68"><mml:math id="mml-ieqn-68"><mml:mi>b</mml:mi><mml:mo>&#x2264;</mml:mo><mml:mi>B</mml:mi></mml:math></inline-formula> and repair strategy <inline-formula id="ieqn-69"><mml:math id="mml-ieqn-69"><mml:mrow><mml:mi>&#x211B;</mml:mi></mml:mrow></mml:math></inline-formula>, define success probability:
<disp-formula id="eqn-3"><label>(3)</label><mml:math id="mml-eqn-3" display="block"><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:munder><mml:mo movablelimits="true" form="prefix">Pr</mml:mo><mml:mrow><mml:mrow><mml:mi>&#x211B;</mml:mi></mml:mrow></mml:mrow></mml:munder><mml:mo stretchy="false">[</mml:mo><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mi>&#x03C0;</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mi mathvariant="normal">&#x03A0;</mml:mi><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>and found within&#xA0;</mml:mtext></mml:mrow><mml:mi>b</mml:mi><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>attempts</mml:mtext></mml:mrow><mml:mo stretchy="false">]</mml:mo></mml:math></disp-formula></p>
<p>The optimization objective of this method is:
<disp-formula id="eqn-4"><label>(4)</label><mml:math id="mml-eqn-4" display="block"><mml:munder><mml:mo movablelimits="true" form="prefix">max</mml:mo><mml:mrow><mml:mrow><mml:mi>&#x211B;</mml:mi></mml:mrow></mml:mrow></mml:munder><mml:mi>J</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>&#x211B;</mml:mi></mml:mrow><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mi>&#x03B1;</mml:mi><mml:mo>&#x22C5;</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>&#x2212;</mml:mo><mml:mi>&#x03B2;</mml:mi><mml:mo>&#x22C5;</mml:mo><mml:mrow><mml:mover><mml:mi>T</mml:mi><mml:mo stretchy="false">&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>&#x2212;</mml:mo><mml:mi>&#x03B3;</mml:mi><mml:mo>&#x22C5;</mml:mo><mml:munder><mml:mo movablelimits="true" form="prefix">max</mml:mo><mml:mi>s</mml:mi></mml:munder><mml:mi>h</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></disp-formula>where <inline-formula id="ieqn-70"><mml:math id="mml-ieqn-70"><mml:mrow><mml:mover><mml:mi>T</mml:mi><mml:mo stretchy="false">&#x007E;</mml:mo></mml:mover></mml:mrow></mml:math></inline-formula> represents robust timing statistics, <inline-formula id="ieqn-71"><mml:math id="mml-ieqn-71"><mml:mi>h</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> represents failure risk at step <inline-formula id="ieqn-72"><mml:math id="mml-ieqn-72"><mml:mi>s</mml:mi></mml:math></inline-formula>, and <inline-formula id="ieqn-73"><mml:math id="mml-ieqn-73"><mml:mi>&#x03B1;</mml:mi><mml:mo>,</mml:mo><mml:mi>&#x03B2;</mml:mi><mml:mo>,</mml:mo><mml:mi>&#x03B3;</mml:mi><mml:mo>&#x003E;</mml:mo><mml:mn>0</mml:mn></mml:math></inline-formula> are weight parameters.</p>
</sec>
</sec>
<sec id="s3_2">
<label>3.2</label>
<title>System Overview and Processing Workflow</title>
<p>To provide readers with an intuitive understanding of our approach, we first present the complete end-to-end processing workflow through a concrete example, then detail each component and mechanism in subsequent sections.</p>
<sec id="s3_2_1">
<label>3.2.1</label>
<title>Overall Pipeline Design</title>
<p>Our system adopts a modular pipeline architecture with six core processing components and two auxiliary control components. The system receives natural language task description <inline-formula id="ieqn-74"><mml:math id="mml-ieqn-74"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula> and obfuscated PDDL problem <inline-formula id="ieqn-75"><mml:math id="mml-ieqn-75"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> as external inputs, and outputs an executable plan <inline-formula id="ieqn-76"><mml:math id="mml-ieqn-76"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula> that achieves goals in the obfuscated symbol space. The pipeline operates through sequential processing stages with validation-driven feedback loops, enabling iterative refinement when failures occur.</p>
<p><xref ref-type="fig" rid="fig-2">Fig. 2</xref> illustrates the complete workflow through a concrete example with goal &#x201C;stack a on c&#x201D; in a Mystery domain. The figure demonstrates:</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>System architecture and processing workflow of the symbol-agnostic closed-loop planning pipeline illustrated with a two-attempt example</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-2.tif"/>
</fig>
<p><list list-type="bullet">
<list-item>
<p><bold>Data flow progression:</bold> How external inputs (<inline-formula id="ieqn-77"><mml:math id="mml-ieqn-77"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula>, <inline-formula id="ieqn-78"><mml:math id="mml-ieqn-78"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-79"><mml:math id="mml-ieqn-79"><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-80"><mml:math id="mml-ieqn-80"><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>) flow through the processing pipeline, transforming from natural language to constraints (<italic>C</italic>), to text plans (<inline-formula id="ieqn-81"><mml:math id="mml-ieqn-81"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>), to symbol plans (<inline-formula id="ieqn-82"><mml:math id="mml-ieqn-82"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>).</p></list-item>
<list-item>
<p><bold>Mystery domain mappings:</bold> The complete symbol obfuscation (pick-up<inline-formula id="ieqn-83"><mml:math id="mml-ieqn-83"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>overcome, stack<inline-formula id="ieqn-84"><mml:math id="mml-ieqn-84"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>feast, clear<inline-formula id="ieqn-85"><mml:math id="mml-ieqn-85"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>province, on<inline-formula id="ieqn-86"><mml:math id="mml-ieqn-86"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>planet, etc.), showing how PDDL structure is preserved while lexical semantics are removed.</p></list-item>
<list-item>
<p><bold>Validation checkpoints:</bold> Three-tier validation mechanism (CC static checking, SIM step-by-step simulation, VAL semantic validation) with explicit branch points for Pass/Reject decisions.</p></list-item>
<list-item>
<p><bold>Failure-repair cycles:</bold> Two complete attempts showing initial failure at step 4 due to blocked preconditions, RC&#x2019;s strategy selection (Parameter Swap &#x0026; Landmarks), and successful convergence after repair.</p></list-item>
<list-item>
<p><bold>Signal aggregation:</bold> Continuous monitoring by SA component collecting validation signals from all checkpoints throughout the process.</p></list-item>
</list></p>
</sec>
<sec id="s3_2_2">
<label>3.2.2</label>
<title>Walkthrough of the Example</title>
<p>The workflow demonstrates two complete processing cycles:</p>
<p><italic>Attempt 1: Initial Generation and Failure Detection</italic></p>
<p>The process begins with SC extracting constraints from task description <inline-formula id="ieqn-87"><mml:math id="mml-ieqn-87"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula>. LP receives both the constraint set <italic>C</italic> (from SC) and <inline-formula id="ieqn-88"><mml:math id="mml-ieqn-88"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula> (as independent input), generating initial text plan [&#x201C;pick-up b&#x201D;, &#x201C;stack b c&#x201D;, &#x201C;pick-up a&#x201D;, &#x201C;stack a c&#x201D;]. ST translates this to Mystery symbols using domain <inline-formula id="ieqn-89"><mml:math id="mml-ieqn-89"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>: [overcome(b), feast(b,c), overcome(a), feast(a,c)].</p>
<p>The plan passes CC&#x2019;s static consistency check and enters SIM for execution with initial state <inline-formula id="ieqn-90"><mml:math id="mml-ieqn-90"><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>. SIM successfully executes steps 1&#x2013;3 but fails at step 4: feast(a,c) cannot execute because its precondition province(c) (Mystery symbol for clear(c)) is not satisfied&#x2014;c is blocked by the earlier feast(b,c) action. This mid-segment failure (s &#x003D; 4) is reported to RC, and the failure signal is archived by SA.</p>
<p><italic>Repair Cycle: Strategic Intervention</italic></p>
<p>RC analyzes the failure pattern&#x2014;a blocked precondition at mid-segment step&#x2014;and selects the Parameter Swap &#x0026; Landmarks strategy from its four available strategies. RC updates constraint set <italic>C</italic> to include landmark injection and parameter reordering instructions, then feeds this enhanced constraint back to LP for regeneration.</p>
<p><italic>Attempt 2: Repaired Generation and Successful Validation</italic></p>
<p>LP regenerates with updated constraints, producing text plan [&#x201C;pick-up a&#x201D;, &#x201C;stack a b&#x201D;, &#x201C;unstack a b&#x201D;, &#x201C;stack a c&#x201D;]. ST translates to: [overcome(a), feast(a,b), separate(a,b), feast(a,c)], where separate is the Mystery symbol for unstack. This enhanced plan includes temporary intermediate actions to avoid blocking.</p>
<p>The repaired plan passes CC&#x2019;s check, successfully executes all steps in SIM (with SA collecting success signals), and passes VAL&#x2019;s final semantic validation confirming goal planet(a,c) is achieved. The system outputs the validated symbol plan, demonstrating successful convergence within budget <inline-formula id="ieqn-91"><mml:math id="mml-ieqn-91"><mml:mi>b</mml:mi><mml:mo>=</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula> attempts.</p>
<p>This example illustrates the core mechanism: validation-driven feedback enables intelligent repair through structured failure analysis, achieving effective planning under lexical-prior-free constraints.</p>
</sec>
</sec>
<sec id="s3_3">
<label>3.3</label>
<title>Core Processing Components</title>
<p>Having seen the overall workflow, we now detail each component&#x2019;s design and functionality.</p>
<sec id="s3_3_1">
<label>3.3.1</label>
<title>Sequential Processing Pipeline</title>
<p>The six core components form the main processing pipeline:</p>
<p><italic>Semantic Comprehension Module (SC)</italic></p>
<p>SC extracts structured constraints from natural language task description <inline-formula id="ieqn-92"><mml:math id="mml-ieqn-92"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula>, forming constraint set <italic>C</italic>. This module does not rely on lexical similarity but extracts action parameter constraints, required predicate sets, and mutual exclusion hints based on structural consistency principles.</p>
<p>Interface definition: <inline-formula id="ieqn-93"><mml:math id="mml-ieqn-93"><mml:mrow><mml:mtext>SC</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:mo stretchy="false">&#x2192;</mml:mo><mml:mi>C</mml:mi></mml:math></inline-formula></p>
<p><italic>Language Planner (LP)</italic></p>
<p>LP receives both constraint set <italic>C</italic> (from SC) and task description <inline-formula id="ieqn-94"><mml:math id="mml-ieqn-94"><mml:mi>&#x03C4;</mml:mi></mml:math></inline-formula> (as independent external input) to generate structured text plans <inline-formula id="ieqn-95"><mml:math id="mml-ieqn-95"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>. This dual-input design maintains natural language context while adhering to extracted structural constraints. The module reduces invalid combinations through templated slots and consistency checking while maintaining generation diversity.</p>
<p>Interface definition: <inline-formula id="ieqn-96"><mml:math id="mml-ieqn-96"><mml:mrow><mml:mtext>LP</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>C</mml:mi><mml:mo>,</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">&#x2192;</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula></p>
<p><italic>Symbol Translator (ST)</italic></p>
<p>ST maps text plan <inline-formula id="ieqn-97"><mml:math id="mml-ieqn-97"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula> to obfuscated symbol plan <inline-formula id="ieqn-98"><mml:math id="mml-ieqn-98"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula> using domain definition <inline-formula id="ieqn-99"><mml:math id="mml-ieqn-99"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>. This translation ensures complete consistency with preconditions and effects of each action in the Mystery domain, performing the critical transformation from natural language to lexical-prior-free symbols.</p>
<p>Interface definition: <inline-formula id="ieqn-100"><mml:math id="mml-ieqn-100"><mml:mrow><mml:mtext>ST</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">&#x2192;</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula></p>
<p><italic>Consistency Checker (CC)</italic></p>
<p>CC performs static screening before expensive simulation, implementing a binary decision mechanism. Plans with obvious errors (unsatisfied preconditions, parameter type mismatches) are rejected with diagnostic information and sent directly to RC. Valid plans proceed to simulation, reducing computational overhead.</p>
<p>Interface definition: <inline-formula id="ieqn-101"><mml:math id="mml-ieqn-101"><mml:mrow><mml:mtext>CC</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo stretchy="false">&#x2192;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mrow><mml:mtext>Pass</mml:mtext></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mtext>Reject</mml:mtext></mml:mrow><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mrow><mml:mtext>Diagnostic Info</mml:mtext></mml:mrow></mml:math></inline-formula></p>
<p><italic>STRIPS Simulator (SIM)</italic></p>
<p>Plans passing CC enter SIM for step-by-step execution simulation using initial state <inline-formula id="ieqn-102"><mml:math id="mml-ieqn-102"><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>. SIM executes each action sequentially, tracking state transitions and identifying the first failure point. The module returns both the resulting state and detailed failure analysis including step location and missing preconditions.</p>
<p>Interface definition: <inline-formula id="ieqn-103"><mml:math id="mml-ieqn-103"><mml:mrow><mml:mtext>SIM</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">&#x2192;</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mtext>State</mml:mtext></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mtext>Report</mml:mtext></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula></p>
<p><italic>VAL Validator Interface (VAL)</italic></p>
<p>Plans successfully passing SIM proceed to VAL for rigorous semantic validation. Using domain <inline-formula id="ieqn-104"><mml:math id="mml-ieqn-104"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, initial state <inline-formula id="ieqn-105"><mml:math id="mml-ieqn-105"><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, and goal condition <inline-formula id="ieqn-106"><mml:math id="mml-ieqn-106"><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>, VAL provides complete PDDL semantic checking, confirming whether plans truly achieve goal conditions.</p>
<p>Interface definition: <inline-formula id="ieqn-107"><mml:math id="mml-ieqn-107"><mml:mrow><mml:mtext>VAL</mml:mtext></mml:mrow><mml:mo>:</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>I</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">&#x2192;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mrow><mml:mtext>Success</mml:mtext></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mtext>Failure</mml:mtext></mml:mrow><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mrow><mml:mtext>Report</mml:mtext></mml:mrow></mml:math></inline-formula></p>
</sec>
<sec id="s3_3_2">
<label>3.3.2</label>
<title>Auxiliary Control Components</title>
<p>Two components provide system-wide control and monitoring:</p>
<p><italic>Repair Controller (RC)</italic></p>
<p>RC is the core control component responsible for parsing validation failure signals and executing repair strategies. RC does not directly modify symbol plan <inline-formula id="ieqn-108"><mml:math id="mml-ieqn-108"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>, but guides next-round generation by updating constraint set <italic>C</italic> (feeding back to LP) or modifying text plan <inline-formula id="ieqn-109"><mml:math id="mml-ieqn-109"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula> (feeding back to ST).</p>
<p>RC implements four core repair strategies:
<list list-type="bullet">
<list-item>
<p><bold>First-Step Constraint:</bold> When failure occurs at <inline-formula id="ieqn-110"><mml:math id="mml-ieqn-110"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>, strengthen precondition constraints for the first action.</p></list-item>
<list-item>
<p><bold>Precondition Probing:</bold> Perform completion or action replacement based on missing predicate information.</p></list-item>
<list-item>
<p><bold>Parameter Swap &#x0026; Landmarks:</bold> Execute parameter swapping for highly coupled action-predicate pairs, or insert intermediate predicate landmarks (as demonstrated in the workflow example).</p></list-item>
<list-item>
<p><bold>Budget-Adaptive Retry:</bold> Dynamically decide continuation strategies based on marginal gains.</p></list-item>
</list></p>
<p><italic>Signal Aggregator (SA)</italic></p>
<p>SA operates as a parallel monitoring component, continuously archiving validation signals from CC, SIM, and VAL throughout the entire pipeline. This aggregation supports statistical analysis and interpretability profile generation.</p>
</sec>
</sec>
<sec id="s3_4">
<label>3.4</label>
<title>Data Contracts and System Invariants</title>
<sec id="s3_4_1">
<label>3.4.1</label>
<title>Core Data Artifacts</title>
<p>Core data artifacts flow through the system:
<list list-type="bullet">
<list-item>
<p><bold>Constraint set <italic>C</italic>:</bold> Contains action parameter constraints, required predicate sets, mutual exclusion hints, and type constraints. Flows from SC to LP, and can be updated by RC during repair.</p></list-item>
<list-item>
<p><bold>Text plan <inline-formula id="ieqn-111"><mml:math id="mml-ieqn-111"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>:</bold> Structured action sequences containing slots and landmark information. Flows from LP to ST, and can be modified by RC.</p></list-item>
<list-item>
<p><bold>Symbol plan <inline-formula id="ieqn-112"><mml:math id="mml-ieqn-112"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>sym</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>:</bold> Action instance sequences strictly matching domain definitions. Flows from ST through CC, SIM, and VAL.</p></list-item>
<list-item>
<p><bold>Validation reports:</bold> Contains failure steps, missing preconditions, violated constraints, etc. Generated by CC, SIM, and VAL; collected by SA; analyzed by RC.</p></list-item>
</list></p>
</sec>
<sec id="s3_4_2">
<label>3.4.2</label>
<title>Inter-Module Invariants</title>
<p>The system ensures structural consistency through invariants:
<list list-type="bullet">
<list-item>
<p><bold>Structure preservation invariant:</bold> All translation and repair operations preserve PDDL structural semantics, disallowing name-based semantic inference.</p></list-item>
<list-item>
<p><bold>Validation consistency invariant:</bold> All validation operations are strictly executed within the obfuscated symbol space, avoiding semantic leakage.</p></list-item>
<list-item>
<p><bold>Repair locality invariant:</bold> Repair operations only affect <italic>C</italic> and <inline-formula id="ieqn-113"><mml:math id="mml-ieqn-113"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula>, without directly modifying symbol-level characters.</p></list-item>
</list></p>
</sec>
</sec>
<sec id="s3_5">
<label>3.5</label>
<title>Repair Strategies and Budget Management</title>
<sec id="s3_5_1">
<label>3.5.1</label>
<title>Failure Mode Analysis</title>
<p>Based on Mystery domain failure patterns identified by [<xref ref-type="bibr" rid="ref-1">1</xref>], the system implements targeted repair strategies:
<list list-type="bullet">
<list-item>
<p><bold>First-step failure (<inline-formula id="ieqn-114"><mml:math id="mml-ieqn-114"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>):</bold> Most common mode caused by unsatisfied basic preconditions (handempty, ontable, clear). Repair strengthens minimal precondition set for initial action.</p></list-item>
<list-item>
<p><bold>Mid-segment failure (<inline-formula id="ieqn-115"><mml:math id="mml-ieqn-115"><mml:mi>s</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>3</mml:mn></mml:math></inline-formula>):</bold> Related to state maintenance errors in stack/unstack chains. In Mystery domains, models struggle with complex state dependencies without lexical cues. Repair injects necessary landmark predicates and sequential constraints, as demonstrated in the workflow example where feast(a,c) failed due to blocked province(c).</p></list-item>
<list-item>
<p><bold>False cue interference:</bold> High-coupling action-predicate pairs discovered through NPMI analysis (e.g., overcome&#x003C;&#x2013;&#x003E;pain) mislead reasoning. Repair prevents false cues through enhanced consistency checking.</p></list-item>
</list></p>
</sec>
<sec id="s3_5_2">
<label>3.5.2</label>
<title>Budget Management</title>
<p>The system evaluates marginal gains after each attempt:
<disp-formula id="eqn-5"><label>(5)</label><mml:math id="mml-eqn-5" display="block"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>b</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></disp-formula></p>
<p>When <inline-formula id="ieqn-116"><mml:math id="mml-ieqn-116"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub></mml:math></inline-formula> falls below threshold or reaches budget limit <italic>B</italic>, the system stops attempting. Experiments show <inline-formula id="ieqn-117"><mml:math id="mml-ieqn-117"><mml:mi>b</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula> typically achieves major gains, as demonstrated in the workflow example.</p>
<p>This chapter&#x2019;s proposed Symbol-Agnostic Planning Pipeline systematically addresses planning challenges in lexical-prior-free environments through modular design and validation-driven repair mechanisms. The method strictly adheres to structural consistency principles, completely avoiding dependence on lexical semantics, providing an effective approach for evaluating the genuine planning capabilities of LLMs. The next chapter will verify this method&#x2019;s performance on PlanBench Mystery domains through detailed experiments.</p>
</sec>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Experimental Setup</title>
<p>This chapter provides detailed specifications of all aspects of the experimental design, including dataset selection, model configuration, and evaluation metrics, ensuring the reproducibility of experimental results and comparability with existing benchmarks.</p>
<sec id="s4_1">
<label>4.1</label>
<title>Tasks and Datasets</title>
<sec id="s4_1_1">
<label>4.1.1</label>
<title>PlanBench Mystery Blocksworld</title>
<p>This study adopts Mystery Blocksworld from the PlanBench benchmark proposed by [<xref ref-type="bibr" rid="ref-27">27</xref>] as the primary evaluation domain. Mystery Blocksworld uses symbol obfuscation techniques to replace all predicate and action names in the original Blocksworld domain with semantically irrelevant random vocabulary. As described in <xref ref-type="sec" rid="s2">Section 2</xref>, this obfuscation preserves the integrity of PDDL structural semantics while completely removing lexical priors, providing an ideal testing environment for evaluating models&#x2019; pure structural reasoning capabilities. Where necessary, we conducted consistency checks on the logistics and sokoban domains to confirm the structure-preserving properties of obfuscation mappings across different task families.</p>
</sec>
<sec id="s4_1_2">
<label>4.1.2</label>
<title>Instance Selection and Evaluation Standards</title>
<p>To ensure consistency and reproducibility of evaluation standards, this study strictly follows the &#x201C;index boundary filtering&#x201D; method from PlanBench&#x2019;s original scripts to determine the evaluation instance set. This filtering criterion, established by [<xref ref-type="bibr" rid="ref-27">27</xref>] in their original research, effectively controls the distribution of instance scale and complexity. To avoid scale ambiguities arising from data selection terminology, we uniformly adopt the &#x201C;all data&#x201D; standard for reporting throughout the main text. All models and configurations are compared on the same instance set, ensuring fairness and comparability of results.</p>
</sec>
<sec id="s4_1_3">
<label>4.1.3</label>
<title>Symbol Obfuscation Consistency Guarantee</title>
<p>In each evaluation run, the obfuscation mapping <inline-formula id="ieqn-118"><mml:math id="mml-ieqn-118"><mml:mi>&#x03D5;</mml:mi></mml:math></inline-formula> remains fixed, ensuring that the same instance uses identical symbol mappings across different models while maintaining consistency across instances. The core objective of this setup is to guarantee that textual and semantic priors are completely unavailable, with all reasoning, simulation, and validation operations executed strictly within the obfuscated symbol space. Through these consistency constraints, we ensure fairness in cross-model comparisons, with any performance differences attributable to the models&#x2019; structural reasoning capabilities rather than differences in evaluation conditions.</p>
</sec>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Model and Inference Configuration</title>
<p>To ensure comparability with the research results of [<xref ref-type="bibr" rid="ref-27">27</xref>], this study selects models that overlap with those in their research for evaluation. Specifically, we use GPT-4 and GPT-4o as LLM representatives, and o1-mini as a large reasoning model (LRM) representative. It should be noted that although Reference [<xref ref-type="bibr" rid="ref-2">2</xref>]&#x2019;s research also included the o1-preview model, this study does not include comparative results for that model due to its discontinued API access. This model selection strategy ensures comparability with existing research while covering the current mainstream range of language model capabilities.</p>
<p>To ensure comparability of cross-model results, all models adopt unified inference parameter configurations. Temperature parameter <italic>T</italic>, top-p sampling, maximum token count, stop sequences, and system prompts are kept consistent across models. In particular, this study employs a default single-sample generation (<inline-formula id="ieqn-119"><mml:math id="mml-ieqn-119"><mml:mi>n</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>) strategy, avoiding the inter-sample variance amplification that multi-sample generation might bring. This unified configuration ensures that performance differences between models reflect their intrinsic reasoning capabilities rather than the influence of parameter settings.</p>
</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Prompt Engineering and Component Configuration</title>
<p>The SC and LP modules employ templated prompt strategies with structured slots. The prompt design explicitly includes action parameter placeholders, required predicate set declarations, and mutual exclusion and rejection constraint hints, providing clear structured guidance to models. Particularly emphasized is that the prompt design strictly prohibits any form of name-based semantic analogy or dictionary matching. These constraints ensure that models must rely on structural logic rather than lexical memory for plan generation, complying with lexical-prior-free evaluation requirements.</p>
<p>The ST configuration similarly follows strict structural principles. The translation process only performs structural mapping and type/parameter consistency checking, maintaining strict consistency with the preconditions (pre), add effects (add), and delete effects (del) of domain definition <inline-formula id="ieqn-120"><mml:math id="mml-ieqn-120"><mml:msub><mml:mi>D</mml:mi><mml:mi>&#x03D5;</mml:mi></mml:msub></mml:math></inline-formula>. The system rejects any &#x201C;meaning-guessing-by-name&#x201D; flexibility, ensuring the translation process is entirely based on structural matching rather than semantic inference.</p>
<p>The CC in this study&#x2019;s main experiments employs complete static screening mechanisms, covering type consistency checking, invariant verification, and basic reachability analysis. This strict static checking can filter obvious errors before entering expensive simulation validation, improving overall system efficiency. It should be clarified that the main experiments in this paper do not perform strict-off downgrading, always maintaining the strictest static screening settings.</p>
</sec>
<sec id="s4_4">
<label>4.4</label>
<title>Budget and Retry Strategies</title>
<p>This study employs the budget set <inline-formula id="ieqn-121"><mml:math id="mml-ieqn-121"><mml:mi>b</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mn>0</mml:mn><mml:mo>,</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mn>2</mml:mn><mml:mo>,</mml:mo><mml:mn>3</mml:mn><mml:mo>,</mml:mo><mml:mn>5</mml:mn><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></inline-formula> for evaluation, with core comparisons focusing on marginal gains under small budget scenarios. The motivation for this setup stems from resource constraints in practical application scenarios and the empirical inflection point phenomenon discovered in previous research. Most performance improvements concentrate in the first few attempts, with <inline-formula id="ieqn-122"><mml:math id="mml-ieqn-122"><mml:mi>b</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula> in particular often representing the optimal balance of cost-effectiveness.</p>
<p>The system evaluates marginal gain <inline-formula id="ieqn-123"><mml:math id="mml-ieqn-123"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>b</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> after each attempt round, terminating attempts when marginal gain falls below preset threshold <inline-formula id="ieqn-124"><mml:math id="mml-ieqn-124"><mml:mi>&#x03B5;</mml:mi></mml:math></inline-formula> or upon reaching budget limit <italic>B</italic>. This dynamic termination strategy avoids resource waste on ineffective attempts. Meanwhile, the system records various statistics for end-to-end execution time <italic>T</italic>, including median, 90th percentile (p90), and trimmed mean, to address the skewed characteristics of time distributions and the impact of outliers.</p>
<p>The feedback routing mechanism routes feedback information to corresponding strategies in the RC (Repair Controller) based on the first failure step <inline-formula id="ieqn-125"><mml:math id="mml-ieqn-125"><mml:mi>s</mml:mi></mml:math></inline-formula> and failure type reported by SIM (Simulator) and VAL. The system implements four core repair strategies: First-Step Constraint for <inline-formula id="ieqn-126"><mml:math id="mml-ieqn-126"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula> failures, Precondition Probing for missing predicate issues, Parameter Swap &#x0026; Landmarks for mid-segment blockages, and Budget-Adaptive Retry for resource allocation optimization. Repair operations only affect constraint set <italic>C</italic> and text plan <inline-formula id="ieqn-127"><mml:math id="mml-ieqn-127"><mml:msub><mml:mi>&#x03C0;</mml:mi><mml:mrow><mml:mrow><mml:mtext>text</mml:mtext></mml:mrow></mml:mrow></mml:msub></mml:math></inline-formula> levels, without directly modifying symbol-level characters, maintaining the integrity and consistency of the symbol space.</p>
</sec>
<sec id="s4_5">
<label>4.5</label>
<title>Comparison Settings</title>
<p>The main experiments in this study employ the complete Symbol-Agnostic Closed-Loop Pipeline (SC<inline-formula id="ieqn-128"><mml:math id="mml-ieqn-128"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>LP<inline-formula id="ieqn-129"><mml:math id="mml-ieqn-129"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>ST<inline-formula id="ieqn-130"><mml:math id="mml-ieqn-130"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>CC<inline-formula id="ieqn-131"><mml:math id="mml-ieqn-131"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>SIM<inline-formula id="ieqn-132"><mml:math id="mml-ieqn-132"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>VAL<inline-formula id="ieqn-133"><mml:math id="mml-ieqn-133"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>RC), using the default strict settings defined above. This pipeline implements the complete &#x201C;generate<inline-formula id="ieqn-134"><mml:math id="mml-ieqn-134"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>verify<inline-formula id="ieqn-135"><mml:math id="mml-ieqn-135"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>repair&#x201D; closed-loop mechanism, representing the full capabilities of the method proposed in this paper. It should be clarified that this study does not conduct ablation experiments, but rather focuses on comparative analysis between the complete system and existing benchmarks.</p>
<p>For external comparisons, we compare the results of this method with the aligned standard results publicly reported by [<xref ref-type="bibr" rid="ref-27">27</xref>] under obfuscated/mystery settings. This comparison can intuitively demonstrate the degree of improvement of this method relative to existing techniques.</p>
</sec>
<sec id="s4_6">
<label>4.6</label>
<title>Evaluation Metrics and Statistical Methods</title>
<p>Success rate is defined as <inline-formula id="ieqn-136"><mml:math id="mml-ieqn-136"><mml:mrow><mml:mover><mml:mi>p</mml:mi><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mi>k</mml:mi><mml:mrow><mml:mo>/</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:math></inline-formula>, where <inline-formula id="ieqn-137"><mml:math id="mml-ieqn-137"><mml:mi>k</mml:mi></mml:math></inline-formula> is the number of successful instances and <inline-formula id="ieqn-138"><mml:math id="mml-ieqn-138"><mml:mi>n</mml:mi></mml:math></inline-formula> is the total number of instances. We employ the Wilson method to calculate 95% confidence intervals (CI), which is more robust than traditional normal approximations in small sample and extreme probability situations. Cross-model comparisons employ two-proportion z-tests rather than ANOVA because our primary outcome is binary (plan success/failure) and comparisons are structured as independent pairwise contrasts rather than multi-group mean comparisons. The z-test directly evaluates whether observed success rate differences between two configurations could arise from sampling variation, making it more appropriate for proportion data than ANOVA which assumes continuous dependent variables and homogeneous variances. We calculate effect size as <inline-formula id="ieqn-139"><mml:math id="mml-ieqn-139"><mml:mi>h</mml:mi><mml:mo>=</mml:mo><mml:mn>2</mml:mn><mml:mi>arcsin</mml:mi><mml:mo>&#x2061;</mml:mo><mml:msqrt><mml:msub><mml:mi>p</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:msqrt><mml:mo>&#x2212;</mml:mo><mml:mn>2</mml:mn><mml:mi>arcsin</mml:mi><mml:mo>&#x2061;</mml:mo><mml:msqrt><mml:msub><mml:mi>p</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:msqrt></mml:math></inline-formula>, specifically designed for proportion differences through the arcsine transformation. This Cohen&#x2019;s <inline-formula id="ieqn-140"><mml:math id="mml-ieqn-140"><mml:mi>h</mml:mi></mml:math></inline-formula> metric is unaffected by sample size and provides stable interpretation across varying baseline rates (<inline-formula id="ieqn-141"><mml:math id="mml-ieqn-141"><mml:mi>h</mml:mi><mml:mo>&#x003C;</mml:mo><mml:mn>0.2</mml:mn></mml:math></inline-formula> small, <inline-formula id="ieqn-142"><mml:math id="mml-ieqn-142"><mml:mn>0.2</mml:mn><mml:mo>&#x2264;</mml:mo><mml:mi>h</mml:mi><mml:mo>&#x003C;</mml:mo><mml:mn>0.8</mml:mn></mml:math></inline-formula> medium, <inline-formula id="ieqn-143"><mml:math id="mml-ieqn-143"><mml:mi>h</mml:mi><mml:mo>&#x2265;</mml:mo><mml:mn>0.8</mml:mn></mml:math></inline-formula> large), offering more reliable practical significance assessment than odds ratios which can be misleading when baseline success rates differ substantially. Given our sufficient sample size (<inline-formula id="ieqn-144"><mml:math id="mml-ieqn-144"><mml:mi>n</mml:mi><mml:mo>=</mml:mo><mml:mn>600</mml:mn></mml:math></inline-formula> per configuration), the normal approximation underlying z-tests remains valid, making parametric approaches more computationally efficient than bootstrapping methods while maintaining equivalent statistical reliability.</p>
<p>Time analysis employs multiple robust statistics to address the skewed distribution of execution times and the impact of outliers. We report median, 90th percentile (p90), and trimmed mean (with trimming parameter <inline-formula id="ieqn-145"><mml:math id="mml-ieqn-145"><mml:mi>&#x03B1;</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mn>0.05</mml:mn><mml:mo>,</mml:mo><mml:mn>0.1</mml:mn><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></inline-formula>). These statistics have lower sensitivity to extreme values and can more accurately reflect typical performance. It should be emphasized that time comparisons are only conducted under &#x201C;equivalent success&#x201D; conditions, ensuring fairness&#x2014;only when the same task is completed does efficiency comparison become meaningful.</p>
<p>Retry benefit analysis characterizes the relationship between success rate and budget through the <inline-formula id="ieqn-146"><mml:math id="mml-ieqn-146"><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub></mml:math></inline-formula> curve, with marginal gain <inline-formula id="ieqn-147"><mml:math id="mml-ieqn-147"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub></mml:math></inline-formula> calculation identifying the empirical inflection point <inline-formula id="ieqn-148"><mml:math id="mml-ieqn-148"><mml:msup><mml:mi>b</mml:mi><mml:mo>&#x2217;</mml:mo></mml:msup></mml:math></inline-formula>. This analysis reveals the return-on-investment pattern of increasing budgets, providing guidance for resource allocation in practical applications. The morphological characteristics of the curve can reflect the system&#x2019;s marginal improvement space at different budget levels, helping understand the efficiency of the closed-loop repair mechanism.</p>
<p>Risk profiling employs the hazard function <inline-formula id="ieqn-149"><mml:math id="mml-ieqn-149"><mml:mi>h</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mo movablelimits="true" form="prefix">Pr</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>F</mml:mi><mml:mo>=</mml:mo><mml:mi>s</mml:mi><mml:mo>&#x2223;</mml:mo><mml:mi>F</mml:mi><mml:mo>&#x2265;</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> to characterize failure step distribution. This function represents the conditional probability of failure at step <inline-formula id="ieqn-150"><mml:math id="mml-ieqn-150"><mml:mi>s</mml:mi></mml:math></inline-formula> given that step <inline-formula id="ieqn-151"><mml:math id="mml-ieqn-151"><mml:mi>s</mml:mi></mml:math></inline-formula> has been reached. By constructing confidence bands through bootstrap methods, we can identify the location and magnitude of major risk peaks, revealing at which reasoning stages the system is most error-prone. This analysis has important value for understanding model weaknesses and guiding targeted improvements, particularly in validating the theoretical predictions about first-step failure (<inline-formula id="ieqn-152"><mml:math id="mml-ieqn-152"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>) and mid-segment failure (<inline-formula id="ieqn-153"><mml:math id="mml-ieqn-153"><mml:mi>s</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>3</mml:mn></mml:math></inline-formula>) patterns proposed in <xref ref-type="sec" rid="s3">Section 3</xref>.</p>
<p>Failure component analysis decomposes failure sources into translation errors (translate), simulation errors (sim), and validation errors (val), analyzing the proportions and overlap patterns of each component. Particular attention to high-overlap regions between sim and val can reveal systematic defects&#x2014;when both validation methods consistently report errors, this often points to deep reasoning problems rather than surface errors. This component decomposition helps understand the root nature and propagation paths of errors.</p>
<p>Semantic association strength analysis employs NPMI to measure association strength between actions and predicates. NPMI is defined as <inline-formula id="ieqn-154"><mml:math id="mml-ieqn-154"><mml:mrow><mml:mtext>NPMI</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo>,</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mrow><mml:mtext>PMI</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo>,</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mrow><mml:mo>&#x2212;</mml:mo><mml:mi>log</mml:mi><mml:mo>&#x2061;</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>a</mml:mi><mml:mo>,</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:math></inline-formula>, with its normalization property allowing associations of different frequencies to be compared on a unified scale. We use <inline-formula id="ieqn-155"><mml:math id="mml-ieqn-155"><mml:mi>&#x03B5;</mml:mi></mml:math></inline-formula>-smoothing to handle zero-frequency problems, set minimum support thresholds to filter low-frequency items, and employ FDR (False Discovery Rate) to control multiple comparison errors. We report Top-K positive and negative coupling pairs where <inline-formula id="ieqn-156"><mml:math id="mml-ieqn-156"><mml:mi>K</mml:mi><mml:mo>=</mml:mo><mml:mn>10</mml:mn></mml:math></inline-formula> is selected based on three criteria: (1) visual interpretability&#x2014;10 pairs provide sufficient detail for pattern identification while maintaining figure readability, (2) statistical coverage&#x2014;the top 10 pairs capture approximately 60%&#x2013;70% of cumulative association mass, representing dominant spurious associations while excluding low-frequency noise, and (3) cross-model comparability&#x2014;a fixed <italic>K</italic> enables direct comparison across models without introducing selection bias. By reporting these Top-10 coupling pairs and their counts, we can reveal spurious association patterns among obfuscated symbols, understanding which random word pairs mislead model reasoning. This analysis provides quantitative evidence for understanding the &#x201C;false cue interference&#x201D; phenomenon in Mystery domains.</p>
<p>The complete evaluation framework established in this chapter ensures reproducibility of experimental results, statistical rigor, and comparability with existing research. Through systematic comparison with the benchmark results of [<xref ref-type="bibr" rid="ref-2">2</xref>], we can objectively evaluate the effectiveness of the Symbol-Agnostic Closed-Loop Pipeline proposed in this paper. The next chapter will report detailed experimental results and analysis based on this framework.</p>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Results and Analysis</title>
<p>This chapter systematically reports and analyzes experimental results. It should be noted that since the baseline study by [<xref ref-type="bibr" rid="ref-2">2</xref>] only publicly reported success rate metrics without releasing complete experimental data including runtime, retry patterns, failure distributions, etc., this chapter conducts method comparison only in the success rate dimension, with all other analyses focusing on the detailed behavioral characteristics of the Symbol-Agnostic Closed-Loop Pipeline proposed in this paper. This analytical strategy ensures comparability with existing research while enabling deep revelation of the working principles of the closed-loop repair mechanism.</p>
<sec id="s5_1">
<label>5.1</label>
<title>Overall Success Rates</title>
<p><xref ref-type="table" rid="table-1">Table 1</xref> presents the overall success rate comparison between our method and baseline methods on PlanBench Mystery Blocksworld. The baseline methods adopt direct generation strategies, where models receive task descriptions and directly output complete plans without verification or repair, evaluated under both one-shot and zero-shot prompting settings.</p>
<table-wrap id="table-1">
<label>Table 1</label>
<caption>
<title>Success rates (%) on PlanBench Mystery Blocksworld. Our symbol-agnostic closed-loop pipeline demonstrates substantial improvements over baseline results with both one-shot and zero-shot settings</title>
</caption>
<table>
<colgroup>
<col align="center"/>
<col align="center"/>
<col align="center"/>
<col align="center"/> </colgroup>
<thead>
<tr>
<th>Model</th>
<th>Baseline (One-Shot)&#x002A;</th>
<th>Baseline (Zero-Shot)&#x002A;</th>
<th>Our Method</th>
</tr>
</thead>
<tbody>
<tr>
<td>GPT-4</td>
<td>4.3</td>
<td>0.16</td>
<td>46.2</td>
</tr>
<tr>
<td>GPT-4o</td>
<td>0.83</td>
<td>0</td>
<td>46.2</td>
</tr>
<tr>
<td>o1-mini</td>
<td>&#x2013;</td>
<td>19.1</td>
<td><bold>48.0</bold></td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="table-1fn1" fn-type="other">
<p><inline-formula id="ieqn-157"><mml:math id="mml-ieqn-157"><mml:msup><mml:mi>Note: </mml:mi><mml:mrow><mml:mo>&#x2217;</mml:mo></mml:mrow></mml:msup></mml:math></inline-formula>Baseline results from [<xref ref-type="bibr" rid="ref-16">16</xref>]. We note a discrepancy between the paper and the associated GitHub repository (<ext-link ext-link-type="uri" xlink:href="https://github.com/karthikv792/LLMs-Planning">https://github.com/karthikv792/LLMs-Planning</ext-link>): the repository reports GPT-4 success rate as 0%, whereas the paper reports 4.3% for one-shot and 0.16% for zero-shot prompting. This discrepancy remains unaddressed in the published materials. <bold>Bold</bold> indicates the best overall result.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Results show that our method achieves significant performance improvements across all evaluated models. For GPT-4, the success rate increases from baseline direct generation&#x2019;s 4.3% (one-shot) and 0.16% (zero-shot) to 46.2%, achieving more than 10-fold absolute improvement. This magnitude of improvement clearly demonstrates the value of the validation-driven closed-loop mechanism&#x2014;in Mystery domains without lexical priors, relying solely on models&#x2019; one-shot generation capabilities makes task completion nearly impossible, while through systematic &#x201C;generate<inline-formula id="ieqn-158"><mml:math id="mml-ieqn-158"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>verify<inline-formula id="ieqn-159"><mml:math id="mml-ieqn-159"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>repair&#x201D; cycles, even the relatively earlier GPT-4 model can achieve close to 50% success rate.</p>
<p>The improvement for GPT-4o is even more pronounced, rising from baseline&#x2019;s 0.83% (one-shot) and 0% (zero-shot) to 46.2%. Notably, GPT-4o&#x2019;s zero-shot baseline is 0%, meaning not a single direct generation succeeded among 600 evaluation instances, highlighting the extreme challenge posed by Mystery domains&#x2019; complete deprivation of lexical prior dependencies. However, equipped with the closed-loop pipeline, GPT-4o achieves the same 46.2% success rate as GPT-4, indicating that when endowed with structured verification and repair capabilities, different LLM architectures tend to converge in final planning quality.</p>
<p>o1-mini, as a representative of large reasoning models, although its zero-shot baseline performance (19.1%) already significantly outperforms GPT-4 and GPT-4o&#x2019;s direct generation results, still improves to 48.0% through our method&#x2019;s closed-loop pipeline, achieving the highest success rate among all models. This approximately 29 percentage point absolute improvement has important theoretical significance: it demonstrates that even for models with enhanced reasoning capabilities, systematic validation-driven methods can still bring substantial improvements. o1-mini&#x2019;s better performance in direct generation scenarios stems from its intrinsic reasoning mechanisms, but this capability does not render the closed-loop repair redundant; rather, it forms a synergistic enhancement effect with the closed-loop mechanism.</p>
<p>It should be emphasized again that the baseline methods employ direct generation strategies, where models have only one generation opportunity without involving verification, repair, or retry processes. Therefore, the comparison between baseline and our method is essentially a comparison between two paradigms: &#x201C;single-shot generation without feedback&#x201D; vs. &#x201C;multi-round validation-driven repair.&#x201D; Subsequent sections&#x2019; detailed analyses of runtime, retry patterns, failure distributions, etc., are specifically focused on the closed-loop pipeline proposed in this paper and do not apply to baseline methods.</p>
</sec>
<sec id="s5_2">
<label>5.2</label>
<title>Runtime Robustness</title>
<p><xref ref-type="fig" rid="fig-3">Fig. 3</xref> presents the end-to-end runtime distribution under our method&#x2019;s closed-loop pipeline for the three models. Time statistics employ three robust statistics&#x2014;median (p50), 90th percentile (p90), and mean&#x2014;to address the skewed characteristics of time distributions. It should be clarified that these timing data only reflect the execution efficiency of our method and do not involve comparison with baseline methods, as the baseline study did not publicly release runtime data.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Runtime distribution overview: end-to-end execution time statistics (p50, p90, mean) across models showing efficiency stratification in the closed-loop pipeline</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-3.tif"/>
</fig>
<p>Across the evaluation instance set, the three models exhibit clear performance stratification. GPT-4o demonstrates the shortest execution latency, with p50, p90, and mean of 13.79, 19.93, and 14.64 s, respectively. GPT-4&#x2019;s corresponding statistics are 36.25, 49.21, and 36.05 s, approximately 2.63 times that of GPT-4o (based on p50 comparison). o1-mini has the longest execution window, with p50, p90, and mean of 53.74, 78.54, and 49.45 s, respectively, approximately 3.90 times that of GPT-4o.</p>
<p>This stratification pattern remains consistent across instance subsets of different difficulty levels. On the relatively difficult gb500 subset, the p50 values for the three models are 37.49, 14.16, and 57.95 s, respectively; on the relatively simple gb3_100 subset, the corresponding values are 26.84, 11.25, and 11.69 s. Simpler instances overall exhibit shorter and more concentrated time distributions, but the relative ordering of &#x201C;GPT-4o fastest, GPT-4 middle, o1-mini longest&#x201D; remains stable. It should be noted that on the gb3_100 subset, o1-mini&#x2019;s latency approaches that of GPT-4o (11.69 vs. 11.25 s), indicating that in simple task scenarios, the additional computational overhead of reasoning models can be effectively amortized.</p>
<p>From a system design perspective, these latency differences reflect different working modes of models in the closed-loop pipeline. GPT-4o possesses significant efficiency advantages while achieving similar success rates (46.2%), making it suitable for application scenarios with higher real-time requirements. Although o1-mini requires a longer execution window to support its deep reasoning process, it achieves the highest final success rate (48.0%), forming a complementary relationship with GPT-4o in the trade-off between &#x201C;low latency vs. robust achievement.&#x201D; Combined with the failure component analysis in <xref ref-type="sec" rid="s5_5">Section 5.5</xref>, it can be seen that o1-mini tends to achieve goals through global planning optimization rather than frequent local repairs, a strategy that, while more time-consuming, can handle more complex constraint relationships.</p>
</sec>
<sec id="s5_3">
<label>5.3</label>
<title>Retry Benefit Analysis</title>
<p><xref ref-type="fig" rid="fig-4">Fig. 4</xref> presents the variation curve of success rate <inline-formula id="ieqn-160"><mml:math id="mml-ieqn-160"><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub></mml:math></inline-formula> with budget <inline-formula id="ieqn-161"><mml:math id="mml-ieqn-161"><mml:mi>b</mml:mi></mml:math></inline-formula> in our method and average attempt count statistics. It should be emphasized that the retry mechanism is one of the core features of the closed-loop pipeline in this paper; the baseline direct generation method does not involve retry processes, so this section&#x2019;s analysis is specifically focused on the behavioral characteristics of the closed-loop pipeline.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Retry benefit curves: success rate progression with budget allocation and average attempt counts demonstrating convergence within <inline-formula id="ieqn-162"><mml:math id="mml-ieqn-162"><mml:mi>b</mml:mi><mml:mo>&#x2264;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula></title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-4.tif"/>
</fig>
<p>Across the evaluation instance set, the average attempt counts for the three models are: GPT-4 1.91, GPT-4o 1.935, o1-mini 1.767. This result indicates that most instances determine success or failure within 1-2 attempts, highly consistent with the assumption about the empirical inflection point <inline-formula id="ieqn-163"><mml:math id="mml-ieqn-163"><mml:mi>b</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula> in the budget management strategy proposed in <xref ref-type="sec" rid="s3">Section 3</xref>. The marginal gain curve <inline-formula id="ieqn-164"><mml:math id="mml-ieqn-164"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>b</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> shows that major gains concentrate in the range <inline-formula id="ieqn-165"><mml:math id="mml-ieqn-165"><mml:mi>b</mml:mi><mml:mo>&#x2264;</mml:mo><mml:mn>2</mml:mn></mml:math></inline-formula>. For additional attempts with <inline-formula id="ieqn-166"><mml:math id="mml-ieqn-166"><mml:mi>b</mml:mi><mml:mo>&#x2265;</mml:mo><mml:mn>3</mml:mn></mml:math></inline-formula>, marginal gains significantly decrease, confirming the rationality of the budget-adaptive termination strategy designed in <xref ref-type="sec" rid="s3">Section 3</xref>.</p>
<p>o1-mini&#x2019;s relatively lower average attempt count (1.767 vs. 1.91/1.935) reveals its unique working mode. Combined with the failure component analysis in <xref ref-type="sec" rid="s5_5">Section 5.5</xref>, it can be seen that o1-mini&#x2019;s failures concentrate more on global goal non-satisfaction rather than local precondition deficiencies. This means o1-mini tends to generate plans with good local consistency; when the first attempt&#x2019;s plan structure is basically reasonable, minor landmark injection or parameter swapping can complete repairs; when structural defects are significant, the model can quickly identify and abandon ineffective paths, avoiding futile repeated attempts.</p>
</sec>
<sec id="s5_4">
<label>5.4</label>
<title>Step-Wise Hazard Profile</title>
<p><xref ref-type="fig" rid="fig-5">Fig. 5</xref> presents the hazard function distribution <inline-formula id="ieqn-167"><mml:math id="mml-ieqn-167"><mml:mi>h</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mo movablelimits="true" form="prefix">Pr</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>F</mml:mi><mml:mo>=</mml:mo><mml:mi>s</mml:mi><mml:mo>&#x2223;</mml:mo><mml:mi>F</mml:mi><mml:mo>&#x2265;</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math></inline-formula> for failure step numbers during our method&#x2019;s execution and its bootstrap confidence bands. The hazard function characterizes the conditional probability of failure at step <inline-formula id="ieqn-168"><mml:math id="mml-ieqn-168"><mml:mi>s</mml:mi></mml:math></inline-formula> given that step <inline-formula id="ieqn-169"><mml:math id="mml-ieqn-169"><mml:mi>s</mml:mi></mml:math></inline-formula> has been reached, enabling identification of high-risk stages during plan execution. This analysis is similarly specifically focused on the internal behavior of the closed-loop pipeline, revealing at which stages the system most needs intervention by verification and repair mechanisms.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Step-wise hazard distribution: conditional failure probability by execution step revealing dual-peak risk pattern at entry and mid-segment stages</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-5.tif"/>
</fig>
<p>Results show that failure risk exhibits a bimodal clustering pattern at the entry point (<inline-formula id="ieqn-170"><mml:math id="mml-ieqn-170"><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>) and mid-segment (<inline-formula id="ieqn-171"><mml:math id="mml-ieqn-171"><mml:mi>s</mml:mi><mml:mo>&#x2248;</mml:mo><mml:mn>3</mml:mn><mml:mrow><mml:mo>&#x2212;</mml:mo></mml:mrow><mml:mn>4</mml:mn></mml:math></inline-formula>). This observation perfectly aligns with the typical failure modes proposed in <xref ref-type="sec" rid="s3">Section 3</xref> based on related work analysis. First-step failures are primarily caused by unsatisfied basic preconditions (such as Mystery-corresponding symbols for handempty, ontable, clear), reflecting models&#x2019; insufficient grasp of precondition consistency during the initialization phase. Without lexical priors, models struggle to directly identify which predicates must be true before executing the first action, causing generated plans to encounter obstacles at the starting stage.</p>
<p>Mid-segment failures relate more to missing necessary landmarks and action sequence design. In Mystery domains, due to complete absence of lexical cues, models struggle to maintain complex state dependencies in action chains like stack/unstack. For example, when needing to move block A from position B to position C, intermediate steps may be required to clear position C or temporarily place A, and managing these intermediate states is extremely challenging without semantic hints.</p>
<p>Cross-model comparison shows that the three models have similar hazard distribution morphologies but differ in peak intensities. o1-mini has relatively lower hazard values at the first step, indicating that its stronger initial planning capability can reduce errors in the entry phase. However, its hazard values in the mid-segment remain significant, indicating that even strong reasoning models still face challenges in maintaining consistency of multi-step state transitions. This finding provides empirical support for the repair strategies designed in <xref ref-type="sec" rid="s3">Section 3</xref>: the First-Step Constraint strategy focuses on completeness checking of basic preconditions, while the Parameter Swap &#x0026; Landmarks strategy focuses on handling mid-segment state maintenance issues, with the two strategies precisely corresponding to the bimodal risk distribution.</p>
</sec>
<sec id="s5_5">
<label>5.5</label>
<title>Failure Composition and Overlap</title>
<p><xref ref-type="fig" rid="fig-6">Fig. 6</xref> presents the failure component distribution for the three models during our method&#x2019;s execution. It should be noted again that these failure data come from validation steps (CC, SIM, VAL) internal to the closed-loop pipeline, reflecting cases that still fail after multiple rounds of repair, which are qualitatively different from baseline direct generation failures. Total failure counts are: GPT-4 323 cases (600-277), GPT-4o 323 cases (600-277), o1-mini 312 cases (600-288), consistent with the success rate data in <xref ref-type="table" rid="table-1">Table 1</xref>.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Failure composition distribution: breakdown of failure reasons across models highlighting distinct failure modes between precondition errors and goal satisfaction issues</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-6.tif"/>
</fig>
<p>The composition proportions of failure reasons reveal fundamental differences in structural reasoning capabilities between different model types. For LLMs GPT-4 and GPT-4o, failures are highly concentrated on missing preconditions (sim.precondition_missing)&#x2014;GPT-4 has 314 cases (approximately 97.2%), GPT-4o has 308 cases (approximately 95.4%). The proportion of goal non-satisfaction (goal_not_satisfied) is very small, with 7 cases (approximately 2.2%) and 12 cases (approximately 3.7%), respectively. This pattern indicates that the main difficulty for LLMs in Mystery domains lies in accurately identifying and satisfying local preconditions for each action. Even after multiple rounds of repair, these models still struggle to establish correct action-predicate dependency relationships without any lexical hints. However, once preconditions are satisfied, plans usually can ultimately achieve goals, indicating that these models&#x2019; global planning capabilities are not entirely absent.</p>
<p>In contrast, o1-mini exhibits a distinctly different failure pattern. Its failures primarily stem from goal non-satisfaction (211 cases, approximately 67.6%), with missing preconditions accounting for only 100 cases (approximately 32.1%). This reversal indicates that o1-mini possesses stronger local consistency maintenance capabilities, able to generate plans where each step satisfies preconditions, but still has room for improvement in strategic selection and path planning for global goal achievement. In other words, o1-mini&#x2019;s plans are often syntactically and locally logically correct&#x2014;each action can be legally executed, but at the global level may have chosen a path that can execute but cannot achieve goals.</p>
<p>This differentiated failure pattern provides an important perspective for understanding the working principles of the closed-loop repair mechanism. For GPT-4/4o, the repair process primarily involves filling missing preconditions and adjusting action parameters, which is precisely the domain of First-Step Constraint and Precondition Probing strategies. For o1-mini, the repair process more involves global path replanning and intermediate state redesign, corresponding to the functionality of Parameter Swap &#x0026; Landmarks strategies. It should be emphasized that the four repair strategies proposed in this paper fully consider such inter-model differences in design, thus achieving robust improvement effects across different models.</p>
</sec>
<sec id="s5_6">
<label>5.6</label>
<title>NPMI</title>
<p><xref ref-type="fig" rid="fig-7">Figs. 7</xref>&#x2013;<xref ref-type="fig" rid="fig-9">9</xref> present the Top-K coupling pairs of NPMI between actions and predicates for the three models in Mystery domains. NPMI analysis is specifically focused on generation patterns observed inside the closed-loop pipeline of our method, revealing association structures among obfuscated symbols. Since symbols in Mystery domains themselves are randomly selected, semantically irrelevant vocabulary, any high coupling reflects reasoning preferences or misleading patterns formed by models without semantic cues.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>NPMI action-predicate associations for GPT-4: Top-K positive and negative coupling pairs revealing semantic association patterns in obfuscated symbol space</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-7.tif"/>
</fig><fig id="fig-8">
<label>Figure 8</label>
<caption>
<title>NPMI action-predicate associations for GPT-4o: Top-K positive and negative coupling pairs revealing semantic association patterns in obfuscated symbol space</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-8.tif"/>
</fig><fig id="fig-9">
<label>Figure 9</label>
<caption>
<title>NPMI action-predicate associations for o1-mini: Top-K positive and negative coupling pairs revealing semantic association patterns in obfuscated symbol space</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-9.tif"/>
</fig>
<p>High positive coupling pairs reflect models&#x2019; tendency to frequently associate certain actions with specific predicates. For example, overcome (corresponding to pick-up in the original domain) may exhibit high positive coupling with pain (corresponding to holding). In the original domain this is a correct structural dependency (pick-up action leads to holding state), but in Mystery domains models must establish such associations through pure structural reasoning rather than lexical memory. The emergence of high positive coupling indicates that models to some extent capture such structural dependencies, but may also reflect spurious associations&#x2014;certain random word pairs are erroneously associated due to accidental co-occurrence in training data.</p>
<p>Negative coupling pairs reflect structural exclusion relationships, such as mutual exclusivity between one action&#x2019;s preconditions and another action&#x2019;s delete effects. These negative couplings are equally important in repair strategies, as they indicate which action combinations are naturally incompatible and should be avoided during planning.</p>
<p>Cross-model comparison shows that the three models&#x2019; NPMI distribution patterns differ, reflecting different strategies in handling obfuscated symbols. GPT-4 and GPT-4o&#x2019;s coupling patterns are relatively scattered, indicating these models attempt to establish diverse action-predicate associations but lack consistent structural understanding. o1-mini&#x2019;s coupling pattern is relatively concentrated, indicating it can more stably identify key structural dependencies. These coupling patterns directly guide the Parameter Swap &#x0026; Landmarks repair strategy designed in <xref ref-type="sec" rid="s3">Section 3</xref>&#x2014;by identifying highly coupled action-predicate pairs, RC can adjust parameter order or insert necessary intermediate predicates in a targeted manner, thereby suppressing spurious associations and completing necessary structural dependencies.</p>
</sec>
<sec id="s5_7">
<label>5.7</label>
<title>Simulation Distribution Analysis</title>
<p><xref ref-type="fig" rid="fig-10">Figs. 10</xref>&#x2013;<xref ref-type="fig" rid="fig-12">12</xref> present the distribution characteristics of actions, predicates, and step numbers during SIM (STRIPS Simulator) validation, respectively. These three types of distributions characterize the structural characteristics of the planning process inside the closed-loop pipeline of our method from different perspectives, providing fine-grained empirical foundations for understanding failure modes and optimizing repair strategies.</p>
<fig id="fig-10">
<label>Figure 10</label>
<caption>
<title>Action distribution in simulation: frequency comparison of action types between successful and failed planning attempts</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-10.tif"/>
</fig><fig id="fig-11">
<label>Figure 11</label>
<caption>
<title>Predicate distribution in simulation: frequency comparison of predicate occurrences between successful and failed planning attempts</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-11.tif"/>
</fig><fig id="fig-12">
<label>Figure 12</label>
<caption>
<title>Step number distribution in simulation: failure concentration across execution steps showing consistency with hazard profile</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_74520-fig-12.tif"/>
</fig>
<p>The step number distribution (<xref ref-type="fig" rid="fig-12">Fig. 12</xref>) exhibits a consistent bimodal pattern with the hazard curve in <xref ref-type="fig" rid="fig-4">Fig. 4</xref>, further confirming that entry and mid-segment are high-incidence areas for failures. This consistency is not coincidental&#x2014;the hazard function characterizes risk from a probability perspective, while the step number distribution characterizes actual failure events from a frequency perspective, and the correspondence between the two validates the robustness of statistical analysis. The action distribution (<xref ref-type="fig" rid="fig-10">Fig. 10</xref>) shows that certain action types (such as obfuscated symbols corresponding to overcome, feast) have significantly higher frequencies in failure cases than their proportions in success cases, indicating these actions involve more complex precondition dependencies or state transition logic. In the predicate distribution (<xref ref-type="fig" rid="fig-11">Fig. 11</xref>), basic state predicates (such as obfuscated symbols corresponding to province, harmony, craves) have the highest appearance frequencies in failure first steps, confirming the conclusion that first-step failures are primarily caused by unsatisfied basic preconditions.</p>
<p>Cross-analysis of these three types of distributions reveals the priority structure of repair strategies. High-frequency clusters in action distributions vary in the same direction as high-coupling segments in NPMI, indicating that certain action-predicate combinations naturally have higher complexity and should be prioritized during repair. Combined with the failure component proportions, optimization paths for the closed-loop pipeline of our method can be summarized as: First, at the entry stage, impose first-step consistency checking and parameter constraints through CC &#x2019;s static screening and First-Step Constraint repair strategy to ensure completeness of basic preconditions; Second, at the mid-segment stage, inject necessary landmarks (such as maintaining sequential relationships of clear, holding, on states) and perform parameter swapping and local reordering through Parameter Swap &#x0026; Landmarks strategy to maintain complex state dependencies. This phased, targeted repair strategy is the key mechanism enabling the closed-loop pipeline to achieve high success rates within limited budgets.</p>
<p>The experimental results above comprehensively validate the effectiveness of the Symbol-Agnostic Closed-Loop Pipeline proposed in <xref ref-type="sec" rid="s3">Section 3</xref>. From significant improvements in overall success rates to fine-grained internal behavior analysis, all metrics consistently indicate that validation-driven repair mechanisms have substantial value in planning tasks without lexical priors. Compared with baseline direct generation methods, the closed-loop pipeline enables models to still achieve close to 50% success rates under extreme conditions completely lacking semantic cues through systematic &#x201C;generate<inline-formula id="ieqn-172"><mml:math id="mml-ieqn-172"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>verify<inline-formula id="ieqn-173"><mml:math id="mml-ieqn-173"><mml:mo stretchy="false">&#x2192;</mml:mo></mml:math></inline-formula>repair&#x201D; cycles.</p>
<p>Having demonstrated the overall effectiveness of our approach, we now turn to ablation experiments that systematically examine the individual contributions of key architectural components. While the preceding analyses reveal what the system achieves, the following ablation study clarifies why each component is necessary and how they synergistically integrate to produce the observed performance gains.</p>
</sec>
<sec id="s5_8">
<label>5.8</label>
<title>Ablation Study</title>
<p>To validate the effectiveness of our symbol-agnostic closed-loop architecture, we conduct ablation experiments that systematically degrade key components while preserving system executability. Unlike conventional ablation studies that completely remove modules, our approach recognizes that certain components (e.g., Symbol Translation, Language Planner, VAL validator) represent hard constraints&#x2014;removing them would cause complete system failure rather than gradual degradation. Instead, we focus on weakening three critical mechanisms that enable the closed-loop refinement process: targeted repair strategies, precise failure diagnosis through step-wise validation, and deep constraint extraction from domain specifications.</p>
<p>We evaluate three degraded configurations against the full system. In the <bold>w/o Repair</bold> configuration, the repair controller performs random regeneration when validation fails, discarding all failure information and restarting from scratch. This tests whether our failure-pattern-driven repair strategies (First-Step Constraint, Precondition Probing, Parameter Swap &#x0026; Landmarks, Budget-Adaptive Retry) provide advantages over naive multi-attempt baselines. The <bold>w/o Step-wise Validation</bold> configuration removes the STRIPS simulator from the validation pipeline, forcing plans that pass consistency checking to proceed directly to VAL validation. Without intermediate state tracking, the repair controller receives only binary success/failure signals rather than precise diagnostic information about which step failed and which predicates were unsatisfied. Finally, the <bold>w/o Deep Constraints</bold> configuration weakens the semantic comprehension module to extract only surface-level type and arity information, omitting dependency chains (e.g., <monospace>holding(?x)</monospace> requires prior <monospace>pick-up(?x)</monospace>), mutex relationships, and landmark orderings. All ablation experiments use the same evaluation protocol as our main results, with attempt budget <inline-formula id="ieqn-174"><mml:math id="mml-ieqn-174"><mml:mi>b</mml:mi><mml:mo>=</mml:mo><mml:mn>3</mml:mn></mml:math></inline-formula> and 600 problem instances from PlanBench Mystery Blocksworld.</p>
<p><xref ref-type="table" rid="table-2">Table 2</xref> shows that removing any component leads to statistically significant performance degradation. The targeted repair mechanism provides the largest contribution, with performance drops of 10.4%, 9.7%, and 7.5% for GPT-4, GPT-4o, and o1-mini respectively when replaced with random retry. This validates our core hypothesis that systematic failure analysis and targeted interventions significantly outperform naive regeneration. Interestingly, o1-mini shows smaller degradation (7.5% vs. 10.4% for GPT-4), suggesting that models with stronger intrinsic reasoning capabilities benefit less from external repair guidance&#x2014;yet even o1-mini experiences substantial improvement from our failure-driven approach, indicating that validation-based refinement remains valuable across the capability spectrum.</p>
<table-wrap id="table-2">
<label>Table 2</label>
<caption>
<title>Ablation study results: success rates (%) on planbench mystery blocksworld. Numbers in parentheses with colored highlights indicate absolute performance drop relative to the full system</title>
</caption>
<table>
<colgroup>
<col align="center"/>
<col align="center"/>
<col align="center"/>
<col align="center"/> </colgroup>
<thead>
<tr>
<th>Configuration</th>
<th>GPT-4</th>
<th>GPT-4o</th>
<th>o1-mini</th>
</tr>
</thead>
<tbody>
<tr>
<td>Full system</td>
<td>46.2</td>
<td>46.2</td>
<td>48.0</td>
</tr>
<tr>
<td>w/o repair</td>
<td>35.8 <styled-content style-type="color" style="color: #FF0000;"> <bold>(&#x2212;10.4)</bold></styled-content></td>
<td>36.5 <styled-content style-type="color" style="color: #FF0000;"><bold>(&#x2212;9.7)</bold></styled-content></td>
<td>40.5 <styled-content style-type="color" style="color: #FF8000;"><bold>(&#x2212;7.5)</bold></styled-content></td>
</tr>
<tr>
<td>w/o step-wise validation</td>
<td>41.7 <styled-content style-type="color" style="color: #0000FF;"><bold>(&#x2212;4.5)</bold></styled-content></td>
<td>42.3 <styled-content style-type="color" style="color: #0000FF;"><bold>(&#x2212;3.9)</bold></styled-content></td>
<td>44.8 <styled-content style-type="color" style="color: #0000FF;"><bold>(&#x2212;3.2)</bold></styled-content></td>
</tr>
<tr>
<td>w/o deep constraints</td>
<td>39.5 <styled-content style-type="color" style="color: #BF0040;"><bold>(&#x2212;6.7)</bold></styled-content></td>
<td>40.1 <styled-content style-type="color" style="color: #BF0040;"><bold>(&#x2212;6.1)</bold></styled-content></td>
<td>43.2 <styled-content style-type="color" style="color: #BF0040;"><bold>(&#x2212;4.8)</bold></styled-content></td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="table-2fn1" fn-type="other">
<p>Note: Red indicates the largest performance degradation (w/o Repair), purple indicates intermediate degradation (w/o Deep Constraints), blue indicates the smallest degradation (w/o Step-wise Validation), and orange highlights o1-mini&#x2019;s relatively smaller degradation in the repair ablation compared to other models.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Weakening constraint extraction causes intermediate degradation of 4.8&#x2013;6.7% across models. This demonstrates that sophisticated structural analysis&#x2014;capturing not just primitive type constraints but also action dependencies, mutual exclusions, and necessary orderings&#x2014;substantially improves initial plan quality. Without these deep constraints, language models generate structurally valid but logically inconsistent plans more frequently (e.g., attempting <monospace>stack</monospace> before satisfying <monospace>holding</monospace> preconditions), increasing reliance on downstream repair mechanisms. The repair controller can partially compensate for degraded constraint extraction, as evidenced by performance remaining well above randomized baselines (39.5% vs. 0%&#x2013;4.3%), but the limited attempt budget prevents full recovery.</p>
<p>Removing step-wise validation causes the smallest but still significant degradation of 3.2%&#x2013;4.5%. While VAL&#x2019;s binary feedback alone can support basic repair functionality, precise failure localization enables more efficient convergence. When the system knows that step 3 failed due to missing predicate <monospace>on(?x,?y)</monospace>, the repair controller can apply targeted precondition probing. Without this information, repair strategies must operate on coarser signals, leading to less effective interventions. The modest impact suggests that binary validation provides substantial value, but incremental improvements from diagnostic precision accumulate meaningfully across multiple repair attempts.</p>
<p>We conduct two-proportion z-tests comparing each ablation against the full system. All degradations achieve significance at <inline-formula id="ieqn-175"><mml:math id="mml-ieqn-175"><mml:mi>p</mml:mi><mml:mo>&#x003C;</mml:mo><mml:mn>0.001</mml:mn></mml:math></inline-formula>, with effect sizes <inline-formula id="ieqn-176"><mml:math id="mml-ieqn-176"><mml:mi>h</mml:mi></mml:math></inline-formula> ranging from 0.065 (w/o Step-wise Validation on o1-mini) to 0.211 (w/o Repair on GPT-4). Notably, the ranking of component importance remains consistent across all three models&#x2014;targeted repair provides the largest benefit, followed by deep constraint extraction, then step-wise validation&#x2014;despite the models&#x2019; diverse architectural foundations and capability profiles. This cross-model consistency suggests that our design choices address fundamental challenges inherent to lexical-prior-free planning rather than compensating for model-specific weaknesses.</p>
<p>The convergence of ablated configurations toward a relatively narrow performance range (35.8%&#x2013;44.8%) further supports this interpretation. When degraded through different mechanisms (weakening repair, diagnosis, or constraint extraction), heterogeneous models with substantially different baseline capabilities arrive at similar performance levels. This implies that the full system&#x2019;s superior performance (46.2%&#x2013;48.0%) emerges from synergistic integration of multiple components rather than any single dominant factor. Each mechanism addresses a distinct failure mode in the symbol-agnostic planning process, and their coordinated operation enables reliable performance under extreme lexical-prior-free constraints where semantic intuitions provide no guidance.</p>
<p>These ablation results confirm that our symbol-agnostic closed-loop pipeline represents a cohesive architectural design where multiple components contribute non-redundantly to overall effectiveness. The substantial gap between even the best single-component degradation and the full system underscores the necessity of complete integration across constraint extraction, failure diagnosis, and targeted repair mechanisms. Combined with the behavioral analyses in preceding sections, this chapter establishes both what our method achieves and why each architectural decision is essential. The next chapter will summarize the main contributions of this research and discuss future directions.</p>
</sec>
</sec>
<sec id="s6">
<label>6</label>
<title>Limitations and Future Directions</title>
<p>While our symbol-agnostic pipeline demonstrates substantial improvements over baseline approaches in lexical-prior-free planning, several limitations warrant acknowledgment.</p>
<p>A fundamental limitation lies in the difficulty of precisely quantifying computational cost-performance tradeoffs. Unlike classical planners where complexity can be characterized through formal bounds (e.g., PSPACE-completeness), our pipeline involves iterative LLM invocations whose costs are heterogeneous and context-dependent. Different repair strategies incur vastly different computational expenses: First-Step Constraint requires minimal overhead, while Precondition Probing may trigger multiple LLM calls, and Budget-Adaptive Retry performs complete plan regeneration. The relative frequency of these failure modes varies unpredictably across problem instances and model architectures. Moreover, LLM inference costs exhibit non-uniform scaling&#x2014;GPT-4 and GPT-4o employ different pricing tiers per token, while o1-mini incorporates internal chain-of-thought reasoning that inflates token consumption without transparent cost attribution. Our budget parameter <inline-formula id="ieqn-177"><mml:math id="mml-ieqn-177"><mml:mi>b</mml:mi></mml:math></inline-formula> controls iteration count but cannot directly bound monetary cost or wall-clock time, as each iteration&#x2019;s expense depends on plan length, repair complexity, and model-specific latency profiles. We cannot derive formal bounds relating problem hardness to expected computational expenditure, nor can we provide principled guidance for practitioners on optimal budget parameter selection beyond empirical observations.</p>
<p>Additionally, our approach fundamentally relies on the availability of sound validators (VAL, STRIPS simulators), limiting applicability to domains where executable semantics are well-defined. Future work could explore learned verifiers as scalable alternatives and adaptive budget allocation strategies that balance success probability against computational expense through reinforcement learning or Bayesian optimization. Despite these limitations, our work establishes that systematic validation and targeted repair can enable reliable symbol-agnostic planning&#x2014;a capability previously unattainable through direct LLM generation or general-purpose reflection mechanisms.</p>
</sec>
<sec id="s7">
<label>7</label>
<title>Conclusion</title>
<p>Addressing the insufficient planning capabilities of LLMs under lexical-prior-free conditions, this research proposes a symbol-agnostic closed-loop planning pipeline. Through a generate-verify-repair mechanism integrating six core components and two auxiliary components, the system performs reasoning, verification, and repair within obfuscated symbol space, addressing typical failure modes including first-step failures, missing preconditions, and mid-segment blockages. Evaluation on PlanBench Mystery Blocksworld demonstrates substantial improvements: GPT-4 and GPT-4o advance from baseline one-shot/zero-shot performance of 0.83%&#x2013;4.3% to 46.2%, while o1-mini improves from baseline zero-shot performance of 19.1% to 48.0%. Ablation studies validate the architectural integrity of our design through systematic degradation of key mechanisms while preserving system executability&#x2014;since certain components represent hard constraints whose complete removal would cause system failure, we employ a degradation strategy that weakens rather than eliminates functionality. Results confirm that targeted repair mechanisms provide the largest contribution, followed by deep constraint extraction and step-wise validation, with this ranking remaining consistent across all models despite their diverse architectural foundations. The substantial gap between degraded configurations and the full system underscores that superior performance emerges from synergistic integration rather than any single dominant mechanism. A particularly noteworthy finding is the convergence of final success rates across all three models within a narrow 1.8 percentage point range, contrasting sharply with their divergent baseline performance spanning nearly 20 percentage points. This convergence reveals a critical insight: when equipped with systematic validation and repair mechanisms, models with heterogeneous reasoning capabilities achieve consistent planning quality, indicating that closed-loop mechanisms become more decisive than intrinsic model capabilities under extreme lexical-prior-free conditions. Failure analysis shows distinct patterns&#x2014;language models fail predominantly on precondition satisfaction while o1-mini struggles primarily with global goal achievement&#x2014;yet targeted repair strategies effectively compensate for respective weaknesses. The research contributes at three levels: proposing a complete symbol-agnostic closed-loop pipeline with empirically validated architectural components, establishing rigorous multi-dimensional evaluation protocols incorporating statistical significance testing and mechanistic failure analysis, and revealing how validation-driven mechanisms enable performance convergence across heterogeneous models. The core insight is that systematic verification and repair mechanisms can be equally or more important than raw model capacity, enabling even weaker models to converge toward stronger model performance through structured iterative refinement. This finding holds general significance for multi-step reasoning tasks including program synthesis and theorem proving, and as AI systems assume increasingly critical decision-making roles, reliable verification and repair mechanisms will become essential infrastructure for ensuring system safety and trustworthiness.</p>
</sec>
</body>
<back>
<ack>
<p>Not applicable.</p>
</ack>
<sec>
<title>Funding Statement</title>
<p>This work was supported by the Information, Production and Systems Research Center, Waseda University, and partly supported by the Future Robotics Organization, Waseda University; the Humanoid Robotics Institute, Waseda University, under the Humanoid Project; the Waseda University Grant for Special Research Projects (grant numbers 2024C-518 and 2025E-027); and was partly executed under the cooperation of organization between Kioxia Corporation and Waseda University.</p>
</sec>
<sec>
<title>Author Contributions</title>
<p>The authors confirm contribution to the paper as follows: Conceptualization, Zhendong Du and Kenji Hashimoto; methodology, Zhendong Du; software, Zhendong Du; validation, Zhendong Du; formal analysis, Zhendong Du; investigation, Zhendong Du; data curation, Zhendong Du; writing&#x2014;original draft preparation, Zhendong Du; visualization, Hanliu Wang and Zhendong Du; writing&#x2014;review and editing, Kenji Hashimoto; supervision, Kenji Hashimoto; project administration, Kenji Hashimoto. All authors reviewed the results and approved the final version of the manuscript.</p>
</sec>
<sec sec-type="data-availability">
<title>Availability of Data and Materials</title>
<p>The data and code that support the findings of this study are openly available in the <italic>GitHub</italic> repository at <ext-link ext-link-type="uri" xlink:href="https://github.com/dzdfuture/Mystery_Planning">https://github.com/dzdfuture/Mystery_Planning</ext-link>.</p>
</sec>
<sec>
<title>Ethics Approval</title>
<p>Not applicable.</p>
</sec>
<sec sec-type="COI-statement">
<title>Conflicts of Interest</title>
<p>The authors declare no conflicts of interest to report regarding the present study.</p>
</sec>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1"><label>[1]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Olmo</surname> <given-names>A</given-names></string-name>, <string-name><surname>Sreedharan</surname> <given-names>S</given-names></string-name>, <string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Large language models still can&#x2019;t plan (a benchmark for LLMs on planning and reasoning about change)</article-title>. In: <conf-name>NeurIPS 2022 Foundation Models for Decision Making Workshop</conf-name>. <publisher-loc>London, UK</publisher-loc>: <publisher-name>PMLR</publisher-name>; <year>2022</year>.</mixed-citation></ref>
<ref id="ref-2"><label>[2]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Marquez</surname> <given-names>M</given-names></string-name>, <string-name><surname>Sreedharan</surname> <given-names>S</given-names></string-name>, <string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>On the planning abilities of large language models&#x2014;a critical investigation</article-title>. <source>Adv Neural Inform Process Syst</source>. <year>2023</year>;<volume>36</volume>:<fpage>75993</fpage>&#x2013;<lpage>6005</lpage>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Achiam</surname> <given-names>J</given-names></string-name>, <string-name><surname>Adler</surname> <given-names>S</given-names></string-name>, <string-name><surname>Agarwal</surname> <given-names>S</given-names></string-name>, <string-name><surname>Ahmad</surname> <given-names>L</given-names></string-name>, <string-name><surname>Akkaya</surname> <given-names>I</given-names></string-name>, <string-name><surname>Aleman</surname> <given-names>FL</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>Gpt-4 technical report</article-title>. <comment>arXiv:2303.08774</comment>. <year>2023</year>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Jaech</surname> <given-names>A</given-names></string-name>, <string-name><surname>Kalai</surname> <given-names>A</given-names></string-name>, <string-name><surname>Lerer</surname> <given-names>A</given-names></string-name>, <string-name><surname>Richardson</surname> <given-names>A</given-names></string-name>, <string-name><surname>El-Kishky</surname> <given-names>A</given-names></string-name>, <string-name><surname>Low</surname> <given-names>A</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>OpenAI o1 system card</article-title>. <comment>arXiv:2412.16720</comment>. <year>2024</year>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>McDermott</surname> <given-names>DM</given-names></string-name></person-group>. <article-title>The 1998 AI planning systems competition</article-title>. <source>AI Maga</source>. <year>2000</year>;<volume>21</volume>(<issue>2</issue>):<fpage>35</fpage>&#x2013;<lpage>5</lpage>.</mixed-citation></ref>
<ref id="ref-6"><label>[6]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Fikes</surname> <given-names>RE</given-names></string-name>, <string-name><surname>Nilsson</surname> <given-names>NJ</given-names></string-name></person-group>. <article-title>STRIPS: a new approach to the application of theorem proving to problem solving</article-title>. <source>Artif Intell</source>. <year>1971</year>;<volume>2</volume>(<issue>3&#x2013;4</issue>):<fpage>189</fpage>&#x2013;<lpage>208</lpage>. doi:<pub-id pub-id-type="doi">10.1016/0004-3702(71)90010-5</pub-id>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Hoffmann</surname> <given-names>J</given-names></string-name>, <string-name><surname>Nebel</surname> <given-names>B</given-names></string-name></person-group>. <article-title>The FF planning system: fast plan generation through heuristic search</article-title>. <source>J Artif Intell Res</source>. <year>2001</year>;<volume>14</volume>:<fpage>253</fpage>&#x2013;<lpage>302</lpage>. doi:<pub-id pub-id-type="doi">10.1613/jair.855</pub-id>.</mixed-citation></ref>
<ref id="ref-8"><label>[8]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Helmert</surname> <given-names>M</given-names></string-name></person-group>. <article-title>The fast downward planning system</article-title>. <source>J Artif Intell Res</source>. <year>2006</year>;<volume>26</volume>:<fpage>191</fpage>&#x2013;<lpage>246</lpage>. doi:<pub-id pub-id-type="doi">10.1613/jair.1705</pub-id>.</mixed-citation></ref>
<ref id="ref-9"><label>[9]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Bylander</surname> <given-names>T</given-names></string-name></person-group>. <article-title>The computational complexity of propositional STRIPS planning</article-title>. <source>Artif Intell</source>. <year>1994</year>;<volume>69</volume>(<issue>1&#x2013;2</issue>):<fpage>165</fpage>&#x2013;<lpage>204</lpage>. doi:<pub-id pub-id-type="doi">10.1016/0004-3702(94)90081-7</pub-id>.</mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Erol</surname> <given-names>K</given-names></string-name>, <string-name><surname>Hendler</surname> <given-names>JA</given-names></string-name>, <string-name><surname>Nau</surname> <given-names>DS</given-names></string-name></person-group>. <article-title>Semantics for hierarchical task-network planning</article-title>. In: <source>Technical report CS-TR-3239, UMIACS-TR-94-31, ISR-TR-95-9</source>. <publisher-loc>College Park, MD, USA</publisher-loc>: <publisher-name>University of Maryland College Park</publisher-name>; <year>1994</year>.</mixed-citation></ref>
<ref id="ref-11"><label>[11]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Du</surname> <given-names>Z</given-names></string-name>, <string-name><surname>Hashimoto</surname> <given-names>K</given-names></string-name></person-group>. <article-title>AcademiCraft: transforming writing assistance for english for academic purposes with multi-agent system innovations</article-title>. <source>Information</source>. <year>2025</year>;<volume>16</volume>(<issue>4</issue>):<fpage>254</fpage>. doi:<pub-id pub-id-type="doi">10.3390/info16040254</pub-id>.</mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Huang</surname> <given-names>W</given-names></string-name>, <string-name><surname>Abbeel</surname> <given-names>P</given-names></string-name>, <string-name><surname>Pathak</surname> <given-names>D</given-names></string-name>, <string-name><surname>Mordatch</surname> <given-names>I</given-names></string-name></person-group>. <article-title>Language models as zero-shot planners: extracting actionable knowledge for embodied agents</article-title>. In: <conf-name>International Conference on Machine Learning</conf-name>. <publisher-loc>London, UK</publisher-loc>: <publisher-name>PMLR</publisher-name>; <year>2022</year>. p. <fpage>9118</fpage>&#x2013;<lpage>47</lpage>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Radford</surname> <given-names>A</given-names></string-name>, <string-name><surname>Wu</surname> <given-names>J</given-names></string-name>, <string-name><surname>Child</surname> <given-names>R</given-names></string-name>, <string-name><surname>Luan</surname> <given-names>D</given-names></string-name>, <string-name><surname>Amodei</surname> <given-names>D</given-names></string-name>, <string-name><surname>Sutskever</surname> <given-names>I</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>Language models are unsupervised multitask learners</article-title>. <source>OpenAI Blog</source>. <year>2019</year>;<volume>1</volume>(<issue>8</issue>):<fpage>9</fpage>.</mixed-citation></ref>
<ref id="ref-14"><label>[14]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Wei</surname> <given-names>J</given-names></string-name>, <string-name><surname>Wang</surname> <given-names>X</given-names></string-name>, <string-name><surname>Schuurmans</surname> <given-names>D</given-names></string-name>, <string-name><surname>Bosma</surname> <given-names>M</given-names></string-name>, <string-name><surname>Xia</surname> <given-names>F</given-names></string-name>, <string-name><surname>Chi</surname> <given-names>E</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>Chain-of-thought prompting elicits reasoning in large language models</article-title>. <source>Adv Neural Inf Process Syst</source>. <year>2022</year>;<volume>35</volume>:<fpage>24824</fpage>&#x2013;<lpage>37</lpage>.</mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Stoev</surname> <given-names>T</given-names></string-name>, <string-name><surname>Sosnowski</surname> <given-names>T</given-names></string-name>, <string-name><surname>Yordanova</surname> <given-names>K</given-names></string-name></person-group>. <article-title>A tool for automated generation of domain specific symbolic models from texts</article-title>. In: <conf-name>2023 IEEE International Conference on Pervasive Computing and Communications Workshops and Other Affiliated Events (PerCom Workshops)</conf-name>. <publisher-loc>Piscataway, NJ, USA</publisher-loc>: <publisher-name>IEEE</publisher-name>; <year>2023</year>. p. <fpage>276</fpage>&#x2013;<lpage>8</lpage>.</mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name>, <string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Guan</surname> <given-names>L</given-names></string-name>, <string-name><surname>Verma</surname> <given-names>M</given-names></string-name>, <string-name><surname>Stechly</surname> <given-names>K</given-names></string-name>, <string-name><surname>Bhambri</surname> <given-names>S</given-names></string-name>, <etal>et al.</etal></person-group> <article-title>Position: LLMs can&#x2019;t plan, but can help planning in LLM-modulo frameworks</article-title>. In: <conf-name>41 International Conference on Machine Learning; 2024 Jul 21&#x2013;27</conf-name>; <publisher-loc>Vienna, Austria</publisher-loc>. p. <fpage>22895</fpage>&#x2013;<lpage>907</lpage>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Silver</surname> <given-names>T</given-names></string-name>, <string-name><surname>Hariprasad</surname> <given-names>V</given-names></string-name>, <string-name><surname>Shuttleworth</surname> <given-names>RS</given-names></string-name>, <string-name><surname>Kumar</surname> <given-names>N</given-names></string-name>, <string-name><surname>Lozano-P&#x00E9;rez</surname> <given-names>T</given-names></string-name>, <string-name><surname>Kaelbling</surname> <given-names>LP</given-names></string-name></person-group>. <article-title>PDDL planning with pretrained large language models</article-title>. In: <conf-name>NeurIPS 2022 Foundation Models for Decision Making Workshop</conf-name>. <publisher-loc>London, UK</publisher-loc>: <publisher-name>PMLR</publisher-name>; <year>2022</year>.</mixed-citation></ref>
<ref id="ref-18"><label>[18]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Stechly</surname> <given-names>K</given-names></string-name>, <string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>On the self-verification limitations of large language models on reasoning and planning tasks</article-title>. <comment>arXiv:2402.08115</comment>. <year>2024</year>.</mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Stechly</surname> <given-names>K</given-names></string-name>, <string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>LLMs still can&#x2019;t plan; can LRMs? A preliminary evaluation of OpenAI&#x2019;s o1 on PlanBench</article-title>. <comment>arXiv:2409.13373. 2024</comment>.</mixed-citation></ref>
<ref id="ref-20"><label>[20]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Yao</surname> <given-names>S</given-names></string-name>, <string-name><surname>Zhao</surname> <given-names>J</given-names></string-name>, <string-name><surname>Yu</surname> <given-names>D</given-names></string-name>, <string-name><surname>Du</surname> <given-names>N</given-names></string-name>, <string-name><surname>Shafran</surname> <given-names>I</given-names></string-name>, <string-name><surname>Narasimhan</surname> <given-names>KR</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>React: synergizing reasoning and acting in language models</article-title>. <comment>arXiv:2210.03629</comment>. <year>2022</year>.</mixed-citation></ref>
<ref id="ref-21"><label>[21]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Shinn</surname> <given-names>N</given-names></string-name>, <string-name><surname>Cassano</surname> <given-names>F</given-names></string-name>, <string-name><surname>Berman</surname> <given-names>E</given-names></string-name>, <string-name><surname>Gopinath</surname> <given-names>A</given-names></string-name>, <string-name><surname>Narasimhan</surname> <given-names>K</given-names></string-name>, <string-name><surname>Yao</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Reflexion: language agents with verbal reinforcement learning</article-title>. <comment>arXiv:2303.11366. 2023</comment>.</mixed-citation></ref>
<ref id="ref-22"><label>[22]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Mitchell</surname> <given-names>M</given-names></string-name></person-group>. <article-title>Abstraction and analogy-making in artificial intelligence</article-title>. <source>Ann New York Acad Sci</source>. <year>2021</year>;<volume>1505</volume>(<issue>1</issue>):<fpage>79</fpage>&#x2013;<lpage>101</lpage>.</mixed-citation></ref>
<ref id="ref-23"><label>[23]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Srivastava</surname> <given-names>V</given-names></string-name>, <string-name><surname>Sampath</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Could the brain function mathematically?</article-title> <source>Neurol Neurosci Res</source>. <year>2018</year>;<volume>1</volume>(<issue>1</issue>):<fpage>4</fpage>.</mixed-citation></ref>
<ref id="ref-24"><label>[24]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Li</surname> <given-names>H</given-names></string-name>, <string-name><surname>Chen</surname> <given-names>Z</given-names></string-name>, <string-name><surname>Liu</surname> <given-names>S</given-names></string-name>, <string-name><surname>Lu</surname> <given-names>Y</given-names></string-name>, <string-name><surname>Liu</surname> <given-names>F</given-names></string-name></person-group>. <article-title>Systematic analysis of LLM contributions to planning: solver, verifier, heuristic</article-title>. <comment>arXiv:2412.09666. 2024</comment>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Davis</surname> <given-names>E</given-names></string-name>, <string-name><surname>Marcus</surname> <given-names>G</given-names></string-name>, <string-name><surname>Chen</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Reasoning from radically incomplete information: the case of containers</article-title>. In: <conf-name>Proceedings of the Second Annual Conference on Advances in Cognitive Systems ACS</conf-name>. Vol. 273. <publisher-loc>New York, NY, USA</publisher-loc>: <publisher-name>ACM</publisher-name>; <year>2013</year>. <fpage>288</fpage> p.</mixed-citation></ref>
<ref id="ref-26"><label>[26]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Can large language models reason and plan?</article-title> <source>Ann New York Acad Sci</source>. <year>2024</year>;<volume>1534</volume>(<issue>1</issue>):<fpage>15</fpage>&#x2013;<lpage>8</lpage>.</mixed-citation></ref>
<ref id="ref-27"><label>[27]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Valmeekam</surname> <given-names>K</given-names></string-name>, <string-name><surname>Marquez</surname> <given-names>M</given-names></string-name>, <string-name><surname>Olmo</surname> <given-names>A</given-names></string-name>, <string-name><surname>Sreedharan</surname> <given-names>S</given-names></string-name>, <string-name><surname>Kambhampati</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Planbench: an extensible benchmark for evaluating large language models on planning and reasoning about change</article-title>. <source>Adv Neural Inform Process Syst</source>. <year>2023</year>;<volume>36</volume>:<fpage>38975</fpage>&#x2013;<lpage>87</lpage>.</mixed-citation></ref>
<ref id="ref-28"><label>[28]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Chen</surname> <given-names>DZ</given-names></string-name>, <string-name><surname>Zenn</surname> <given-names>J</given-names></string-name>, <string-name><surname>Cinquin</surname> <given-names>T</given-names></string-name>, <string-name><surname>McIlraith</surname> <given-names>SA</given-names></string-name></person-group>. <article-title>The 2025 planning performance of frontier large language models</article-title>. <comment>arXiv:2511.09378</comment>. <year>2025</year>.</mixed-citation></ref>
<ref id="ref-29"><label>[29]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Li</surname> <given-names>H</given-names></string-name>, <string-name><surname>Chen</surname> <given-names>Z</given-names></string-name>, <string-name><surname>Zhang</surname> <given-names>J</given-names></string-name>, <string-name><surname>Liu</surname> <given-names>F</given-names></string-name></person-group>. <article-title>PLANET: a collection of benchmarks for evaluating LLMs&#x2019; planning capabilities</article-title>. <comment>arXiv:2504.14773. 2025</comment>.</mixed-citation></ref>
<ref id="ref-30"><label>[30]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Mireshghallah</surname> <given-names>F</given-names></string-name>, <string-name><surname>Berg-Kirkpatrick</surname> <given-names>T</given-names></string-name></person-group>. <article-title>Style pooling: automatic text style obfuscation for improved classification fairness</article-title>. <comment>arXiv:2109.04624</comment>. <year>2021</year>.</mixed-citation></ref>
<ref id="ref-31"><label>[31]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Cassani</surname> <given-names>G</given-names></string-name>, <string-name><surname>G&#x00FC;nther</surname> <given-names>F</given-names></string-name>, <string-name><surname>Attanasio</surname> <given-names>G</given-names></string-name>, <string-name><surname>Bianchi</surname> <given-names>F</given-names></string-name>, <string-name><surname>Marelli</surname> <given-names>M</given-names></string-name></person-group>. <article-title>Meaning modulations and stability in large language models: an analysis of BERT embeddings for psycholinguistic research</article-title>. <source>psyArXiV</source>. <year>2023</year>. doi:<pub-id pub-id-type="doi">10.31234/osf.io/b45ys</pub-id>.</mixed-citation></ref>
<ref id="ref-32"><label>[32]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Moskvichev</surname> <given-names>A</given-names></string-name>, <string-name><surname>Odouard</surname> <given-names>VV</given-names></string-name>, <string-name><surname>Mitchell</surname> <given-names>M</given-names></string-name></person-group>. <article-title>The conceptarc benchmark: evaluating understanding and generalization in the arc domain</article-title>. <comment>arXiv:2305.07141</comment>. <year>2023</year>.</mixed-citation></ref>
<ref id="ref-33"><label>[33]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Smith</surname> <given-names>BD</given-names></string-name>, <string-name><surname>Feather</surname> <given-names>MS</given-names></string-name>, <string-name><surname>Muscettola</surname> <given-names>N</given-names></string-name></person-group>. <article-title>Challenges and methods in testing the remote agent planner</article-title>. In: <conf-name>AIPS&#x2019;00: Proceedings of the Fifth International Conference on Artificial Intelligence Planning Systems</conf-name>. <publisher-loc>Palo Alto, CA, USA</publisher-loc>: <publisher-name>AAAI Press</publisher-name>; <year>2000</year>. p. <fpage>254</fpage>&#x2013;<lpage>63</lpage>.</mixed-citation></ref>
<ref id="ref-34"><label>[34]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Bacchus</surname> <given-names>F</given-names></string-name></person-group>. <article-title>AIPS 2000 planning competition: the fifth international conference on artificial intelligence planning and scheduling systems</article-title>. <source>AI Mag</source>. <year>2001</year>;<volume>22</volume>(<issue>3</issue>):<fpage>47</fpage>.</mixed-citation></ref>
<ref id="ref-35"><label>[35]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Howey</surname> <given-names>R</given-names></string-name>, <string-name><surname>Long</surname> <given-names>D</given-names></string-name>, <string-name><surname>Fox</surname> <given-names>M</given-names></string-name></person-group>. <article-title>VAL: automatic plan validation, continuous effects and mixed initiative planning using PDDL</article-title>. In: <conf-name>16th IEEE International Conference on Tools with Artificial Intelligence</conf-name>. <publisher-loc>Piscataway, NJ, USA</publisher-loc>: <publisher-name>IEEE</publisher-name>; <year>2004</year>. p. <fpage>294</fpage>&#x2013;<lpage>301</lpage>.</mixed-citation></ref>
<ref id="ref-36"><label>[36]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Fox</surname> <given-names>M</given-names></string-name>, <string-name><surname>Long</surname> <given-names>D</given-names></string-name></person-group>. <article-title>PDDL&#x002B;: modeling continuous time dependent effects</article-title>. In: <conf-name>Proceedings of the 3rd International NASA Workshop on Planning and Scheduling for Space</conf-name>. Vol. 4. <publisher-loc>Washington, DC, USA</publisher-loc>: <publisher-name>NASA</publisher-name>; <year>2002</year>.</mixed-citation></ref>
<ref id="ref-37"><label>[37]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Gerevini</surname> <given-names>AE</given-names></string-name>, <string-name><surname>Haslum</surname> <given-names>P</given-names></string-name>, <string-name><surname>Long</surname> <given-names>D</given-names></string-name>, <string-name><surname>Saetti</surname> <given-names>A</given-names></string-name>, <string-name><surname>Dimopoulos</surname> <given-names>Y</given-names></string-name></person-group>. <article-title>Deterministic planning in the fifth international planning competition: PDDL3 and experimental evaluation of the planners</article-title>. <source>Artif Intell</source>. <year>2009</year>;<volume>173</volume>(<issue>5&#x2013;6</issue>):<fpage>619</fpage>&#x2013;<lpage>68</lpage>. doi:<pub-id pub-id-type="doi">10.1016/j.artint.2008.10.012</pub-id>.</mixed-citation></ref>
<ref id="ref-38"><label>[38]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Patil</surname> <given-names>K</given-names></string-name></person-group>. <article-title>LLMs for AI planning: a study on error detection and correction in PDDL domain models [dissertation]. Stuttgart, Germany: University of Stuttgart</article-title>; <year>2024</year>.</mixed-citation></ref>
</ref-list>
</back></article>