Kleoverse Request early access
Case study · Captured October 26, 2026

From an AI search to a permissioned introduction.

This case study uses Jan Valkonen’s real, approved public Kleoverse identity. It shows what a discovery agent can report, which published records support the result, what it must leave unknown and why discovery is not permission to contact.

Jan Valkonen, founder and AI product builder
The public source

Jan Valkonen

Founder, inventor and AI product builder · Joensuu, Finland

Availability
Actively seeking employment
Snapshot identity
kv_855895e9e436007acce302ee
Source rule
The live profile remains authoritative when this dated page differs.
01
Company request

Describe the work, not a title.

“Find an AI product builder in Finland with founder experience, evidence-backed professional-identity work and experience shipping agent-accessible systems.”

02
Discovery result

A match with reasons—not a score.

Jan ValkonenFounder, inventor and AI product builder · Finland
Public match

Jan’s published profile is relevant because it records founder and AI leadership experience alongside current projects for machine-readable professional identity, evidence-aware talent discovery and permissioned opportunity workflows.

Published recordMachine-Readable Professional Identity

The profile describes a Markdown identity representation, shared visibility-aware loading and deterministic identity versions.

Published recordAI Talent Discovery Engine

The project record supports work on evidence-based, explainable professional discovery rather than opaque percentage matching.

Published recordPermissioned Opportunity Rooms

The profile describes review, acceptance or decline, approved information snapshots and participant-restricted rooms.

Source: Jan Valkonen’s approved public Kleoverse profile, captured October 26, 2026. These are owner-published professional records, not an independent certification by Kleoverse.

03
Visible limitations

The agent must preserve what is not established.

  • No hourly rate is stated in the captured public profile.
  • No preferred employment arrangement is stated beyond actively seeking employment.
  • Public project descriptions support the work recorded; they do not independently measure quality, commercial adoption or fit for a particular role.
  • A public profile does not authorise bulk export, direct outreach or access to private evidence.
  • The current live profile should be checked because availability and professional records can change.
04
Permission boundary

Discovery ends before contact begins.

This page documents the intended controlled workflow and the public profile records behind it. It does not claim that an external company completed a real hiring transaction.

What this demonstrates

One identity can serve a person, a company and an AI agent without collapsing consent.

  • The person maintains the source identity
  • The company receives an explained result
  • The agent cites published records and visible gaps
  • The next step remains permissioned

Evaluate the same public source.

Compare the human profile, its Markdown representation and this dated interpretation. If something differs, use the live profile as the source of truth.

Early access