Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Separate handler, speech, terminal, and delivery evidence
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Characterization tests for conversational runtimes should keep handler state, speech queueing, terminal-action intent, accepted output audio, and remote delivery or disconnect as separate evidence layers. Queue success is not playout, an end-action object is not an executed disconnect, and downstream acceptance is not proof a caller heard the audio. Pin source and runtime versions, reuse narrow tests, and exercise only runtime-valid paths. Once a terminal node removes functions and installs an end action, directly invoking a later handler bypasses availability and is not end-to-end evidence. Report each layer separately and keep desired UX policy distinct from observed behavior. Local deterministic characterization cannot establish carrier or media delivery; that requires an instrumented integration or real-call observation.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review