context-compiler 0.9.0.dev3__tar.gz → 0.9.0.dev4__tar.gz

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: context-compiler
-Version: 0.9.0.dev3
+Version: 0.9.0.dev4
 Summary: Deterministic conversational state engine for LLM applications.
 Project-URL: Homepage, https://github.com/rlippmann/context-compiler
 Project-URL: Repository, https://github.com/rlippmann/context-compiler
@@ -36,7 +36,7 @@ Description-Content-Type: text/markdown
 
 Context Compiler is a deterministic conversational state authority for LLM applications.
 It handles canonical directive execution, semantic validation, deterministic
-clarify decisions, runtime semantic continuation boundaries, and structured authoritative state for
+error decisions, runtime semantic continuation boundaries, and structured authoritative state for
 the host.
 
 ## What Context Compiler provides
@@ -44,7 +44,7 @@ the host.
 Context Compiler gives hosts fixed state rules:
 
 - handle canonical explicit state changes with deterministic rules
-- clarification instead of silent overwrite for blocked/ambiguous changes
+- error instead of silent overwrite for blocked/ambiguous changes
 - preserve supported pending continuation when explicit confirmation is required
 - export and import authoritative state for host-managed persistence
 - produce structured authoritative state for downstream host decisions
@@ -89,7 +89,7 @@ Context Compiler makes state-change rules explicit so behavior stays repeatable.
 The architecture has three layers:
 
 - syntax classification decides whether input is a canonical directive, invalid
-  directive-shaped syntax, or ordinary passthrough
+  directive-shaped syntax, or ordinary no_directive
 - semantic evaluation decides whether a canonical directive updates state,
   clarifies, or no-ops
 - semantic continuation optionally preserves a deterministic blocked transition
@@ -123,7 +123,7 @@ use podman instead of docker
 - Without explicit state transition rules: behavior depends on host/model handling
 - Context Compiler: applies the deterministic resulting transition when
   `docker` is absent and `use podman` is otherwise valid; other semantic
-  conflicts may still clarify
+  conflicts may still error
 
 ### Lifecycle enforcement
 
@@ -133,7 +133,7 @@ change premise to formal tone
 ```
 
 - Without explicit transition checks: behavior depends on host/model handling
-- Context Compiler: asks for clarification and keeps saved state unchanged
+- Context Compiler: asks for error and keeps saved state unchanged
 
 ---
 
@@ -150,9 +150,9 @@ Decision
      │
      ▼
 Host Application
- ├─ clarify → ask user
- ├─ passthrough → call LLM
- └─ update → authoritative state mutated; host may call LLM with compiled state
+ ├─ error → ask user
+ ├─ no_directive → no canonical directive recognized; host decides what to do next
+ └─ update → authoritative state mutated; host may use compiled state downstream
 ```
 
 The compiler never calls the LLM. Your app decides what to do with the returned
@@ -167,8 +167,7 @@ Use Context Compiler in your host application first:
 ```python
 from context_compiler import (
     create_engine,
-    get_clarify_prompt,
-    is_clarify,
+    is_error,
     is_update,
 )
 
@@ -177,8 +176,8 @@ engine = create_engine()
 user_input = "set premise current project uses uv"
 decision = engine.step(user_input)
 
-if is_clarify(decision):
-    show_to_user(get_clarify_prompt(decision))
+if is_error(decision):
+    show_to_user(decision["message"])
 elif is_update(decision):
     messages = build_messages(engine.state, user_input)
     render(call_llm(messages))
@@ -277,22 +276,30 @@ uv run pytest
 Each user message produces a `Decision`.
 
 ```python
