# App and operator compatibility

{/* Generated by scripts/generate-compat-reference.mjs from src/data/compat/operator-compat.json.
    Do not edit by hand: run `pnpm generate:compat-reference` and commit the result. */}

Each Airdress Chat build is checked against the operator versions the fleet runs. A feature gets a **level** on each operator version, a **confidence** that says how the level is known, and the age of that evidence.

Generated from the matrix of **2026-10-29**. Ages count from that date.

For what this means for you, read [Which operator your app works with](/chat/compatibility/).

## Levels and confidence

| Level | Meaning |
| ----- | ------- |
| full | The feature works as the app's release notes describe it. |
| degraded | It works, with a notice in the app about what differs. |
| absent | The app does not offer the feature on this operator and says so, or draws nothing when the build predates the feature. |
| broken | It fails, hangs or reports success that did not happen. |
| unknown | Not assessed yet. |

**Measured** means a run of the app build against that operator version. **Inferred** means read from the code of both. **Assumed** means nothing better than the previous version's result.
A measured result older than 30 days is marked **stale**. A feature marked with a flag variant changes level when the operator turns that flag on or off; the evidence lists each variant.

A feature marked with a dagger (†) is **cardinal**: chat depends on it, and any level below full on it makes the pair unsupported.

## Airdress Chat 0.8.0 (37)

Live on the App Store since 2026-10-29. Built from commit `7ba50222c4ef`. This build has no compatibility screen: it learns what its operator offers one feature at a time.

Columns are operator versions, each on the fleet profile it was assessed on (`ipv6-operator-2026-10-14` and `ipv6-operator-2026-10-29`).

| Feature | v0.1.123-hotfix.1 | v0.1.161 |
| ------- | --- | --- |
| Sign in and pair this device † | full measured · 15 d | full inferred · 0 d |
| Join from another device, or reset the airdress † | full measured · 15 d | full inferred · 0 d |
| Chat myself † | full assumed · 0 d | full inferred · 0 d · 1 flag variant |
| Chat the operator agent and the model † | full assumed · 0 d | full inferred · 0 d |
| People on this airdress † | — | full inferred · 0 d · 1 flag variant |
| People on other airdresses † | — | full inferred · 0 d · 1 flag variant |
| The installed build reaches its operator † | full measured · 15 d | full assumed · 0 d |
| Group conversations | — | absent inferred · 0 d · 1 flag variant |
| Notifications while the app is closed | — | full inferred · 0 d |
| Push-to-talk | — | full inferred · 0 d |
| Location to your own airdress | — | absent inferred · 0 d · 1 flag variant |
| Events tab | — | full inferred · 0 d |
| Home Assistant link | — | full inferred · 0 d |
| Apps on your own machine | — | unknown inferred · 0 d |
| Send to a screen | — | unknown inferred · 0 d |
| Block and report a person | full measured · 34 d · **stale** | full inferred · 0 d |
| Publish my name and photo | — | full inferred · 0 d |
| Shells on your own machines | — | absent inferred · 0 d · 1 flag variant |
| Agent devices (editor sessions as devices) | — | degraded inferred · 0 d |
| Places and live location on the map | — | absent inferred · 0 d |

### Evidence for Airdress Chat 0.8.0 (37)

<details>
<summary>Evidence: Sign in and pair this device</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, measured.

- measured, 2026-10-14, by App Store review: Store review: join request 16:30:08, enrolled 16:31:49 with 0 active rows. Approved 2026-10-29 on iPad Air 11-inch (M3) and iPhone 17 Pro Max.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue + live client config. POST /v1/endpoints/enrollments and pairing-codes unchanged; hub_enrollment true; enrollment v2 on both sides.

</details>

<details>
<summary>Evidence: Join from another device, or reset the airdress</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, measured.

- measured, 2026-10-14, by App Store review: Root_key_mismatch -&gt; Ask your other device -&gt; Reset and start over -&gt; second sign-in. The reviewer path.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue + fleet configuration. All six device-join-requests routes served (withdraw is new and uncalled); [recovery] on; root-recovery reads present.

</details>

<details>
<summary>Evidence: Chat myself</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, assumed.

- assumed, 2026-10-29, by @eljefedelrodeodeljefe: The review was approved; whether a note was sent to Myself is not recorded.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue, client config routes, MLS member routes. Self route, messages, events, key packages, envelopes served; mls_v2_cutover true both sides; the app's MLS library predates 0.3.0 so it performs no revocation check (a client-side rule); OPEN: the one-to-one commit sequencer and fail-closed one-to-one commits (v0.1.154 and v0.1.156) touch this lane and are unmeasured against a pre-0.3.0 client.
- When `person_mls: true`: degraded. An owner device keeps its v2 credential; member devices move to v3.

</details>

<details>
<summary>Evidence: Chat the operator agent and the model</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, assumed.

- assumed, 2026-10-29, by @eljefedelrodeodeljefe: The review was approved; the agent thread is what the review notes direct the reviewer to.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue + QA matrix. Operator.local lane unchanged; the operator has a healthy model pool member.

</details>

