Skip to content

Prepare public, signed, multi-architecture distribution #27

Description

@KulmanD

Objective

Make mx3-lite installable by nontechnical users without changing worker behavior, privacy, startup policy, or runtime architecture.

Planned branch: release/public-distribution-readiness
Performance report: docs/performance/public-distribution-readiness.md
Performance gate: #20

Scope

Repository and documentation:

  • add a license selected explicitly by the owner
  • add a concise repository description and relevant topics
  • prepare the repository for public visibility without exposing personal data
  • verify release links work for users who are not collaborators

Build and release:

  • produce separate Apple Silicon and Intel artifacts, or a universal app when measurements justify its disk-size cost
  • retain the lightweight helper and separate settings process
  • document Developer ID signing and notarization
  • verify signatures, architecture, bundle structure, archive extraction, and checksums
  • keep manual startup; do not add a launch agent or login item
  • do not add an updater, telemetry, network access, or normal background logging

Repository visibility, topics, certificates, signing, and notarization are owner-controlled deployment steps; the branch should prepare and document them but must not fabricate credentials.

Validation

  • install from a freshly extracted release archive
  • first-launch Gatekeeper and permission workflow
  • Start, quit settings app, Status, Stop
  • no worker after Stop
  • no network socket or normal log file
  • release helper does not link test frameworks
  • architecture verified for every published artifact
  • source and release archives contain no personal paths, user config, build cache, or credentials

Performance experiment

Measure each architecture independently where hardware is available:

  • worker RSS, threads, idle CPU, and wakeups
  • executable/app/archive sizes
  • launch and stop behavior
  • confirm a universal binary affects disk size only and does not load both architecture slices

Definition of done

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions