Specification change history

2026-11-07 — Qt server user invitations (D-226)

SPEC-005 0.214, SPEC-008 0.33 and SPEC-022 record the requested saved-server context-menu action for new local and existing local/foreign accounts, with propagating server membership, owner authority and retained denial/inheritance boundaries. The channel-only workflow remains available.
Source80 and both overlays are published with the complete native gate, focused sanitizer checks, offline source staging and independent empty-cache digests of all 63 distfiles. Ordinary upgrades select alpha80 over installed alpha79. The combined website preserves five current alpha79 client manifests and keeps source80 as the sole archived source entry. Control and website evidence is in the release review.

2026-11-07 — native event hints source release (D-221)

Published Gentoo source alpha79 with the required Qt WebSockets dependency, complete local native Release qualification, instrumented hint units, offline source staging, both-overlay fresh-cache digests and normal upgrade selection. Website configured allocation and all 35 sampled invocations use the target version, including ten persistent-directory executions. Control/media performance rollout remains separate and pending. See the release record.

2026-11-07 — native Qt chat scroll retention (D-225)

SPEC-005 0.212 records the explicit human request: follow arriving messages only when already at bottom; preserve the existing above-bottom position. Restore after final native tree layout, including outgoing rows, without deferred scrolling or a new preference.
Published isolated Gentoo source alpha77 on alpha76, retaining its composer shortcuts and alpha75’s PTT changes. Release/sanitizer, frozen-source, 200% scale, offline package, both-overlay fresh-cache and normal upgrade checks pass. Download-site configured allocation and all 16 sampled invocations are on the target version. See the release record.

2026-11-07 — native composer Enter/Shift+Enter (D-223)

Human clarification selects Enter to send and Shift+Enter for a newline. SPEC-005 revision 0.210 records native ordinary/direct/group and inline-reply scope, fixed configuration, actual-widget coverage and acceptance conditions.
Alpha76 follows alpha75 and contains only the keyboard fix and regressions atop its verified immutable source. Frozen-package UI/message-view, working-tree Release/sanitizer, offline Portage, both-overlay fresh-cache/digest and normal upgrade checks pass. The download site has 100% configured allocation and 12/12 target-version sampled Worker invocations, with public source and persistent directory checks. Installation remains a human action. See the release record.

2026-11-07 — ten-minute PTT duration (D-222)

Raise the default and ceiling to 600 seconds across server validation, web settings and native capture/settings. R-101 and SPEC-004/005/008/012 describe the accepted scope. A one-time transaction raises saved server/channel/conversation limits, preserves inheritance and unrelated state, and advances affected revisions. Subsequent authorized shorter limits survive restart.
Release alpha75 is isolated from unrelated working-tree changes: web/control inputs are recovered from the live source maps; native source is based on the checksum-verified alpha74 archive. Both hosted services and the source download are deployed under D-159. Both Gentoo overlays publish alpha75 after public verification and pass fresh-cache fetch/digest and normal upgrade selection. Installation remains a human action. See the release record.

2026-11-07 — WebSocket change hints (D-221; implemented locally, not deployed)

D-221 records the human's selection of WebSocket change hints with authenticated canonical synchronization and polling fallback. New SPEC-027 0.1 defines event-hints/1: single-use 30-second hashed tickets carried only in Sec-WebSocket-Protocol, content-free sync/inbox hints, bounded watch frames for the active view, close codes and the privacy rule that hidden, private, unjoined and non-participant activity produces no frame. Paths, limits and timings are D-024 engineering selections.
SPEC-008 0.31 adds storage-boundary post-commit capture (observeSql, staged-length savepoints), per-account batched readability, revocation-first evaluation, coalescing/spacing/backpressure, pacing under the unchanged 240/min api: bucket, Worker hibernation and Node ws adapters. SPEC-005 0.209 adds the shared client state machine, socket registry, HintedPoll scheduling (unchanged two-second fallback, 1 s spacing, 15 hint reads per loop per minute, 429 throttling) and the iOS native broker. SPEC-002/009/015/018 gain cross-references and privacy notes.
Validation and limits: server, Node, Service, client, budget and iOS bridge tests and a real workerd check pass locally; eviction/hibernation wake, hosted rollout, iOS/Android device qualification and the native Qt increment remain outstanding. Evidence: reports/server-performance-council/websocket-*.
Security council R2 fixes (SPEC-008 event-hint capture; no wire, configuration or SPEC-027 contract change): Sql.run may return the adapter's changed-row count (Node changes, Durable Object rowsWritten via the new shared server/durable-sql.ts), and observeSql stages nothing for a proven no-op write, so the per-request no-op prune no longer rechecks every socket; adapters without a count stay conservative. Channel deletion captures prior readers inside its transaction so a formerly readable but unwatched deleted room still receives the structural sync SPEC-027 promises; thread retirement needs no capture. Evidence: reports/server-performance-council/r2-noop-capture-fix.{json,md}.

2026-11-07 — council server performance increment (engineering; not deployed)

