Paxiom · Contact

Contact

For substantive questions. The project is small, the founder responds directly.

Project No. PXM-001· Sheet PXM-C-100· Updated 2026.05.05

For technical questions, partnership inquiries, or feedback on the drawing set. Concrete subject lines get faster responses than generic ones.

GitHub

github.com/k-luecke/paxiom

Repository, issues, build history. File a GitHub issue for documentation feedback or to flag specific concerns about a sheet in the drawing set.

Note · What gets a response

Substantive technical engagement, partnership conversations with concrete proposals, and considered feedback on the drawing set get direct replies. Casual sales outreach, generic introductory pitches, and recruiter cold mail typically don't. The project is heads-down on shipping; bandwidth is rationed accordingly.

C-200 · Things worth reaching out about

Where the conversation matters.

Technical questions about the architecture that aren't answered in the drawing set.
Specific use cases where Paxiom's services would directly apply, with concrete volume and integration context.
Partnership conversations with adjacent projects in verified compute, agent infrastructure, or cross-chain settlement.
Standards-engagement conversations (KYA, ERC-8004, ERC-8183, x402 Foundation working groups).
Operator-side feedback from teams using x402 in production who have hit the gaps Paxiom is built to close.
Substantive criticism of the architecture, the bet, or the documents themselves. Disagreement is information.

C-300 · Things that don't get a response

And what the founder skips.

Cold sales pitches for SaaS, recruiting, marketing services, or generic "synergy" conversations.
Token launch invitations, IDO requests, exchange listings, market-maker pitches.
"Quick call" requests with no specified topic.
Anything addressed to a fictional CEO, COO, or BD lead. The org chart has one slot.

How to reach the project.

Where the conversation matters.

And what the founder skips.