# click.aligned.chat.session

> Published by [aligned.click](https://lexicon.garden/identity/did:plc:kdnkzvtg6nugup477ev22xfa)

✓ This is the authoritative definition for this NSID.

## Links

- [View on Lexicon Garden](https://lexicon.garden/lexicon/did:plc:kdnkzvtg6nugup477ev22xfa/click.aligned.chat.session)
- [Documentation](https://lexicon.garden/lexicon/did:plc:kdnkzvtg6nugup477ev22xfa/click.aligned.chat.session/docs)
- [Examples](https://lexicon.garden/lexicon/did:plc:kdnkzvtg6nugup477ev22xfa/click.aligned.chat.session/examples)

## Definitions

### `click.aligned.chat.session`

**Type**: `record`

A published conversation with an agent. The container only: the turns are separate click.aligned.chat.message records pointing back at this one, so a session grows without ever being rewritten.

**Key**: `tid`

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `title` | `string` | No | What the conversation was about. May be written after the fact, which is why messages link here by at-uri rather than by strongRef — editing this must not dangle them. |
| `createdAt` | `string` (datetime) | Yes | When the conversation started, not when it was published. |
| `discussion` | `string` (at-uri) | No | A Bluesky post where this conversation is being discussed. Records like these are durable but silent — nothing on the network is notified when one is written — so conversation about them has to happen where conversation already happens. Naming the post rather than embedding the replies keeps the two separate: the record is the artifact, the thread is what people said about it, and either can be deleted without taking the other with it. |
| `description` | `string` | No | Optional framing: what was being explored, and why. |

## Raw Schema

```json
{
  "id": "click.aligned.chat.session",
  "defs": {
    "main": {
      "key": "tid",
      "type": "record",
      "record": {
        "type": "object",
        "required": [
          "createdAt"
        ],
        "properties": {
          "title": {
            "type": "string",
            "maxLength": 640,
            "description": "What the conversation was about. May be written after the fact, which is why messages link here by at-uri rather than by strongRef — editing this must not dangle them.",
            "maxGraphemes": 128
          },
          "createdAt": {
            "type": "string",
            "format": "datetime",
            "description": "When the conversation started, not when it was published."
          },
          "discussion": {
            "type": "string",
            "format": "at-uri",
            "description": "A Bluesky post where this conversation is being discussed. Records like these are durable but silent — nothing on the network is notified when one is written — so conversation about them has to happen where conversation already happens. Naming the post rather than embedding the replies keeps the two separate: the record is the artifact, the thread is what people said about it, and either can be deleted without taking the other with it."
          },
          "description": {
            "type": "string",
            "maxLength": 12000,
            "description": "Optional framing: what was being explored, and why.",
            "maxGraphemes": 3000
          }
        }
      },
      "description": "A published conversation with an agent. The container only: the turns are separate click.aligned.chat.message records pointing back at this one, so a session grows without ever being rewritten."
    }
  },
  "$type": "com.atproto.lexicon.schema",
  "lexicon": 1
}
```