<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-06-07-1-execution-state-canonical-surface/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-06-07-1-execution-state-canonical-surface/</id>
  <title>ADR 2026-06-07-1: Execution-State Canonical Surface (`mission_runtime`)</title>
  <updated>2026-06-07T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-06-07-1-execution-state-canonical-surface/"/>
  <summary>Gives execution state a physical home in a net-new top-level `src/mission_runtime/` package, grown Strangler-Fig style while `core/execution_context.py` becomes a shim.</summary>
  <content type="html">&lt;h2 id=&quot;context&quot;&gt;Context&lt;/h2&gt;
&lt;p&gt;ADR &lt;a href=&quot;/adr/3.x/2026-06-03-1-execution-state-domain-model/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-06-03-1-execution-state-domain-model.md&lt;/code&gt;&lt;/a&gt;
ratified the bounded-module decomposition and named &lt;strong&gt;Execution / Runtime&lt;/strong&gt; as
the owner of workspace resolution, branch state, and CWD-invariant context. It
also recorded that the residue surfaces (~40 command surfaces re-deriving
execution context) must route through &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;What that ADR did &lt;em&gt;not&lt;/em&gt; lock in was the &lt;strong&gt;physical home&lt;/strong&gt; of the execution-state
domain. Today &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt; and its &lt;code dir=&quot;auto&quot;&gt;ActionContext&lt;/code&gt; value object live
in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/execution_context.py&lt;/code&gt;, buried inside the CLI package.
That placement makes the domain invisible at the package level: there is no
top-level module name that &lt;em&gt;screams&lt;/em&gt; “this is where execution state lives”, and
nothing prevents new surfaces from re-deriving their own context rather than
importing the canonical one.&lt;/p&gt;
&lt;p&gt;The design analysis in
&lt;a href=&quot;../../../docs/plans/engineering-notes/runtime_and_state_overhaul/06-proposed-domains-and-splits.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/plans/engineering-notes/runtime_and_state_overhaul/06-proposed-domains-and-splits.md&lt;/code&gt;&lt;/a&gt;
§4/§5 resolves this. §4 records the operator decision (Stijn, 2026-06-03) to
create a net-new top-level &lt;code dir=&quot;auto&quot;&gt;mission_runtime/&lt;/code&gt; umbrella package, and §5 fixes the
owner shape (Strangler façade → operation service; value-object resolver as
fallback).&lt;/p&gt;
&lt;p&gt;Per C-006, this ADR is written &lt;strong&gt;before&lt;/strong&gt; any mass code lands. The umbrella is
stood up empty-but-registered in this work package (WP02); the relocation of the
hardened &lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; logic into it is WP03.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;1-module-name-top-level-mission_runtime&quot;&gt;1. Module name: top-level &lt;code dir=&quot;auto&quot;&gt;mission_runtime/&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;The canonical execution-state surface is a &lt;strong&gt;net-new top-level package&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/&lt;/code&gt;. Rationale (doc 06 §4):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Screaming Architecture&lt;/strong&gt; — the package structure should name the domain. A
top-level &lt;code dir=&quot;auto&quot;&gt;mission_runtime/&lt;/code&gt; makes the execution-state domain discoverable at
the highest level of the source tree, rather than hiding it under
&lt;code dir=&quot;auto&quot;&gt;specify_cli/core/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Strangler Fig&lt;/strong&gt; — the new home grows alongside the old. The umbrella is the
new canonical surface; existing call-sites are strangled onto it
incrementally, and the old &lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt; becomes a thin
re-export shim removed once unreferenced (FR-003).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; is preferred over harden-in-place (keeping the logic in
&lt;code dir=&quot;auto&quot;&gt;core/&lt;/code&gt;) for domain clarity. The trade-off — a new top-level package must be
registered in the layer meta-guard — is accepted and discharged below.&lt;/p&gt;
&lt;h3 id=&quot;2-layer-placement-charter-level-sibling-of-runtime&quot;&gt;2. Layer placement: charter-level sibling of &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; is registered in &lt;code dir=&quot;auto&quot;&gt;_DEFINED_LAYERS&lt;/code&gt; in &lt;strong&gt;both&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_layer_rules.py&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;landscape&lt;/code&gt; fixture in
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/conftest.py&lt;/code&gt;. Omitting either causes
&lt;code dir=&quot;auto&quot;&gt;test_no_unregistered_src_packages&lt;/code&gt; to fail (doc 06 §4).&lt;/p&gt;
&lt;p&gt;It sits at the &lt;strong&gt;charter level&lt;/strong&gt;, consistent with &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;. The
spine remains &lt;code dir=&quot;auto&quot;&gt;kernel ← doctrine ← charter ← specify_cli&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;, and now &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; are siblings above &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; may import &lt;code dir=&quot;auto&quot;&gt;specify_cli.*&lt;/code&gt; (it delegates to today’s resolver
during migration) but must not import CLI presentation layers
(&lt;code dir=&quot;auto&quot;&gt;specify_cli.cli&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;specify_cli.next&lt;/code&gt;), mirroring the &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt; boundary.&lt;/p&gt;
&lt;h3 id=&quot;3-lean-public-api-expressed-over-context-objects&quot;&gt;3. Lean public API expressed over context objects&lt;/h3&gt;
&lt;p&gt;The package root exposes a minimal &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; (the &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; Declaration
Convention, C-007):&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;python&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;__all__ &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;ExecutionContext&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;resolve_action_context&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;ActionContextError&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;]&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; — the immutable, complete resolved context (read/write/dest
dirs, branch, WP identity, prompt). The API is expressed over &lt;strong&gt;this context
object&lt;/strong&gt;, never over path fragments. Consumers receive a resolved context;
they do not reconstruct &lt;code dir=&quot;auto&quot;&gt;main_repo_root / &quot;kitty-specs&quot; / mission_slug&lt;/code&gt;
themselves (FR-009).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_action_context(repo_root, mission, wp_id=None, *, mode=None) -&gt; ExecutionContext&lt;/code&gt;
— the single resolution entry point. CWD-invariant, topology-aware,
mode-correct &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, and raises &lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt; on unresolvable
context with &lt;strong&gt;no silent fallback&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt; — the only error type consumers catch.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything else is internal. The implementation lives in submodules
(&lt;code dir=&quot;auto&quot;&gt;mission_runtime/context.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_runtime/resolution.py&lt;/code&gt;) that consumers
&lt;strong&gt;must not import directly&lt;/strong&gt; — enforced by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_mission_runtime_surface.py&lt;/code&gt; (FR-005). This keeps the
surface lean and prevents the internal-leakage that let the old &lt;code dir=&quot;auto&quot;&gt;core/&lt;/code&gt; resolver
sprawl.&lt;/p&gt;
&lt;h3 id=&quot;4-stage-c-shape-only&quot;&gt;4. Stage-C shape only&lt;/h3&gt;
&lt;p&gt;This umbrella adopts the &lt;strong&gt;Stage-C&lt;/strong&gt; shape from doc 06 §5: a Strangler façade
(&lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt;) returning an immutable &lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; value
object, delegating to today’s resolver during migration (option C → A). The
Stage-B operation service / &lt;code dir=&quot;auto&quot;&gt;CommitTarget&lt;/code&gt; (commit-seam atomicity) is &lt;strong&gt;out of
scope&lt;/strong&gt; (C-008) — doc 06 §6 step 7 confirms &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; already enforces the
commit invariant, so &lt;code dir=&quot;auto&quot;&gt;CommitTarget&lt;/code&gt; is an ergonomic improvement deferred to
later work, not a safety gate this surface must provide.&lt;/p&gt;
&lt;h3 id=&quot;5-strangler-migration-order&quot;&gt;5. Strangler migration order&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;WP02 (this WP)&lt;/strong&gt; — stand up &lt;code dir=&quot;auto&quot;&gt;mission_runtime/&lt;/code&gt; empty-but-registered:
package skeleton + lean &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; (stub symbols), layer-guard registration in
both files, sole-resolver surface test, and this ADR.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP03&lt;/strong&gt; — relocate the hardened &lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt;
logic from &lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt; into the umbrella; wire the &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt;
symbols; leave &lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt; as a thin re-export shim
(NFR-001: behaviour preserved).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Downstream WPs&lt;/strong&gt; — strangle the residue surfaces onto
&lt;code dir=&quot;auto&quot;&gt;mission_runtime.resolve_action_context&lt;/code&gt;; delete duplicated path-builders;
remove the &lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt; shim once unreferenced (FR-003).&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;what-changes&quot;&gt;What changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new top-level package &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/&lt;/code&gt; exists and is enforced by the
layer meta-guard. Future code that adds execution-state logic has a named home.&lt;/li&gt;
&lt;li&gt;The lean &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; becomes the contract; the surface test makes internal
imports a build failure, so the leakage that bloated the old resolver cannot
recur.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;what-stays-the-same&quot;&gt;What stays the same&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Nothing relocates in this WP. &lt;code dir=&quot;auto&quot;&gt;core/execution_context.py&lt;/code&gt; and all current
call-sites are untouched (relocation is WP03). The umbrella symbols are stubs
until WP03 wires them.&lt;/li&gt;
&lt;li&gt;Legacy missions continue to resolve through the existing resolver until they
are strangled (NFR-001).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;what-is-now-explicit&quot;&gt;What is now explicit&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The execution-state domain has a screaming, top-level home: &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The public surface is lean and expressed over context objects (originally four
symbols; &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt; was retired 2026-08-21 — see Amendments), and internal
submodules are import-forbidden from outside the package.&lt;/li&gt;
&lt;li&gt;The migration is Strangler-ordered: umbrella first (WP02), relocation second
(WP03), call-site cutover and shim removal after.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendments&quot;&gt;Amendments&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;2026-08-21 — &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt; retired (mission &lt;code dir=&quot;auto&quot;&gt;rc3-execution-mode-consolidation-01M0GGX1&lt;/code&gt;, M7).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;mission_runtime.context.ExecutionMode&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; enum) was
never consumed: &lt;code dir=&quot;auto&quot;&gt;MissionExecutionContext.execution_mode&lt;/code&gt; carries a raw &lt;code dir=&quot;auto&quot;&gt;str&lt;/code&gt;, and
no code compared against the enum’s members. It was removed from &lt;code dir=&quot;auto&quot;&gt;context.py&lt;/code&gt;, from
the package &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt;, and from this ADR’s public-API listing. The worktree-vs-direct
execution-mode axis is owned by the external &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.status.ExecutionMode&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;direct_repo&lt;/code&gt;); the retired local enum was a dead, mis-named duplicate
of that axis whose &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; token also collided with the &lt;em&gt;ownership&lt;/em&gt; enum’s
unrelated &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; (“WP produces code”). Retiring it removes both the dead
symbol and one half of that class-name/token footgun.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;2026-09-28 — &lt;code dir=&quot;auto&quot;&gt;OwnedCheckout&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;OwnedRefusalCode&lt;/code&gt; added to the root surface (mission
&lt;code dir=&quot;auto&quot;&gt;owned-checkout-lifecycle-authority-01M3M2ZB&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_runtime.OwnedCheckout&lt;/code&gt; is the
validated ownership fact: the owned checkout, the repository root checkout, the mission’s
stored topology and its target branch, proven once per command. The placement seam,
WP workspace resolution, the status transition pipeline, the &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; runtime and the prompt
builder consume it, so it lives in this package and adds no outbound edge into the CLI
application layer. It is minted only by &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.owned_mission&lt;/code&gt; (architectural gate
G3) and is exported on the root because MR-1/MR-2 forbid submodule imports.
&lt;code dir=&quot;auto&quot;&gt;mission_runtime.OwnedRefusalCode&lt;/code&gt; is a second new root export: a &lt;code dir=&quot;auto&quot;&gt;StrEnum&lt;/code&gt; (value == name)
holding the &lt;code dir=&quot;auto&quot;&gt;OWNED_*&lt;/code&gt; refusal-code registry from &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt;, exported alongside
&lt;code dir=&quot;auto&quot;&gt;OwnedCheckout&lt;/code&gt; so code and tests import the member instead of repeating the literal
(Sonar S1192). &lt;code dir=&quot;auto&quot;&gt;OwnedCheckoutPathRefused&lt;/code&gt;, the exception that subclasses the already-public
&lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt;, is deliberately not exported.
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_mission_runtime_surface.py&lt;/code&gt; pins both &lt;code dir=&quot;auto&quot;&gt;OwnedCheckout&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;OwnedRefusalCode&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;_PUBLIC_SURFACE&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mission spec: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/execution-state-canonical-surface-01KTG6P9/spec.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Contract: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/execution-state-canonical-surface-01KTG6P9/contracts/mission_runtime_api.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Design basis: &lt;a href=&quot;../../../docs/plans/engineering-notes/runtime_and_state_overhaul/06-proposed-domains-and-splits.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/plans/engineering-notes/runtime_and_state_overhaul/06-proposed-domains-and-splits.md&lt;/code&gt;&lt;/a&gt; §4/§5 (and §6 sequencing); doc 17 (consolidated domain model)&lt;/li&gt;
&lt;li&gt;Prior ADR: &lt;a href=&quot;/adr/3.x/2026-06-03-1-execution-state-domain-model/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-06-03-1-execution-state-domain-model.md&lt;/code&gt;&lt;/a&gt; — bounded-module decomposition&lt;/li&gt;
&lt;li&gt;Prior ADR: &lt;a href=&quot;/adr/3.x/2026-06-03-2-executioncontext-owner-and-committarget/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-06-03-2-executioncontext-owner-and-committarget.md&lt;/code&gt;&lt;/a&gt; — ExecutionContext owner / CommitTarget rationale&lt;/li&gt;
&lt;li&gt;Tactic: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/tactics/built-in/refactoring/refactoring-strangler-fig.tactic.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Issue #1619: root-cause analysis and Strangler Fig sequence&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
