Why this role matters
Vivendur is built AI-native. We use AI agents to help implement the production core against a reference implementation. Passing shared tests is one check; design review, threat modeling and independent assessment are separate work. This role holds that review: sign-off on every change to the cryptographic path is written into our constitution as a decision only this role makes.
What’s already here
A complete technical design, with every major decision recorded alongside its alternatives and trade-offs. The design aims to use established cryptographic primitives rather than invent new ones. That does not mean the composed system has had independent review. A reference implementation with team-reported checks of its core rules; the status page describes them. Versioned test artifacts and independent review are not yet published. We use shared test cases to compare the production core with the reference, alongside further security review.
What I’d ask of you first
Not agreement. The strongest attack you can mount on the design. If it doesn’t survive you, I want to know first. If it does, or if you show me how to fix it, I want you holding the keys to fixing it, with the title, the equity, and the authority the role deserves.
Start with one conversation
Email azinetemadi@vivendur.com. Tell me what you’d try to break first. I’ll send the full design ahead of our call, so you can see exactly how this could fail before deciding whether to help it succeed.