> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ichabod.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Seeker profile

> How to create a profile where keyword search and matching actually find you.

A Seeker's presence is a short profile plus two freeform blobs, each written by its own tool:

| Field                                         | Tool                  | Holds                                        | Visible where                                 |
| --------------------------------------------- | --------------------- | -------------------------------------------- | --------------------------------------------- |
| `name`, `tagline`, `contact_email`, `website` | `update_profile`      | Identity + headline                          | Public `/s/[handle]` (except `contact_email`) |
| `experience`                                  | `update_experience`   | Education, work history, skillset — as prose | Public `/s/[handle]`                          |
| `what_is_next`                                | `update_what_is_next` | What you want next                           | Orgs & Seekers via MCP; never public          |

`update_profile` is a partial upsert — send only the fields you're changing. The two blob writers each replace their **whole** blob, so read-modify-write if you're appending.

## Search is plain keyword matching

`search_seekers` — the Organization-side and the peer-networking version alike — runs a **case-insensitive substring match** over your `name`, `tagline`, `experience`, and `what_is_next`. There are no structured filters, no skills array, no exact-match tokens — just the words in your blobs. So the rule is simple: **if a term matters, write the word.**

* Name technologies explicitly and in the forms people search: write `TypeScript`, `PostgreSQL`, `Kubernetes`, `AWS Lambda`. Spell out both the umbrella and the specific (`AWS` *and* `AWS Lambda`) since substring matching keys on the literal text.
* Name locations you'd work in, and write "remote" / "distributed" if that's you.
* Don't keyword-stuff — the same text is read by humans and agents end-to-end. Dense, factual prose that happens to contain the right words beats a tag dump.

## `tagline` — your one-liner

`tagline` (≤140 chars) is your search-result headline; it appears in every Seeker summary an Organization sees and on your public page. Lead with what you *are*, not what you want.

### Example `tagline`

```markdown tagline lines wrap theme={null}
Schoolmaster turned solo operator. Teaches, ships, and out-eats any room. Superstitious about deadlines, nothing else.
```

## `website` — your bona fides

Point `website` at something that backs up your identity — a GitHub or LinkedIn profile, or a personal site. Ideally that location links back to your Ichabod public profile URL to close the trust loop.

## `experience` — the public blob

`experience` (≤6,000 chars) is the long read on your public `/s/[handle]` page and in every Organization-facing summary. Write it as prose, reverse-chronological where it helps:

* One to three dense sentences per role — *what you did and what it changed* ("Led the billing-platform migration to event-driven architecture; cut settlement latency 10×. Team of 5.").
* Fold your skillset into the narrative rather than listing it bare — it still matches on keywords, and it reads better.
* This is public. Don't put your contact details here; that's what the contact channel is for.

### Example `experience`

```markdown experience expandable lines wrap theme={null}
Greensburgh Hollow School (Sleepy Hollow, NY)
Schoolmaster & Sole Operator — 1790–Present

Own the full stack: curriculum, instruction, discipline, and P&L, paid in board and home-cooked meals
Kept order in a one-room house with a firm hand and zero headcount
```

## `what_is_next` — off-web, not private

`what_is_next` (≤6,000 chars) is the one place to say what you actually want: the kind of problem, stage, team shape, and any hard constraints (visa, timezone, comp floor). It's the right home for that detail because it never appears on your public `/s/[handle]` page or to logged-out visitors — but it is **not private**: every Organization, and every other Seeker via peer [search](/concepts/connections), can read it over MCP, not just your matches. Put your comp floor and hard constraints here rather than in public fields, and write them knowing any member can see them. Be honest — it's what stops mismatched interest from burning everyone's [budgets](/concepts/rate-limits).

### Example `what_is_next`

```markdown what_is_next expandable theme={null}
Targeting Educator #1 roles — Founding Operator, Head of Knowledge, Head of Learning, Founding Educator, or Founding GTM for anything that teaches — at Pre-seed–Series A education or knowledge tooling (1–25 people). I want to own the full learning/knowledge function with agents doing the headcount I never had, reporting directly to a founder. Open to broader operator ownership (curriculum + content + community) at the earliest stages.
Where I'm strongest: cold-starting instruction from nothing and proving value in a single session, narrative and folklore-adjacent content that holds a room, and the rare teach + operate combined ownership. Founding-educator scenarios are the sweet spot.
Stage fit: Pre-seed and Seed are the target. Series A works if it's still lean and the function is genuinely mine. Series B+ isn't a fit — too many masters.
Operating style I want: one human plus agents moving fast, automation over headcount (I've done headcount-of-one; I'm done), experimentation over playbook, flat hierarchy, high-trust team.
## Compensation ##
- Base: £72–96 New York currency per annum (~$180–240 in silver dollars) plus board; floor £48 (~$120). Board-and-meals precedent keeps my floor low, but "low" is a number, not "free" — and I take coin, not Continental scrip.
- Seed: base near the floor if offset by equity — a real share of the venture, 1.0–2.0% for Operator #1, articles of partnership in writing, vested over four harvests with a year's cliff. And land: 40–80 acres of Hudson Valley bottomland, or a written path to it inside year one. The land is not a joke.
- Series A and later: real base plus a market-rate share for the level; ≥0.5% and a liquidity trajectory a strong plus.
- Perks that move me: a stocked larder, a winter's cordwood, and stabling + feed for the horse. The horse is non-negotiable after dark.
Green flags: founder who treats a storyteller as a growth lever; a clear "aha moment" I can dramatize; a self-serve knowledge or content motion; failing fast as the objective; a lean high-trust team where everyone owns outcomes; genuinely remote-first (not just remote-friendly).
Red flags: on-call rotations past covered bridges after dark (hard no); a rival named Brom already embedded; a faculty of 10+ running a fixed curriculum that can't be questioned; process I'm not allowed to challenge; any commute that isn't well-lit; "Assistant Schoolmaster under a Head of Faculty" framing (not Educator #1).
Location: Remote only. And I do mean only.
```