<details>
<summary>Evidence: People on this airdress</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Live client config: principal_lane_operator_held true, person_mls false. The profile's airdress has no sub-users, so the case does not arise on it.
- When `person_mls: true`: degraded. Household threads become MLS groups; what a 0.8.0 member's device does is unmeasured.

</details>

<details>
<summary>Evidence: People on other airdresses</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue + MLS member routes. Federation routes unchanged; the peer revocation route is additive and the fail-closed rule lives in the 0.3.0 client, which 0.8.0 does not carry; the agent-to-agent application lane has been absent since the MLS credential v2 cutover on both columns.
- When `federation: false`: absent. Explained: Nothing answered at \{airdress\}.

</details>

<details>
<summary>Evidence: The installed build reaches its operator</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, measured.

- measured, 2026-10-14, by App Store review: The reviewer's device reached its operator over the real network and enrolled.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, assumed.

- assumed, 2026-10-29, by @eljefedelrodeodeljefe: Nothing between the versions changes the relay or TLS path. Measure with the CF-8 live leg on a test operator.

</details>

<details>
<summary>Evidence: Group conversations</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: absent, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Chat changelog (the group model is 0.10.0) + live client config group_conversations false.
- When `group_conversations: true`: degraded. A group envelope reaches a build with no group model; the unknown counterparty kind should render "This version can't show this conversation" - inferred from the app's strings, not measured.

</details>

<details>
<summary>Evidence: Notifications while the app is closed</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Fleet configuration push_enabled true; the three push-subscription routes served; APNs keys in place. Envelope_wake false: the MLS-lane wake is a 0.10.0 app feature and 0.8.0 does not read the key; the reviewer-welcome schedule is off between reviews so a single-principal airdress gets no notification by design.

</details>

<details>
<summary>Evidence: Push-to-talk</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Live client config ptt_enabled true; floor routes and audio_burst unchanged in the catalogue. Last hardware measurement 2026-09-08 on a v0.1.40-era operator.

</details>

<details>
<summary>Evidence: Location to your own airdress</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: absent, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Live client config location_enabled false; 0.8.0 reads the flag (changelog: the operator has not said no while pairing loads).
- When `location_enabled: true`: full. Assumed; location_track_heartbeat_seconds is served and a 0.8.0 build that finds none beats every 10 minutes.

</details>

<details>
<summary>Evidence: Events tab</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Operator route catalogue ingest routes + an ingress endpoint configured.

</details>

<details>
<summary>Evidence: Home Assistant link</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: /v1/kinds routes served; 0.8.0 carries the Home detail and the older-operator CLI fallback copy.

</details>

<details>
<summary>Evidence: Apps on your own machine</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: unknown, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: The route catalogue lists no /v1/apps route while the apps module serves one; the profile has apps off and /readyz says apps ok (disabled). Either an explained absence or the catalogue is incomplete; measure on a test operator.

</details>

<details>
<summary>Evidence: Send to a screen</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: unknown, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: The route catalogue lists no /v1/surfaces route while the surface module serves one and 0.8.0 draws the screens card. Same action as apps-fan-in.

</details>

<details>
<summary>Evidence: Block and report a person</summary>

**v0.1.123-hotfix.1** on profile `ipv6-operator-2026-10-14`: full, measured.

- measured, 2026-09-25, by @eljefedelrodeodeljefe: Hardware run on v0.1.88 (migrations 0068/0069 present; on v0.1.86 Block did nothing). V0.1.123 carries 0068/0069.

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Migrations 0068/0069 are below head 114; nothing between names a change. The routes are not in the catalogue either; 0.8.0 has no explained absence for an operator before v0.1.88.

</details>

<details>
<summary>Evidence: Publish my name and photo</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: full, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: /v1/me/publication and the block routes served.

</details>

<details>
<summary>Evidence: Shells on your own machines</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: absent, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Chat changelog (shells are 0.9.0); fleet configuration shells off.
- When `shells: true`: absent. Nothing drawn; shell_host_linked and shell_attention arrive on the client stream and 0.8.0 should ignore unknown event types - inferred, test owed.

</details>

<details>
<summary>Evidence: Agent devices (editor sessions as devices)</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: degraded, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Client config routes (device_join_requested.device_class is additive), chat changelog (agent devices, approval by delegation and Approve-only-where-the-root-is are 0.10.0), fleet configuration (agent_devices on since 2026-10-29). Not measured, and it needs a measurement before anyone relies on it: a 0.8.0 build shows an agent's join request as a plain device join; its approve path seals the root via root-transfers where 0.10.0 approves by delegation; whether the operator refuses a root deposit for device_class agent is not established from the code read.

</details>

<details>
<summary>Evidence: Places and live location on the map</summary>

**v0.1.161** on profile `ipv6-operator-2026-10-29`: absent, inferred.

- inferred, 2026-10-29, by @eljefedelrodeodeljefe: Chat CHANGELOG (the map is 0.10.0).

</details>

## Operator versions

| Version | Released | Migration head |
| ------- | -------- | -------------- |
| v0.1.123-hotfix.1 | 2026-10-09 | — |
| v0.1.161 | 2026-10-24 | 114 |