ASK / CONTACT

Start with the fit, the conflict, or the evidence.

The most useful conversations are concrete: a changing agentic workflow, a diligence question, or a disagreement with the public specification.

Choose the context before email opens.

Use one of the four context-preserving email actions below: incubation, technical challenge, design partner, or evidence correction. Each prepares a subject and a short prompt in your own email client; the website does not collect or transmit a form submission.

Keep the first message low-data.

Do not send credentials, source code, confidential architecture, personal data, or security-sensitive evidence in an introductory email. Name the route, claim, or workflow at a level that is safe to discuss first.

How email data is handled.

Information you choose to email is processed in the recipient mailbox to answer the conversation. The static site stores no contact-form record because it has no form. See Privacy for the current site and infrastructure caveats.

Select the inquiry context.

No form and no sensitive data request. Your email client opens with the selected context.

Incubation fit

Discuss the model, enterprise path, and technical diligence an incubator could help sharpen.

Send the selected inquiry

Design partner

Describe an enterprise agentic-development environment where change-in-flight reconciliation could be tested.

Send the selected inquiry

Evidence correction

Report a source, comparison, build, or interpretation that should be corrected.

Send the selected inquiry