BlueMinutes v0.2.0 — Default-Off Meeting / Research Foundation

BlueMinutes v0.2.0 — Default-Off Meeting / Research Foundation

• Released: 2026-07-23
• Tag: v0.2.0
• Distribution scope: source code only

BlueMinutes v0.2.0 is a source-only developer milestone. It adds contract,
compatibility, and fail-closed validation foundations for possible future
Meeting / Research workflows while deliberately leaving every Research
capability disabled.

Highlights

• Provider-neutral, versioned identities and contracts for logical Research
  workspaces, shared-source references, exact-version artifacts, citation
  associations, append-only Conversation histories, structured instruction
  profiles and snapshots, and transcript-source discovery and resolution.
• Read-only compatibility adapters preserve the exact authoritative Meeting
  source, briefing, historical-comparison, and evidence revisions.
• Transcript-source resolution rejects disallowed external selections and
  requires application-owned, exact-source proof before text can qualify for
  canonical-audio coverage.
• Timed transcript-source segments must be zero-based, contiguous,
  chronological, gap-free, and non-overlapping; an untimed segment cannot hide
  overlap between surrounding timed segments.
• Conversation histories remain bound to one logical Meeting identity or one
  Research workspace identity while exact revision references may evolve
  within that identity.
• A composition-owned capability snapshot keeps research,
  transcriptSourceResolution, sharedObjectStore, and
  conversationPersistence disabled by default.
• Resource-bound coverage and historical-scale tests are isolated in CI so
  their validation thresholds are exercised once without changing product
  behavior.
• Task cancellation re-reads and retries bounded optimistic-lock conflicts
  caused by concurrent checkpoint persistence; unrelated repository failures
  still surface and job-owned temporary data is still cleaned.

What this release does not add

This release does not add a Research navigation item or interface, Conversation
or Chat interface, external transcript connector, Codex/OpenAI or other
external model provider, credential or login flow, persistent Research data,
database migration, backfill, second data root, new task executor, CLI command,
MCP tool, entitlement, network destination, or changed Meeting workflow.

SQLite remains at schema v10. GRDB 7.11.1 remains the only external package
dependency. Existing user workspaces, semantic payloads, managed files, and
compatibility identifiers are unchanged.

Source-release boundary

GitHub provides the standard source archives automatically. No BlueMinutes app
bundle, installer, maintainer-built archive, signing material, or other binary
asset is attached.

The v0.2.0 tag identifies the reviewed source tree. The development app bundle
retains its separately gated 0.1.0 internal-alpha version and packaging
evidence. Advancing that bundle, signing it with Developer ID, notarizing it,
and proving clean-machine installation remain a separate future distribution
milestone.

Developers and early evaluators can build and stage BlueMinutes locally by
following the README. The default launch path and visible Meeting workflow are
unchanged from the preceding public source release.

Privacy and security

Meeting content remains local by default. No new provider, connector, network
route, telemetry service, remote MCP, HTTP API, cloud synchronization, or
remote-control path is introduced.

The contract foundation fails closed when external transcript use is denied,
source identity or content binding is incomplete, canonical-audio alignment is
unproved, timing is incomplete or contradictory, or a Conversation crosses its
logical Meeting or Research workspace boundary.

Compatibility naming

BlueMinutes remains the public project and product name. Compatibility-sensitive
Swift targets, executables, bundle and database identifiers, protocol names,
commands, and persistent formats continue to use the legacy MeetingBuddy
identifier.

Known limitations

• Every Meeting / Research integration capability added in this release is
  disabled by default and has no visible product surface.
• Apple Silicon is the currently validated architecture.
• Automatic Apple transcription, translation, analysis, and briefing require
  macOS 26, supported hardware and locales, and installed model assets.
• Briefing currently provides one multilateral template and three sections.
• Historical retrieval remains conservative lexical and exact-identity search.
• UN Web TV support remains metadata-only; no media acquisition is
  implemented.
• Native capture still has the intended-OS and physical-device proof gaps
  documented in the repository.
• BlueMinutes supports evidence-linked drafting and review; users must validate
  consequential output against source material and applicable processes.

See CHANGELOG.md for the detailed version history and
README.md for build and usage instructions.

BlueMinutes v0.1.0 — First Public Source Release

BlueMinutes v0.1.0 — First Public Source Release

• Released: 2026-07-22
• Tag: v0.1.0
• Distribution scope: source code only

Why BlueMinutes

BlueMinutes grew from firsthand experience with the time pressure of UN
conferences and multilateral meetings. It brings local transcription,
translation, evidence-linked position analysis, human review, briefing
preparation, and qualified meeting history into one native macOS workflow.

Highlights

• Local-first native macOS application built with Swift 6 and SwiftUI.
• Local media intake and visible audio capture with managed storage,
  deterministic canonical audio, checkpoints, retry, and recovery.
• Apple on-device transcription, translation, diplomatic analysis, and
  briefing routes, with explicit review and confirmation boundaries.
• Typed provenance, immutable revisions, exact evidence links, complete source
  accounting, and fail-closed publication gates.
• Independent briefing sections, Markdown export, qualified historical review,
  and visible learned preferences.
• A typed local CLI and a local stdio MCP server with seven bounded read tools;
  no HTTP listener or remote-control surface.
• Apache License 2.0, public contribution and security policies, protected
  main, and a synthetic-safe CI suite.

See CHANGELOG.md for the detailed version history and
README.md for build and usage instructions.

Source-release boundary

This GitHub Release identifies the first reviewed public source version.
GitHub provides the standard source archives automatically; no BlueMinutes app
bundle, installer, maintainer-built application ZIP, signing material, or other
binary asset is attached.

Developers and early evaluators can build and run BlueMinutes locally by
following the README. A Developer ID signed, notarized, and clean-machine-tested
app download remains a separate future distribution milestone.

Compatibility naming

BlueMinutes is the public project and product name. Some internal Swift targets,
executables, bundle and database identifiers, protocol names, and persistent
formats retain the legacy MeetingBuddy identifier to preserve compatibility.
Exact legacy command names in the README are intentional implementation
identifiers, not a second brand.

Known limitations

• Apple Silicon is the currently validated architecture.
• Automatic Apple transcription, translation, analysis, and briefing require
  macOS 26, supported hardware and locales, and installed model assets.
• Briefing currently provides one multilateral template and three sections.
• Historical retrieval is conservative lexical and exact-identity search.
• UN Web TV support is metadata-only; no media acquisition is implemented.
• Native capture remains subject to the intended-OS and physical-device proof
  gaps documented in the repository.
• BlueMinutes supports evidence-linked drafting and review; users must validate
  consequential output against source material and applicable processes.

Privacy

Meeting content remains local by default. There is no outbound inference
provider, cloud synchronization, remote MCP, HTTP API, telemetry service, or
remote-control path in this version. The only implemented network route is an
explicit, bounded metadata request to an exact webtv.un.org asset page, and
offline/no-outbound mode disables it.