What does a green build prove?
How Auths and auths-proof led to Proof-Driven Development and Proofbound, an assurance compiler that keeps tests, proofs, bounds, and assumptions distinct.
Architecture
5 entries exploring this thread.
Why I built Auths
I built Auths to separate identity from authority and make exact, bounded authorization portable across systems that will inevitably change.
A function signature should say what the function can do
How capsec makes filesystem and network authority visible in Rust types, what the compiler rejects, and where audit must take over.
The repository rejects reverse dependencies
How auths-proof turns layer direction, offline verification, deterministic CBOR, and protocol bounds into executable repository checks.
One authority model, many identity and transport systems
How auths-proof admits KERI, raw keys, P-256, Iroh, HTTPS, and other systems without letting them redefine permission.