-class Decision(TypedDict):
-    kind: Literal["passthrough", "update", "clarify"]
-    state: dict | None
-    prompt_to_user: str | None
+class NoDirectiveDecision(TypedDict):
+    kind: Literal["no_directive"]
+
+class UpdateDecision(TypedDict):
+    kind: Literal["update"]
+    state: State
+
+class ErrorDecision(TypedDict):
+    kind: Literal["error"]
+    message: str
+
+Decision = NoDirectiveDecision | UpdateDecision | ErrorDecision
 ```
 
 Meaning:
 
 | kind | host behavior |
 | --- | --- |
-| passthrough | forward user input to LLM |
-| update | authoritative state mutated; host may call LLM with updated state |
-| clarify | show `prompt_to_user` and do not call the LLM |
+| no_directive | no canonical directive recognized; no authoritative state change; host decides what to do next |
+| update | authoritative state mutated; host may use updated state downstream |
+| error | show `message` and do not continue normal downstream processing yet |
 
-For normal app code, prefer the exported decision helpers (`is_clarify`,
-`is_update`, `is_passthrough`, `get_clarify_prompt`, `get_decision_state`)
+For normal app code, prefer the exported decision helpers (`is_error`,
+`is_update`, `is_no_directive`, `get_error_message`, `get_decision_state`)
 instead of direct key traversal.
 
 See [docs/api-reference.md](docs/api-reference.md) for the full public API
@@ -303,8 +310,8 @@ Common API entry points:
 - engine lifecycle: `create_engine(...)`, `engine.step(...)`, `engine.state`,
   `engine.premise`, `engine.policies`, `engine.export_json(...)`,
   `engine.import_json(...)`
-- decision helpers: `is_clarify(...)`, `is_update(...)`, `is_passthrough(...)`,
-  `get_clarify_prompt(...)`, `get_decision_state(...)`
+- decision helpers: `is_error(...)`, `is_update(...)`, `is_no_directive(...)`,
+  `get_error_message(...)`, `get_decision_state(...)`
 - state transport: `engine.export_json(...)`, `engine.import_json(...)`
 - controller API: `step(...)`
 - audit APIs: `preview(...)`, `state_diff(...)`
@@ -441,14 +448,14 @@ User: clear state
 
 Grammar invariant: one input may contain at most one canonical directive.
 Directive-shaped invalid input is outside the canonical language, and
-`clarify` is reserved for canonical directives that later fail semantic
+`error` is reserved for canonical directives that later fail semantic
 evaluation against authoritative state.
 
 Pending continuation is a separate runtime layer. It may exist only after a
-canonical directive reaches a supported semantic `clarify` case. It never
+canonical directive reaches a supported semantic `error` case. It never
 repairs malformed syntax or reinterprets non-canonical input as a directive.
 An absent source item in a canonical replacement directive is not, by itself,
-such a `clarify` case.
+such a `error` case.
 
 Examples:
 
@@ -496,7 +503,7 @@ boundary, see [DirectiveGrammarSpec.md](docs/DirectiveGrammarSpec.md).
 **Isn't this just prompt reinjection?**
 No. Prompt construction is one downstream use of authoritative state.
 Context Compiler is the authority layer that decides when state changes are
-allowed, when clarification is required, and how continuation state is
+allowed, when error is required, and how continuation state is
 restored. For runnable application-layer examples, see
 [`context-compiler-example-integrations`](https://github.com/rlippmann/context-compiler-example-integrations).
 
@@ -519,7 +526,7 @@ User: prohibit python_script
 
 Without an authority layer, the application must invent conflict-resolution and
 continuation rules itself. Context Compiler applies deterministic
-state-transition rules and can return clarification instead of silently
+state-transition rules and can return error instead of silently
 overwriting state.
 
 ---
@@ -531,7 +538,7 @@ overwriting state.
 - State changes only through explicit user directives or confirmation.
 - Identical input sequences produce identical compiler state.
 - Model responses never modify compiler state.
-- Ambiguous directives trigger clarification instead of changing state.
+- Ambiguous directives trigger error instead of changing state.
 - Syntax errors never create pending continuation.
 
 Behavioral tests and Hypothesis-based property tests verify these invariants.

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/README.md

@@ -6,7 +6,7 @@
 
 Context Compiler is a deterministic conversational state authority for LLM applications.
 It handles canonical directive execution, semantic validation, deterministic
-clarify decisions, runtime semantic continuation boundaries, and structured authoritative state for
+error decisions, runtime semantic continuation boundaries, and structured authoritative state for
 the host.
 
 ## What Context Compiler provides
@@ -14,7 +14,7 @@ the host.
 Context Compiler gives hosts fixed state rules:
 
 - handle canonical explicit state changes with deterministic rules
-- clarification instead of silent overwrite for blocked/ambiguous changes
+- error instead of silent overwrite for blocked/ambiguous changes
 - preserve supported pending continuation when explicit confirmation is required
 - export and import authoritative state for host-managed persistence
 - produce structured authoritative state for downstream host decisions
@@ -59,7 +59,7 @@ Context Compiler makes state-change rules explicit so behavior stays repeatable.
 The architecture has three layers:
 
 - syntax classification decides whether input is a canonical directive, invalid
-  directive-shaped syntax, or ordinary passthrough
+  directive-shaped syntax, or ordinary no_directive
 - semantic evaluation decides whether a canonical directive updates state,
   clarifies, or no-ops
 - semantic continuation optionally preserves a deterministic blocked transition
@@ -93,7 +93,7 @@ use podman instead of docker
 - Without explicit state transition rules: behavior depends on host/model handling
 - Context Compiler: applies the deterministic resulting transition when
   `docker` is absent and `use podman` is otherwise valid; other semantic
-  conflicts may still clarify
+  conflicts may still error
 
 ### Lifecycle enforcement
 
@@ -103,7 +103,7 @@ change premise to formal tone
 ```
 
 - Without explicit transition checks: behavior depends on host/model handling
