I explore how systems work, from managing digital identities to designing connected devices and learning blockchain fundamentals. This portfolio brings my technical work and evolving prototypes into one place.
IAM & identity governance · IoT automation · Solana experimentation
Featured technical projects
Primary career focus
Hands-on learning & documented design
Each project explores a different layer of technology: who can access a system, how the physical world connects to software, and how digital assets are represented on a blockchain.
One self-directed identity governance project, documented in my Vepy / VetCare ISC Notion workspace. I modeled employee onboarding, transfers, and offboarding through role policies, JSON examples, and Postman test plans.
Started in May 2025 to explore an affordable way to let my dog out while I was away. I programmed an ESP32 and got the motor working by remote command, but did not complete the door installation because of concerns about motor strength.
A personal exploration of the Solana token ecosystem, related metadata concepts, and GitHub-based project organization. Sensitive details stay private.
Project stages are described conservatively. A prototype design or reconstructed case study is not represented as a production deployment.
VetCare is a single self-directed IAM learning project originally documented in my Vepy workspace and its VetCare ISC Notion page. I used a fictional veterinary hospital to explore how SailPoint Identity Security Cloud could manage employee access as staff join, change departments, or leave. My documentation covers identity lifecycle scenarios, role mappings, sample JSON requests, and an ordered Postman API test plan.
My Vepy and VetCare ISC notes from August–September 2025 include diagrams, role-and-permission graphics, test-step descriptions, and illustrative JSON payloads. They reference a Postman collection named VetCare_ISC_Postman_Collection_v2.json, but the original collection file, execution results, and any live SailPoint tenant integration are still being recovered or verified. This is a documented proof of concept, not a production deployment.
Recover and reproduce the API test collection, capture verifiable request/response evidence, add access certifications and SoD exception handling, and explore Splunk audit dashboards.
{
"department": "Surgery",
"jobCode": "VetTech2",
"effectiveDate": "2025-10-01"
}WorkTail HR, PetID SSO, and VetEMR are fictional demo systems. The flows and sample payload show the design; they are not proof of executed SailPoint provisioning.
In May 2025, I set out to build a lower-cost automatic sliding glass door opener so I could let my dog outside when I was not home. Commercial solutions cost around $400–$600, so I explored a DIY design with a target budget of about $100–$150. I programmed an ESP32, developed familiarity with Arduino-style microcontroller programming, and successfully operated the motor with Bluetooth remote commands (open, close, and stop), as demonstrated in my video. I ultimately stopped the project before installing it: the existing sliding glass door is old and difficult to move, and I was concerned the small motor would not have enough torque to open it reliably. Replacing the door was not financially feasible. Wi-Fi/internet access and an optional RFID/NFC pet-collar trigger were ideas for later development, not completed features.
Working proof of concept: I programmed the ESP32 and remotely controlled the motor, including open, close, and stop. I paused development before connecting the motor to my older, hard-to-move sliding glass door because its resistance raised concerns about the motor's torque. Replacing the door was outside my budget. The opener was not installed or tested on the door; Wi-Fi/internet control and pet-collar activation remained planned features.
I explored how Solana token projects are organized and represented, including token-list repositories and artwork assets. This is a private learning project, so the portfolio focuses on concepts and publicly viewable artifacts rather than exposing wallet access or confidential token data.
The token name, mint address, blockchain network, minting transaction, and deployment status have not been independently verified from the accessible files. Those fields can be added after the supporting evidence is available and you decide what to publish.
The letter “S” is placeholder artwork, not a verified token brand or logo.
My project work draws on cybersecurity training, systems reasoning, hands-on exploration, and documenting processes so they can be reviewed and improved.
JML processes, RBAC, least privilege, access-change scenarios.
Postman workflows, JSON structure, scenario mapping.
Microcontrollers, driver circuits, IoT automation planning.
Solana ecosystem, token metadata, repository research.
I'm especially interested in entry-level IAM, identity governance, and access-management opportunities, while continuing to develop projects across other technologies.