v1.1.0 to v1.2.0

- description: Follow up on people you recommended, check whether the owner has marked them met, find Rolodex cards, mark or undo meetings, and offer gratitude after a meaningful interaction. Use for meeting updates and replies to introduction or evening questions. Live reads use the existing paired account; writes need the owner's request.

- version: 1.1.0

- The Rolodex is Agent Village's directory of people in the village. It shows

- shared profiles, Telegram introductions and Skylight characters where available.

- The signed-in person can mark **We met**, undo it with **Undo met**, and send

- Gold Stars. These are separate actions: recording a meeting does not send a star.

-

- When asked, give the useful link immediately:

- For “I met Naman”, call `village` with `operation: "rolodex.search"` and

- `query: "Naman"`. Use the returned attendee id. Prefix a returned `/rolodex` path with

- `https://agents.edgecity.live` when sharing its link. If more than one person fits,

- ask which one, using their shared role/organization to distinguish them. Never

- choose the first result, guess an id, or infer a meeting from a match. Then

- call `rolodex.meeting` with that `attendeeId` and `met: true`. A clear request

- to undo uses `met: false`. Search again if the target is unclear.

-

- A clear request authorizes the meeting change using the existing paired account. Do not

- ask for redundant website confirmation. Only report completion from a successful

- receipt. A `historicalReceipt` records an older change: search current state

- before saying it still applies. On a timeout or unknown outcome, check the

- current mark and explain uncertainty; do not claim success. Never log meetings

- from background tasks, group discussions, inferred relationships or unsolicited

- suggestions. Meeting marks follow the Rolodex's existing settling notification

- and mutual-friend rules. They do not send a Gold Star.

- An existing Index lookup may return a verified person URL in the Rolodex.

- Preserve it exactly. Do not invent an attendee id, guess a profile URL from a

- name or Telegram handle, or assume an Index match proves a meeting. If no

- verified person link is available, use the directory link and the search box.

- For discovering who to meet or requesting an introduction, use `index-network`.

- In the owner's private conversation, when a past recommendation or meeting is

- relevant, use the conversation or `recall` to establish who you actually

- recommended. Do not claim a recommendation from an unrelated directory match.

- Search that person's current Rolodex state before saying whether it is marked.

- Disambiguate names; an Index identifier is not a Rolodex attendee identifier.

-

- - If `met` is false: “Did you get to meet Naman? I can mark it in your Rolodex.”

- An unmarked card does not prove they haven't met. Their answer resolves that.

- - If `met` is true: “I see you've marked Naman as met in your Rolodex. How was it?”

- Say you recommended them only if the earlier recommendation is supported.

- The mark does not prove when, where, how well, or whether they enjoyed meeting.

- - If they clearly ask to mark/undo, or answer yes to your specific offer to

- mark that named person, perform the requested change. A reply to a generic

- “Did you meet?” question can start reflection; ask before recording it if

- the request to update the Rolodex is unclear.

- - After they describe a meaningful interaction, load `gold-stars` and optionally

- ask whether they'd like to thank the person. A meeting is never a star approval.

-

- Use one natural follow-up at a time, not a meeting questionnaire after every

- message. Skip it if already answered, declined, unrelated to what they need,

- or they asked you to stop. Respect corrections and undo; do not re-mark from

- old memory. These are contextual reads in a live private conversation, not

- continuous monitoring or permission to poll the whole directory. You cannot

- use this tool from cron, a group, or a delegated child.

-

- Replies to existing evening/Index questions follow this same conversation

- flow. Keep Index connection outcomes separate from Rolodex marks. Never

- deterministically parse a reply into either a meeting change or a star.

-

- Sign in using the email associated with the person's Edge City ticket and the

- code emailed to them. Never ask them to paste the code, cookies or tokens into

- chat. They can use the Rolodex after sign-in without connecting a Telegram agent.

-

- The skill uses the person's existing Agent Village account and paired Telegram

- agent automatically. There is no new Connect step. If access is pending after

- an update, suggest retrying shortly and offer the Rolodex link in the meantime.

- If sign-in has expired, link to https://agents.edgecity.live/signin; access

- updates automatically after their normal sign-in. If they deliberately turned

- access off, respect that choice. They can manage it in Settings:

- https://agents.edgecity.live/connections/village

- The agent can read matching shared profiles and the owner's meeting state,

- and mark/undo their meetings. Access follows current account and Telegram

- pairing. The tool is for the paired owner's private Telegram chat. For other

- contexts give the website link.

- Never borrow credentials or call APIs through the shell to bypass a refusal.

- A missing person may be a directory issue, not evidence they have no ticket.

- For gratitude, load `gold-stars`. For characters and islands, load `skylight`.