v1.17.4 — docs: add AtomS3R + atoms3r-http-bridge to architecture diagrams#57
Merged
Conversation
The high-level flow and sequence timeline diagrams previously only showed the Frontend UI as the operator-facing client. AtomS3R is now a first-class hardware face (3D LCD render + Echo speaker + PTT mic) but was invisible in the architecture docs, which created a gap between the README prose and the diagrams. - high-level-flow.mmd / .svg / .png: add `AtomS3R Device` and `atoms3r-http-bridge` nodes. AtomS3R uplink (mic WAV → `/api/operator/asr` and `operator_response` → `/api/operator/response`) goes direct to face-app over HTTP, in parallel with the Frontend UI's uplinks. Downlink (face / TTS payloads and audio) fans out through the bridge to AtomS3R's `/api/headroom/payload` and `/api/headroom/audio` endpoints. - sequence-timeline.mmd / .svg / .png: add Input path D (AtomS3R PTT) alongside paths A/B/C, and add the bridge fan-out for face/tts payloads in the output section. - README.md: keep English and Japanese inline `mermaid` blocks in sync with the .mmd sources (4 blocks total). - Fallback exports re-rendered at `--width 2400 --scale 2` so the static PNGs stay legible at higher zoom levels. AtomS3R's face is described as 2D throughout (the LCD-rendered animated face is 2D); the existing "3D face" references for the Frontend UI are unchanged because the browser-side face is genuinely 3D. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Patch release for the architecture diagram update (AtomS3R added). Six sites move together: package.json, mcp-server/dist/index.js SERVER_VERSION, tts-worker/pyproject.toml, asr-worker/pyproject.toml, and both uv.lock files (refreshed via `uv lock`). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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
AtomS3R Device(2D face LCD + Echo speaker + PTT mic) andatoms3r-http-bridgenodes to both diagrams. AtomS3R uplinks (mic WAV / operator_response) go direct to face-app HTTP; downlinks (face / TTS payloads + audio) fan out through the bridge to/api/headroom/{payload,audio}.mermaidblocks kept in sync with the.mmdsources (4 blocks updated).--width 2400 --scale 2so the static images stay legible.Test plan
npx mmdc -i high-level-flow.mmd -o high-level-flow.svg(and .png) succeedednpx mmdc -i sequence-timeline.mmd -o sequence-timeline.svg(and .png) succeededAtomS3Randatoms3r-http-bridgetext nodes🤖 Generated with Claude Code