Builder, architect, and lifelong problem-solver focused on privacy-first systems and digital trust. Senior-level architect currently working in systems analysis (with a bias toward building what should exist next).

• Applicert — Consent-Based Data Objects (CBDOs)
  A new model for verification where systems ask questions of data and receive verifiable answers — without exposing the underlying information.

👉 https://github.com/applicert/cbdo-core-engine

I’ve spent years working across the stack as a developer and systems architect — designing, building, and troubleshooting real-world systems under real constraints.

My experience includes:

• Software architecture and full-stack development
• Database design and data modeling
• Building and maintaining production systems
• Translating messy real-world problems into clean technical solutions

More recently, I’ve been focused on:

• Verifiable Credentials (W3C)
• Decentralized Identity (DID)
• Privacy-preserving system design
• Cryptographic verification models

I tend to question assumptions — especially when “that’s just how it’s done” is the answer.

I’m interested in systems that:

• Minimize unnecessary complexity
• Reduce ambiguity and trust gaps
• Align technical behavior with real-world expectations
• Solve problems at the model level, not just the implementation layer

CBDOs are an attempt to move from:

sharing data
to
answering questions about data

When I’m not building:

• Writing and producing music (E-Z-A 🎤, HardTap 🎸)
• Developing creative story universes (ASA-9, The Shadow Master)
• Co-developing and play testing RPG campaign settings (Moons of Ibis)
• Exploring AI-assisted content creation
• Thinking about systems, incentives, and how things actually work under the hood

• Technical discussion and critique
• Collaboration in identity / privacy / trust systems
• Conversations that challenge assumptions and improve the model

If you’ve taken a look at CBDOs, I’d genuinely value your take.