-- Context Compiler: asks for clarification and keeps saved state unchanged
+- Context Compiler: asks for error and keeps saved state unchanged
 
 ---
 
@@ -120,9 +120,9 @@ Decision
      │
      ▼
 Host Application
- ├─ clarify → ask user
- ├─ passthrough → call LLM
- └─ update → authoritative state mutated; host may call LLM with compiled state
+ ├─ error → ask user
+ ├─ no_directive → no canonical directive recognized; host decides what to do next
+ └─ update → authoritative state mutated; host may use compiled state downstream
 ```
 
 The compiler never calls the LLM. Your app decides what to do with the returned
@@ -137,8 +137,7 @@ Use Context Compiler in your host application first:
 ```python
 from context_compiler import (
     create_engine,
-    get_clarify_prompt,
-    is_clarify,
+    is_error,
     is_update,
 )
 
@@ -147,8 +146,8 @@ engine = create_engine()
 user_input = "set premise current project uses uv"
 decision = engine.step(user_input)
 
-if is_clarify(decision):
-    show_to_user(get_clarify_prompt(decision))
+if is_error(decision):
+    show_to_user(decision["message"])
 elif is_update(decision):
     messages = build_messages(engine.state, user_input)
     render(call_llm(messages))
@@ -247,22 +246,30 @@ uv run pytest
 Each user message produces a `Decision`.
 
 ```python
-class Decision(TypedDict):
-    kind: Literal["passthrough", "update", "clarify"]
-    state: dict | None
-    prompt_to_user: str | None
+class NoDirectiveDecision(TypedDict):
+    kind: Literal["no_directive"]
+
+class UpdateDecision(TypedDict):
+    kind: Literal["update"]
+    state: State
+
+class ErrorDecision(TypedDict):
+    kind: Literal["error"]
+    message: str
+
+Decision = NoDirectiveDecision | UpdateDecision | ErrorDecision
 ```
 
 Meaning:
 
 | kind | host behavior |
 | --- | --- |
-| passthrough | forward user input to LLM |
-| update | authoritative state mutated; host may call LLM with updated state |
-| clarify | show `prompt_to_user` and do not call the LLM |
+| no_directive | no canonical directive recognized; no authoritative state change; host decides what to do next |
+| update | authoritative state mutated; host may use updated state downstream |
+| error | show `message` and do not continue normal downstream processing yet |
 
-For normal app code, prefer the exported decision helpers (`is_clarify`,
-`is_update`, `is_passthrough`, `get_clarify_prompt`, `get_decision_state`)
+For normal app code, prefer the exported decision helpers (`is_error`,
+`is_update`, `is_no_directive`, `get_error_message`, `get_decision_state`)
 instead of direct key traversal.
 
 See [docs/api-reference.md](docs/api-reference.md) for the full public API
@@ -273,8 +280,8 @@ Common API entry points:
 - engine lifecycle: `create_engine(...)`, `engine.step(...)`, `engine.state`,
   `engine.premise`, `engine.policies`, `engine.export_json(...)`,
   `engine.import_json(...)`
