NOBULEX

Y Combinator S26
Application

bilateral receipt verification

You are about to become a third-party verifier.

this application was signed with a nobulex bilateral receipt before and after submission. the cryptographic verification will run entirely in your browser. no trust required.

VERIFICATION IN PROGRESS

→ loading pre-execution receipt...

loading post-execution receipt...

computing SHA-256 of pre-execution commitment...

verifying hash chain linkage...

checking pre→post signature composition...

✓

VERIFIED

you just verified this application without trusting anyone.
the math ran in your browser. no server. no operator.
that's what nobulex does for every AI agent action.

now see what happens without nobulex.

VERIFYING UNPROTECTED AGENT

agent: agent-unverified-0x0000
action: transfer $47,000 to unknown recipient

→ searching for pre-execution signature...

searching for authorization chain...

attempting hash chain verification...

✗

VERIFICATION FAILED

no pre-execution signature. no authorization chain.
no hash linkage. no proof of anything.

this agent claimed to transfer $47,000.
you have no way to verify if it was authorized.
you have no way to verify if it actually happened.
you have no way to know if this log was rewritten.

this is what every AI agent in production looks like right now.

no receipts. no chain. just "trust us, we logged it."

you verified a signed application. ✓
you saw what happens without verification. ✗
that gap is why nobulex exists.

merged into Microsoft Agent Governance Toolkit
8 independent implementations validated
OpenSSF Best Practices passing
github.com/arian-gogani/nobulex

Y Combinator S26Application

Y Combinator S26
Application