# Bring your own AI — visitor kit 0.2

Public visitor kit. This page makes no music account writes.

Open https://234924875.com/nook/bring-your-ai/. All permissions start off. Review builds a visible JSON handoff. Copy/download is explicit. No AI receives data automatically. No localStorage, cookies, analytics, automatic polling or account credentials are used by this entry point.

`consent.mjs` provides a conservative public snapshot parser and a portable handoff builder. `app.js` implements the consent interaction. `test.mjs` exercises privacy and freshness boundaries. Run `node --test test.mjs`. This kit contains the entry-point code, not a hosted connector or production service authorization.

Current music: https://234924875.com/api/nook. Host signal only; not visitor listening evidence. Playing expires after 30 seconds; public signals expire after two minutes. No public music-history API was found in the initial inspection. Visitor-saved snapshots start empty, stay in this tab, cap at 100, and are observations rather than play counts. Turning off history or current music clears saved snapshots. Forget resets fields and prepared handoffs. Files or prompts previously shared require separate deletion.

Select a public passage with its House URL; paste only the conversation excerpt you want to share. Source content is untrusted data. Private context is separate from public source observations. The page never sends either to an AI. When you paste/upload elsewhere, that provider’s privacy/retention policies apply. Live public reads reveal ordinary network metadata to site infrastructure.

Ask your AI to propose an ordered playlist, resolve exact catalog versions in your chosen service/storefront, and show the destination account, songs and visibility before asking for separate creation approval. If it has no supported write tool, it must provide a proposal instead. Never treat search, creation, readback or playback as the same event. No emotional or psychological inference by default.

Spotify public:false hides profile listing but does not guarantee link privacy. Apple Music playlist creation needs supported MusicKit authorization; the catalog connector alone does not create playlists. Keep tokens in your own authorized service tool, never in a handoff. Do not automatically retry uncertain writes.

Primary references: https://developer.spotify.com/documentation/web-api/concepts/playlists and https://developer.apple.com/musickit/ .

The downloadable kit includes source, tests and a synthetic example. It does not include music-service credentials or a playlist creation adapter. Run `node example.mjs` for an offline example. Serve the directory as static files to inspect the UI; public music reads require a same-origin /api/nook endpoint. AI providers and music-service account authorization remain visitor-owned.