Access

How to engage AIvan at the current product stage

AIvan is still a private core. Access is intentionally curated, but the site should still route serious visitors into the right conversation instead of leaving them at the edge of the brand.

Early collaborator

For people who want to test flows, pressure-test positioning, or help shape the product surface.Visible product context, curated walkthroughs, and direct feedback loops into the roadmap.

Partner or client-fit exploration

For teams evaluating whether AIvan's transform, workflow, or orchestration model matches a real operating problem.A focused conversation around use case fit, boundaries, and what a safe first integration would look like.

Technical peer review

For senior builders who want to challenge the architecture, execution model, or product claims.Concrete proof surfaces, architecture mapping, and discussion anchored in shipped behavior instead of hype.

Current process

Three steps to start in the right lane

Start from the proof surfaces on this site so the conversation begins from current reality.
Use the main portfolio contact path or GitHub profile to open the conversation.
Expect manual curation for any deeper access; AIvan is still a private core with selective exposure.

Boundary

Expect a public-safe conversation first

Public: product shape, capabilities, command lanes, architecture posture, release log, and deployment status.
Private: research artifacts, patent work, internal prompts, sensitive memory, and detailed orchestration internals.
Rule: show confidence and specificity without leaking the materials that create AIvan's edge.

Contact routes

Use the public surfaces that already exist

GitHub / KeGolkgithub.com/KeGolk

Best public technical identity for reviewing shipped work and starting a conversation.

ivanm.devwww.ivanm.dev

Main portfolio surface for broader contact and project context.

Current stance

Manual curation is a feature, not a missing form.

AIvan is still being actively shaped. The right next step is a focused conversation grounded in the proof and system pages, not a generic waitlist funnel pretending the product is already broad and open.