Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

feat(presets): read the state field a question set uses out of its own instructions

Aashish6c8817af6653
diff --git a/laya/presets.py b/laya/presets.py
index ea2efd38..90c855bd 100644
--- a/laya/presets.py
+++ b/laya/presets.py
@@ -1,6 +1,29 @@
"""Ready-to-use question presets for common production decision workflows."""
+import re
from typing import Dict, Optional
+# A preset says which part of the state it reads by naming it in backticks: "What does the
+# customer want in `message`?". That convention is what `state_field` below depends on, and it is
+# the reason no table of preset -> key has to be kept in step by hand.
+_STATE_FIELD_RE = re.compile(r"`(\w+)`")
+
+
+def state_field(questions: Dict) -> Optional[str]:
+ """The state key ``questions`` reads, or ``None`` when that is not exactly one key.
+
+ Every built-in preset names a single field -- `message`, `body`, `prompt`, `post`, `request` --
+ and a caller that puts its text under a different key is asking the model about a field that is
+ not in the state. Surfacing the name lets a caller place the text correctly instead of guessing.
+ ``None`` covers both "names nothing" and "names several", because then only the caller knows
+ which field the request belongs in.
+ """
+ named = {match
+ for spec in questions.values()
+ for match in _STATE_FIELD_RE.findall(spec.get("instructions") or "")}
+ if len(named) != 1:
+ return None
+ return next(iter(named))
+
def triage_questions() -> Dict:
"""Preset questions for customer support ticket triage."""