The Ed25519-Signed Witness Manifest is a cryptographic artifact used to verify the integrity and authenticity of software installations. Specifically, it documents verified code changes and uses Ed25519 digital signatures to ensure that shipped software versions have not been tampered with and originate from authoritative sources. This approach combines cryptographic verification with transparent change documentation to establish trust in software distribution chains.

A Witness Manifest serves as a detailed record of all code fixes, patches, and changes included in a particular software release or version range. By combining this manifest with Ed25519 signatures—a modern elliptic curve digital signature algorithm—developers and end users can verify that the installed software version matches exactly what was shipped by the original developers. This is particularly important in development tools and critical infrastructure where code authenticity directly impacts security and reliability ¹⁾.

The Ed25519 signature scheme provides several advantages over older RSA-based approaches: it offers strong cryptographic security, requires smaller key sizes, and generates smaller signatures while maintaining comparable or superior security properties ²⁾.

In the context of Ruflo—a tool for managing Claude-generated code—the Ed25519-Signed Witness Manifest documents specific verified fixes shipped across consecutive version releases. Between versions v3.6.28 and v3.6.30, Ruflo's manifest recorded 55 distinct verified fixes, each cryptographically signed to prevent unauthorized modification or injection of malicious code.

The verification process uses the command `ruflo verify`, which cryptographically validates the manifest against the installed code. This command checks that the Ed25519 signature is authentic and matches the documented fixes, ensuring the installation integrity. Users can confirm that their installed version contains exactly the fixes documented in the manifest and nothing more, without relying solely on secure network connections or trusting intermediate parties ³⁾.

The manifest-based verification approach provides several security benefits. Rather than trusting a single distribution channel, users can independently verify that their installation matches the authoritative manifest using only public cryptographic key material. This follows the principle of defense in depth—even if a download is compromised, the Ed25519 signature verification provides an additional security layer that cannot be spoofed without access to the private signing key.

The 55 verified fixes in the v3.6.28 to v3.6.30 range represent incremental improvements to code generation, error handling, or performance characteristics. Each fix is explicitly enumerated in the manifest rather than described vaguely, enabling users to understand exactly what changes have been applied to their system.

Ed25519-Signed Witness Manifests are particularly valuable in development tool chains where code generation or automation is involved. The Ruflo system demonstrates one concrete implementation where Claude-generated code is packaged with cryptographic proof of authenticity. This pattern can be extended to other automated code generation systems, package managers, or infrastructure deployment tools where users need strong assurance of code provenance ⁴⁾.

Similar manifest-based verification approaches have been adopted in container image signing (via notary and other systems), software supply chain security initiatives, and package management frameworks where tamper-evidence is critical. The use of cryptographic manifests allows organizations to maintain audit trails and ensure compliance with security policies requiring verified installation records.

• Cryptographic Manifest Verification
• Ed25519 Digital Signatures for Agent Communication
• ADR-096: Encryption at Rest Implementation