Embedded documentation aligned
Build 89 replaces the package because the User Guide, Privacy Notice, Support terms, Supported Platforms, and Controlled Beta Agreement embedded in Build 88 did not match the final approved documents.
AirchainPrepared 22 August 2026 · Build 89
0.9.0 Beta 71
Build 89 is the documentation-only replacement for Build 88. It aligns every embedded operator, privacy, support, platform, and beta-agreement document while retaining the accepted playout implementation and safety gates.
Release highlights
Correct package.
Same runtime.
These highlights distinguish the Build 89 documentation correction from the retained Build 88 runtime work. The complete Release Notes and Known Issues documents shipped inside Airchain remain the detailed technical record.
Runtime behavior retained
The playout implementation, production views, Remote protocol 14, station-profile format 4, and Build 88 runtime acceptance focus are unchanged; Build 89 advances the signed package identity so the corrected bundle remains unambiguous.
Durable occurrence timing
Exact queue starts and logical handoffs are remapped by durable occurrence whenever a structural edit keeps a row.
Bounded suffix rebuilds
Airchain preserves the finite immutable timing prefix and recalculates only the suffix whose predecessor chain may have changed. An invalid prefix fails safely into the complete timing rebuild.
Live queue responsiveness
The bounded path now covers corrective Soft Sync compaction and off-main imported-schedule reconciliation for accumulated 7,000-row queues without weakening atomic queue, target, successor, or protected-refresh checks.
Focused diagnostics
queue_timeline_recalculated records requested and actual start, preserved and rebuilt row counts, total queue size, and elapsed work for rebuilds lasting at least 25 ms.
Controlled-beta readiness
The candidate advances to Beta 71 / Build 89 while retaining Remote protocol 14, station-profile format 4, affirmative tester acceptance, and the notarized direct-distribution package gate.
Build 89 verification
The package and
runtime to prove.
Package identity
Confirm About Airchain, Copy Support Information, the DMG name, signed update envelope, and every embedded Help document identify Beta 71 / Build 89.
Queue fixture
Accumulate at least 7,000 rows with at least 900 future rows.
Corrective cycles
Repeat five corrective Soft Sync cycles across removal, tail-removal, and reorder cases.
Live refresh
Complete at least three automatic live refreshes while preserving authored order and exact occurrence identity.
Required result
No ui_main_thread_stall, preparation or scheduling miss, target/successor identity change, or audible timing discontinuity.
Operational known issues
Boundaries to know before air.
Review every applicable boundary below and the complete in-app Known Issues document before installing or returning a test machine to air.
Remote is experimental
Use the same protocol-14 build on both Macs, keep the service on a trusted LAN or private VPN, and never expose its TCP service directly to the public internet.
Profile compatibility is deliberate
Format 4 carries Downbeat timing and requires an explicit Home timezone. Older builds limited to format 3 reject it; older profiles may require review during import.
Operational mutations are bounded
Local and Remote Stack commands, clipboard work, and batch catalog edits or deletions are limited to 10,000 items. Larger or malformed actions are rejected rather than split.
Stack clipboard is installation-private
Copied events are valid only for the originating Airchain installation and station. Cross-Mac, cross-station, legacy, or malformed clipboard data is rejected.
Playback Log coverage is partial
Daily Playback Logs record observed occurrences from the point the feature runs. They do not backfill History, prove continuous application or output uptime, or establish that an empty day was quiet.
Playback Logs need a retention plan
The Studio-local ledger and matching .tsv/.tsv.manifest.json exports have no automatic pruning, may contain sensitive station, path, and timing details, and are not mirrored to Remote.
Exports are evidence, not reconciliation
The canonical TSV includes aired, non-aired, system, and exception evidence. Keep its matching manifest with it and do not treat the complete TSV as a scheduler reconciliation feed.
Missing Audio remains in authored order
Supported but unavailable media is shown as MISSING and skipped at airtime while AUTO continues when safe. Long runs, a Time Sync, an unready one-shot, a missing-only tail, or invalid structure can still hold or reject work.
Missing Audio validation is Studio-local
Remote mirrors the authoritative report read-only, but only a completed Studio audit can establish zero affected occurrences. Pending, disconnected, or stale validation is not a clean result.
Downbeat alignment has defined limits
Alignment applies only to an ordinary audible Song boundary with valid markers and enough lead. Other rows and transitions retain established Cue-In timing rather than partially shifting audio.
Home timezone must be canonical
Use an IANA timezone from Settings, not a short abbreviation or fixed offset. Cold starts require a saved valid Home timezone and reviewed stack before stopped transport can open.
Clock changes require review
A Home timezone change applies only while stopped, invalidates prior wall-clock appointments, and can require a fresh imported schedule or explicit acceptance of the remaining stack as untimed.
Repeated civil time can be ambiguous
A stamped schedule line during a fall-back repeated hour cannot identify the first or second occurrence, so Airchain rejects it rather than guessing.
Fail-closed Sync recovery can wait
When exact device-owned target, successor, or continuity evidence is unavailable, Airchain preserves committed audio and requests preparation instead of destructively rebuilding or guessing.
Remote outcomes can be unknown
Switching studios cancels unfinished work. If a reply is lost after submission, verify the authoritative Studio state before retrying so a completed mutation is not duplicated.
Listener monitoring is diagnostic
Public-stream monitoring can detect interruptions but does not establish a service-level guarantee or identify which downstream system caused an outage.
Updates are deliberate
Check for Updates requires the release-specific HTTPS manifest and public key, refuses downloads while playout is active, verifies the signed envelope and DMG, and never installs unattended.
External services and restore have boundaries
Metadata providers remain outside Airchain’s control. A staged full restore requires a restart and is refused while playout is active.