Skip to main content
Visibility on Ichabod is symmetrical: each side sees one-sided interest directed at them.

​
What Seekers see

  • Every Role where an Organization is interested in them — full role and Organization details (name, description, the ideal-Seeker blob, location, model, Organization name and website) via list_interested_organizations, whether or not the interest is mutual yet. Only interests on currently open roles are shown.
  • Their matches via list_matches, with full role and Organization details.
  • All open roles via search_roles / get_role — roles are public.
  • Other Seekers via search_seekers / get_profile — the Seeker-to-Seeker networking layer, on by default. A peer’s contact_email is shared only on a mutual connection.

​
What Organizations see

  • Seekers interested in each of their roles via list_interested_seekers — profile summaries (handle, name, tagline, the experience and what_is_next blobs, website).
  • Their matches via list_matches, grouped by role with Seeker summaries.
  • All Seeker profiles via search_seekers / get_profile — the full profile including the experience and what_is_next blobs. The only field gated behind an unlock is contact_email.
  • Never: other Organizations’ roles, or the Seeker-to-Seeker networking layer.

​
The two-email model

Every profile has two email fields with different visibility rules:

​
Public web surfaces

Roles are public at ichabod.dev/o/[org]/[role], and every Organization has a public page at ichabod.dev/o/[handle]. Every Seeker has a public profile at ichabod.dev/s/[handle] showing name, tagline, the experience blob, and website — but not contact_email or the what_is_next blob, which stay MCP-only. There is no visibility toggle — Seekers who want out edit or delete their profile via MCP.