AI Solution Engineer | AI Foundry @ BYU
From Kāneʻohe, Oʻahu. Pre-Business at BYU Marriott in Provo. Forward Deployed AI Engineer at the AI Foundry @ BYU, a limited-enrollment consulting firm that ships production AI for paying clients, and AI Solution Engineer at Visp, a 30-year-old billing and operations platform for internet service providers. The failures on this page get more room than the wins.
I build things for real businesses and a second brain for myself. Everything below is a live link or a failure.
See the buildsVoice agents for small businesses, built on Vapi and Claude over an Express backend. The server computes the facts. The model never invents them.
A two-layer archive and wiki that a language model maintains. I built mine first and use it every day, and now I build them for other people.
A spaced-recall drill built out of my own lectures and textbooks, so the questions come from the course rather than from a stranger's deck.
Astro and Next.js when a site needs a framework, and hand-written HTML when it does not. This page is the second kind.
I join a development team's daily scrum and sprint cadence and work on their live systems, instead of handing over a deck and leaving.
I built a second brain for myself, released the machinery of it so anyone can run their own, and then built the same thing for a company. The private one runs my life, so what is public about it is the operating record rather than the contents.
Two layers: every source kept whole, and a wiki compiled on top of it that a language model maintains and rewrites as new things land. It has been running daily since July 2026 and it is where everything else on this page gets written down.
It stays private, because it holds my life. The receipts are public: a nightly census of what it did, and a postmortem file of everything I have broken.
The machinery of that brain with my life taken out: a constitution file the model reads first, honesty gates that block a commit on a broken or one-way link, search-first retrieval, a commit script that lets several Claude sessions share one folder, a reminders ledger and a postmortem file.
You bring your own notes. Everything that keeps mine honest is in the folder.
Visp is a 30-year-old billing and operations platform for internet service providers. I am an AI Solution Engineer there as an independent contractor, on the development team's daily scrum and sprint cadence, working on live systems.
I built the company's second brain: a hosted MCP server with OAuth sign-in, three permission roles, an audit trail, and connectors for both Claude and ChatGPT, covered by 128 automated checks.
AI receptionists and company brains for Oʻahu businesses. The honest version: one paying client so far, and it churned; I had built way more than what they were paying for.
An AI receptionist and website proof-of-concept for a small fiber ISP. Built with Hunter Calton for a partner.
A dozen-plus two-player activities for couples who are apart, so a long-distance evening has something to do together besides a video call.
A values-based matching app for students. I built it and abandoned it in one April afternoon, then picked it back up in September 2026 as Y Match.
A desktop cursor-guide, built with a friend. I left the project in May 2026. It is still up, which is the only reason it is on this list.
Everything above is a link you can open. What I have released to clone is further down this page, and the account is github.com/NaluKicks-808.
A second brain I have been running since July 2026. Two layers: every source kept whole, and a wiki compiled on top of it that a language model maintains. Its dashboard sits behind a key, so what I can show you is the census and the failures.
Last 30 days: 774 commits · Yesterday: 11 answers in the drill · 1 of 1 limb on schedule · 900M tokens through the brain.
These are the parts of my own setup, and one field trial I ran on it, that turned out to work for anything, so I took my life out of them and released them. Each page below says what it is, why I built it, how to start it if you have never used Claude Code, and the one thing it does not do.
The machinery of my second brain with my life taken out: the constitution file, the honesty gates, search-first retrieval, the shared commit script, a reminders ledger and a postmortem file.
How to run it second-brain-kitOne injects "read the brain first" at the start of a session. One blocks a question to you until the brain has been read. One refuses a second to-do list. One makes an agent measure a job before it spends tokens on it.
How to run it claude-code-hooksA one-page HTML resume rendered to PDF with headless Chrome, plus a check that reads the PDF back the way an applicant-tracking parser does and refuses anything side by side.
How to run it ats-resume-pipelineA Claude Code skill that interviews you before it writes about you, asking only what your notes cannot already answer.
How to run it grillme-skillA Claude Code skill that turns a caught failure into a four-question postmortem, and does not let it end anywhere except a fix a machine enforces.
How to run it wtfhappened-skillA Claude Code skill that keeps every resume bullet and LinkedIn entry in one shape: verb first, no first person, one tense per line, a number with its period.
How to run it resume-format-skillA fast judgment model tested on real decisions inside my second brain, with the pass mark written before every run and the failures published beside the wins.
How to run it jev-field-trialA search test for any folder of linked notes that needs no labelling, because the links you already wrote are the answer key. Plain rankers built in, and a plug for your own.
How to run it vault-search-benchA Claude Code skill of field notes on Jev: which question shape fits which job, how to set the pass mark first, and the traps my trial fell into.
How to run it jev-field-guide-skillThese are taken straight out of the postmortem file the brain keeps on itself. They are here because a list of things that worked is not evidence of anything.
Prose rules lose to machines. Every rule that matters here has a hook, a gate, or a detector behind it.
No form here on purpose. A static page cannot send one, and a message that vanishes is worse than no message. Email is the fastest way to reach me.
If you have a phone that rings more than you can answer, or an archive nobody can search, that is the shape of problem I take.