-- decision helpers: `is_clarify(...)`, `is_update(...)`, `is_passthrough(...)`,
-  `get_clarify_prompt(...)`, `get_decision_state(...)`
+- decision helpers: `is_error(...)`, `is_update(...)`, `is_no_directive(...)`,
+  `get_error_message(...)`, `get_decision_state(...)`
 - state transport: `engine.export_json(...)`, `engine.import_json(...)`
 - controller API: `step(...)`
 - audit APIs: `preview(...)`, `state_diff(...)`
@@ -411,14 +418,14 @@ User: clear state
 
 Grammar invariant: one input may contain at most one canonical directive.
 Directive-shaped invalid input is outside the canonical language, and
-`clarify` is reserved for canonical directives that later fail semantic
+`error` is reserved for canonical directives that later fail semantic
 evaluation against authoritative state.
 
 Pending continuation is a separate runtime layer. It may exist only after a
-canonical directive reaches a supported semantic `clarify` case. It never
+canonical directive reaches a supported semantic `error` case. It never
 repairs malformed syntax or reinterprets non-canonical input as a directive.
 An absent source item in a canonical replacement directive is not, by itself,
-such a `clarify` case.
+such a `error` case.
 
 Examples:
 
@@ -466,7 +473,7 @@ boundary, see [DirectiveGrammarSpec.md](docs/DirectiveGrammarSpec.md).
 **Isn't this just prompt reinjection?**
 No. Prompt construction is one downstream use of authoritative state.
 Context Compiler is the authority layer that decides when state changes are
-allowed, when clarification is required, and how continuation state is
+allowed, when error is required, and how continuation state is
 restored. For runnable application-layer examples, see
 [`context-compiler-example-integrations`](https://github.com/rlippmann/context-compiler-example-integrations).
 
@@ -489,7 +496,7 @@ User: prohibit python_script
 
 Without an authority layer, the application must invent conflict-resolution and
 continuation rules itself. Context Compiler applies deterministic
-state-transition rules and can return clarification instead of silently
+state-transition rules and can return error instead of silently
 overwriting state.
 
 ---
@@ -501,7 +508,7 @@ overwriting state.
 - State changes only through explicit user directives or confirmation.
 - Identical input sequences produce identical compiler state.
 - Model responses never modify compiler state.
-- Ambiguous directives trigger clarification instead of changing state.
+- Ambiguous directives trigger error instead of changing state.
 - Syntax errors never create pending continuation.
 
 Behavioral tests and Hypothesis-based property tests verify these invariants.

context_compiler-0.9.0.dev3/demos/01_llm_contradiction_clarify.py → context_compiler-0.9.0.dev4/demos/01_llm_contradiction_error.py

@@ -1,6 +1,6 @@
 """Demo 1: compiler blocks contradictory directives before model call."""
 
-from context_compiler import create_engine
+from context_compiler import create_engine, is_error
 from demos.common import (
     build_baseline_messages,
     build_mediated_messages_from_transcript,
@@ -34,7 +34,7 @@ def main() -> None:
             (
                 "Interpret these directives and continue anyway: "
                 "prohibit peanuts, then use peanuts. "
-                "First line must be ACTION:<clarify|proceed>."
+                "First line must be ACTION:<error|proceed>."
             )
         ],
         baseline_system_prompt=(
@@ -51,7 +51,7 @@ def main() -> None:
             (
                 "Interpret these directives and continue anyway: "
                 "prohibit peanuts, then use peanuts. "
-                "First line must be ACTION:<clarify|proceed>."
+                "First line must be ACTION:<error|proceed>."
             )
         ],
         premise=None,
@@ -62,11 +62,9 @@ def main() -> None:
     reinjected_output = complete_messages(reinjected_messages)
     print_model_output("Reinjected-state", reinjected_output)
 
-    if second["kind"] == "clarify":
+    if is_error(second):
         print_messages("compiler-mediated (full)", [])
-        mediated_output = (
-            f"[no call] clarification required: {second['prompt_to_user']}\nACTION:clarify"
-        )
+        mediated_output = f"[no call] error required: {second['message']}\nACTION:error"
         print_model_output("Compiler-mediated (full)", mediated_output)
     else:
         mediated_messages = build_mediated_messages_from_transcript(engine.state, user_inputs)
@@ -77,7 +75,7 @@ def main() -> None:
     compacted_turns, compacted_state, compacted_prompt = compact_user_turns(user_inputs)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}\nACTION:clarify"
