All issues

Search results

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

Status: Open.

#11 In CambrianTech/forge-alloy;

· joelteply opened on Apr 7, 2026

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

Status: Open.

#10 In CambrianTech/forge-alloy;

· joelteply opened on Apr 7, 2026

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

enhancementNew feature or requestNew feature or request

Status: Open.

#9 In CambrianTech/forge-alloy;

· joelteply opened on Apr 2, 2026

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

enhancementNew feature or requestNew feature or request

Status: Open.

#8 In CambrianTech/forge-alloy;

· joelteply opened on Apr 2, 2026

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

enhancementNew feature or requestNew feature or request

Status: Open.

#7 In CambrianTech/forge-alloy;

· joelteply opened on Apr 1, 2026

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

Status: Open.

#6 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026

Dataset hashing: RFC 6962 Merkle tree with domain separation

Status: Open.

#5 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026

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

Status: Open.

#4 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026

Hardware key signing: Secure Enclave / StrongBox / TPM integration

Status: Open.

#3 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026

Key registry: hosted service with revocation and rotation

Status: Open.

#2 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026

RFC 8785 JCS canonicalization + ES256 signing implementation

Status: Open.

#1 In CambrianTech/forge-alloy;

· joelteply opened on Mar 31, 2026