Trace where an offline claim stops

What you'll need

• A non-sensitive technical note describing components and their connections

Steps

1. Paste the note into the prompt below.
2. Read the connection map alongside the original note.
3. Remove any connection the note does not explicitly support.

Organize this note into a component connection map. Use plain text with no Markdown formatting and fewer than 150 words. Give each explicitly stated connection its own line in the form: component A connects to component B: purpose. Then add a section titled Access limits listing only explicitly stated restrictions, and a section titled Unspecified listing any connection endpoints or purposes the note leaves unclear. Write None stated when a section has no entries. Do not infer connections or treat one component's offline status as applying to the whole system. Note: [paste your technical note]

What you should get

Four connection lines preserve the stated endpoints and purposes. Access limits identifies only the player’s internet restriction. Unspecified identifies the missing destination for the download station’s status messages.

Tested example: Tested on sample input

The listening-room player reads audio files from a local storage box. The player has no internet access. A separate download station connects to an online audio catalog to fetch new recordings, then copies them to the storage box. The room controller sends playback commands to the player. The note says the download station also sends status messages, but does not say where those messages go.

Listening-room player connects to local storage box: reads audio files.
Download station connects to online audio catalog: fetches new recordings.
Download station connects to local storage box: copies new recordings.
Room controller connects to listening-room player: sends playback commands.

Access limits
The listening-room player has no internet access.

Unspecified
The destination of status messages sent by the download station is not stated.