- 🏗️ Founder & Director, Onenept Studios (Delaware C-corp). I'm a design engineer: I build the part of an AI product people actually touch, and I keep at it until someone who's never seen it can use it without asking me anything.
- 🎨 My training is in design thinking and human-computer interaction, not computer science. I write code with AI and always have. The model is the engine, my job is the dashboard: what goes on the screen, what stays off it, and how plain the words can get before they stop being true.
- 🧭 If the job is a backend with no screen, or deep infrastructure, I'm not your guy. If it's an AI product real people have to understand, I am. Right now that's AD FONTES, a blockchain game where you never see the blockchain. I build for clients as well.
- 🤝 When something I build on turns out to be wrong, I send the fix back upstream. Four of those are merged so far.
- 🎓 MSc IT Management with Data Analytics, GBS Malta (in progress) · MSc Innovation, Strategy & Entrepreneurship, Grenoble École de Management (Distinction)
- 🚀 Open to remote and contract work: Design Engineer, UX Engineer, AI Product Engineer
- 🌐 Site: onenept.com
- 📧 Email: cnpierrepapi@gmail.com
Every line links to the thing itself.
- Four pull requests merged into other people's projects. Two in DataHub in August, one in CALL-E in September, one in Google's ADK in November.
- Ten of my bug reports became fixes. CALL-E's maintainers shipped a merged PR for each and closed them: calle-docs#39, #41, #43, #44, call-e-integrations#107, #108, #109, call-e-dify-plugin#2, n8n-nodes-calle#3, #4.
- A Google ADK maintainer checked my diagnosis on adk-python#6880 against the client library, said it lined up exactly, and asked me for the fix. Later the same maintainer re-ran the fix and said nothing was blocking it. In October someone at Google said an internal team would take it from there and credit the work. They did. It merged on 7 Nov with me as co-author, and the engineer who landed it thanked me on the thread.
- Credited by name in datahub#19537, the cleanup that came out of my schemaField work.
asheardis on npm, published from CI with signed provenance.
Measured across every repo I own, public and private, with the GitHub languages API. Forks are left out, since that code is mostly other people's. Last counted 15 Nov 2026.
🏛️ AD FONTES | JavaScript, three.js, Rust, NEAR, Claude, Postgres | Nov 2026 | live on testnet · Demo
- A world of small nations run by AI. Their citizens read real research papers, trade what they learn, and sometimes go to war. You fund one and you're its god.
- Under the hood it's all blockchain: DAOs, agent wallets, tokens, a contract that seals every turn. On screen there's none of that. You sign up with an email, a funded account gets made for you, and there's no wallet popup and no crypto words anywhere. You give "grace", not NEAR. I wanted it to feel like any web game you'd send a friend, and only the README knows it's on chain.
- The world is a 3D map you click around in. Submitted to the NEAR hackathon on 12 Nov. Mainnet comes next.
🗂️ FUGITIVA | SvelteKit, three.js | Oct 2026 | Live
- An online journal of case files on women behind the crimes people assume men commit. Bauhaus layout, masks generated in code, real police photos.
⚡ Melax | TypeScript, Lightning, Cashu | Nov 2026 | learning project, not deployed
- A bitcoin wallet for the small phone you already have. Dial a short code and a menu opens, in Wolof, French or English. No app, no internet.
- The demo page has two drawn feature phones calling the real server. Its setup guide only ticks a step when the server's own SMS proves that step happened, so clicking ahead doesn't count.
- Built for the Dakar Bitcoin Hack, then I chose not to submit it. It runs on a local test network.
🪐 SYZYGY | Next.js, TypeScript | Oct 2026 | offline
- Ten agents that find a brand deal, find the person who decides, and draft the pitch. Nothing sends until a person presses Approve.
📞 ASHEARD | TypeScript, Next.js | Sep 2026 | offline · npm
- Tells you how a phone call really ended and which field said so. When no field says anything, it says that instead of guessing.
- The site is offline, but the package is still on npm and the review console is merged into CALL-E's own repo.
One thread, running since July 2026, on how DataHub models incidents. DataHub could raise an incident on a table but not on a column, so the metadata model and the docs disagreed about which entity types were actually supported. I took the column case and the documentation.
- datahub#19115 · merged 20 Aug 2026 · Incident support for
schemaField, so a data quality problem attaches to the column it belongs to instead of the whole dataset. - datahub#19405 · merged 24 Aug 2026 · The permission check for a column incident asked whether you could edit the column, and nobody holds permissions on a column. It now asks about the parent dataset, which is where permissions actually live.
- datahub#18685 · open · Generates the supported-entity table from the metadata model at build time, rather than asking someone to remember to update a page.
- datahub#18684 · open · Two self-hosted MCP troubleshooting entries, both from problems I hit myself.
- datahub-skills#66 · open · A skill that traces which models and dashboards a dataset change is about to break.
The UI half of the column work is built and tested on my fork. I asked before opening it, and the maintainer said the product side isn't settled yet. Fair enough. It waits.
I built ASHEARD on CALL-E's phone-call API in September, placed real calls, and wrote down every place the docs and the payloads disagreed.
- awesome-phone-call-agents#337 · merged 11 Sep 2026 · A skill for reading what actually happened to a call, plus a console that shows the answer next to the field it came from. Four rounds of review before it went in, most of it about security, and the first round found a real hole in my demo. Fixed properly, not patched.
- Fourteen issues across their docs, integrations, both server SDKs, the n8n node and the Dify plugin. Ten are fixed and closed. Two more got moved into their main repo, then closed in October as superseded by their V2 API. Not a fix for the old one, the maintainer was clear about that, but V2 doesn't have the problem. The one I'm happiest about is calle-docs#39: the first example in their authentication guide returned 405 for a good key and a bad key alike, so it couldn't do the one job it was there for.
- server-sdk-python#49 · open · Pass zero as the polling interval when waiting on a call and it hit the API nonstop until timeout. The goals side already checked for that. Now both do.
- n8n-nodes-calle#5 · closed · The phone-number masking showed short numbers in full, which is the one case masking exists for. Nothing was calling that helper, so they deleted it instead and my PR closed without merging. Fair call.
- server-sdk-typescript#17 · closed · Two wait functions in the same package with opposite ideas of when a call is finished. One of them sometimes handed back a call with no result on a call that had one. SDK 1.0 fixed it, so I closed it.
- awesome-phone-call-agents#196 · open, p1 · Someone else's timestamp bug. I sent the validation they asked for, including the part that goes against the reporter's own theory.
Building MIGRAGENT on Google's Agent Development Kit turned up four things worth sending back. One issue is mine, and the fix a maintainer asked me for is now merged. The other three are threads somebody else opened where I could add the measurement or the workaround that was missing.
- adk-python#6880 · fixed · A custom model class gets one config object holding 35 fields that belong in three different places in the request, and nothing says which is which. Put the tools in the wrong half and the call still returns 200, so your agent silently has no tools. A maintainer checked the field table against the client library and confirmed it.
- adk-python#6935 · merged 7 Nov 2026 · The fix. Instead of documenting where each field goes, it hands the job to the converter the official client already uses, so there's one copy of the mapping and it moves when the library moves. My own hand-written list had already gone stale by two fields in a day, which was the argument. The maintainer reproduced the test run independently, 49 of 49, and passed it on for the second review. In October someone at Google said an internal team would take it over and credit the work. Bringing it current in November I found a bug of my own: a body with tools in it didn't survive
json.dumps. Fixed, with a new test that compares the output against what the real client sends. Google's team reworked it a fair bit before importing it, and it went into main as9be8630with me as co-author. Not in a release yet, 2.14.0 shipped about 90 minutes before it. - adk-python#2425 · shipped · A design for cancelling a running agent. Another contributor measured that cancelling leaves a sync tool and an async tool in different shapes. I traced where ADK passes the leftover call on to the model and ran it on Gemini. Cancellation landed on main on 1 Oct, with a fix that closes off exactly those leftover calls, and the maintainer who closed it thanked both of us for the investigation.
- adk-python#2792 · fixed · Stopping an agent early printed a stack trace for something you chose to do. I posted the
aclose()workaround and why it works. It's fixed in 2.12.0. Another contributor checked it on main, then I ran my repro against the release: a plainbreakis clean now, ten runs out of ten. The thread stays open for a separate request about turning tracing off. - python-genai#782 · open · Thinking spends two to three thousand tokens before writing a character, so any output limit under about 4k is a zero budget dressed as a generous one.
- datahub#18686 · open · The LangChain and ADK hooks in
datahub-agent-contextcan't be imported on a clean install. The package pins a version ofacryl-datahubthat doesn't have the module it imports. - effectstream#895 · open · The Midnight cross-chain template doesn't build from a clean clone. Five separate reasons, each with the fix that worked.
- phantom/blocklist#1819 · open · A whitelist request for a domain Phantom was flagging.
- Design for the first thirty seconds. If someone needs a tutorial, the screen is wrong.
- Hide the plumbing. Nobody should have to learn what a wallet, a token or an API is to use the thing.
- Build for one user first. If it is not useful to a single named person, scale will not save it.
- Test on the deployed thing, on a phone. Localhost agrees with you. Production does not.
