AIMech AI

Concurrent planning and execution metareasoning model

Model Families AIMech:ConcurrentPlanningExecutionModel DRAFT
A formal metareasoning model that represents competing plan-computation processes, their known executable action heads and induced-deadline distributions, and poses the problem of selecting a joint computation/execution policy to maximize timely solution probability in the source’s concurrent-planning setting.
Identity Notes & Concept Scope The source-specific formal decision model for concurrent planning and execution, with planning-process performance profiles, known action heads, induced deadlines and a joint computation/execution policy objective. Retain one named formal model. Its problem statement and MDP encoding are representations of the same scoped subject; do not create separate identities for the encoding or every assumption-restricted subcase. General Definition 1, the four simplifying analysis assumptions, and KID-CoPE special-case results are distinct layers. This is not a claim that every instance has the properties of the restricted MDP analysis. CoPE is used for a broader setting and in the 2025 source; omit it as a global alias. The descriptive canonical name narrows this proposal to the 2023 metareasoning model. Current insertion identity was assessed on 2026-10-16 at merged HEAD 8650bfb55ef0c67902b5a80f1527920c87ad1d9d and tree cd6972cabe7b7f1cdf9ca5ee69bd6263a991ba50. The complete inventory contains813 maintained and442 pinned AIO records,1255 total, with no normalized collision among the four candidates. Eight ignored- and hidden-inclusive searches across data/, research/, sources/ and docs/ account for167 distinct matching contents and856 match events. Of these,105 groups retain exact historical scoped-event attribution and62 contents received fresh semantic reading with complete relevant parent context. The newly added manufacturing record was fully compared;22 prior native contexts are byte-identical and retain attributed semantic comparisons. The current mapping assessment read21 complete pinned AIO nodes and72 incident edges. The peer independently checked the current-state work with original scientific authorship disclosed. This is bounded identity clearance for the selected corpus and pin, not universal novelty or source exhaustion. Historical131-content/588-occurrence searching used four whole checkouts and included review/vendor contexts; it is retained by attribution rather than described as the current four-root search. The existing main911 source coordinator is accepted for this insertion without merging method identities or closing source questions.

Claims & Grounded Evidence

6 Claims
Mechanism #formal-input-and-objective
The CoPE problem supplies a set of base actions with positive durations and n planning processes. Each process has a possibly empty known action head H_i, a computation-completion performance profile M_i and an induced-deadline distribution D_i. A policy allocates computation and legally initiates head actions to maximize the probability of executing a timely solution. The model is a static decision abstraction rather than a single search procedure.
Mechanism #serial-actions-and-prefix-invalidation
A legal initiated prefix starts no earlier than time zero, starts each later action no earlier than the preceding action finishes, and respects operative individual action deadlines. Base actions are non-preemptible and cannot execute in parallel, while computation can overlap a base action. Executing a prefix invalidates a process whose known head is incompatible with that prefix. The unknown suffix cannot start before its planning process terminates.
Mechanism #induced-deadline-construction
For process i, let X_i be the time by which the complete solution must finish and R_i the unknown remainder duration revealed when planning terminates. The source defines the induced deadline as D_i=X_i−R_i and writes timely suffix initiation as start(beta_i)<=X_i−R_i. This subtraction is meaningful even when X_i and R_i are dependent. The later mutual-independence premise for the M_i and induced D_i variables is separate from this definition.
Scope #restricted-analysis-assumptions
The analyzed construction assumes discrete time, known action durations, mutual independence of all performance-profile and induced-deadline variables, and no operative individual base-action deadlines. Positive base-action durations are already part of Definition 1. The statement that an implementation can allow individual action deadlines does not extend the displayed analyses to all such cases.
Mechanism #decision-state-and-computation-transition
The analyzed MDP records wall time T, computation already allocated to each process and its failure state, remaining execution time W for the current base action, and the number L of initiated or completed base actions, with terminal SUCCESS and FAIL states. A computation action allocates one unit to an eligible process; conditional on unfinished positive survival, its termination probability is m_i(T_i+1)/(1−M_i(T_i)). Computation advances wall time while an executing base action can progress. Base initiation is allowed only when no other base action is executing and the action is next in a surviving head. The source assigns reward one to SUCCESS and zero elsewhere.
Scope #known-deadline-policy-results
For KID-CoPE, the known-induced-deadline restriction under the stated analysis assumptions, the source states that policies are linear and that an optimal policy exists which is linear, computation-contiguous and lazy. Contiguity applies to the computation subsequence CA(sigma), so base-action initiations may still intervene. Laziness delays base initiations until a further adjacent delay would be tardy or illegal. These are source-stated restricted existence results, not a claim that every policy is optimal or that the general heuristic schemes solve all CoPE instances optimally.

⚠️ Curated Limitations & Negative Results

Artificial Intelligence Ontology (AIO) Grounding

Mapped AIO Classes
AIO Target Class Mapping Relation Mapping Rationale
AIO:Model
Model
broad_match The pinned definition covers an abstract logical, mathematical or conceptual representation of a complex system. The source-defined CoPE decision model is such a representation, so broad_match is defensible for the model only. Named executable-control schemas are not themselves this model; sharing a model input is not class identity.

Evidence Sources & Primary Literature

2 Sources
Source ID Publication / Document Type / Access Reference & Checksum
elboher2023
Amihay Elboher, Ava Bensoussan, Erez Karpas, Wheeler Ruml, Shahaf S. Shperberg, Eyal Shimony
primary paper
full_text
ID: doi:10.1609/aaai.v37i10.26464
sha256:ad81b149dda7…
elboher2023-arxiv
Amihay Elboher, Ava Bensoussan, Erez Karpas, Wheeler Ruml, Shahaf S. Shperberg, Solomon E. Shimony
primary paper
full_text
ID: arxiv:2303.02664v1
sha256:1e4af5c0e79f…

Curation Provenance

Curator: Codex
Method: ai_assisted
Model: GPT-6
Created: 2026-10-16T09:15:13Z
Updated: 2026-10-16T09:15:13Z
Source File: data/curated/ConcurrentPlanningExecutionModel.yaml