Issues

• Forge stages must persist intermediate weights as content-addressed artifacts; lost intermediate = chain break, detectable at audit time

  CambrianTech/forge-alloy#11 · Filter by author joelteply opened on Apr 7, 2026

• AlloyTarget.runtimes: declare deployment runtimes; validate-runtime stage hard-fails on incompatibility

  CambrianTech/forge-alloy#10 · Filter by author joelteply opened on Apr 7, 2026

• Universal attestation chain: typed QR codes, linked stages, domain-agnostic

  enhancement
  CambrianTech/forge-alloy#9 · Filter by author joelteply opened on Apr 2, 2026

• Client-side verification: no trusted server, math is the authority

  enhancement
  CambrianTech/forge-alloy#8 · Filter by author joelteply opened on Apr 2, 2026

• Stage types are LLM-specific — forge-alloy should be domain-agnostic

  enhancement
  CambrianTech/forge-alloy#7 · Filter by author joelteply opened on Apr 1, 2026

• Post-quantum migration: dual-signing with ML-DSA / SLH-DSA

  CambrianTech/forge-alloy#6 · Filter by author joelteply opened on Mar 31, 2026

• Dataset hashing: RFC 6962 Merkle tree with domain separation

  CambrianTech/forge-alloy#5 · Filter by author joelteply opened on Mar 31, 2026

• Enclave execution: TEE for tamper-proof attestation (marketplace requirement)

  CambrianTech/forge-alloy#4 · Filter by author joelteply opened on Mar 31, 2026

• Hardware key signing: Secure Enclave / StrongBox / TPM integration

  CambrianTech/forge-alloy#3 · Filter by author joelteply opened on Mar 31, 2026

• Key registry: hosted service with revocation and rotation

  CambrianTech/forge-alloy#2 · Filter by author joelteply opened on Mar 31, 2026

• RFC 8785 JCS canonicalization + ES256 signing implementation

  CambrianTech/forge-alloy#1 · Filter by author joelteply opened on Mar 31, 2026