Repository navigation
docs(blog): rework "Building a Voice Agent That Knows" as a reference architecture - #224
Merged
Merged
Conversation
… architecture Rewrite the voice agent post around the live knowledge graph as the thing the cascade orchestrates around. Every model stays (VAD, STT, intent model, LLM, TTS); InputLayer holds runtime data, session goals, rules, tool policies and work state. The post specifies the demo-ready architecture: observation adapters with guarded replacement, the intent write gate, the rule pack (claims, speech, work, eligibility), standing-query delivery, atomic programs and the .require guard extension, the speech owner with a playback state machine and receipts, multitasking dispatch with leases, idempotency keys and reconciliation, failure semantics, and a fault suite. The complete pack is an appendix and was executed on the engine; the state transitions are its output. Benchmark numbers are quoted exactly. Add five SVG figures under front/public/blog/voice-agent/ and an inline SVG renderer (front/components/inline-svg.tsx, wired as the img override in mdx-components.tsx) so figures follow the site theme and open full size. Regenerate the content bundle.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reworks the published post Building a Voice Agent That Knows into a reference architecture for the voice cascade around the live knowledge graph. Every model stays in the cascade (VAD, STT, intent model, LLM, TTS). InputLayer is what the cascade orchestrates around: runtime data, knowledge and workflows embedded in the agent; tool calls and their policies modelled as facts and rules; general rules and guardrails enforced deterministically with provenance; a clean cascade that enables multitasking dispatch.
The article specifies the demo-ready target architecture end to end, with invariants and failure semantics per hop:
run_ok, cancellation and reconciliation;inserted/retracted,seq,revision,generation, streamed deltas, reset), recovery, and the registration race;.requireguard as a stated target extension;Appendix A is the complete pack; it was executed on an engine built from this branch (rebased on main), and Appendix B is that run step by step.
Figures
Five SVG figures under
front/public/blog/voice-agent/(cascade as one pipeline with both lanes and an edge legend, data versus control flow, the fact/rule/subscription loop, the mid-utterance correction timeline, the dispatch sequence). They are theme-aware:front/components/inline-svg.tsxinlines same-origin SVG figures so the site's CSS variables apply, scoped per figure, with a link to the full-size file; it is wired as theimgoverride infront/components/mdx-components.tsx. Standalone fallbacks followprefers-color-scheme.Review process
Author and challenger iterated through four rounds (47 numbered challenges with engine-run counterexamples) until the challenger signed off: every technical claim checked against the inputlayer and voicestack sources, every IQL block and guard shape executed on an engine, wording consistent.
Validation
make front-buildpasses; the built page renders the five figures inlined with the site theme and no image fallbacks.