CONTACT
A question, critique, practical problem, collaboration idea, introduction, or strange edge case is enough. You do not need a polished pitch or the right internal category.
WHAT BRINGS YOU HERE
A practical problem, product idea, implementation question, or possible collaboration.
A software, systems, AI-governance, architecture, workshop, or advisory problem.
Product / licensing / distributionA product, teaching tool, software surface, licensing path, distribution opportunity, or user channel.
Collaboration / pilot / partnershipA bounded review, pilot, co-development effort, institutional relationship, or introduction.
Technical criticism, research discussion, funding, capitalization, sponsorship, or institutional support.
Domain review, adversarial criticism, replication, prior-art correction, or technical discussion.
Funding / capitalization / sponsorshipRunway, sponsorship, research/public-good funding, product-specific capital, or another bounded resource for converting existing capacity.
Media, education, Open Lab, introductions, or anything that does not fit neatly elsewhere.
Interview, podcast, event, classroom, workshop, public explanation, or educational collaboration.
Open Lab / unusual submissionA criticism, consequential system, strange artifact, or piece of work that does not fit the ordinary categories.
General / not sureUse this when the reason for contact is real but the institutional lane is not obvious yet.
WRITE A NOTE
Tell us what you are thinking about, point us to anything relevant, and say what kind of response would be useful. Save sensitive material for later.
WHAT HAPPENS NEXT
The reason for contact and the page you came from stay attached so you do not have to reconstruct the whole story.
Not every message needs to become a project. The useful question is whether there is something concrete worth doing next.
That might be a reply, a question, a conversation, a review, a referral, a pilot, or a straightforward no.
If the conversation becomes a project, collaboration, funding process, review, or client engagement, it moves into the appropriate Lab workflow instead of living only in email.
A FEW PRACTICAL BOUNDARIES
You can be informal. Just avoid sending secrets or protected material before there is an appropriate way to handle it.
Do not send credentials, private keys, patient data, protected personal information, export-controlled material, or confidential proprietary content through first contact.
A reply, conversation, review, or meeting does not imply partnership, funding, authorship, validation, or endorsement.
The page you came from and the reason you wrote stay attached so the conversation can move to the right place without losing what you meant.
Contact does not subscribe you to a marketing list. If you contact us about Applied Work, we may ask a few qualification questions so we can tell whether there is a real bounded problem and a responsible next step.
NOT SURE YET?
If something here made you curious, skeptical, excited, confused, or useful to talk to, that is enough reason to send a note. These pages are here if you want more context first.