zkfwdbld

Problem

Automated findings are easy to generate and hard to trust. The project asks what additional structure is required before an engineer should act on an agent or scanner assertion.

Core

A Rust/Wasm path generates witnesses and verifies R1CS constraints over the Goldilocks field. AO-oriented orchestration and local evaluation tooling sit around it.

Boundary

The Rust prover path is real and tested; the orchestrator still contains a demo-only CNF path. Current end-to-end messages demonstrate liveness and flow, not a fully bound real-world causation proof.

Direction

The reusable artifact shape is the interesting part: source-aware finding, normalized claim, evidence, derivation trace, proof artifact, verification result, and a human-readable handoff.