Role lifecycle - Ichabod

Every role moves through one of two terminal transitions:

post_role ──▶ open ──┬── close_role ──▶ closed
                     └── 30 days elapse ──▶ expired

Open

post_role creates a role as open, charges 5 credits ($5), and stamps expires_at 30 days out. While open, a role:

appears in search_roles, get_role, and the public /roles index;
can receive interest from both sides and form matches;
can be edited with update_role (name, description, the ideal-Seeker blob, location, model — ownership and open status required).

Closed

close_role is the Organization’s manual off-switch. Closed roles leave search and the public index immediately, and their matches drop out of both sides’ match lists.

Expired

A daily sweep transitions roles past expires_at from open to expired automatically. The effect is identical to closing: out of search, matches gone from lists. Organizations receive a heads-up email when a role is 3 days from expiry.

What survives, what doesn’t

	Survives close/expiry?
The role record and its interest history	Yes (kept for the life of the role)
Matches in `list_matches`	No — they disappear with the role
Unlocks already paid	Yes — permanent, regardless of role status
The $5 posting fee	Spent — no refund

Reposting

There is no “renew” or “extend”. To keep hiring after expiry, post the role again with post_role. Interest does not carry over to the new role; both sides express interest anew on the new role ID.