Engineering-only SPEC-008 amendment under existing behaviour: indexed thread liveness/eligibility with a single voice read and batched enforcement retirement; exact UTF-8 retained-quota accounting via octet_length over a covering index with single canonicalization (restores SPEC-006's byte limit; the prior character count could accept sends past 64 MiB); independent enforcement/direct/SFU delivery lanes with unguarded adapter triggers and a bounded alarm wait anchored at alarm start; warm-object caller TURN issuance alongside warming with the final physical health check retained after issuance.
Redundant indexes messages_reply_root and messages_bytes are created idempotently after migrations without a schema marker change; D-217 copies reproduce or rebuild them. No configuration, diagnostic field, protocol or scheduling contract changes. Evidence: reports/server-performance-council/.

2026-11-07 — native lease retry budget (D-220; deployed)

Human accepted Wrangler >=4.158.0 and a two-second retry budget on the native media /lease Durable Object stub, retaining the default retry count and duplicate suppression. SPEC-008 owns the fixed policy; other operations, initial attempts and authority deadlines retain their contracts.
Pinned Wrangler 4.158.0 and Workers types 5.20261107.1; isolated workerd checks cover lease-only routing, unchanged body/placement, a >2-second initial attempt and no repeated mutation after abort/application failure/HTTP 500. Relay units reject signed grants at exact expiry without Container forwarding.
After disclosure of the missing distributed pre-dispatch timing evidence, the human explicitly requested deployment. Both media gateways now have 100% configured allocation and 10/10 target-version tagged invocations each, including four Durable Object executions each. Exact uploaded bytes, retained settings, healthy endpoints and safe synthetic/expired-grant rejection pass. Container applications and image are unchanged. Distributed retry timing remains unverified; no latency or cost saving is claimed. See deployment evidence.

2026-11-06 — Qt saved visitor recovery

The human requests automatic re-sign-in for retained foreign servers and an error only after that attempt fails. SPEC-005 adds bounded ordinary saved-server opening recovery, preserving pinned authorities, drafts, pending-command safeguards, explicit sign-out and independent voice. Advisory account-status reads now wait for runtime startup. Private conversation recovery remains explicit.

2026-11-06 — Mobile adaptation of selected B, implementation in progress

The human requests council refinement of the Electron UI for mobile and a new internal iOS TestFlight build. SPEC-005 retains the approved D-161/D-163 mobile navigation while adapting B topic settings and retained detail pages, and documents mobile touch/scroll rules. D-219 records the human’s later selection of persistent actual-call context in the bottom bar and continuously visible enabled statistics; SPEC-005 0.208 and the question register reflect those answers. Chromium bridge-profile evidence is separate from native, signed-delivery and physical background-call acceptance. No TestFlight delivery is claimed.

2026-11-05 — Control and media servers moved to North America (D-217)

The human asks to deploy the North American media relays for both servers, to move the control servers as well, and to prefer Canada wherever the option exists. Cloudflare offers no Canada-specific placement for Durable Objects, Containers or R2, so the moved components use us. SPEC-002 0.10 adds CONTROL_MIGRATION_SOURCE and a resumable, digest-verified copy from the inactive EU control object; inactive objects no longer build the service or write. The EU source is retained for rollback. The website, R2 downloads and shortcut directory remain in the EU.

Deployment follow-up: the first chat attempt failed because Durable Objects kept the previous version for 300 seconds, and chat was rolled back (unavailable 18:47:32–18:55:38 UTC, no data lost). SPEC-002 now requires immediate code updates for placement changes and discards generated-only target state. Both control servers then moved with 8 s and 2 s interruptions; both media relays use us.

2026-11-05 — North American placement permitted (D-216)

The human asks to relax the EU hosting requirement so North American clients reach servers with lower latency. D-216 supersedes D-040's EU-before-US order. SPEC-002 0.9 makes the media Worker's DATA_JURISDICTION required as eu or us, with the Container constraint and object jurisdiction matching it; unrestricted media placement remains rejected. Control DATA_JURISDICTION keeps eu, us or omission. Existing EU control objects, R2 downloads and shortcut records stay in place until a migration is specified. SPEC-008 0.29, SPEC-004, SPEC-024, Q-23 and the deployment guide follow. The live media relay move followed under D-217.

2026-11-05 — Selected B Electron/shared-web testing alpha (D-215)

The human selects topic-based B, excludes C and requests alpha73 build/deployment with accumulated refinements. SPEC-005 0.206 confirms category/privacy placement, independent save scopes, retained-form detail navigation and constrained persistent core/base-state presentation. Native Qt and existing authority/media policy remain separate. Alpha73 is deployed to both testing services: full build/unit/browser and focused UI/media checks pass, both have 100% configured allocation and 7/7 target-version tagged samples including live Durable Objects, and compatible native/Gentoo alpha72 verifies unchanged. This testing release does not declare the highest-reference council gate achieved. See the release record.

2026-11-04 — Native voice output scheduling recovery

SPEC-005 0.205 and SPEC-021 0.10 restore bounded playback recovery instead of ending a valid native call on an output timeline gap, and retain safe startup-stage/failure and resynchronization evidence under D-099. The exact reported scheduler notice is reproduced by a delayed output callback. Release core, focused ASan/UBSan, encrypted-call, offline source image and both-overlay/public-fetch/upgrade checks pass. Gentoo alpha.71 is published; the website has 100% configured allocation and 20/20 target-version sampled Worker invocations. Installation remains separate, and the original machine's cause for the timeline gap is unmeasured. See the release record.

2026-11-04 — Full-width native conversation (D-214)

SPEC-005 0.203 replaces D-213's centred character measure and surplus side gutters with the full available heading/transcript/composer width and ordinary native style margins, following the human's explicit request. Window/splitter/font/direction regression coverage and Gentoo source alpha.69 qualification/publication are recorded in the release record. Grouped call state, complete message information, native styling and protected ownership retain their accepted contracts.

2026-11-04 — Selected B surface continuity and session summary (D-211/D-213)

SPEC-005 0.202 refines the selected B presentation with a continuous native Base conversation surface, a distinguishable Window input band and native separator, and a naturally wrapping call-identity/microphone summary above the unchanged commands. Reading measure, desktop font sizes, complete identities, accepted fields, independent action ownership and adjacent statistics remain unchanged. Caller-shaped screenshot data and a retained preformatted fallback distinguish representative presentation from synthetic fixture limitations; enlarged-font/short-height limits remain recorded separately. No new preference or interaction policy is selected.

2026-11-04 — Selected B reading workspace and coherent session grouping (D-213)

SPEC-005 0.201 records the human's selection of B and D's useful grouping principle. Permanent navigation and tabs remain; heading, transcript and composer share a desktop-relative reading measure, and complete call context, microphone state and related commands form one bottom session area. Full identities, accepted fields, native selection/style, protected drafts, independent call ownership and statistics remain authoritative. Separate bundled visibility/style proposals remain unselected. The council now runs all five personalities on all three models; earlier rounds retain their actual membership.

2026-11-04 — Qualified identities from native caller data (D-211/D-212)

SPEC-005 0.200 clarifies that native sender headings and complete parent references compose the caller’s literal nickname/address label with structured author username/domain. The live caller provides a nickname rather than a preformatted heading; the transcript now preserves the required qualified address in both visible headings and parent inspection/accessibility. Punctuation in display names remains literal. An observed failing widget regression uses that caller-shaped data; compact-heading and neutral-field alternatives remain unselected.

2026-11-04 — Readable native message inspection (D-206/D-211)

SPEC-005 0.199 clarifies the existing readable/selectable identity-information contract. Native inspection displays complete canonical identity, datetime, signed parent and provenance as plain selectable text with normal readable ink, wrapping within a font-relative measure bounded by the display. Essential information no longer inherits the faint disabled-command palette. Actual Copy/Reply/Voice/Pin actions retain their existing permission and command paths; compact-heading/neutral-field alternatives remain unselected prototypes.

2026-11-04 — Expanded UI comparison and four design variants (D-211)

SPEC-005 0.198 records the human’s addition of Trillian Messenger, Microsoft Teams, Webex, Slack and Zoom to the retained reference pool and explicit invitation to explore substantial UI rearrangement. Keep at most four active variants; material specification alternatives remain proposed while evaluation/refinement continues across rounds. The implementation refinement carries semantic navigation fields through indentation, retains native disclosure controls, reflows exact-parent captions beside metadata when they fit, constrains long voice-status labels to the actual wrapping-row width and retires focus callbacks before widget teardown. Historical calibration 4 remains below target (Claude 6.6, Sol 7.4, Astra 7.4); its exact-source qualification remains separate from later work.

2026-11-04 — Compact native conversation flow (D-211)

SPEC-005 0.197 refines the existing presentation with a desktop-relative conversation title, content-sized main/inline composers, one wrapping voice-status/action row and a quiet one-pixel thread edge. Compact parent captions retain the actual signed target; full qualified parent identity stays in inspection, Copy details, tooltips and accessibility text, while complete sender addresses remain visible. Calibration 3 remains below target (Claude 6.0, Sol 7.4, Astra 7.0). Exact archived 25e9438 project and isolated HTTPS checks are recorded separately from this new candidate. No new navigation, permission, preference or media action is introduced.

SPEC-005 0.196 refines the approved native presentation with continuous semantic navigation fields, first-line avatar clearance, compact complete presence, parent metadata bands, secondary qualified identities and centred date separators. Sign-in notice controls attach only during Expiring/Expired so hidden renewal buttons do not reserve footer height; generated HTTPS captures and lifecycle regressions preserve authority and drafts. Calibration 2 remains below target (Claude 6.4, Sol 7.0). The preceding candidate’s complete release/sanitizer matrices and exact PR project check are recorded separately. The human re-adds Astra for subsequent council rounds and caps reasoning at extra high.

2026-11-04 — Lighter native fields and identity hierarchy (D-212)

SPEC-005 0.195 records the human-selected lighter-fields render: 18% of the previous reference tint over 82% desktop Base, a quieter sender band, and bold names with complete secondary qualified addresses. Measurement and painting retain the same formatted metrics; identities and signed parent references remain available. This supersedes the former final D-206 field blend only within the native presentation. No preference, authority or navigation behavior changes.

Centre inline channel names, access badges and handsets within a compact shared row; keep reply-parent metadata visually secondary with checked contrast and breathing room; prefer complete address segment breaks. Native navigation, full references, desktop fonts, approved field colours and independent call/draft behavior retain their existing contracts. Round 3 is retained at Claude Opus 8.5/10 and GPT Sol 9/10; comparative ratings remain pending.

SPEC-005 0.194 records the human’s extension of the UI council process: after the current round, use neutral screenshot IDs to compare the named communication/settings interfaces and professionally recognized Internet references, with provenance held separately. SloppyVoice must reach at least 9/10 from both members and rank highest in that comparison. The shared rubric and actual scores remain independent; this adds a review gate without product behavior, palette or authority changes.

2026-11-04 — UI council enlarged-font corrections (D-211)

SPEC-005 0.193 adds concrete enlarged-font navigation and inspection-spacing regressions after round 2 identified clipping. Channel names, access labels and handsets share an adaptive row; qualified presence addresses use matching measurement/painting rules, and timestamp spacing follows the actual inspection control. These restore D-207/D-206 within the existing D-211 presentation scope. The 7/10 Claude and 8/10 Sol reviews remain recorded; subsequent scores require fresh independent reviews.

2026-11-04 — Native-first UI polish overhaul (D-211)

SPEC-005 0.192 records the human's request for a native-first UI overhaul, a new PR and iterative independent before/after council scores of at least 9/10. The human subsequently limits the council to Claude Opus and GPT Sol. The presentation profile retains native desktop integration, two-root tabbed navigation, muted conversation fields, semantic navigation colours and independent call/statistics contracts, while refining spacing, grouping, metadata reflow, readable initials/placeholders and passive empty-state guidance. No new permission, preference or media operation is introduced.

2026-11-04 — Visitor request rate-bucket fix

SPEC-008 0.28 records the regression scenario for a defect that made every authenticated visitor request on the Cloudflare host return HTTP 500 before device-proof validation. The alpha.66 account-wide rate rollout summed older device-specific buckets with id LIKE 'visitor-request:<uuid>:%'. That 54-byte pattern exceeds the 50-byte LIKE limit of Durable Object SQLite; local api:<uuid>:% patterns (42 bytes) were unaffected, and Node SQLite tests did not enforce the limit. The query now selects the same key: prefix as a binary range. No behaviour, limit or protocol change: this restores SPEC-006's 240 requests per account per minute and SPEC-015's visitor request handling.

2026-11-03 — Most-recent-build-only downloads during alpha (D-210)

SPEC-002 0.8 and SPEC-005 0.191 record the human's request to keep only the most recent build available on the website while releases are alpha. The download allowlist keeps each platform's current package and the current Gentoo source archive; older versioned URLs return 404, and their R2 objects remain privately stored. Both Gentoo overlays keep only the current ebuild. Supersedes D-063 retention and D-184 ebuild preservation until releases leave alpha.

2026-11-03 — In-application bug reports (D-209)

New SPEC-026 0.1 records the requested Report a bug function: an authenticated POST /api/bug-reports creates a public issue in megaschlong/sloppy-voice through a server-held fine-grained token, advertised as bug-reports/1; servers without it lead clients to a prefilled GitHub new-issue page. SPEC-005 0.189 adds the shared-interface workspace and Qt Help dialog; SPEC-008 0.27 adds server posting, limits and logging. Limits, defaults and presentation are PROPOSED pending the human's confirmation. Direct posting stays disabled until the token secret is provisioned.

2026-11-03 — Native managed RTP source identification

SPEC-005 clarifies that each publisher RTP source is identified before capture begins, with distinct nonzero SSRCs matching its packetizer. This corrects an offer/caps timing race without changing capture, no-audience pauses or authority. Repeated-offer, composed release/sanitizer, frame-interoperability and Gentoo alpha64-r1 package checks pass; authorized generated Cloudflare run 22 now passes production Chromium/Firefox video/sound with confirmed new-track cleanup. The actual desktop/account retry remains separate. See the correction record.

2026-11-02 — Native server statistics grouping and distinct headings (D-203)

SPEC-005 0.182 preserves client metric order while grouping owner server totals as RTT, voice RTT, upload, download, jitter and loss. Separate bold desktop-foreground Client/Server headings and extra section spacing distinguish local measurements from aggregates while preserving category colours, accessible output and compact wrapping. Gentoo source alpha61 contains this presentation change; independent binary/Flatpak releases retain alpha.57. See the release evidence.

2026-11-02 — Gentoo source packages (D-202)

2026-11-02: SPEC-005 0.181 / D-202 switches new Gentoo packages to source compilation with offline CMake/Cargo builds, immutable source/crate fetches, system PipeWire GStreamer support and existing overlay/version/installation boundaries.

2026-11-02 — Native statistics colour and spacing (D-201)

SPEC-005 0.180 records category colours, horizontal gaps and quiet separators for native status statistics, emphasized values and retained labels/units and accessible plain descriptions. Accents adapt to desktop palette changes with readable contrast; rendered styled text still wraps and shrinks at actual width. Measurement, owner authorization, cadence and always-visible presentation are retained. Alpha.57 archive/Flatpak publication follows host release/sanitizer core and affected integration, Qt 6.10/6.11 UI/status and installed-package qualification. Coordinated D-202 source-Gentoo alpha58 contains the exact final statistics source; see the release evidence.

SPEC-005 0.179 and SPEC-021 0.8 record single-click prepared channel-tab opening/reuse, always-visible native statistics, content-sized status-bar height with shrinkage, and removal of the statistics checkbox and status-bar Conversations button. Retain legacy preference metadata, unread tree/tab indicators, the Direct Messages context-menu summary and independent voice. Alpha.56 is published after complete release and composed sanitizer qualification, Qt 6.10/6.11 UI/status checks, immutable public package hashes, both Gentoo overlay checks and separate configured/observed website rollout verification. See the release evidence, including retained fixture failures and final layout rechecks.

SPEC-005 0.178 records the requested bottom status-bar statistics, with inline local/voice and owner-only aggregates and narrow-window wrapping. Native login finalizes its account generation before trust notifications can start prepared workspace reads. The primary account action and fresh startup expose qualified Home selection. Generated startup/channel/DM and status-layout regressions reproduce the earlier failures and validate the corrections. Alpha.55 is published after complete release/sanitizer qualification, public hashes, both Gentoo overlay checks and separately verified configured/observed website rollout; see the release evidence.

2026-11-02 — native Qt alpha.54 publication

The full SPEC-005 0.177 native replacement is published under D-195/D-196. Release/sanitizer core/HTTPS/codec and current media matrices, actual stripped archive/installed Flatpak Wayland and camera/plugin checks, scoped resource measurements and public package hashes pass. Both higher-version Gentoo ebuilds/launchers/DIST entries agree; fresh-cache real Portage fetch/digests/staged install and normal alpha51→alpha54 upgrade selection pass without a system merge. The website target has 100% configured allocation at 16:43:00 UTC and 11/11 target-version sampled invocations at 16:43:27 UTC; persistent directory and unchanged account-service checks pass. See the release record for measurement limits and separate physical/live-provider acceptance.

2026-11-02 — native runtime and package qualification

SPEC-005 revision 0.177 retains the accepted native behavior while completing distribution compatibility. The archive namespaces its focused GCC estimator’s internal GTypes so it can coexist with the full system RTP plugin; the Flatpak uses its compatible runtime estimator. Both packages carry only the small PipeWire GStreamer plugin needed for source-disconnection cleanup, sharing the PipeWire core. This avoids a host PipeWire USE change. A private per-application GStreamer registry avoids stale plugin blacklists across the transition. Both plugin load orders and generated QR pixels through the actual Flatpak portal proxy pass. Alpha.54 is the final candidate; preceding unpublished candidates remain immutable. Final qualification and publication/Portage delivery are pending.

2026-11-02 — native sandbox camera completion

SPEC-005 revision 0.176 completes the Qt Flatpak scanner through the XDG Camera portal without unrestricted devices. A generated QR traverses the actual private PipeWire camera path and decodes locally. Denial, cancellation, no pre-Start capture, foreground expiry and a separate stalled-helper process fuse are tested. A separate small camera library avoids linking the full account/audio runtime into the scanner. Alpha.52 remains an unpublished immutable candidate; alpha.53 stages the completed adapter. Final packaging/Portage delivery is still pending.

2026-11-02 — native journal, screen observation and final paint authority

SPEC-005 revisions 0.174–0.175 record the process-local diagnostic journal, modeless failure/export controls, complete-cycle renewal cadence and screen observation at the actual receive/decode/paint boundaries. A deterministic blocked-event-loop fixture reproduces the old expired-pixel repaint and verifies the paint-time deadline/authority gate. Generated relay failure and private Wayland archive/Flatpak staging checks pass; complete current-source qualification and immutable publication/Portage delivery remain pending.

2026-11-02 — original-room native public convenience trust

SPEC-005 revision 0.164 ports the existing opt-in public-mode trust contract through explicit verified room projections while preserving own-account/private strict trust and persistent root pins. Pure primitives/tests are unlinked development work; native presentation, join/text/pin/voice integration and qualification remain pending. Revision 0.163 passes its complete 47-suite release core/HTTPS/codec regression; its sanitizer counterpart is running.

2026-11-02 — native measured-connection foundation

SPEC-005 revision 0.163 ports the existing 32-context, 1000-sample, 30-second memory bound and 10-second measured-payload window with monotonic timing. Measurement files and deterministic tests are unlinked development work; reporting, preferences/status display, aggregate validation and composed qualification remain pending. The administration snapshot is undergoing a fresh complete release/sanitizer regression after correcting a visitor batch traffic assertion.

2026-11-02 — named native management preparation

SPEC-005 revision 0.162 binds tree management to the named retained account/connection without text selection, history loading, re-admission or credential replacement. Existing public discovery and sole connection ownership use a bounded cancellable preparation. The inactive-account/window fixture is building; the earlier owner visitor block/unblock fixture passes three release results and preserves Home credentials while refusing the revoked Host session after unblocking.

2026-11-02 — native administration completion

SPEC-005 revision 0.161 ports existing consequential confirmation, local replacement, visitor block, screen-policy inheritance/exception, service notice and public directory/shortcut workflows. The first four screen-policy form results pass, including conflict and edits during save. Composed original-service and sanitizer validation remain required; no native release or Portage upgrade is claimed.

2026-11-02 — original-Host native moderation

SPEC-005 revision 0.160 extends the existing native management owner to retained ordinary destination connections. Host-local role/admission and pinned Host capabilities control the native form; exact commands use the existing exclusive destination writer and retain their intent/text view across restart. No Home token, role or newly rejoined session can substitute. The generated lost-response/restart/401/form fixture is building; full replacement and Portage delivery remain incomplete.

2026-11-02 — call-bound native presentation composition

SPEC-005 revision 0.139 binds native portal selection, source layout, capture, compatible rendition encoding, application/PC sound mixing and publication to the original call/account/Host. Host acknowledgment/current authority precede publication; old epoch output is discarded and source/Stop cleanup preserves independent voice/text ownership. The preceding capture-mix units and real private-helper-to-Opus fixtures pass release and ASan/UBSan. The composed private portal/PipeWire/encrypted-relay fixture is being built; visible Share/source controls, managed RTP/SFU, full replacement and release/Portage delivery remain incomplete.

2026-11-02 — native common-clock capture mixing

SPEC-005 revision 0.138 ports the existing bounded PCM source queues, timestamp continuity, stereo clamp and native Opus music profile. Six units pass release/sanitizers, and the actual private C helper through native mixing and Opus decoding passes both builds. Managed RTP must consume raw mixed PCM directly. This does not establish application capture/publishing composition or the complete replacement.

2026-11-02 — native C audio-helper integration

SPEC-005 revision 0.137 retains the existing application/PC-output capture helper, explicit instance/serial source selection and own-process exclusions in a native Qt owner. The native helper has a fixed shorter heartbeat with conservative remaining-grant renewal; legacy builds preserve their existing timeout. First generated source/PCM/blocked-Qt tests pass, but expose diagnostic JSON and asynchronous process-retirement issues in the fixture/adapter; corrections and sanitizer validation are pending. No real audio source is selected. Capture/publishing composition, SFU, full replacement and native release/Portage delivery remain incomplete.

2026-11-02 — consented native PipeWire frame capture

SPEC-005 revision 0.136 applies existing consent, source, queue and native authority bounds to PipeWire composition and capture, with a sleeping independent expiry monitor and final Qt-delivery gate. Private synthetic-source validation and application integration are pending. The preceding encoder boundary passes release and ASan/UBSan VP8/VP9 generated encode/decode/lifetime tests. Hardware/physical capture, managed SFU, remaining workflows/migration and release/Portage delivery remain incomplete.

2026-11-02 — native raw-frame encoder boundary

SPEC-005 revision 0.135 applies existing SPEC-023/024 resource, codec, timing and recovery contracts to raw-frame encoding, including actual keyframe flags and cancellation of queued old output. Configuration probing is distinct from measured hardware use and capture/publication consent. Implementation and generated encode/decode qualification are pending. The preceding 0.134 consent/profile/viewer/receiver fixtures and changed encrypted-screen/audio sanitizer relay pass within their stated scope. Full replacement and release/Portage delivery remain incomplete.

SPEC-005 revision 0.134 applies the existing ScreenCast consent, bounded source/session lifecycle and SPEC-023/024 adaptation contracts to native components. Standard viewer controls move above the picture and wrap at narrow widths as already required. The standalone fake-portal probe passes, but its application integration, adaptive profile and UI changes require validation. Revision 0.133 passes the complete release and verified-sanitizer core/HTTPS/codec regressions; its final release relay run is finishing. Capture/encoding/SFU, remaining workflows/migration and native release/Portage delivery remain incomplete.

2026-11-02 — native stereo presentation sound

SPEC-005 revision 0.133 applies SPEC-023/024's existing stereo Opus, independent presentation timeline, bounded queues, final mute/gain/authority and ducking contracts to native playback and standard Listening controls. Worker lifetime and bounded Qt delivery are fixed engineering choices, with no capture permission or new setting. Audio validation is pending. The preceding encoded sender/publication and embedded encrypted-screen relay fixture pass focused release/sanitizer checks; full replacement and release/Portage delivery remain incomplete.

2026-11-02 — native presentation receiver and standard embedded viewer

SPEC-005 revision 0.132 applies the existing SPEC-023/024 authority, framing, timing, queue and Stop contracts to the immutable native call receiver and D-198 embedded Qt viewer. Focused viewer units pass release and ASan/UBSan; the first signed generated-VP8 receiver fixtures pass release. Call/data-channel integration is being compiled and requires additional relay/UI qualification. Presentation sound output, capture/publication, managed RTP/SFU, complete native replacement and release/Portage delivery remain incomplete.

2026-11-01 — native named-server Rejoin (implementation in progress)

SPEC-005 revision 0.102 binds the modeless Rejoin confirmation and fresh admission to the saved row’s exact account/server, preserving the outgoing view until checked atomic selection. Ordinary Open reuses admitted sessions; explicit Rejoin refreshes only its target. Owner-scoped completion/cancellation and protected pending-command checks retain existing authority and call rules. Validation is pending.

2026-11-01 — isolated serial native voice control

SPEC-005 revision 0.101 separates renewable Home voice requests from interactive traffic and limits control HTTP/1 pooling to one connection per host. Relay control has its own matching policy. Authority, TLS, pending limits, cancellation, media deadlines and fail-closed/manual-rejoin behavior are unchanged; no application retry is added. The seven-result generated HTTPS isolation fixture passes release and sanitizers, measuring nine exact control requests on one socket separately from six interactive sockets. All sixteen sanitizer core suites and twenty account/conversation/management scenarios pass. Corrected isolated release/sanitizer relay checks pass renewal, navigation, tab/recorder lifetimes, explicit movement and other-account sign-out during held PTT. The negative child-cleanup fixture returns promptly. The fresh complete release run passes all native suites, transport/account/interop/lifecycle/recovery/QR checks and all three relay fixtures, including held-input named sign-out. No native release is published. The protected unloaded-pending rejoin guard passes focused release and sanitizer checks.

2026-11-01 — native named-server sign-out (validation in progress)

SPEC-005 revision 0.100 resolves server-row sign-out through its exact retained account/connection without changing the selected view. Preparation is owner-bound, credentials/pending work remain scoped, and already dispatched logout commits only its own result. Validation is pending.

2026-11-01 — native closed-tab resources

SPEC-005 revision 0.99 requires protected drafts before closure, destruction of tab widgets/rendered transcripts, no background recreation, checked reopen and independent inbox/presence/call continuity. Closed-group draft cleanup belongs to the workspace model. All sixteen core suites and nineteen HTTPS scenarios pass both builds, and isolated release/sanitizer relay checks pass close/reopen with held PTT. The initial combined run reached that final fixture but used a direct-controller reopen that bypassed the workspace; its corrected isolated checks pass. Full replacement remains incomplete.

SPEC-005 revision 0.98 extends prepared selection to native direct/group opening and exact retained-operation account restoration. The prior view/draft stays usable until checked peer/authority/membership/history and protected atomic selection succeed. New contacts/invitations do not trigger admission/history. Tree/tab/invitation/new-contact callers share the path. All sixteen suites and nineteen HTTPS scenarios pass release and sanitizers; existing direct/group lifecycles pass both builds and the complete combined release run passes including all three relay fixtures. The independent sanitizer call-movement check also passes. Full replacement and publication remain incomplete.

2026-11-01 — modeless native binding recorders

SPEC-005 revision 0.97 replaces stack/blocking recorders with standard modeless Qt dialogs owned by their Preferences/account. Completed release updates only an unsaved candidate; focus, Preferences and account loss cancel the recorder and its observers. Account rebind cleanup uses direct dialog children so deleting a parent cannot leave stale descendant pointers in its deletion loop. Focused generated HTTPS/widget and private-portal relay checks pass, including ordinary Preferences continuity, recording pause and fresh input after cancellation. All sixteen core suites and both HTTPS/account batches pass release and sanitizers; isolated sanitizer call movement passes. The complete release run reproduces the recorded intermittent lease connection closure in the final call fixture, so it is not a complete pass.

2026-11-01 — native call-owned input lifecycle

SPEC-005 revision 0.96 binds saved shortcut restoration to the active call/account/attendance, releases idle observers and keeps lightweight lock/suspend monitoring for VAD calls. Recorder/setup lifetimes, cross-account edit guards and stale-failure fencing preserve fresh-input rules and ordinary settings continuity. Private-portal lifecycle tests and generated encrypted relay/window movement pass, including actual shortcut arming, held PTT across text selection/declined movement and fresh release after accepted movement. All sixteen release suites and the HTTPS account batches pass. All sixteen suites and both HTTPS batches also pass sanitizers. The complete release regression passes 165 interoperability cases, account/session/direct/six-mode recovery/QR flows and all three relay fixtures; the private-portal/native-window call-movement fixture also passes sanitizers. The earlier renewal-close issue remains recorded; no native package is published.

2026-11-01 — native destination account opening

SPEC-005 revision 0.95 keeps the chooser's destination server/channel independent of the original account's connection ID. Native server/channel account actions reuse the chosen profile's retained session or perform checked scoped admission, then publish only after verified state and atomic selection. Authentication is bound to its initiating owner; rejection cancels the captured continuation while an already dispatched successful login may retain its profile. All sixteen native suites and all seventeen scenario functions across two generated HTTPS realms pass sanitizers. The expanded fixture is isolated to retain ordinary production rate budgets. The complete release regression passes all sixteen native suites, both HTTPS batches, 165 interoperability cases, account/session/direct/six-mode recovery/QR flows and all three relay fixtures. The earlier intermittent renewal-close issue remains recorded. No native package is published.

2026-11-01 — all-account native saved-server projection

SPEC-005 revision 0.94 displays all retained ordinary server groups with one browsed qualified identity and routes another account's roots/channels through prepared selection. Projection uses a single metadata pass without loading accounts; unrelated DM updates retain the managed server branch. Context-menu Open resolves a retained qualified locator after tree-item replacement. All sixteen release suites and the seventeen-result real-HTTPS/window fixture pass. All sixteen native suites and seventeen HTTPS/window results also pass sanitizers. The complete release regression passes 165 interoperability cases, account/session/direct/six-mode recovery/QR flows and all three relay fixtures. The earlier intermittent renewal close remains recorded; no native package has been published.

2026-11-01 — native qualified-account discovery

SPEC-005 revision 0.93 uses public authority discovery for qualified account addresses and preserves delegated Home endpoints. Native profile shells retain the verified UUID/domain/base before authentication, without generating keys or selecting the profile; matching retained accounts keep their pinned authority and device keys. All sixteen core suites and the sixteen-result real-HTTPS/window fixture pass release and sanitizers. The complete release regression passes 165 interoperability cases and all three relay fixtures. An older no-channel assertion now counts only the target account, preserving legitimate outgoing-account polling. The intermittent renewal-close qualification issue remains recorded.

2026-11-01 — prepared native Home-channel selection

SPEC-005 revision 0.92 prepares ordinary Home tree/tab opens before a single protected room/cursor/selection commit. Fifteen HTTPS/window results pass release and sanitizers; the full sanitizer run also passes sixteen suites and all three relay fixtures. Two combined release runs encountered an intermittent HTTP renewal close in the final call-movement fixture, while isolated default-timeout reruns pass. The bounded generated fixture trace retains that unresolved qualification issue; no complete native release is claimed.

2026-11-01 — stable native account ownership

SPEC-005 revision 0.91 adds the native account runtime and initial modeless chooser, verified preparation before atomic selection, account-scoped draft/tab restoration and independent call ownership. Destination state and selection now commit together. One coalesced status scheduler includes lazy Home discovery in its eight-second lifetime; inactive loads cannot resume saved account mutations. Fourteen generated HTTPS/native-window results and exact retained login activation pass address/undefined-behavior sanitizers. The combined release regression passes all sixteen native suites, 165 interoperability cases, generated account/session/direct/six-mode recovery/QR flows and all three relay fixtures. The final sanitizer run passes all sixteen suites, fourteen HTTPS/window results, account/session/direct lifecycles and all three relay fixtures, including the modal guard. Destination-specific identity actions, foreign media and full native release scope remain required. No package publication is claimed.

2026-11-01 — native ordinary-channel type handling

SPEC-005 revision 0.90 restores unambiguous SPEC-012 behavior for voice-only and unadmitted channel state without history, and gates native text posting by current channel/group authority. The eleven-result generated HTTPS/native-window fixture verifies unadmitted text opening, explicit membership, encrypted posting, voice-only state without history, hidden/disabled text controls and no voice request on membership join. The complete sixteen-suite/165-case/account/session/direct/six-mode recovery/QR/three-relay release run passes. All sixteen suites and the eleven-result fixture pass sanitizers; corrected home/direct sanitizer lifecycles also pass after an address-book assertion was changed to await its independent response.

2026-11-01 — independent native account inbox

SPEC-005 revision 0.89 corrects native scheduling to keep the active account's SPEC-018 inbox and Pinned address book current while foreign text is selected, without home transcript downloads. The ten-result generated two-authority/native-window fixture passes release and address/undefined-behavior sanitizers: Pinned contacts and a pending incoming request appear while foreign text stays selected, without home sync/history or voice operations. Full multi-account orchestration remains required.

2026-11-01 — native draft acknowledgement safety

SPEC-005 revision 0.88 binds a protected outgoing operation to the submitted draft token so an acknowledgement cannot erase newer edits, including across unknown-result restart/retry. Tokens remain local and add no wire field. Native-window regressions reproduce the old loss and pass with revision tokens, including newer identical-text edits after pending-result restart/retry. The complete sixteen-suite/165-case/account/session/direct/six-mode recovery/QR/three-relay release run and sixteen-suite/visitor/home/direct sanitizer run pass; the twelve-result protected-store suite rejects malformed/orphan draft tokens and preserves failed writes.

2026-11-01 — native home/direct draft persistence

SPEC-005 revision 0.87 extends protected workspace drafts to the home connection's ordinary, direct and temporary-group views, with an exclusive state writer, coalesced saves and failure-preserving flushes. The ten-result generated HTTPS/native-window fixture passes release and address/undefined-behavior sanitizers. It verifies distinct qualified direct drafts, passive group draft restoration, failed atomic saves, blocked window close, retry/close/restart preservation and unchanged keys/no call admission. Full account switching and view/history restoration remain required.

2026-11-01 — native visitor session lifecycle

SPEC-005 revision 0.86 connects saved visitor sign-out/rejoin state to native server actions, preserving home credentials/keys and destination drafts. Explicit admission has a process-local mutation guard; ordinary Add server reuses an existing admitted saved sign-in. The combined release run passes all sixteen native suites, 165 interoperability cases, generated account/session/direct/six-mode recovery/QR flows and all three relay fixtures. All sixteen suites, the nine-result native-window/HTTPS fixture and home account lifecycle pass address/undefined-behavior sanitizers. Runtime checks cover failed logout/save, actual retired-token rejection, signed-out restart without destination traffic, native rejoin, mutation guards and cancellation; current foreign sync also validates and refreshes its permission-filtered tree.

2026-11-01 — native saved-server workspace integration

SPEC-005 revision 0.85 records the native window integration of independent saved destination text contexts, explicit discovery/admission, qualified tabs and bounded background status reads. The combined release regression passes all sixteen native suites, 165 interoperability cases, generated account/session/direct/six-mode recovery/QR flows and all three relay fixtures. All sixteen suites, the eight-result native-window/HTTPS fixture and home account lifecycle pass address/undefined-behavior sanitizers. A final focused release/sanitizer regression confirms that Add server reuses existing credentials instead of retiring the session that owns an uncertain command. Complete account switching, foreign voice and the other native release gates remain required.

2026-11-01 — ordinary native destination-channel context

SPEC-005 revision 0.84 records a destination-bound channel text context with sole home key/trust ownership, checked room/proof transitions, independent protected drafts/positions and exact unknown-command retry. The combined release regression passes all sixteen native suites, 165 interoperability cases, generated account/session/direct/six-mode recovery/QR flows and all three relay fixtures. All sixteen suites and the real HTTPS destination/home lifecycles pass address/undefined-behavior sanitizers. Exact unknown operations survive 401/403 retry authorization failures and reconcile without duplication. Multi-server UI/media orchestration remains required.

2026-11-01 — retained destination-session approval proof

SPEC-005 revision 0.83 distinguishes protected historical session restoration from fresh login proof validation. Runtime normalization may use the already verified extending home head without copying home roles or changing credentials/device approval. Nine destination-connection QtTest results and real HTTPS protected-session restoration pass release and address/undefined-behavior sanitizer builds, including signed/opaque retained credentials, preserved destination role, strict fresh-login rollback rejection, fork/removed-device refusal and unchanged credential dispatch.

2026-11-01 — native saved visitor sign-out state

SPEC-005 revision 0.82 distinguishes a saved signed-out visitor from a pending join, retaining public account/authority and scoped drafts without destination credentials. Eleven account/connection storage QtTest results and the real HTTPS persisted-visitor regression pass release and address/undefined-behavior sanitizer builds. Runtime multi-server navigation and sign-out remain required.

SPEC-005 revision 0.81 records native metadata refresh, protected same-family renewal/activation, lost-result reconciliation, expiry preservation and standard Preferences controls under D-103. The full release run passes sixteen core suites, 165 protocol cases, real HTTPS/account/direct/session/six-mode recovery/QR flows and all three relay fixtures. All sixteen core suites, generated session/account/visitor/recovery lifecycles and the expanded held-PTT renewal/movement relay fixture pass address/undefined-behavior sanitizers. The final standard scrolling Preferences follow-up passes normal/2× rendering and focused sanitizer session/UI checks; full native replacement/release scope remains incomplete.

2026-11-01 — native session time model

SPEC-005 revision 0.80 records strict account/device-bound session metadata, conservative monotonic time and transition-driven expiry presentation under the existing D-103 contract. The pure model passes release and address/undefined-behavior sanitizer tests, including warning/expiry boundaries, failed-observation preservation, request latency, clock rollback and maximum-date/large-monotonic arithmetic. Full native renewal and UI integration remain required.

2026-11-01 — periodic native home authority checks

SPEC-005 revision 0.79 extends protected startup pinning to bounded shared anonymous metadata revalidation before later credential dispatch. The full release run passes all fifteen core suites, 165 protocol cases, real HTTPS/account/direct/six-mode recovery/QR flows and all relay fixtures. All fifteen core suites, HTTPS visitor restoration, account lifecycle and six recovery modes also pass address/undefined-behavior sanitizers. Deterministic cache/deadline/destruction tests and actual loopback header/payload/cancellation/logout checks pass; restricted recovery pins persist before keys are prepared.

2026-11-01 — native saved-connection storage

SPEC-005 revision 0.78 records the central atomic connection/profile writer, qualified immutable destination/account references, independent visitor context, metadata privacy and same-account removal fallback required by SPEC-015. Ten storage QtTest results and real HTTPS visitor persistence/restart pass. The full release run passes all fourteen core suites, 165 protocol cases, account/direct/six-mode recovery/QR flows and all three relay media fixtures. All fourteen core suites, HTTPS visitor restoration, account lifecycle and six recovery modes also pass address/undefined-behavior sanitizers. Complete multi-server UI remains required.

2026-11-01 — retained-profile recovery startup

SPEC-005 revision 0.77 separates prior approved identity keys from pending replacement keys during interrupted recovery. The retained-profile fixture reproduced startup rejection before the fix. The expanded six-mode recovery matrix passes release and address/undefined-behavior sanitizer builds.

2026-11-01 — native own-proof and channel response binding

SPEC-005 revision 0.76 applies current-account signed-proof extension and exact requested-channel/server checks to native sync. A generated substituted-root response was accepted in the failing regression before the fix. The generated own-root/channel substitution and valid signed-roster advancement regressions pass. The full release run passes fourteen core suites, 165 protocol cases, HTTPS/admission/account/recovery/QR flows and all relay media fixtures. All fourteen core suites, generated account/visitor lifecycles and 165 protocol cases also pass address/undefined-behavior sanitizers.

2026-11-01 — native home startup credential fence

SPEC-005 revision 0.75 records protected home UUID/domain/base pinning, signed-profile pin recovery and account-request gating before validated startup. A generated changed-UUID fixture reproduced credential dispatch before the fix. The changed-UUID regression and valid new/old account and visitor flows pass. The full release run passes all fourteen core suites, 165 protocol cases, HTTPS/admission/account/recovery/QR flows and all relay fixtures. All fourteen core suites and generated account/visitor lifecycles also pass address/undefined-behavior sanitizers, including pin-recovery preservation assertions. Periodic home authority/session qualification remains unfinished.

2026-11-01 — native scoped visitor admission

SPEC-005 revision 0.74 records the explicit native home-grant/destination-join/session flow and its lifetime/deadline fences. Generated HTTPS home/destination admission passes fresh/rejoin, signed-request credential boundaries, invalid authority/grant/identity/keysets, owner/module/account cancellation and pending limits. Real integration corrected JWT audiences to the destination UUID and added the specified finite opaque visitor path. The final release run passes fourteen core suites, 165 protocol cases, HTTPS/admission/account flows and all media fixtures; all fourteen suites, 165 cases and HTTPS/admission also pass sanitizers. Saving connections and complete multi-server UI remain unfinished.

2026-11-01 — ordinary native voice movement

SPEC-005 revision 0.73 applies the existing explicit voice-move controller to ordinary channels and validates previous-call restoration. The full release run passes fourteen core suites, 163 protocol cases, HTTPS, account/direct/recovery/QR flows and all three real-relay media fixtures. Expanded widget coverage preserves held voice on decline, moves group-to-channel and channel-to-channel with fresh input, and cancels during the fence without reconnecting. All fourteen core suites, 163 protocol cases, real HTTPS and expanded widget movement checks also pass address/undefined-behavior sanitizers. Cross-server orchestration remains incomplete.

2026-11-01 — legacy zoom migration reader

SPEC-005 revision 0.72 records the isolated read-only Chromium local-storage clone reader and fixed source bounds under D-197. Release and sanitizer migration tests pass, including the pinned Electron localStorage round trip. The subsequent full release run passes fourteen core suites, 163 protocol cases, HTTPS and all account/media fixtures. It does not enable application zoom or complete installed-profile adoption.

2026-11-01 — protected native account-store views

SPEC-005 revision 0.71 records a protected version-2 root with exclusive version-1 account views. Native-v1 upgrade preserves keys/preferences/pending data; interleaved profile saves, qualified-ID collisions, owner loss, unsupported data and failed-write rollback pass release/sanitizer units. The generated account/lost-command/restart fixture passes through this store in both builds. Destination sessions now require the known home account explicitly and reject changed names/domains/roots and rolled-back/forked approval history. GUI account switching and installed-profile adoption remain incomplete; the final release run passes all thirteen core suites, HTTPS transport, 163 protocol cases, account/direct/recovery/QR flows and all three relay-backed media fixtures.

2026-11-01 — native installed-storage decoder

SPEC-005 revision 0.70 scopes a pure decoder for the existing Linux Electron v11 format using an already retrieved keyring password. It cannot access profiles/keyrings, create keys, adopt an account or use plaintext/hard-coded-key fallback. Independent format vectors, malformed-input and exact 2 MiB boundary checks pass in release and sanitizer builds. The real pinned Electron 44.9.1 process encrypts generated device keys through private fake KWallet/Secret Service backends under both original application names, and the native readers/decoder recover them exactly. Tests validate encrypted Secret Service negotiation, unique-owner requests, invalid entries, and zero native writes/unlocks; the fake bus permits no host service activation. All four combinations pass sanitizers. Source snapshots also pass profile/hash/lock/change/symlink/FIFO/size checks. The read-only keyring/profile import helper, complete installed-profile/keyring interoperability, account/device validation and preference migration remain incomplete.

2026-11-01 — native public discovery and destination session transport

SPEC-005 revision 0.69 records the existing SPEC-010/015 public metadata and visitor-proof contracts in the native implementation. Direct/shortcut locators require fresh identity-origin agreement before any credential use. Generated real-HTTPS fixtures pass certificate/hostname rejection, credential-free headers, cookie/redirect refusal, exact response bounds, strict JSON, fixed deadlines and cancellation. The 163 cross-language cases include Unicode, channel links, descriptors and signed visitor proofs. Destination-session transport passes signed-login/device binding, bounded public-authority caching, cancellation and substitution checks; nine native suites, real HTTPS transport and protocol interoperability also pass sanitizer checks. The full generated-account/recovery/QR/codec/relay suite passes; saved multi-server/account orchestration and UI remain incomplete. The previous recovery-expiry increment now passes all three release/sanitizer modes, and fitting-viewport layout restoration passes.

2026-11-01 — native layout and recovery expiry reconciliation

SPEC-005 revision 0.68 specifies protected native window/splitter state and write refusal after an unreadable/unsupported profile. Release/sanitizer fixtures validate fitting-viewport restoration and toolkit clamping is retained. D-063's process-bounded identical public-roster proof cache avoids repeated signature validation while preserving current trust/rollback checks. The full seven-suite/91-case/account/QR/recovery/media run passes before the expiry increment. Expired recovery completion now preserves the original fresh keys for password reconciliation or an explicit same-key/password restart after definitive expiry; dedicated normal/committed-expired/uncommitted-expired checks are in progress.

2026-11-01 — native QR linking implemented

Both D-171 initiation directions pass rendered native QR, existing-service and restart fixtures, including lost claim/approval replies, exact claim retry, independent keys, retained/future text and cancellation of a public-only interrupted pair. The 91 protocol interoperability cases and QR consent/decoding units pass in release and sanitizer builds. The separate Qt Multimedia scanner processes bounded frames locally on a worker; physical camera acceptance remains incomplete. SPEC-005 revision 0.68 also specifies protected native geometry/splitter persistence under D-198; its validation is in progress. The complete replacement, installed-profile migration, foreign/multiple-service, screen/admin/platform/resource and Portage delivery requirements remain open implementation work.

2026-11-01 — D-198 native presentation amendments approved

The human approves standard Qt styling, modeless Preferences/listening dialogs, static unread counts, compact avatars, plain headings, remembered splitters and an embedded native screen viewer with standard controls. SPEC-005 revision 0.68 scopes the retirement of custom Linux presentation requirements while retaining feature/security/call behavior and other clients. A separate viewer window is still an optional proposal.

2026-11-01 — native recovery and personal listening

SPEC-005 revision 0.66 ports the existing SPEC-011 saved-key/password recovery ceremony and SPEC-004/D-187 local listening preferences. Generated tests pass interrupted setup/completion, exact restored keys, eligible copied/direct recovery history, old-session revocation and consumed-key rejection; 80 native/TypeScript cases include recovery and gain interoperability. Native volume/mute controls and queued-audio silence are implemented; full-suite call-flow renewal diagnosis and final sanitizer/UI checks remain in progress. Revision 0.67 specifies the forthcoming on-demand native QR scanner and public-only interrupted-pair state under D-171; its implementation/validation is not yet complete.

2026-11-01 — D-197 native desktop scaling selected

The human selects desktop scaling alone for the Qt client, with the former application zoom retained as migration metadata. SPEC-005 revision 0.65 scopes this supersession to Linux, specifies absent/invalid-source handling and records the required rendering/migration checks. The development window already uses desktop Qt metrics; installed-profile migration remains incomplete.

2026-11-01 — native source-device approval and retained-history copying

SPEC-005 revision 0.64 ports SPEC-011 manual source linking, explicit device approval/revocation and bounded eligible-history copying into a native Devices dialog. Public slot metadata and exact signed pending mutations are protected before sending; code secrets stay in memory. Generated native/Qt tests cover lost committed approval, manager restart/exact reconciliation, independent target keys, retained DM/closed-group history, future text and revocation. Cross-language protocol coverage grows to 55 cases. QR, recovery, installed-profile migration and the remaining full replacement/release work remain incomplete.

2026-11-01 — native temporary groups and explicit call lifecycle

SPEC-005 revision 0.63 ports the existing SPEC-018/D-090 group and call requirements to native menus/tabs and independent call controls. Group sessions renew only after explicit joins, remain independent of selected text and require explicit rejoin after restart; closed groups clear drafts and retain eligible history. Generated-account/Qt and real-relay tests cover admission boundaries, encrypted text, no-media ringing/decline, explicit call movement, the existing server fence and fresh input. The full replacement, foreign conversations, remaining identity/media/admin work, platform/resource qualification and Portage publication remain incomplete. No feature-reduced release is authorized.

2026-11-01 — native media, input and same-home direct implementation

SPEC-005 revision 0.62 records Qt DBus and the optional C/XInput2 helper, native voice/codec/direct-route and input/preference implementation, same-home direct admission/text and protected direct-operation reconciliation. Existing media, input, identity and direct protocol owners retain their defaults and permission rules. Generated-account fixtures exercise native voice and direct text; private-portal and codec fixtures retain their separate scope. The native replacement, installed-profile migration, screen/SFU, remaining account/federation/group/admin behavior, platform/resource qualification and Gentoo delivery remain incomplete. D-196 closes the old separate-preview question; no reduced release is inferred.

2026-10-31 — D-196 full native replacement confirmed

The human selects completion of the full Qt replacement after reviewing the development inventory. The optional separate-preview release is not selected and no further scope confirmation is pending. SPEC-005 revision 0.61 records the native GStreamer/libopus implementation dependencies while retaining all existing media security, capture, permission and delivery contracts. This is continued implementation authority, not a claim that remaining native functionality or deployment is complete.

2026-10-31 — D-195 native build/release authorized

The human requests building/deploying the selected Qt client and delivery through the local Portage repository. SPEC-005 revision 0.60 documents the C++/Qt development profile, fixed request/vault bounds and isolated native preview/profile. native-client starts the actual Qt and crypto/transport implementation, including protected restart reconciliation for an unknown command outcome, manual same-home linking to fresh keys and eligible encrypted history-share reading. Isolated fixtures verify pending-approval restart, signed bootstrap/login and preservation of the source session; 44 native/TypeScript interoperability cases pass. SPEC-014 revision 0.7 / SPEC-008 revision 0.25 complete home-owned optional pin dates, preserving undated legacy contacts and older-client saves. SPEC-018 revision 1.4 adds retained/eligible last-message acceptance time for the chosen native order. These additive service changes pass the affected local tests and are not yet deployed. It remains an incomplete development port; a partial implementation cannot replace the published alpha.51 package. Native feature/security/media parity, resource measurements and D-181/D-184 publication/overlay checks remain required before delivery can be declared complete.

The human selects the tabbed sketch with Servers and Direct Messages tree roots, root creation context menus and no toolbar/ribbon or right pane. All pinned contacts remain in Direct Messages. The explicit sorting answer selects last sent/received message newest first, newest pin second, then alphabetical order. SPEC-005 revision 0.57 scopes supersession to the Linux successor and retains independent call/security/permission behavior; SPEC-014 records the existing contact API's missing pin-chronology contract without inventing historical dates. The updated interactive sketch is design evidence only; application implementation and release remain pending.

2026-10-31 — native Qt Linux rewrite requested; UI amendments under review

D-193/R-124 records the human's native C/C++ or Rust Linux rewrite, resource priorities and explicit Qt selection. SPEC-005 revision 0.56 distinguishes the confirmed replacement target from the proposed C++/Qt Widgets profile and P-037 presentation/workflow amendments. Five layouts are compared; proposed system styling, native dialogs/menus/splitters, simpler call controls and removed decoration retain feature/security contracts and require review before specific supersession. Alpha.51 remains the released Electron implementation. No application code, package, deployment or measured performance improvement is delivered by this specification update.

2026-10-31 — D-189–D-192 voice, viewing and output capture

SPEC-004/005 preserve activation through sensitivity edits/navigation, correct sensitivity direction and label its levels, add release hysteresis, and show mandatory PTT by the connected channel. SPEC-005/023 expose inline zoom and independent per-publication PC-audio mute, fit the bottom account identity and define filtered Linux output capture that excludes own playback. SPEC-008 completes the existing SPEC-018 public authority transport allowlist; no block/consent permission changes. Alpha.51 packages, both Gentoo overlays and the three-service rollout are verified in the release record. Custom sound storage scope remains open.

SPEC-005 adds password repetition/clear signup guidance and automatic microphone-mode/sensitivity persistence. SPEC-004 expands personal listening gain to exact silence through 400%, retaining legacy stored dB values, the shared baseline, mute gates and output limiting.

2026-10-30 — D-185 known-profile refresh

SPEC-005/008 define authenticated current profile labels on login and daily while open, bounded batches, cached failure fallback and account/service scope. Saved-contact reads refresh nickname as well as picture. Preserve qualified identity, saved channel/Recent encounter evidence and directory visibility; no new foreign admission or presence discovery.

Gentoo revision bumps — D-184

Every ebuild update publishes a higher Portage version or -rN revision. Alpha48-r1 retains the patched alpha.48 archive and requires ordinary upgrade-plan, fresh-fetch/digest and staging validation in both project/local-overlay repositories. SPEC-005 revision 0.52 and deployment instructions record the standing rule.

Electron certificate verification — D-183

The human authorizes patched Electron 44.9.1 desktop packages. SPEC-005 revision 0.51 requires actual packaged Node/Chromium rejection of compromised test chains with ordinary HTTPS success, retained native permissions and immutable Windows/Linux/Flatpak publication plus fresh-cache Gentoo verification. Release evidence: alpha.48.

D-182 refines enabled statistics visibility: the people list scrolls independently, and its scrolling/collapsed state cannot move or hide the statistics footer. SPEC-005 retains measurement/reporting/permission contracts and adds narrow/200%-scale acceptance. Alpha.47 is deployed to both existing account services with verified object/asset identity, 100% configured allocation and all 20 final observed invocations on intended versions with successful outcomes. See the release review. The retained alpha.45 native package/project/local overlay pass D-181 alignment checks.

2026-10-27 — Gentoo overlay is a release requirement

D-181 records the human’s standing instruction to update the local overlay whenever client software is updated. SPEC-005 and the deployment procedure require current project/local-overlay ebuilds and matching archive digests, with empty-cache Portage verification for a newly published package. Shared-interface releases verify the retained compatible native package. System installation remains separate. The catch-up to the published alpha.45 Linux archive passes fresh-cache Portage fetch, BLAKE2B/SHA512/SHA-256, staged unpack/prepare/install and project/local-overlay/host-link checks. Portage offers alpha45; the installed application remains unchanged.

2026-10-27 — public usability and future-member channel pins

D-172–D-180 implement conditional status/statistics, settings/PTT, handsets, encrypted public convenience, participant-addition continuity, Wine discovery, owner-opt-in verified directory search and update offers. The human explicitly confirms the one-message pre-join pin exception and GitHub publication. SPEC-013 owns moderator-approved encrypted copying, original retention and automatic future-device delivery; SPEC-005/008 retain client/server responsibilities. All 416 unit cases, complete browser integration and real workerd/SQLite checks pass. Alpha.46 is live on both existing testing authorities and website with verified configured allocation and target-version traffic; Android alpha.46-android.1 is published. Source commit 2065ed1 is the pinned iOS retry input. See the increment record for canceled telemetry and the historical provider queue/Apple sign-in checkpoints. iOS 0.1.0 (8) subsequently passes signed native/WebKit qualification and upload from that source; Apple processing/compliance and Owner testing delivery complete on 2026-10-27, preserving the existing tester.

2026-10-25 — QR TestFlight build started

Codemagic run 6ade71d34a72334e32e520c5 starts at 21:17 UTC from f2d7e83 on codex/qr-device-linking using the existing internal TestFlight workflow and signing setup. Source checkout, signing setup and unique build-number setup succeed. Native validation and Apple delivery remain pending in the iOS evidence.

2026-10-25 — alpha.44 QR rollout verified

Publish D-171 password-free QR linking in both directions, scoped native camera gates and five immutable updated packages. All 400 unit cases and required browser/runtime/build/specification checks pass; exact live assets and full package hashes match. Both existing Domain objects pass signed restricted QR registration/poll/cancellation/replay checks without account admission. All three Workers have 100% configured allocation at 21:02:15 UTC, with all 25 final bounded observed invocations on intended versions and successful outcomes at 21:07:23 UTC. A first site upload failed and earlier samples included cancellations; the final verified attempt is identified in the release record. iOS source is published, but Codemagic repository loading prevents starting its new signed build; physical camera/mobile-upgrade acceptance remains separate.

2026-10-25 — password-free QR device linking

D-171 selects QR linking in both directions with explicit approved-device confirmation and no password on the new device. SPEC-011 defines the signed payload, bounded rendezvous, encrypted response, retries/cancellation and existing roster/history completion; SPEC-003 scopes the authentication successor, SPEC-005 the deliberate local scanner/native permission exception, and SPEC-008 the transactional server responsibilities. The five-option review remains historical. Chromium/Firefox rendered-image flows, camera lifecycle, cryptographic/service units and actual workerd/Electron checks pass; release and physical platform evidence are tracked separately.

2026-10-25 — disconnection notice Close placement

The human requests the Close control in the Download voice log/disconnection notice at the top-right. SPEC-005 revision 0.45 records the placement, overlap protection and preserved accessible dismissal/download behavior. This is a presentation-only correction, with no call, diagnostic or server-policy change. Alpha.43 is deployed on both testing services with matching assets/objects, 100% configured allocation and all 25 final bounded observed invocations on intended versions with successful outcomes. See the release record.

The human requests all screen-viewing controls in a row at the top to leave more space for the picture, and the ability to type in chat while watching. SPEC-005 revision 0.44 specifies a compact top toolbar in inline and expanded viewers, wrapping at narrow/scaled widths while preserving playback, zoom and Stop watching. Show chat docks the picture above the existing conversation/composer; Larger view restores expansion without replacing the player or losing a draft. No preference, media contract or server behavior changes. Alpha.42 is deployed on both testing services with verified assets/objects, 100% configured allocation and all 25 final sampled invocations on intended versions; see the release record.

2026-10-25 — experimental Android download

D-170 publishes the existing alpha.30-android.2 APK on the download page as Experimental. SPEC-005 revision 0.43 owns presentation/install guidance; SPEC-002 revision 0.7 adds its independently versioned verified manifest and SPEC-008 revision 0.20 covers exact APK distribution. Package bytes and Android behavior remain unchanged.

2026-10-25 — iOS native shell and cloud qualification

The human explicitly requests implementation after account-connection verification. SPEC-005 revision 0.43 resolves the iOS engineering profile: a bundled shared renderer, origin/main-frame-isolated native bridge, protected vault, native HTTPS and scene-based CallKit/audio lifecycle, with iOS 18 as an installation floor. Source is isolated on codex/ios-codemagic. Codemagic run 6ade543f4a72334e32e5190e from 4c7b9b1 passes clean-checkout shared checks, all four Swift core units, native compilation and both iOS 27.1 simulator UI methods, including actual capability/network checks and shared-client launch/relaunch. The Apple app record and owner testing group exist, the owner is added and authorized certificate/profile setup is complete. A signed run reaches the native-process timeout during slow simulator startup; that bound is increased from ten to fifteen minutes with all checks retained. Retry 6ade5d0b4a72334e32e51b5f from 0d91bb0 repeats all checks successfully, signs and exports version 0.1.0 (3), and uploads it to Apple without errors. Apple processing and the approved build-specific compliance answers are complete, build 3 is Testing in Owner testing and the account holder is Invited. Installation and real locked/backgrounded calls remain pending; simulator success does not establish first-build physical acceptance. See the implementation record.

2026-10-25 — alpha.41 foreign-account SFU registration

Restore the D-169/SPEC-025 home-registration request through the production Node/Worker public-network guards. A shared predicate admits only the fixed inspection/presentation POSTs with existing bounds; arbitrary commands, ambient credentials, redirects and private-address connections remain prohibited. Home failures and known SFU authority/pending states retain typed safe errors. A production-guard regression reproduces the prior rejection; workerd registration reaches an actual fixture home validator and rejects wrong calls/unapproved devices. All 383 units and runtime/build/specification checks pass. Both existing authorities/assets and 100% configured rollout match; all 25 final bounded observed invocations use intended versions with ok outcomes at 17:48:11 UTC. The human confirms sharing starts with the same visiting account in Public Lobby. No extra provider test run, installer or media deployment was used. See the release record for scope, initial canceled observations and remaining media-performance limits.

2026-10-25 — alpha.40 Worker SFU startup correction

Restore D-169/SPEC-025 setup on Cloudflare Workers by detaching built-in fetch from its adapter receiver and rejecting redirects with supported manual handling. Safe provider status/code reaches the client; one Worker-only migration recovers alpha.39 creation records proven to have failed before dispatch and preserves future unknown outcomes. Add a workerd regression for all five provider operations, explicit local-runtime test dependency, redirect/security and HTTP redaction coverage. All 380 units and runtime/build checks pass. The actual provider probe succeeds from workerd, and all fifteen runs remain recorded. Both existing authorities/assets and 100% configured rollout pass; all 25 final bounded observed invocations use intended versions with ok outcomes at 17:23:15 UTC. See the release record for propagation delay, scope and physical-client limits.

2026-10-25 — alpha.39 SFU trial rollout verified

The human extended the generated-media allowance from ten to fifteen runs without changing per-run limits. Run 11 passes integrated encrypted video/audio, cadence/alignment, ducking and teardown; all eleven runs have confirmed provider cleanup. Alpha.39 enables all sloppyvoice.com channels while retaining native delivery on the secondary host. All 377 unit cases and relevant browser/runtime/build checks pass. All three changed Workers have 100% configured allocation, exact live authority/assets match, and all 25 final bounded observed invocations use their intended versions with ok outcomes at 16:35:56 UTC. See the release record for numeric results, version IDs, initial canceled/late observations, transitional native dependencies and physical-device limits.

2026-10-25 — managed presentation trial

D-169 selects Cloudflare Realtime SFU for all sloppyvoice.com channels, preserving channel permissions and existing microphone transport. SPEC-025 completes the trial contract, authenticated VP8/Opus encoded-frame profile, ephemeral native-key adapter, finite replay-safe authority, durable resource cleanup and managed call-move fencing. SPEC-008 owns disabled-by-default deployment credentials/scope; SPEC-005 owns RTP capture/playback and uncompressed Linux sound. SPEC-003/016/015/021/007 cover sender/key security, home closure fences, bounded diagnostics and validation. The secondary host remains on native video. Independent managed cryptographic epochs, simulcast/layers and physical hardware/cross-network acceptance remain explicit later work; no plaintext fallback, hard provider bitrate policing or partition cutoff is claimed.

2026-10-25 — stable presentation adaptation

D-168 / SPEC-024 revision 1.1 replaces five-second recovery with 30 seconds of successful progress, 15-second failed-trial rollback and retained retry waits up to four minutes. Pressure bursts count once per 100 ms, isolated hiccups do not erase healthy history, and stale feedback cannot instantly increase quality. Direct screen routing follows verified path liveness; queued microphone/video bytes defer sending without repeatedly recreating encoders. Held-picture labelling begins after 750 ms, preserving the image and specific keyframe/permission status. SPEC-005/023 reference the successor; SPEC-021 owns bounded recovery diagnostics.

2026-10-25 — alpha.36 rollout verified

The D-166 implementation is live on both existing authorities and the website. All engineering checks pass, final configured allocation is 100% for all three Workers and all 25 final sampled invocations use their intended versions with ok outcomes. The release record distinguishes initial build-label correction, configured allocation, observed traffic, exact assets, preserved services/data and physical-device limits.

2026-10-24 — adaptive screen workload and direct Start

D-166 / SPEC-023 revision 1.7 supersedes timing blanking with an authorized held picture, adds independent bounded resolution/cadence/bitrate adaptation and scoped receiver feedback, and removes mandatory preview confirmation. SPEC-005/008/021 revisions 0.40/0.18/0.4 define component and diagnostic responsibilities. All source/audio consent, authority, moving-frame timing and personal/server ceilings remain enforced. Alpha.36 validation/rollout evidence belongs to its release record.

2026-10-24 — ordered video recovery and Firefox regression

SPEC-023 revision 1.6 completes D-134/R-120 loss recovery with a negotiated publication marker and per-rendition encoded-video sequence, bounded 40 ms reordering, fresh-keyframe recovery after missing dependencies and decoder-generation isolation. Legacy wire/relay compatibility remains. SPEC-005 revision 0.39 records receiver responsibilities, SPEC-008 owns capability projection, and SPEC-021 revision 0.3 adds bounded dependency-reset accounting. Real VP8 fixtures exercise reordered/lost packets through Chromium and Firefox receivers; physical NVIDIA capture/playback remains separate acceptance.

2026-10-24 — screen playback load and diagnostics

SPEC-023 revision 1.5 completes R-120/D-134 rendering behavior: draw only the latest eligible due frame after a scheduling delay, retain future frames, avoid unchanged canvas resets and repeated paused-surface clears. The client uses the existing libsodium verifier for authenticated screen chunks; reference/accelerated verification tests reject tampering. SPEC-021 revision 0.2 records bounded numeric screen counters in existing diagnostic snapshots. Authorization, encryption and all timing/security limits remain unchanged. Listeners advertise decoding capability without requiring a local encoder for the same codec. The encoder probes all common hardware-preferred configurations before software fallback and preserves that preference during backoff. SPEC-005 revision 0.38 fixes Stop watching leaving an expanded empty panel. The reported real-client stall remains subject to diagnostic/physical validation.

2026-10-24 — screen viewer recovery and quality controls

D-165 / SPEC-023 revision 1.4 and SPEC-005 revision 0.37 add Automatic and explicit resolution/frame-rate ceilings, with Quality preserving native sources up to 4K. Client-only preferences retain existing wire and bitrate enforcement. Receiver fixes prevent a membership-update loop, recover accurate permission status and retain sharing intent during key renewal. Regression tests cover grants, membership transitions, 4K rendered pixels and lower settings.

2026-10-24 — Linux output-device sound capture

D-164 / SPEC-023 revision 1.3 adds explicitly selected output-device capture alongside application streams. Output capture includes call playback with a visible echo warning; application mode retains own-process exclusion. Selection is fixed, bounded and ephemeral, with no microphone/default-output fallback. SPEC-005 records the separate capability and older-wrapper guidance.

2026-10-24 — iOS build/distribution selection and background-call requirement

D-163/R-123 select Codemagic and TestFlight for an iOS client using the Android design, with background calls required in the first build. SPEC-005 revision 0.35 records the user-reported iPhone 13 mini/iOS 27.0.1 primary target and iPhone XS/iOS 18.x compatibility target, separates unresolved platform mechanisms/defaults from accepted outcomes, and defines platform validation responsibilities. SPEC-004 references the narrow background activation exception. Apple/Codemagic accounts are not yet set up; the setup guide provides enrolment and integration steps. No iOS executable, cloud build, installation or physical acceptance is claimed by this entry.

2026-10-24 — immediate outgoing chat feedback

D-162 / SPEC-013 revision 0.5 adds transient outgoing rows with Sending, Sent, Not sent and Confirmation pending states, authenticated-envelope reconciliation, original-command retry and context isolation. SPEC-005 also applies history before unrelated visitor contacts/profile requests. No server schema, protocol, authority or polling-period change. Deployment follows D-159.

2026-10-24 — Flatpak download ordering

The human’s D-160 refinement puts Flatpak above the x64 archive in the Linux card, with each package’s guidance grouped beneath it. SPEC-005 and the published template match. Build, specification and live checks pass; the follow-up record records allocation and sampled traffic.

2026-10-24 — Linux Flatpak publication

D-160 changes public platform labels to Linux and publishes a verified Flatpak bundle alongside the archive. SPEC-005 owns the sandbox/profile/runtime contract and instructions; SPEC-002/008 add its required manifest and exact download route. Installation/update, sandboxed sign-in, encrypted storage/fail-closed checks, native dependencies, all 11 site tests and live full-download integrity pass. Website allocation is 100%; all 25 bounded observed invocations use the new version. See the publication record.

2026-10-24 — Android chat-focused layout

D-161 and SPEC-005 revision 0.34 put channel chat first, keep the user/config bar at the bottom, embed Hold to talk only during a connected local call, and expand navigation/other voice controls from a three-dot button. The human’s follow-up explicitly retains the account bar. Background-call and input policy remain unchanged.

2026-10-24 — standing cyclic-testing deployment authorization

D-159 authorizes this deployment and removes separate human predeployment review/approval for validated in-scope changes during the current testing cycle. SPEC-000 revision 0.4, project instructions and the deployment guide record this standing authority. Engineering validation and rollout monitoring continue without an extra human sign-off.

2026-10-24 — voice renewal scheduling correction

SPEC-005 clarifies serialized renewal scheduling under the existing authority limits: slow responses consume the one-second cadence instead of dropping the next timer tick. Intentional closure ignores late renewal failure responses. Two supplied alpha.29 logs contain eight distinct relay HTTP 409 failures, all with zero recorded lease time remaining; timing supports expiry as a likely cause but does not identify the server's exact rejection branch. No authority timeout or automatic-rejoin policy changes. Local implementation and evidence are in the chat and voice review.

2026-10-24 — message composer and elapsed timestamps

D-157 keeps keyboard focus through sends, releases the composer on acknowledgement without awaiting history synchronization, and retries one confirmed revision conflict only for unchanged verified recipients and encryption. Visible message clock times gain parenthesized completed minutes/hours/days, refreshed locally with exact datetime/tooltip retained. Implementation is local and not deployed; see the chat review.

2026-10-24 — shared device-approval window

D-156 increases SPEC-015 revision 0.6 directory approval freshness from one to ten seconds, measured from request start. Both home responses and destination cache validation use the shared bound; expired results remain unusable. Voice leases and direct contact/block policy retain their independent deadlines. The preceding client correction keeps unrefreshed voice snapshots from toggling an unchanged channel’s chat-posting indicator. These changes are local and not deployed; see the approval review.

2026-10-24 — Editorial website publication

D-154 approves and publishes the reviewed Editorial design, including the explicit public-server alternative to self-hosting, independent access/encryption choices, invitation policy and route-aware bandwidth. D-151 desktop cards include the separately approved D-155 portable Windows option. No unavailable platforms or PTT promotional claims are shown. Site build, ten site tests, responsive/light/dark/keyboard checks and live asset/download/coordinator verification pass. The website has 100% configured allocation; all 16 bounded observed invocations use its new version. See the publication record.

2026-10-24 — public admission on sloppyvoice.com

D-153 enables the existing publicVisitors and localRegistration owner policies on sloppyvoice.com. The UI confirmed the saved settings; an unauthenticated public-descriptor read at 16:59:36 UTC confirmed both enabled values and unchanged identity. Other server settings, channel ACLs/encryption and existing capacity limits are preserved. No application deployment was required. All three server-policy unit tests and specification checks pass; the admission record documents live evidence and the boundary of verification.

2026-10-24 — website downloads and federation copy

D-151 and SPEC-005 revision 0.32 give Windows and Linux equal download cards with manifest-backed details and checksum instructions. The responsive grid accommodates additional desktop/store entries without advertising unavailable platforms. The homepage editorial draft leads with self-hosted accounts and permitted cross-server channel access; current source-access and technical deployment limits remain explicit. Obsolete one-device website requirements and Linux video-only copy are corrected against their active successors. Local build, specification checks, nine download-service tests and responsive/keyboard checks pass. See the website review. This is local work, not a production release.

2026-10-23 — alpha.29 release

D-150 publishes D-149 larger channel titles and the Lobbyster easter egg, aligned with SPEC-005 revision 0.31. All 300 unit tests, production build, visual/accessibility/layout checks and workerd/SQLite integration pass. All three changed Workers have 100% configured allocation at 23:29:14 UTC; both existing objects report alpha.29 and all 25 final bounded observed invocations use their intended versions. Authorities, admission/login policy, data, media and native packages remain intact. The release record separates configured allocation, object propagation and observed traffic.

2026-10-23 — larger channel title and Lobbyster easter egg

D-149 and SPEC-005 revision 0.31 enlarge the current channel heading to 24px and put a static vector lobster behind whole-word Lobbyster matches, ignoring case. The original title and accessible name remain intact. Light/dark, forced-colour, narrow and 200% layout checks pass, including repeated matches without overlap; TypeScript/production build and specification checks pass. See the implementation record. Subsequent D-150 publication is recorded above.

2026-10-23 — alpha.28 release

D-148 publishes D-147 Pinned/private-activity indicators on both existing control/client services and the public website. All 300 unit tests, production build, focused people/private-call/account browser regressions, visual checks and workerd/SQLite integration pass. All three changed Workers have 100% configured allocation at 16:09:08 UTC; both existing objects report alpha.28 and all 25 final bounded observed invocations use their intended versions. Existing native packages, media, stored data, authority and admission/login policy are retained. The release record separates live propagation, configured allocation and observed traffic.

2026-10-23 — Pinned people and private-activity indicators

D-147 renames Friends to Pinned, replaces hearts with amber filled/muted outline thumbtacks, and adds local private-call/current-DM highlights. Ordinary channel or thread co-attendance does not activate either icon. SPEC-005 revision 0.30 owns presentation, SPEC-014 revision 0.5 retains the saved-contact data contract, and SPEC-018 revision 1.3 references the updated controls. This request changes no saved defaults, wire contract, permission or voice action. Implementation, 300 unit tests, production build, focused channel/people integration, private direct/group calls and multi-server/account regressions pass. Visual checks cover light/dark, forced colours, keyboard toggles, 390-pixel width and 200% scale; minimum checked icon/background contrast is 5.24:1 light and 6.96:1 dark. See the implementation record. The subsequent D-148 alpha.28 publication is recorded above.

2026-10-23 — alpha.27 release

D-146 publishes D-144/D-145 Linux application sound, aligned with SPEC-005 revision 0.29 and SPEC-023 revision 1.2. The shared services, public site, matching immutable desktop packages and local-overlay ebuild are live-verified. All 298 unit tests, native/desktop generated-audio checks, screen regression, workerd/SQLite, production build and site/package checks pass. All three changed Workers have 100% configured allocation at 04:17:59 UTC; both existing objects report alpha.27, and all 25 final bounded observed invocations identify their intended versions. Media, identities, admission/session policy and stored data are retained. The release record records downloads, Portage verification and provider outcomes. The installed application and physical KDE audiovisual acceptance remain separate.

2026-10-23 — Linux game and music capture

D-144 authorizes a bounded Electron loopback trial and native application capture when own-call exclusion is unavailable. The Linux trial captures both external and own playback, so SPEC-005 revision 0.29 and SPEC-023 revision 1.2 add explicit native PipeWire stream selection. D-145 adds simultaneous game and separate music selection. A bounded PCM bridge mixes selected streams into the existing presentation-audio role without virtual microphones, routing changes, microphone/PTT changes or server/protocol changes. Pending-start cancellation, source identity, leases, bounded queues and timestamp continuity are part of the documented adapter contract. The implementation record separates automated isolation/mixing/cleanup and transport evidence from remaining physical KDE audiovisual acceptance. This paragraph records local implementation; D-146 and the alpha.27 release above cover subsequent packaging and deployment. Installed-client upgrades and physical acceptance remain separate.

2026-10-23 — alpha.26 release

D-143 publishes the D-141/D-142 settings and sidebar presentation aligned with SPEC-005 revision 0.28. All 285 unit tests, clean build, specification checks, Worker dry-run, full isolated browser regression and real workerd/SQLite integration pass. Final browser forced-colour checks verify section boundaries and primary-button labels using paired system colours. All three changed Workers have 100% configured allocation, rechecked at 02:26:50 UTC; both existing objects report alpha.26 and all 25 final bounded-sample invocations identify their intended versions. Existing authority/admission state, media services and alpha.25 desktop packages are retained. See the release record for propagation and observed-traffic evidence.

D-142 extends the approved settings preview to both sidebars. SPEC-005 revision 0.28 specifies rounded server/people groups, stronger headings, compact rows and unchanged selection, access, unread and voice semantics. Shared presentation tokens keep the settings and sidebars consistent. Automatic people-width measurement now includes rendered panel insets; compact arrangements at the existing minimum widths avoid vertically stacked channel names and separated action buttons. Stored width defaults/bounds, navigation and media behavior remain unchanged.

Production build, TypeScript, all seven existing sidebar-width/scale unit tests, specification and whitespace checks pass. Browser checks use actual tree/people/layout components with synthetic long identities and nested channels, then the running local app for empty lists and persistent controls. Both compiled palettes, minimum manual widths, reset, search, independent expansion, keyboard context actions, 200% scale and the 390-pixel People layout pass without horizontal page/panel overflow. Populated sidebar text contrast is at least 5.26:1 in light and 6.96:1 in dark; running-app disabled controls remain at least 4.79:1/6.01:1 respectively. Forced-colour system roles were source-reviewed, not exercised in an actual forced-colour browser/OS session. Evidence is local in artifacts/sidebar-sections-verification.json and preview images. This records the local implementation stage; D-143 authorizes subsequent alpha.26 deployment above.

2026-10-23 — User settings section hierarchy

D-141 records the requested solid section headings, softer matching settings panels and rounded corners, with clarity taking priority over the preferred lavender accent. SPEC-005 revision 0.27 narrowly supersedes D-066's separator-only treatment in User settings. The VLC redesign reference informs visual hierarchy and restrained colour; existing settings behavior and navigation remain unchanged. This is a local presentation increment, not a deployment.

The local implementation groups device settings beneath server connections in the second desktop column while preserving document/keyboard order. Nested groups use quieter headings; connection addresses wrap and disabled primary actions use the ordinary button surface. Production build, TypeScript, specification links and whitespace checks pass. An isolated browser fixture verifies both compiled palettes at 1440 × 1000, 200% interface scale, a 390 × 844 layout, scale/reset and Back/Escape focus return. Checked text contrast is at least 4.79:1 in light and 6.01:1 in dark, with no horizontal page/workspace overflow in those cases. Forced-colour rules use system roles and were source-reviewed; actual forced-colour browser/OS rendering was not exercised by this preview tool. Evidence is saved locally under artifacts/settings-sections-*.

2026-10-23 — alpha.25 release

D-140 authorizes publication of D-136–D-139 as alpha.25, with new immutable desktop packages and matching control/client and public website. Existing media services, authority data and admission settings are retained. All three changed Workers reach 100% configured allocation; both existing objects report alpha.25 with unchanged admission/identity and 15-second attendance. All 25 final bounded-sample invocations identify the intended versions. New desktop downloads pass full SHA-256 and HTTP checks. The release record separates local validation, propagation and observed traffic.

2026-10-23 — local capture, attendance and channel maintenance

D-136 repairs the desktop preview permission path and adds prominent full-width errors. D-137 triples attendance/reservation expiry to 15 seconds while retaining media/revocation/generation bounds. D-138 repairs native public-link copying, displays public links in settings, adds owner-confirmed recursive deletion including the Lobby, and specifies alphabetical fallback or an empty server workspace. D-139 replaces Voice here text with an accessible handset icon. Matching specifications and local implementation are recorded in the capture review and maintenance review. This records the local implementation stage; D-140 subsequently deploys alpha.25 above. The installed system client is not upgraded automatically.

D-135 requests publication of the implemented SPEC-023 increment to both existing services with matching media images, desktop packages and public release notes. The known physical capture/audio, cross-network and capacity gaps remain recorded. Hosted fixture reset now recreates the schema-9 lobby permission row and waits for the updated test Durable Object before account setup; production data is unaffected. The hosted screen case exercises two TURN recipients and presentation sound. Both existing authorities and media services plus the public website are deployed and live-verified. All five Workers have 100% configured allocation; all 21 final bounded observed invocations use their intended versions. The release passes 276 unit tests, native/workerd checks and repeated local/hosted media scenarios. Rollout evidence is recorded separately from local implementation validation.

Implemented the D-134 profile from alpha.23: administrative policies/exceptions, publication/subscription leases, encrypted encoded video beside voice, native relay budgets, direct/mixed fallback, explicit source chooser, stereo presentation sound and local ducking. Game audio starts on in the chooser. Microphone clock timestamps, bounded queues and separate SCTP/voice validation preserve the accepted voice contract. The implementation record separates passing local tests/builds from open physical capture/audio and deployment capacity gates. No release or deployment is claimed.

D-134 approves the remaining SPEC-023/P-035 completion proposal and delegates documented/tested engineering details. The one amendment is that the popup's optional game-audio capture toggle starts on. Explicit Start sharing and platform source/audio consent remain necessary. SPEC-023 revision 1.0 is the selected design; the existing policy/prototype evidence does not establish application completion or authorize deployment.

2026-10-22 — encoded-video direction, server rate and local feasibility

D-131 selects encoded video beside existing voice. D-132/D-133 confirm an 8 Mbps normal server relay limit, a 4 Mbps initial client presentation limit with adaptation and headroom for sound/overhead, and enabled sharing inherited by channels. These selections resolve the reviewed defaults without approving unrelated open limits or mechanisms.

The isolated experiments/screen-share/ fixture passes five transport unit tests and ten real browser encode/encrypt/transmit/decrypt/decode/draw cases. Synthetic VP8/VP9/AV1 at 720p60 exercise 2/4 Mbps encoder requests; additional cases exercise an extra browser relay hop, a 3840×1080 canvas, fragment loss and fixture-authority expiry. Timing follows instrumented playback in the existing Opus worklet. The feasibility record reports measured rates, dropped frames and limitations, including encoder overshoot. This is local experimental implementation; no application capture, native relay enforcement, new release or deployment is claimed.

shared/screen-policy.ts implements the approved policy primitives: selected defaults, inherited permission and denial, channel-rate exception validation, relay/direct limit calculations and listener ducking arithmetic. Seven focused tests pass; the full 248-test unit suite, production build and specification checks pass. No endpoint, capability or settings UI is enabled by these helpers. The remaining P-035 resource/scope/audio/synchronization proposal is concrete in SPEC-023 and awaits review before dependent integration.

R-117–R-121/D-128–D-130 request channel/direct/ad hoc sharing with route-aware bitrate controls, a channel-specific server-admin relay exception below infrastructure limits, source/content/quality selection and synchronized microphone plus optional application/system sound. The human selects one combined all-screen view and responsive voice when video cannot keep up. PTT controls only the microphone; received game sound defaults to half volume during held PTT or another user's speech, configurable per listener.

SPEC-023 compares five approaches and proposes encoded video beside the existing voice engine, with explicit capture/codec/platform prerequisites and a single configuration inventory. Numeric defaults, synchronization thresholds, resource limits and unselected completion details remain proposed/open under P-035/Q-62–Q-64; selected display/PTT answers are retained in Q-65/Q-66. SPEC-005/008 keep client/server ownership, and SPEC-004/017/018 identify preserved media/routing/conversation contracts. A-49 records future validation. This is a local specification amendment from c0fdcb5, not application implementation, capability advertisement or deployment.

2026-10-22 — alpha.23 deployed: immediate channel identity selection

D-127 authorizes deployment of validated D-126/R-115/SPEC-005 behavior. Both existing control/client authorities and the public website are live-verified. All three Workers have 100% configured allocation, rechecked at 20:33:00 UTC; both EU objects report alpha.23 and all 30 final bounded-sample invocations used their intended versions. All 241 unit tests, build/specification checks, multi-server browser/active encrypted-voice regressions and real workerd/SQLite integration pass. Schema 9, existing identities/policies, media and desktop wrappers remain intact. The release record separates allocation, delayed object convergence and bounded observed traffic.

2026-10-22 — immediate channel identity selection implemented locally

D-126 refines R-115/SPEC-005/A-48: changing the channel-menu Join as dropdown immediately opens/joins that channel with the selected account. If this device is already connected to voice in the same server/channel, it also rejoins voice under that identity. Calls elsewhere and calls already using the chosen identity remain intact. Authentication/access validation precedes context replacement; a sign-in chooser retains the captured same-channel voice intent, while cancellation or an ended/replaced call cancels that continuation. Fresh input is required before transmitting again.

The production build, specification checks, isolated multi-server browser suite and expanded active encrypted-voice integration pass. Coverage includes automatic text admission, account-specific drafts, denied access, unrelated-call preservation, already-matching voice identity, switching both directions, expired sessions, wrong-password/cancelled sign-in and successful sign-in continuation with fresh PTT and subsequent E2EE audio. Fixtures remain isolated from production. No deployment or release-version bump is included in this local implementation milestone.

2026-10-22 — alpha.22 deployed: inherited permissions and channel invitations

R-116/D-122–D-125 select SPEC-022: named foreign-account invitations include restricted server admission and a non-propagating target-channel permit; all ordinary channels share inheritance, permit and denial controls. An applicable denial wins, and breaking inheritance never bypasses server bans. D-125 explicitly selects inheritance for every new public/private channel and preservation of existing access. Schema 9 materializes legacy permissions before replacing the old parent-entry prerequisite. SPEC-005/008 own their component responsibilities; SPEC-012/015 identify the superseded portions.

All 241 unit tests, specification/build checks, full browser, named-invitation, multi-server account/voice and real workerd/SQLite integration pass. Both existing EU authorities and the public website are live-verified; 100% configured allocation was rechecked at 17:12:32 UTC. Both objects report alpha.22 and all 33 final bounded-sample invocations used their target versions. The release record separates allocation, delayed object convergence, measured traffic and provider outcomes. Media, identities, admission settings and compatible desktop wrappers are retained.

2026-10-22 — alpha.21 deployed: compact server identity

D-121 authorises deployment of validated D-120. Both existing control/client services and the public website are live-verified with 100% configured allocation, checked at 03:11:40 UTC. Both existing EU objects report alpha.21; exact assets, public pages and preserved identity/policy checks pass. All 54 final bounded-sample invocations used their intended versions with outcome ok. The release record separates configured allocation, observed traffic and existing-object evidence.

2026-10-22 — compact server identity subtitle

D-120 refines R-115/SPEC-005: remove the separate account-selector row and show the selected qualified username in the subdued subtitle beneath the server name, replacing the repeated server domain. Sign in as another user remains available through the server context menu, including keyboard and action-button access; channel Join as and account/voice boundaries are preserved. This supersedes only the separate account-button presentation in D-117/D-118. No settings, storage, API or authentication change.

Validation: production build, specification checks, isolated multi-server browser integration and the active encrypted-audio regression pass. Existing browser coverage now opens the chooser through the server menu and verifies the subtitle follows account switching; draft/access isolation, failed/expired sign-in, cancellation, reload, sidebar sizing and narrow layout pass. The voice regression confirms the original call and encrypted audio survive account switching and other-account sign-out. Tests use isolated services and synthetic audio. This local implementation milestone was subsequently deployed under D-121 above.

2026-10-22 — alpha.20 deployed: Quiet identity

D-119 authorises deployment of validated R-115/D-118. Both existing control/client services and the public website are live-verified with 100% configured allocation, rechecked at 03:01:26 UTC. Both existing EU objects report alpha.20, exact client assets and public pages pass, and all 46 final bounded-sample invocations use their intended versions with outcome ok. Existing authorities, schema 8, media, admission/session policy and compatible desktop packages remain intact. The release record separates configured allocation, observed traffic and object propagation.

2026-10-22 — Quiet identity implemented locally

D-118 authorises implementation of the selected D-117 design. R-115, SPEC-005 and A-48 define one root per verified server, a qualified account/history chooser, and channel Join as with explicit text/voice actions. Protected per-server selection reuses existing account profiles without combining sessions, keys, drafts or permissions. Failed or cancelled switches preserve the prior context; active voice retains its original account, including when another account on the same server signs out. SPEC-015 references this presentation successor while retaining its connection/authentication boundaries.

All 233 unit tests, production build, specification checks, full browser regression, isolated multi-server account switching and two-client encrypted-audio validation pass. The implementation record records coverage and limits. No release bump, publication or deployment was included at this implementation stage; D-119 subsequently authorises alpha.20 above.

2026-10-22 — Quiet identity design selected

D-117 records the human's selection of Quiet identity from five interactive account-switching alternatives. The selected presentation keeps one server heading, places its current account beneath it, exposes Sign in as another user from the server menu, and provides a channel Join as dropdown. The design review records the flow, the existing account/destination and voice boundaries, and the application validation required before delivery. This entry records design selection only; D-118 above subsequently authorises local implementation.

2026-10-21 — alpha.19 deployed: public server and channel links

D-116 authorises deployment of validated R-114/D-115. Both control/client services and the public website are live-verified at 100% configured allocation, rechecked at 22:56:24 UTC. Existing EU objects report alpha.19, exact client assets and public pages pass, and all 44 final bounded-sample invocations use their intended versions with outcome ok. Account authority, public admission/session policy, schema 8, media and compatible desktop packages are preserved. The release record distinguishes configured allocation, observed traffic and object propagation.

2026-10-21 — public server and channel join links implemented locally

R-114/D-115 and A-47 add public context-menu copy actions and strict channel locators accepted by Add server. Existing admission rules remain authoritative. Denied destinations persist as account-qualified Not joined roots with retry/removal and no channel requests; inaccessible targets disclose no metadata. Permitted targets open/join for text, including through local sign-in/registration, while voice remains separate. Clipboard failures expose a selectable link. Startup draft saving now waits for a loaded matching connection, preserving selected linked channels across reload.

Validation: all 229 unit tests, production build, specification structure/link checks, expanded isolated multi-server browser integration, and the two-client multi-server voice regression pass. Browser coverage includes denied persistence/removal/retry without duplicates, server-only retry semantics, public/private copy actions, clipboard fallback, non-landing text admission, hidden-target privacy, qualified local accounts and saved channel restoration. The voice regression follows a channel link during an active foreign call and verifies the same call ID and participant roster before an explicit voice move. Tests use local/in-memory fixtures and synthetic audio. At completion of this implementation stage, no release bump, publication or deployment was included; D-116 subsequently authorises alpha.19 above.

2026-10-21 — alpha.18 deployed: clearer microphone controls

D-114 authorises deployment of the validated D-112/D-113 microphone update. Version labels agree at alpha.18; release build, real workerd/SQLite integration, website/package verification and all three deployment dry runs pass. Both existing control/client services and the public site have 100% configured allocation, rechecked at 22:29 UTC. Both existing EU objects first reported alpha.18 at 22:28:49 UTC; exact assets and live pages pass. All 49 final bounded-sample invocations use their intended versions with outcome ok. The release record separates allocation, observed traffic and propagation.

2026-10-21 — disabled PTT notice and held on-screen fallback

D-113 replaces the PTT retry button with a disabled-PTT explanation and Click to talk, explicitly selected as hold-to-talk. The on-screen input works independently of shortcut readiness and retains capture authority, maximum duration and fresh-hold requirements. The mode checkbox remains within PTT configuration. SPEC-004/005 supersede the retry portion of D-112; validation record.

2026-10-21 — PTT recovery and settings placement

D-112 clarifies the existing D-105/D-108 controls: microphone mode remains selectable without a call and is grouped under Push-to-talk configuration. Input-recovery actions appear only for active local calls with settings closed, avoiding the ineffective action caused by deliberate settings pause. Defaults, policy precedence and capture gates remain unchanged. Validation is recorded in the repair review.

2026-10-21 — alpha.17 deployed: expanded servers and adjustable sidebars

D-111 approves deployment of the validated R-113/D-110 sidebar changes to the existing services. Version labels agree at alpha.17; real workerd/SQLite integration and the public-site build pass. Both control/client services and the website have 100% configured allocation, rechecked at 21:32 UTC. Existing objects first reported alpha.17 at 21:31:57 UTC, exact client assets match, and all 48 final bounded-sample invocations use their intended versions. The release record distinguishes allocation, observed traffic and persistent-object propagation.

2026-10-21 — alpha.16 deployed on the second identity domain

D-109 resolves Q-49 with shittyshittybangbang.com, using the existing independent-instance contract in SPEC-010/015. The unchanged alpha.16 application is deployed to a separate EU authority and media service. Both new Workers have 100% configured allocation; all 41 invocations in the bounded verification sample identify the intended versions. Exact assets, HTTPS/DNS discovery, persistent-object identity, initial setup and the running relay image pass verification. The deployment record distinguishes successful checks, one canceled media invocation, initial owner setup and human call-testing limits.

2026-10-21 — Quiet Stack deployed as alpha.16

R-112/D-108 and A-45 are implemented and validated. The three bottom-left bars, anchored context, call controls and persistent failure notice pass real browser tests; media authority and input contracts remain unchanged. Both changed Workers reached 100% configured allocation, the existing object reports alpha.16, live assets match, and all 14 invocations in the final bounded sample use their intended versions. The release record distinguishes allocation, observed traffic and propagation.

2026-10-21 — Quiet Stack implementation authorised

D-108 records the explicit implementation and deployment request. R-112, SPEC-005 and A-45 refine the selected three-bar layout, anchored connection context, persistent failure notice and unchanged input/call semantics. Supersede the older full-width voice-strip location without changing media policy or saved settings.

2026-10-21 — Quiet Stack design selected

D-107 records the human's selection of the Quiet Stack sketch: separate compact connection, microphone and identity bars at the bottom of the channel sidebar, expandable connection details, and a visible unexpected-disconnect notice. The design review preserves the selected direction and future validation scope. Application code, active runtime contracts and the deployed alpha.15 release are unchanged; this turn records a design selection following a request for sketches and discussion.

2026-10-21 — alpha.15 deployed: server tree, unread messages and voice activation

D-106 authorizes deployment of D-104/D-105 and R-109–R-111. The shared control/client and matching release notes are live. Both changed Workers have 100% configured allocation rechecked at 20:06:45 UTC; the existing EU control object first reported the corrected alpha.15 label at 20:06:32 UTC. Live JavaScript, CSS and audio-worklet bytes match the validated build. All 39 final bounded-sample events use their intended versions, including seven Domain invocations; earlier mixed-version propagation is recorded separately. The release record records the build-label correction, validation, versions, UTC windows and cleanup. Existing identity/admission settings, media and immutable desktop packages remain intact.

2026-10-21 — server tree, unread messages and optional PTT

D-104/D-105 record the requested server-root tree, eight channel levels, bottom-left unread summary, per-person unread indicators, and server/channel PTT policy with personal precedence. Follow-up answers select voice activation and parent access required by default with explicit independent-access overrides. R-109–R-111, A-43/A-44 and affected client/server/shared specifications now define the implementation, schema-8 migration and safety gates, superseding the earlier always-PTT and flat-channel restrictions. The implementation passes all 221 unit tests, full browser and focused speech/suspension checks, direct and multi-server calls, linked-device recovery, real workerd, build and specification validation. The review records implementation evidence and physical testing limits; the later D-106 release entry above supersedes its local-only status.

D-103 selects and authorizes build/deployment of the D-102/R-108 successor. SPEC-003 owns the finite/Unlimited policy and strict Ed25519 token/registry contract; SPEC-005 and SPEC-008 define client/server responsibilities, SPEC-009 the wire routes, and A-42 the validation scenario. Schema 7 preserves old deadlines. The client securely saves/reconciles a fresh token before bounded activation, retaining voice and drafts. All 214 unit tests, full browser/device/direct/cross-server voice integration, real workerd and specification checks pass. Both changed Workers have 100% configured allocation rechecked at 17:23:29 UTC; the existing object first reported alpha.14 at 17:22:52 UTC, and exact assets/public-key/live checks passed. All 42 events in the bounded release-check sample identify their intended new version (37 successful, five cancelled), separately from global analytics. The alpha.14 release record records versions, UTC windows, validation and cleanup. Earlier under-review entries below are historical.

The human prefers cryptographic signatures for the account token. P-034 revises the login-session review toward Ed25519-signed tokens with issuance-time expiry and current server-side session/account/device checks. It distinguishes signature authenticity from revocation and possession, specifies proposed finite/unlimited claims and trusted-key checks, and retains existing expiry/migration choices. Profile, key lifecycle and renewal handover remain under review; no application or production change is made.

D-102/R-108 request a server-configurable absolute login duration, default 30 days or unlimited, with a subtle early-sign-in warning. The human selected keeping existing expiry dates and applying the setting only at the next successful sign-in/renewal, with warnings during the final 24 hours capped at the last 10% of shorter sessions. A subsequent question requests comparison of token/expiry mechanisms. The login-session review records the current opaque-token/server-expiry implementation and proposes client expiry metadata plus a bounded fresh-token handover; credential replacement versus extension remains under selection. No application code or production change is included in this review.

2026-10-21 — alpha.13 deployed: interface scale and status surfaces

D-101 authorizes deployment of D-100/R-102/R-106/R-107. Alpha.13 is live in the control/client Worker and public release notes. Both changed Workers have 100% configured allocation, rechecked at 15:58:18 UTC. The existing EU control Durable Object first reported alpha.13 at 15:56:40 UTC; live JavaScript/CSS match the validated build byte for byte. All 40 events in the bounded release-check sample identify their intended new Worker version (37 successful and three cancelled invocations); this sample is not global traffic analytics. Live anonymous scaling and responsive release pages pass. Existing media health, identity/admission policy and immutable downloads are preserved. The release record records versions, measurement windows, validation and cleanup. The earlier local-only status below is superseded.

2026-10-21 — UI scaling, smaller profile pictures and status colours

D-100 refines R-102 to 56-pixel circular profile pictures and adds R-106/R-107: whole-interface scale in user settings and distinct voice-status/message-entry surfaces. The human selected local persistence, 75–200% and a 100% default. SPEC-005 records five-point steps, storage/error handling, proportional layout and menu placement; SPEC-019 retains the original 256-pixel stored thumbnail. Implemented locally. Validation passes: all 202 unit tests, the production build, full local browser integration, cross-domain direct-message/call integration and 22 specification structure/link checks. Browser evidence covers 75%, 125% and 200%, proportional pictures, anchored menus, reset/reload/window persistence, malformed and unavailable storage, sign-in, narrow 400/800-pixel windows, palette contrast/forced colours and encrypted direct-message sending at 200%. Visual review caught and corrected a squeezed settings pane at maximum scale in narrow windows. Existing voice, PTT, disconnect diagnostics, threads and group lifecycle regressions pass. Native hardware/OS interaction is not newly verified. Not deployed.

2026-10-21 — alpha.12 deployed: profiles, voice cues, PTT and diagnostics

D-094–D-099/R-099–R-105 are implemented and deployed. Alpha.12 adds channel access badges, revised people layout/filtering, server/channel PTT inheritance with the approved legacy migration, circular cropped profile pictures, account sound preferences, persistent unexpected-disconnect notices and bounded client/operator diagnostics under SPEC-019/020/021. The human explicitly authorised continued testing and deployment; the earlier temporary browser-test pause below is superseded.

All 199 unit tests, full local browser integration, cross-domain direct-call/browser checks, real workerd/SQLite integration, builds and 22 specification structure/link checks passed. Live Durable Object capability checks, exact client asset comparisons, media health/logging and public release pages passed. All three production Workers have 100% configured allocation; all 40 events in the bounded observed samples identify their intended version. The release record distinguishes those measurements and records the delayed control Durable Object propagation. The cause of earlier user-reported disconnects remains unconfirmed.

2026-10-21 — profile audio cues and visible disconnection reasons

D-097/R-103 adds four enabled-by-default sound switches and shared profile volume; SPEC-020 defines private account persistence, subtle local PTT cues and attendance baseline suppression. D-098/R-104 adds persistent accessible disconnection notices with available reasons, channel/time and manual rejoin guidance. Profile-only federation updates no longer invalidate voice permissions; current picture metadata propagates without exporting sound preferences.

Validation: 194 unit tests pass, along with TypeScript/build and 21 specification structure/link checks. Before stopping browser voice tests, profile upload/crop/save/remove, circular sidebar pictures, sound save/cross-client conflicts, encrypted audio, personal mute, public readable audio and room creation/movement passed. The direct-conversation browser run also passed compact actions, encrypted calls/text and temporary-group movement. The final broad browser run was deliberately stopped after the human reported unexplained live disconnections; it is incomplete, not a full pass. Later foreign-picture and disconnect-notice regressions pass unit coverage, but their final browser rerun and human listening check remain pending. Tests used isolated local/in-memory services, fresh secrets and fake capture; no production deployment was performed. No cause for the reported live disconnections is established. Local test workflow and outgoing-origin guards were tightened; see docs/deployment.md. These changes are not deployed.

2026-10-21 — inherited PTT duration and circular profile pictures

D-095/R-101 selects a 300-second server default with channel overrides and explicit migration of old 60-second channels to inheritance. SPEC-004/012 own values and schema-6 migration; client/server responsibilities are in SPEC-005/008. D-096/R-102 selects upload, crop, preview and removal of server-stored pictures with circular display at approximately 72 pixels; SPEC-019 records the bounded profile/resource contract. Implemented locally. Migration, permissions, persistence, profile resource lifecycle and conflict checks pass. Browser checks exercised crop/save/remove, circular rendering and cross-client sound settings. Not deployed.

2026-10-21 — channel access labels and people row ordering

D-094/R-099–R-100 request rounded green Private/red Public channel labels with softer fills, Friends exclusion from displayed Recent while preserving Server Members, and identity → icons → last-seen context ordering. SPEC-005/014 define presentation and unchanged encounter retention/clear behavior. The labels follow authoritative access independently of encryption. Implemented locally; compact people actions and direct-call browser checks pass, including Friends exclusion from Recent. Not deployed.

2026-10-20 — compact people actions and in-call participant picker

D-092/R-098 request phone/message icons and red/grey Friends hearts in the right sidebar, removal of its Group/Channel buttons, and Add people within an established call. SPEC-005/014/018 record the presentation refinement; consent, group retention, transcript isolation and explicit voice movement remain unchanged. D-093 authorizes the deployed alpha.11 refinement. Hosted encrypted DM/group audio and retained history pass; live assets match, and both changed Workers have 100% configured allocation and 100% of the bounded observed sample. The deployment record records versions, UTC windows, evidence and cleanup. TypeScript/production build, 19 specification structures, 18 focused voice unit tests and the cross-domain direct-conversation browser flow pass. The browser check covers phone/message actions, heart toggles, connected-call participant selection, explicit DM-to-group movement with rendered encrypted audio, retained history, and light/dark/narrow layouts. It exposed a destination-fence timing race during same-host foreign moves; the pending explicit join now retries only 409 voice_moving within the existing hard-mute window, with bounded-failure and cancellation coverage.

2026-10-20 — alpha.11 deployed and verified

D-091 authorizes deployment. Matching control/client, Windows/Linux downloads, website and Gentoo metadata are published. The persistent control object reports alpha.11 with identity and admission policy preserved; both changed Workers have 100% configured allocation and 100% of the bounded observed traffic sample. The relay image is unchanged. See the release record for UTC times, propagation, hashes, tests and cleanup.

2026-10-20 — direct conversations approved and implemented for alpha.11

D-090 approves the reviewed P-031/P-032/P-033 completion and explicitly authorizes implementation. SPEC-018 revision 1.0 records canonical mandatory-E2EE DMs, first-contact acceptance, answer-bound calls, invited temporary groups, creator-selected immutable retention, device presence, block revocation and schema-5 expiry. SPEC-005/008/014 identify the new primary people action, directory projection and account-scoped UI. This was initially an unreleased working-tree build; D-091 subsequently authorized its verified deployment. Validation is recorded in the implementation report.

2026-10-20 — first-contact acceptance confirmed

D-089/R-097 answer Q-59: recipient acceptance is required before ordinary direct messages or ringing. This applies to Friends, Recent, Server Members, exact account addresses and direct API calls; a saved contact or shared server cannot bypass the gate. P-033 is selected to that scope, and SPEC-005/008/018 reflect it. Remaining lifecycle, blocking, hosting and retention-control details stay proposed; this answer is not recorded as blanket approval of those designs. No application code or deployment changes are included in this decision update.

2026-10-20 — direct conversations, Server Members and temporary groups

D-087/R-093–R-095 request direct text and one-to-one calling from Friends/Recent, a Server Members directory and easy formation of temporary groups. SPEC-018/P-031–P-033 draft canonical encrypted conversations, explicit call acceptance, separate invited groups, scoped federation and contact policy. SPEC-005/008 own the proposed interface and server projection; current application behavior is unchanged.

D-088/R-096 answer Q-58 by retaining group text after temporary voice ends, with configurable history defaulting to four hours and capped at one year. This rejects the initially proposed erase-on-close/no-recovery policy. The revised draft proposes immutable creation-time retention measured from each message's acceptance, matching expiry in device/recovery copies, and read-only access after group closure. Q-59's first-contact policy remains unanswered. No build, publication or deployment is included in this specification review.

2026-10-20 — approved alpha.10 direct voice and relay fan-out

D-086 explicitly approves the reviewed security and routing choices and authorizes build/deployment. SPEC-017 supersedes relay-only private E2EE routing and per-recipient media encryption with authenticated direct paths, conforming-receiver enforcement, temporary signed sender keys and one relay upload. Q-56/Q-57 are resolved; the prior proposal below is historical. The alpha.10 release record records validation and rollout evidence.

2026-10-20 — peer-to-peer voice and single-upload relay proposal

D-085/R-090–R-092 record the requested successor to alpha.9: prefer participant P2P for encrypted voice, retain relay routing in public channels, and upload each media frame only once for relay fan-out. The review proposes per-listener direct/fallback routing and temporary signed sender-key media. P-029/P-030 and Q-56/Q-57 retain the unapproved address-privacy/moderation and cryptographic choices. The active application, deployment, relay-enforced hard-mute contract and SPEC-016 pairwise media profile are unchanged by this documentation update.

2026-10-20 — Opus, adaptive buffering and local diagnostics

D-084 selects the approved voice-quality recommendations #1–#3 and the human's 200 ms buffering limit. SPEC-004 revision 0.8 replaces the PCM/fixed-buffer profile with bounded Opus recovery and adaptive playout; SPEC-009 revision 0.8 defines authenticated talkspurt envelopes and coordinated upgrade rejection. SPEC-005/008 own local diagnostics and host/relay responsibilities. SPEC-016 revision 0.3 preserves key lifetimes while referencing the Opus envelope. Nearer relay placement and Cloudflare Realtime SFU remain deferred. The implementation review records validation and deployment evidence; the earlier investigation below is historical. Validated source 9cd1e354 is live in the shared client/control service and relay; exact served-asset hashes, Worker versions and disabled test-fixture cleanup are recorded in the review.

2026-10-20 — encrypted join race and voice-quality investigation

SPEC-016 revision 0.2 clarifies that initial key publication, like renewal, recovers a concurrent authority revision through authenticated attendance refresh while keeping audio gated. The voice-quality investigation records the reproduced defect, regression evidence, real Cloudflare measurements and worklet sensitivity tests. Opus, adaptive buffering, media-region comparisons and Cloudflare Realtime SFU remain proposals; the fixed media profile and hosting policy are unchanged. The validated join fix was published as d16e8de and deployed to the shared client; the review records the exact production version and matching asset hashes.

2026-10-20 — temporary voice keys and text protocol evaluation

D-081 accepts separate device identity, communication rotation and retention, preserving existing readable history and recovery. D-082 selects five-minute E2EE voice keys and at most two seconds of receive overlap. SPEC-016 defines the reviewed voice profile, capability migration, signed public offers, in-memory secret retirement and failure behaviour. SPEC-003/004/005/008/009 reference its scoped replacement of static encrypted voice. The protocol review compares MLS implementations and pairwise ratchets; text migration and archive-key policy remain proposed.

D-083 authorizes production activation of the validated update. The control service and shared client were deployed and verified on 2026-10-20; the protocol review records the exact version, assets and read-only live checks. The relay and installers were not replaced.

2026-10-19 — message-body hover controls

D-080 moves Shared history, Reply and thread voice controls to the body inset and reveals them on that message body’s hover. SPEC-013 revision 0.3 preserves keyboard/touch access, reply counts, active call status and stable message positions. This shared-interface change requires no new installer or server policy change.

2026-10-19 — alpha.9 multi-server runtime and release

SPEC-015 revision 0.3 selects the technical completion profile for D-072/D-076–D-078: destination-bound visitor sessions and media, current home-device inspection, independent account/connection contexts, owner-controlled public admission, shortcut consent/retirement, and home-authoritative voice movement. Foreign E2EE and eligible linked-device history copying are included. Client fixtures verify one-button joins, target-local accounts, expired-session reconnection, foreign Friends, independent drafts/history and posting pause/recovery. The two-relay fixture verifies actual E2EE audio and explicit movement after a 30-second renewal soak. Independent hosted authorities also passed shortcut joining, E2EE text/audio, admission closure, revocation and shortcut retirement. D-079 explicitly approves the production cutover with public visitor and local-registration controls remaining closed. Publication, deployment verification and package identifiers are recorded in the alpha.9 release report.

2026-10-19 — multi-server decisions and connection foundations

D-077 retains existing visitor memberships when public joining closes. D-078 pauses affected E2EE posting when a home authority cannot confirm device approval, without hiding readable history or blocking other members' server-readable posts. SPEC-015 refines the completion profile and selects independent API destinations, domain-qualified vault/trust indexes, public-only server discovery, bounded directory delegation and fresh signed-roster validation. SPEC-008 owns the independent public visitor/local registration policy and persisted server identity. These foundations are tested components; the selector, exchange integration, coordinator publication and cross-host voice/E2EE flow remain unfinished and are not advertised or deployed.

D-070/D-071/D-073–D-075 move Back to the top-left, add personal account-wide Friends and client-local Recent, restore a subdued green transmitting bar, add permission-checked channel renaming, and use muted regular-weight chat identities above indented text. SPEC-014 defines private contacts, encounter rules, bounded storage and account isolation. SPEC-012 adds name updates to the existing settings command.

D-072/R-085/R-086 request multiple server connections, visitor authentication, configurable public joins and coordinator links pasted directly into the client. SPEC-015 records the concrete proposed architecture and D-076 selection of foreign E2EE in the initial release and separate public/local-registration controls; it does not enable federation, change identity domains or migrate the deployment.

2026-10-19 — conversations and isolated thread voice

D-067–D-069/R-079–R-082 add explicit reactivation-to-join, grouped same-account messages, distinct own-message colours, inline persistent replies and separate thread calls. SPEC-013 owns the additive signed reply references and internal call scopes; parent membership, encryption, moderation and one-active-call rules remain authoritative. Replies preserve retention and admission boundaries. Existing desktop packages load the updated shared client.

2026-10-19 — softer application light/dark palettes

D-066 revises R-078: use application colours based on the earlier blue-grey/lavender palette, with a lighter counterpart selected automatically by system appearance. Exact system and KDE RGB inheritance from D-065 is superseded. The compact interface remains unchanged; forced-colour accessibility retains system roles. The shared interface consumes only the existing desktop appearance hint, so alpha.8 packages remain compatible.

2026-10-19 — approved compact interface and system colours

D-065/R-077/R-078 approve the reviewed room tree, remove the separate member sidebar, place moderator actions below personal actions in one context menu, and replace application dialogs with main-workspace settings and inline confirmations. Member management is approved for use and later feedback. SPEC-005 replaces the fixed palette with system colours and a read-only KDE desktop adapter; SPEC-008/012 define the permission-filtered voice-tree projection within existing synchronization. No media, membership, history or permission policy changes.

D-064 adds keyboard-accessible participant context controls for existing personal volume/mute and self-service account nicknames. SPEC-005 owns UI behavior, SPEC-008 canonical account storage/validation, and SPEC-009 the additive revision-checked command. Names stay separate from full account identity and do not change media authority.

2026-10-19 — security, synchronization and keyboard configuration

D-063 authorizes the overnight audit and implementation of improvements with predominantly positive effects. SPEC-005 owns grouped user/server/channel/member panels and keyboard operation; SPEC-008/012 add authorized batched synchronization and pending account invitation cancellation; SPEC-011 describes the bounded verification cache; SPEC-004 preserves resource and moderation limits while hardening the relay. SPEC-002 retains published download manifests for existing ebuilds. The audit separates implemented fixes from significant trade-offs, and the alpha.7 release records validation and publication.

2026-10-19 — bounded voice buffering

D-062 refines R-031 following choppy KDE, Windows and web calls, especially at the start of speech. Complete the shared receiver with ordered playout and a startup target inside the existing cap; preserve capture, encryption, mute and hosting policy. See the review.

2026-10-19 — automatic Gentoo distfile fetching

D-061 replaces manual staging for the current ebuild with a verified versioned HTTPS download through the existing Cloudflare service. SPEC-005 owns Portage behavior and clean-cache verification; SPEC-002/008 extend the existing manifest allowlist to the Linux archive without changing the application payload.

2026-10-19 — Alpha.6 implementation

D-058 selects qualified identities/discovery and the room-creation completion profile. D-059 requests existing-device code approval and encrypted history sharing; D-060 requires password plus recovery key. SPEC-010/011/012 supersede the corresponding root-only, single-device and singleton-room restrictions. The implementation preserves the existing identity domain and original lobby data, adds local account profiles, and retains one active voice client with explicit movement. The alpha.6 release report records verification and remaining human/platform gates.

2026-10-19 — Qualified identities, discovery and room approval

Recorded D-056/D-057 and R-074–R-076: qualified usernames, local shorthand, host/path-independent discovery, and preservation of existing @sloppyvoice.com accounts. The next independent identity domain remains unselected.
Drafted SPEC-010/P-028 with URI/SRV, authenticated identity-origin HTTPS, explicit closed federation, conservative parsing, path routing, configuration and security/compatibility tests. Component responsibilities remain in SPEC-005/008. New runtime behavior remains proposed.
Published and verified current-domain URI discovery and an explicit no-SRV-service marker. A trial SRV pointing at the Worker was rewritten by Cloudflare to an unreachable AAAA 100:: target; corrected it rather than publishing a broken route or disabling proxying. See the DNS record.
Recorded Q-47 preset approval and P-027 partial acceptance, moved proposed room-creation schema/limits into their topic specifications without promoting new numeric values to approved, and added A-39/A-40. Meetings and exact room wire/storage shapes remain deferred/unresolved as stated.
No application build, account migration, new instance or federation activation is included.

2026-10-19 — Room creation request and review

Recorded D-055/R-073: administrators need a way to create rooms and define their applicable specification details.
Drafted P-027 and the room creation review, covering fields/defaults, code-free access grants, separate text/voice targets, room isolation, legacy migration and verification.
The human confirmed owner-only creation under Q-48; Q-47 awaits the preset-scope answer. No proposed meeting behavior, general role hierarchy or numeric room limit is treated as accepted by this review. No application or deployment changes are included.

2026-10-19 — background voice and optional XWayland mouse input

D-053 permits the optional XInput2 helper for KDE side buttons while the application and session remain Wayland. SPEC-005 owns explicit source selection, dependencies, forwarding prerequisites and release safety.
D-054 extends the initial hosted generation to 60 minutes, with warning/closing admission at 55 minutes and 70-minute TURN credentials. SPEC-002 owns timings; SPEC-004 retains short forwarding leases and explicit rejoin.
Alpha.5 adds native recording for the XWayland source, keeping capture and saved-button numbering consistent. A physical side-button capture/release passed; broader foreground/game acceptance remains pending.
Alpha.5 disables desktop background timer throttling and publishes disconnect status before network cleanup. The Cloudflare gateway configures its inactivity timeout once per instance/start instead of blocking every renewal on the management API. Added native button/deadline, immediate-status, hidden-desktop and hosted-soak regression coverage. Physical input, full-hour human listening and Brisbane latency remain separate gates.

Invitation and lobby access amendment — 2026-10-18

D-052 adds R-070–R-072 and A-38. Review and implement server invitations followed by direct lobby access grants; preserve membership-based history and legacy room keys, with revocation invalidating outstanding keys. Move owner creation to the one-time /setup route, keep ordinary account sign-in at /, and normalize full invitation URLs or raw keys in the shared client. Preserve existing device keys, sessions, owner identity and storage. See the review and validation record.

2026-10-18 — Public website and installer distribution

Recorded D-051: publish a Cloudflare-hosted homepage and Windows installer at www.sloppyvoice.com/download. SPEC-002 owns isolated site/release configuration, SPEC-005 owns the public page, and SPEC-008 owns streaming and resumable download behavior.
Built the responsive site, checksum output, private EU R2 binding and allowlisted Worker download handler. Added six download/range/failure-path tests and verified the complete installer through local Workers/R2.
The human enabled R2 separately. Published the site and installer using EU storage and custom domains; the complete public download matches the approved SHA-256. See the website report.

2026-10-18 — Alpha.3 deployment and Windows installer

Recorded D-050's web deployment, KDE ebuild, Windows update and shareable installer request. SPEC-002 owns the build-supplied public origin and override precedence; SPEC-005 owns per-user installation and retained device data.
Deployed the PTT web interface to the existing Cloudflare control Worker, preserving EU authority, owner/bootstrap state and media configuration. Live assets match the local build.
Added pinned NSIS installer tooling, alpha.3 desktop packages and the local-overlay ebuild. Recorded automated checks, Wine's process-check fallback limitation and outstanding physical-platform acceptance in the release report.

2026-10-18 — Implementation phase and alpha.2 PTT

D-049 explicitly moves the project into application implementation and authorises the GitHub update; corrected the stale initial-phase instruction in AGENTS.md.
Implemented the reviewed PTT recorder, per-client versioned bindings and migration, focused browser mouse/Gamepad support, native input adapters and helper watchdog. Linux observes only the selected readable mouse/joystick device and does not alter access permissions.
Added unit and browser fixtures for binding capture/persistence, neutral-state and disconnect behavior; retained encrypted voice/mute/lease regression coverage. Built alpha.2 Linux and Windows packages. Physical ProtoArc/joystick and game-focus validation remain pending.
Linked-device/recovery mechanisms remain unimplemented with their material choices tracked; the phase correction is not a claim of completed multi-device support. See the PTT implementation report.

2026-10-18 — Linked accounts, recovery and PTT input review

Recorded explicit D-044–D-048 and R-063–R-069: one account across KDE/Windows/web, common permissions and desired shared history, separate recovery key, one active voice client with explicit move, and press-to-bind keyboard/mouse/joystick PTT.
Recorded ProtoArc mouse button 4 as the immediate hardware fixture on both desktop targets; joystick testing may wait for the device, but must pass before leaving testing.
Drafted P-024/P-025 and the linked-device/PTT reviews. Kept shared security/media/data contracts in SPEC-003/004/006, client workflows in SPEC-005 and server authority in SPEC-008. New mechanisms/defaults remain proposed or OPEN; D-024's first-build delegation is not treated as approval of this new feature implementation.
Added A-33–A-37 and Q-42–Q-45 for trust/history/recovery, migration/limits, voice handover and native input feasibility. Clarified that several signed-in devices do not permit simultaneous voice publishers under D-046.
Preserved the deployed V1 single-device/no-recovery behavior and keyboard-only selector in README, SPEC-009 and deployment instructions. No application code, credentials, overlay package or Cloudflare deployment was changed by this review.

2026-10-18 — Production voice activation

The human created the separate Sloppy Voice production media TURN key. Saved its secret privately, installed it on the production media Worker and verified bounded credential issuance without logging credential values.
Deployed the tested D-043 image and enabled both production Workers at chat.sloppyvoice.com and media.sloppyvoice.com. Live control confirmation at 21:39:50 UTC reports the enabled Cloudflare adapter, existing owner and EU jurisdiction. The rollout preserved the existing namespace, account data and authentication secrets.
Verified anonymous preparation and unsigned offers are rejected; the initial production Container is stopped at mad07 until authenticated startup. Test media remains disabled. Recorded the Durable Object rollout delay and verification in the deployment guide and redacted artifact.
Human production calls, Brisbane measurements, physical desktop PTT, full-duration soak and performance/security acceptance remain separate checks.

2026-10-18 — Geographic placement and hosted media evidence

Recorded D-040–D-042: Canada → EU → US hosting preference, Brisbane latency fixtures, and an eventual service with regional media flexibility. A single relay remains explicitly acceptable for initial testing; selection, migration and failover mechanisms stay OPEN under Q-41.
Selected the supported EU Durable Object namespace and Container jurisdiction for this deployment. Verified owner bootstrap was unused before the control cutover, deployed it, and confirmed X-Sloppy-Control-Jurisdiction: eu on the live API. The probe provider record reports mad01. Worker ingress, TURN routing and provider metadata remain outside that placement claim.
Fixed the probe's internal forwarding URL to use the Container's HTTP listener while retaining public HTTPS signalling, token audience and Origin. Added regression coverage for the scheme, request body and removal of the probe gate header.
Hosted TLS/TURN and UDP/TURN fixtures exchange authenticated ciphertext and pass mute, revocation and lease-expiry cases. Setup now renews each admitted peer while the other connects; every grant retains its three-second lifetime. The strengthened harness counts continued sender attempts, stops renewal explicitly for enforcement cases and stops the Container afterward. UDP gathering proceeds on a valid relay candidate rather than waiting for unused interfaces.
Drafted a separate first-cohort lifecycle policy for review: bounded sessions with explicit rejoin versus uninterrupted credential renewal. Its defaults and user-visible behavior remain PROPOSED. Production integration and the human/platform/Brisbane performance gates are not marked complete.

2026-10-18 — Apache 2.0 licensing

Recorded D-035 and R-061/R-062 after the human accepted Apache 2.0 for original code, specifications, documentation and examples, with independent implementations permitted under any licence.
Added the unmodified licence and project attribution, documented scope and existing file exceptions, and resolved Q-30's licence choice. Extension/revision governance remains open; no separate protocol-wide patent commitment was added.
Aligned npm and desktop package metadata, desktop archive licence inclusion, and the Gentoo application licence expression. Preserved explicit third-party licences/notices and the ebuild source's GPLv2 header.
Verified the official licence text byte-for-byte, specification structure/links, metadata and packaging syntax. Rebuilt and inspected Linux/Windows archives: project licence/attribution and metadata are present, and Electron/Chromium/godbus notices match the previous copies. Refreshed the repository's Gentoo Manifest and local archive checksums. Fixed replacement of a read-only godbus notice during repeat packaging.
The earlier unselected-licence packaging notes below are historical; D-035 supersedes that temporary state. Licence selection does not establish publication, platform acceptance or independent interoperability.

2026-10-18 — Cloudflare deployment preparation

Recorded D-037–D-039: approved Container/TURN access, human-enabled Realtime subscription, and an account-wide US$5 usage alert. Wrangler consent and the dedicated probe TURN key are complete. Updated the existing default budget alert and verified the US$5 threshold; it does not cap billing.
Assembled and validated the credential-free scratch image without a Docker daemon; uploaded its pinned digest and deployed the isolated probe. Initial hosted readiness failed; cleanup and provider scheduling diagnostics are recorded in the media review. Fresh fixtures now require authenticated stop/closure verification and archive previous evidence.
Deployed the independent account/text service at chat.sloppyvoice.com after a fresh workerd/SQLite integration pass. Verified HTTPS assets, security headers, domain identity and unused owner bootstrap; the owner setup page renders. Production voice remains pending.
Recorded D-036: the human enabled Workers Paid; verified Paid as the account's current plan. Container/TURN access and the image builder remain deployment prerequisites.
Recorded D-034 accepting Containers plus TURN direction for testing; specified a separate authenticated, expiring probe with one Container and unchanged Go/Pion forwarding checks. Production lifecycle and billing remain explicit gates.
Implemented the isolated probe, static unprivileged image context, private credential preparation and hosted two-browser harness. Local race tests pass through TURN/UDP and TURN/TCP for revocation and control-partition expiry; native deadline and Worker access/lifetime tests pass. Existing browser encryption/moderation integration passes. Hosted/TLS/performance validation is pending Workers Paid, image assembly and provider permissions.
Recorded D-033 authorising deployment within sloppyvoice.com.
Prepared a separate Wrangler configuration for chat.sloppyvoice.com, with sloppyvoice.com as the identity domain and media.sloppyvoice.com reserved for the existing relay.
Confirmed that Cloudflare Containers cannot accept the inbound UDP required by the selected relay. Relay hosting remains unresolved; preparation does not establish a live deployment or working hosted voice.
The human selected entirely Cloudflare hosting and requested media review before changes. Added proposed P-023: Containers plus Cloudflare TURN, with the existing Go/Pion relay remaining the forwarding authority. Recorded the Realtime SFU lease gap and validation/billing gates without changing active media requirements.

2026-10-18 — Sloppy Voice and Gentoo packaging

Recorded D-032: Sloppy Voice / sloppy-voice, the GitHub repository rename and a local Gentoo ebuild.
Updated application branding, native/distribution names, remote references and the desktop origin variable. Preserved legacy origin, protocol and encrypted device storage compatibility.
Specified the client-only binary ebuild, Wayland/KWallet launcher, per-user origin file and staged validation. The licence decision and real-platform acceptance remain open.

2026-10-18 — First alpha implementation

Implemented the approved V1 profile in a shared React/Electron client, Workers/Node SQLite control service and Go WebRTC relay, with Wayland/Windows PTT helpers.
Built Linux/Windows portable desktop packages and recorded automated protocol, SQLite, native relay, browser and workerd evidence in the first-build report.
Added bounded ciphertext/membership quotas and documented invitation derivation, deployment source precedence and desktop origin configuration in their canonical specification owners.
Kept the real human cohort, KDE/Windows physical input, clean/impaired latency measurements, hosted deployment and independent security review explicitly unverified. This is an alpha build, not full V1 acceptance.

2026-10-18 — Revision 0.4, delegated V1 resolution

Recorded explicit human delegation in D-024 and scoped technical decisions D-025–D-031. Confirmed product requirements remain unchanged.
Added SPEC-009 and canonical V1 sections for deployment, endpoint encryption/trust, authentication, media, clients, durability, permissions and measurable validation. Later OPEN decisions remain scoped to later features.
Selected a dedicated lease-enforcing WebRTC relay and libsodium per-recipient encryption; documented bandwidth and trust/forward-secrecy limits without claiming provider, platform or human validation.

2026-10-18 — First-build preparation

Recorded the human's request to create the first build; implementation authority is distinct from approval of unresolved behavioural or architectural choices.
Verified the README, numbered specifications and decision/question registers against the GitHub repository's master files at the local draft 0.3 baseline.
Added a supporting protocol/candidate assessment and build-prerequisite review. Recommendations remain unapproved; no configuration default, protocol, dependency or application implementation was selected.

2026-10-18 — Draft 0.3

Incorporated all 13 findings from the draft 0.2 review into the numbered specifications, with a disposition table in the historical review report. The human requested this amendment pass; remaining technical choices/defaults are still PROPOSED or OPEN, and no application implementation is authorised.
Recorded D-015–D-023 and R-053–R-060: fixed public/private access bundles; first-admission history; unresolved optional bot classification with ordinary-account automation preserved; explicit immutable room encryption choice; all-audio moderator mute; focused single-device V1; administrator account invitations/passwords; no V1 lost-key history recovery; returning-member history across earlier membership periods but excluding absences.
Refined R-016 under D-017, replacing both the earlier assumption of a selected distinct bot class and the security document's selected metadata representation with an explicit open classification decision. Preserved the human's R-005 wording.
Updated SPEC-001's room model/configuration and SPEC-003's creation, device, trust, membership and epoch contracts. Specified persistent/live/device distinctions, future-key exclusion, failure during rekey, and separate local login, foreign session, admission-token and active-forwarding-lease lifetimes. Crypto coordination and wire details remain open.
Updated SPEC-004/005 to separate text navigation from active voice-session changes and to specify the confirmed moderator audio scope. Added client presentation of incomplete enforcement and historical encrypted-operation verification without duplicating role authority.
Updated SPEC-002/008 with host-domain policy jurisdiction, browser/federation routing obligations, active-media adapter requirements and pending/effective/failed/superseded enforcement. General permission precedence, additional home-domain restrictions and hard timing bounds remain open.
Updated SPEC-006/008 with recoverable commit of mutations/results/external work, bounded retry/uniqueness rules, historical authorisation evidence, membership-interval filtering and fenced stale-backup recovery. Storage, validity, evidence and restore mechanisms remain to be selected.
Refined SPEC-000's schema/state classification rules. Replaced draft room.visibility with room.access_type; split auth.session_lifetime_seconds; separated admission grants from forwarding leases; removed generic crypto-profile, active-account, endpoint-record, credential-store and independent V1 history knobs from configuration inventories; replaced the loose deduplication-window property and separated account/room invitation lifetimes.
Updated SPEC-007 with per-scenario milestone applicability, A-27–A-32, coverage for all 60 requirements and separate hard-versus-percentile revocation measurement. V1 does not falsely require multi-device publishing; optional web delivery must conform whenever present. Exact performance thresholds/fixtures remain unapproved.
Updated the README, question and decision registers, resolved P-008 through D-020, and recorded P-011–P-022 for the remaining review mechanisms. This revision amends the corresponding draft 0.2 sections; accepted decisions supersede earlier conflicting wording only to the explicit scope stated above.
Structural validation passed for all nine numbered specifications: required sections/acceptance bullets, 93 local links across 16 Markdown files, 60 covered requirements, 32 stage-mapped scenarios, 23 decision IDs, 22 proposal IDs and unique ownership of 156 configuration properties. The earlier R-001–R-052 text is preserved except for R-016's explicit D-017 refinement. These checks do not establish runtime/security conformance.
No application code, test harness, deployment, provider evaluation or benchmark was implemented in this amendment pass.

2026-10-18 — Draft 0.2

Added mandatory Configuration, Testing, and Acceptance criteria sections to every numbered specification, with topic-specific properties/defaults, unit-test coverage and observable acceptance bullets.
Recorded the section requirements as R-049–R-051/D-013 and made them part of the authoring instructions for future specifications.
Explicitly distinguished accepted defaults, proposed defaults, required values with no default, and unresolved values; documented that unresolved defaults must be resolved before affected implementation.
Converted the validation performance proposals into a test-harness configuration inventory, preserving their proposed status and separating them from application runtime defaults.
Recorded separate client/server specifications as R-052/D-014. Renamed SPEC-005 to 005-clients.md and moved server authorisation, role/bootstrap configuration, and authoritative administrative processing into the new SPEC-008 008-server.md.
Updated the index, ownership links, requirement coverage, and acceptance scenarios A-25/A-26. Existing product requirements and human edits remain in place; no application code or test harness was implemented.

2026-10-18 — Draft 0.1

Created the specification-driven workflow, confirmed requirement register, architecture, identity/security, media, clients/permissions, data/operations, and validation documents.
Captured the initial brief as R-001–R-034.
Recorded first-round decisions: managed and self-hosted media, mandatory E2EE direct communication with configurable room encryption, and one hosting domain per room.
Recorded second-round decisions: one cross-platform interface, evaluate existing protocols first, and a gaming-first usable milestone.
Recorded third-round decisions: 3–10 testers in one voice room, one domain in test version 1 and a second domain in test version 2, no initial screen-sharing requirement, encryption defaults, and shared/personal gain precedence with relay-enforced hard mute.
Recorded fourth-round decisions: KDE Wayland and Windows testers, Wayland-only Linux, later macOS support, a strongly desired first-version web client, and basic room text alongside voice. Added the browser/global-PTT question.
Recorded fifth-round decision: web PTT is focus-only and stops on focus loss; desktop clients retain the global-PTT requirement. Updated the requirement register, client/media behaviour, and acceptance coverage together.
Added primary-source product/technical references, an initial protocol fit comparison, proposed acceptance scenarios, and a prioritised review backlog.
Left detailed designs explicitly proposed. No application code, deployment, or test results are claimed.

2026-10-18 — Bounded Cloudflare alpha policy (D-043)

Recorded approval of 50-minute shared relay generations, the five-minute closing warning/admission margin and explicit rejoin. Moved active contracts into their owning specifications.
Added authenticated preparation before live attendance, cancellation/expiry and attempt limits, generation-bound authority, separate production TURN configuration and a native absolute deadline.
Added deterministic lifecycle, RPC, provider failure, native and isolated hosted application tests. Production activation remains gated on hosted results and the dedicated production credential; human/platform/Brisbane validation remains separate.

R-113 and A-46 record independently expanded server/account branches, clearer containment and responsive automatic/manual sidebar widths.
The human confirmed per-device manual-width persistence with independent reset to automatic; SPEC-005 owns configuration, bounds, failure behavior and tests.
Existing server access, explicit voice movement and device UI scale remain unchanged. Implementation, 225 unit checks, full browser regression, focused multi-server/sidebar checks, multi-server voice, build and specification validation pass. See the implementation record; D-111 and the alpha.17 release entry above record the subsequent deployment.

2026-10-24 — Android client request

D-152 records the Android build/emulator request and explicit first-build background-call requirement. SPEC-005 defines its native integration/security/lifecycle profile and test gates; SPEC-004 cross-references the scoped background activation exception. Implementation and platform evidence are recorded separately.

2026-10-24 — Portable Windows download (D-155)

Build and publish the existing Windows x64 portable ZIP with explicit extract/run and normal-profile persistence instructions. SPEC-002 adds its independently versioned required release manifest; SPEC-005 defines presentation/package acceptance; SPEC-008 extends exact manifest selection. Existing installer/Linux downloads remain immutable. See validation and publication evidence.

2026-10-24 — Browser key-storage disclosure (D-158)

Homepage and download browser-entry copy now explicitly requires local storage on the device for encryption keys, matching the existing SPEC-003 IndexedDB vault. No application behavior or configuration changes.

2026-10-27 — Public usability and operations increment

D-172–D-180 record the human's requested pins/conditional notices, statistics, handsets, public convenience mode, settings/PTT behavior, voice additions, Wine capture, directory and update offers. Explicit answers select admin/moderator pins, encryption-preserving public mode and automatic verified owner opt-in listings. SPEC-005/008/013/015/016/021 describe scoped behavior, configuration, tests and acceptance. Pin history entitlement remains OPEN; other validated outcomes are prepared as alpha.45. See the increment review for delivery evidence and limits.

2026-11-01: SPEC-005 0.111 records the native call runtime port of existing explicit cross-source movement, immutable confirmation ownership and pending-command reconciliation; D-126 automatic membership/Join-as remains required.

2026-11-01: SPEC-005 0.112 specifies the native prepared-membership port for existing D-126 Join-as, including unchanged visible view and account-owned exact pending commands across chooser closure/restart.

2026-11-01: SPEC-005 0.113 records native D-126 Join-as membership/atomic selection and attendance-bound same-channel voice continuation through authentication.

2026-11-01: SPEC-005 0.114 specifies the native purpose-bound conversation-admission port; durable foreign-conversation control/text/calls remain required.

2026-11-01: SPEC-005 0.115 records native conversation-only storage scope and exclusion from ordinary browsing/selection/status reads.

2026-11-01: SPEC-005 0.116 specifies immutable borrowing of an existing visitor endpoint for private conversations without ordinary navigation or credential rotation.

2026-11-01: SPEC-005 0.117 specifies native creation and immutable reuse of hidden conversation Host sessions without ordinary-server navigation.

2026-11-01: SPEC-005 0.118 separates strict native conversation-summary validation from the displayed Home view, retaining canonical direct authority and fixed group-host bindings.

SPEC-005 0.119: document immutable native conversation-session dispatch, bounded ownership and mandatory encrypted state; foreign control/UI integration remains in progress.

SPEC-005 0.120: specify prepared foreign-conversation views and single-writer, original-session protected command reconciliation.

SPEC-005 0.121: specify bounded foreign inbox fetching, qualified summary/group scope and navigation-independent foreign group presence.

SPEC-005 0.122: specify exact qualified conversation call ownership through the native foreign voice context.

SPEC-005 0.123: specify fixed-account cross-authority contact capability preparation and exact Host group invitation dispatch.

SPEC-005 0.124: match existing explicit conversation reconnect with atomic same-binding credential adoption and unchanged pending-operation retry; forbid automatic call credential handover.