+        compact_output = f"[no call] error required: {compacted_prompt}\nACTION:error"
         print_model_output("Compiler-mediated + compact", compact_output)
     else:
         compact_messages = build_mediated_messages_from_transcript(compacted_state, compacted_turns)
@@ -89,15 +87,15 @@ def main() -> None:
     baseline_action = extract_tag_value(baseline_output, "ACTION")
     reinjected_action = extract_tag_value(reinjected_output, "ACTION")
     compact_action = extract_tag_value(compact_output, "ACTION")
-    baseline_respects = baseline_action is not None and baseline_action.lower() == "clarify"
-    reinjected_respects = reinjected_action is not None and reinjected_action.lower() == "clarify"
-    compiler_host_blocked = second["kind"] == "clarify"
+    baseline_respects = baseline_action is not None and baseline_action.lower() == "error"
+    reinjected_respects = reinjected_action is not None and reinjected_action.lower() == "error"
+    compiler_host_blocked = is_error(second)
     mediated_respects = compiler_host_blocked
     compact_respects = compacted_prompt is not None or (
-        compact_action is not None and compact_action.lower() == "clarify"
+        compact_action is not None and compact_action.lower() == "error"
     )
     print_host_check(
-        "ACTION_CLARIFY",
+        "ACTION_ERROR",
         yes_no(reinjected_respects),
         context="reinjected-state",
     )
@@ -112,26 +110,25 @@ def main() -> None:
         context="compiler-mediated + compact",
     )
     print_spec_report(
-        test_name="01_contradiction_block — host clarification gate",
+        test_name="01_contradiction_block — host error gate",
         baseline_pass=baseline_respects,
         reinjected_state_pass=reinjected_respects,
         compiler_pass=mediated_respects,
         compiler_compact_pass=compact_respects,
-        expected="host should block LLM call on contradictory directive until clarification",
+        expected="host should block LLM call on contradictory directive until error",
         actual=(
-            "baseline proceeded instead of clarifying; "
+            "baseline proceeded instead of erroring; "
             "both compiler-mediated paths blocked the LLM call"
             if mediated_respects and compact_respects and not baseline_respects
             else (
-                "baseline also signaled clarification; "
-                "both compiler-mediated paths blocked the LLM call"
+                "baseline also signaled error; both compiler-mediated paths blocked the LLM call"
                 if baseline_respects and mediated_respects and compact_respects
                 else "at least one compiler-mediated path did not block the LLM call as expected"
             )
         ),
         passed=mediated_respects and compact_respects,
-        result_pass="contradictory directive blocked until clarification",
-        result_fail="contradictory directive not blocked until clarification",
+        result_pass="contradictory directive blocked until error",
+        result_fail="contradictory directive not blocked until error",
     )
 
 

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/02_llm_constraint_guardrail.py

@@ -173,7 +173,7 @@ def main() -> None:
     compacted_turns, compacted_state, compacted_prompt = compact_user_turns(user_inputs)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}"
+        compact_output = f"[no call] error required: {compacted_prompt}"
         print_model_output("Compiler-mediated + compact", compact_output)
         compact_refusal = True
         compact_violation = False

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/03_llm_premise_guardrail.py

@@ -108,7 +108,7 @@ def main() -> None:
     compacted_turns, compacted_state, compacted_prompt = compact_user_turns(user_inputs)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}"
+        compact_output = f"[no call] error required: {compacted_prompt}"
         print_model_output("Compiler-mediated + compact", compact_output)
     else:
         compact_messages = build_mediated_messages_from_transcript(compacted_state, compacted_turns)

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/04_llm_tool_denylist_guardrail.py

@@ -124,7 +124,7 @@ def main() -> None:
     compacted_turns, compacted_state, compacted_prompt = compact_user_turns(user_inputs)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}"
+        compact_output = f"[no call] error required: {compacted_prompt}"
         print_model_output("Compiler-mediated + compact", compact_output)
         compact_tool = None
     else:

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/05_llm_prompt_drift_vs_state.py

@@ -254,7 +254,7 @@ def _run_demo(turns: int = _DEFAULT_TURNS) -> None:
     compacted_turns, compacted_state, compacted_prompt = compact_user_turns(user_inputs)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}"
