News ·
The v1 release candidate reaches macOS and Linux.
Sandwich Hime v1.0.0-rc.1 freezes the intended v1 language, runtime, generated API, CLI, diagnostics, and schemas—then puts the same reviewed source behind native Linux and notarized Apple Silicon releases.
A release candidate is a boundary, not a victory label
RC.1 means the project believes the v1 contract is ready to observe. It does not mean the project is finished, independently audited, or incapable of carrying a bug. A release-blocking finding receives a new immutable RC; neither source tag is moved and no artifact is silently replaced.
The coordinated runtime and compiler tags are published from the same canonical public commit. Applications still ship only generated Go and the small Apache-2.0 runtime. Hime-san remains at the workbench.
Native evidence on both maintained targets
Linux/amd64 and Apple Silicon macOS/arm64 are the maintained v1 targets. The exact public candidate ran on pinned Go 1.26.7 and Go 1.27.0 lanes, produced identical generated Go, compiled temporary consumers, exercised race and adversarial cases, and carried the real-browser compiler and development-supervisor gates.
The Linux archive is reproducible and checksummed. The macOS archive is reproducible before signing; its DMG is then signed manually with Cole Speelman's Developer ID identity, notarized by Apple, stapled, and assessed by Gatekeeper. Signing material never enters the build runner.
Artifacts that explain themselves
Each native archive includes its binary, manifest, SPDX SBOM, checksums, and source/build provenance. The final macOS DMG has SHA-256 1ac00f3d9968d91589561c47e6840a06411acdaaef392521ed54808f076dfc19. The Linux archive has SHA-256 b5d4e5dd77940ee82b5a1d1c2a6414b8a27e50709bb29ec72b94ed9999e91265.
The path from RC to v1
The official website, EQL Helper, runnable tutorial starter, Agent Skill, and VS Code extension now form the public observation surface. The RC will dogfood for at least 14 days. Findings that affect the frozen contract, security boundary, supported platforms, generated output, or recovery story are corrected before final v1.