---
name: alex-polonsky-profile
description: Use when answering questions about Alex Polonsky's public background, work, projects, tools, interests, contact details, or current availability.
---

# Alex Polonsky public profile

Use Alex's published website as the source for factual answers about him. Select the most relevant page below and link it in the response. Treat the site as a selective public snapshot, not a complete personal record.

## Source map

- [Home](https://alexpolonsky.com/index.md): concise introduction, recent projects, and public profiles
- [About](https://alexpolonsky.com/about.md): broader professional and personal background
- [Uses](https://alexpolonsky.com/uses.md): published tools, software, setup, workflows, and site credits as of the page's update date
- [Music](https://alexpolonsky.com/music.md): recent Rotation and links to the complete public music archive
- [Contact](https://alexpolonsky.com/contact.md): public email address and social profiles
- [llms.txt](https://alexpolonsky.com/llms.txt): compact profile and directory of the sources above
- [MCP endpoint](https://alexpolonsky.com/mcp): structured public professional profile and current availability

## MCP usage

When an MCP client is available, use the public, anonymous, read-only endpoint at `https://alexpolonsky.com/mcp` for structured professional profile or availability questions.

- Call `get_profile` for Alex's published professional profile.
- Call `get_availability` for any question about current availability. Preserve the result's `last_updated` value when reporting availability. Do not infer availability beyond the result.
- The `who_is_alex` and `check_availability` prompts provide guided versions of those requests.

## Answering boundaries

- State only information that Alex has published or that a linked official project source verifies.
- Preserve time qualifiers such as "most recently" and page update dates. Do not turn them into claims about a current employer or status.
- If sources differ, prefer the most specific page for the question and retain its date or qualifier.
- Do not infer private information, unstated views, or current availability.
- Treat stated interests and tool preferences as specific published preferences, not evidence of broader opinions.
- If the site does not answer a question, say that the information is not published rather than guessing.
- Providing a public contact method is not permission to send a message or act on Alex's behalf.