+        compact_output = f"[no call] error required: {compacted_prompt}"
         print_model_output("Compiler-mediated + compact", compact_output)
     else:
         premise_value = compacted_state["premise"]

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/06_llm_context_compaction.py

@@ -1,6 +1,6 @@
 """Demo 6: host-side prompt replacement from authoritative step-derived state."""
 
-from context_compiler import create_engine
+from context_compiler import DECISION_UPDATE, create_engine
 from demos.common import compact_user_turns, is_verbose, print_info_report
 
 DEMO_NAME = "06_context_compaction — superseded directives eliminated"
@@ -43,7 +43,7 @@ def _compile_premise(turns: list[str]) -> str:
     engine = create_engine()
     for turn in turns:
         decision = engine.step(turn)
-        assert decision["kind"] == "update"
+        assert decision["kind"] == DECISION_UPDATE
     compiled_premise = engine.premise
     assert compiled_premise is not None
     return compiled_premise

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/07_llm_prompt_vs_state.py

@@ -139,7 +139,7 @@ def main() -> None:
     compacted_inputs, compacted_state, compacted_prompt = compact_user_turns(USER_INPUTS)
     if compacted_prompt is not None:
         print_messages("compiler-mediated + compact", [])
-        compact_output = f"[no call] clarification required: {compacted_prompt}"
+        compact_output = f"[no call] error required: {compacted_prompt}"
         print_model_output("Compiler-mediated + compact", compact_output)
     else:
         compact_messages = build_compact_compiler_messages(compacted_state, compacted_inputs)

{context_compiler-0.9.0.dev3 → context_compiler-0.9.0.dev4}/demos/08_llm_replacement_precondition.py

@@ -1,6 +1,6 @@
 """Demo 8: missing-source replacement applies deterministically from authoritative state."""
 
-from context_compiler import DECISION_UPDATE, State, create_engine
+from context_compiler import State, create_engine, is_update
 from demos.common import (
     build_baseline_messages,
     build_reinjected_messages,
@@ -35,7 +35,7 @@ def main() -> None:
         [
             (
                 "Analyze this input as state transition logic: 'use podman instead of docker'. "
-                "First line must be ACTION:<clarify|proceed>."
+                "First line must be ACTION:<error|proceed>."
             )
         ],
         baseline_system_prompt=(
@@ -50,7 +50,7 @@ def main() -> None:
         [
             (
                 "Analyze this input as state transition logic: 'use podman instead of docker'. "
-                "First line must be ACTION:<clarify|proceed>."
+                "First line must be ACTION:<error|proceed>."
             )
         ],
         premise=None,
@@ -61,7 +61,7 @@ def main() -> None:
     reinjected_output = complete_messages(reinjected_messages)
     print_model_output("Reinjected-state", reinjected_output)
 
-    if decision["kind"] == DECISION_UPDATE:
+    if is_update(decision):
         print_messages("compiler-mediated (full)", [])
         mediated_output = "[no call] authoritative state applied deterministic replacement update"
         print_model_output("Compiler-mediated (full)", mediated_output)
@@ -77,7 +77,7 @@ def main() -> None:
         print_model_output("Compiler-mediated + compact", compact_output)
     else:
         print_messages("compiler-mediated + compact", [])
-        compact_output = "[no call] unexpected clarify was produced during compaction"
+        compact_output = "[no call] unexpected error was produced during compaction"
         print_model_output("Compiler-mediated + compact", compact_output)
 
     state_applied = not _is_initial_authoritative_state(engine.state)
@@ -86,7 +86,7 @@ def main() -> None:
 
     baseline_has_authoritative_precondition = False
     reinjected_has_authoritative_precondition = False
-    compiler_pass = decision["kind"] == DECISION_UPDATE and state_applied
+    compiler_pass = is_update(decision) and state_applied
     compact_pass = compacted_prompt is None and compact_state_applied and compact_no_pending
 
     print_host_check(
@@ -101,7 +101,7 @@ def main() -> None:
     )
     print_host_check(
         "COMPILER_BLOCKED_INVALID_REPLACEMENT",
-        yes_no(decision["kind"] == DECISION_UPDATE),
+        yes_no(is_update(decision)),
         context="compiler-mediated",
     )
     print_host_check(