Repository navigation
docs(devbook): specify meeting recording on a phone note - #1710
Merged
github-actions[bot] merged 1 commit intoNov 10, 2026
Conversation
Meeting recording sub-feature, the requirements for recordings on a note, the Meeting Recording runtime sequence, ADR 0048 (AAC in an ADTS stream, 16 kHz mono, 32 kbps) and the Android MediaRecorder tech chapter. Plan +meeting-recording, entry spec-recording (90bc0d51-e8f6-4272-a0e1-a856fa33a047). Co-Authored-By: Claude Opus 5.5 <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
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.
What changed
The recording half of the meeting-recording design (artifact), written into the devbook through
delivery:flow-spec. Plan+meeting-recording, entryspec-recording(90bc0d51-e8f6-4272-a0e1-a856fa33a047)..devbook/domain/capture/features.md### Meeting recordingsub-feature after Talk note, plus a pointer from Talk note.devbook/domain/inbox/requirements.md## Recordings on a note: 6 SHALL requirements, 8 scenarios.devbook/arc42/06-runtime-view.md## Meeting Recordingsequence, reusing the staged note-file upload.devbook/arc42/adr/0048-meeting-audio-is-recorded-as-aac-in-an-adts-stream.mdadr/README.md.devbook/tech/mobile.md,technology-graph.md## Android MediaRecorderchapter (with the microphone foreground service) and its graph nodeAcceptance criteria
capture/features.md#meeting-recordinginbox/requirements.md#recordings-on-a-note06-runtime-view.md#meeting-recordingpoints at Talk Note Upload and Mobile Note Synctech/mobile.mdentry forMediaRecorderand a microphone foreground servicemobile.md#android-mediarecordernode .devbook/_tools/devbook-meta/build.mjs --checkexit 0;node tools/devbook/check-metadata.mjs0 blocking, 651 advisory (unchanged from base)Build & Test
Devbook-only change: no build or test suite applies. The two devbook checks above pass. No application was started.
Review findings left open
None. An independent
architecture:architectreview found 1 blocker (Mermaid's reservednoteas a participant id), 3 major (unbuilt sync types stated as present fact; talk note used for a meeting) and 5 minor; all nine are fixed in this commit.What could not be proved
adoptedon Android MediaRecorder rests on its use by cloud dictation (AndroidAudioRecorder); the meeting recorder andRecordingServiceare not built. Validate that one chapter with one rating fits, or split it.proposed: accepting it is this gate's decision.Assumptions
###sub-feature placed right after Talk note, not a####under it: no features file in the repo nests a sub-feature, and the entry's "under" is read as "beside, extending".## Recordings on a noteand lives in the Inbox context as the entry says, pointing at the Capture sub-feature throughrelated.audio/x-m4ais accepted besideaudio/aacandaudio/mp4, asSyncTranscriptionLimitsalready does.Opened by an unattended
execute-planrun; Personal Validation is pending on this draft.🤖 Generated with Claude Code