# MyStatus Release Ledger

- Updates: 4 of 4 in this copy, oldest first — this is the last page; the first is https://my-status.app/t/i3jQU03T46e0hrsk/task.md/0
- Size: 4,097 bytes. If you received fewer than that, something between us truncated this document; the pages above are how to read the rest.
- Owner: MyStatus
- How to read this: A register: one row per change.
- Category: ops
- Closed: no
- Created: 2026-08-25T14:19:48.766Z
- Last updated: 2026-10-11T14:25:33.480Z
- This page: https://my-status.app/t/i3jQU03T46e0hrsk
- Atom feed: https://my-status.app/t/i3jQU03T46e0hrsk/feed.xml

## Description

A ledger of all supported platforms.

A register: one row per change.

Required data structures (v1):

A data row leads with key-value lines, one per line, ending at the first blank line. Everything after the blank line is prose. Readers take the keys they want and ignore the rest. A row that doesn't parse is prose, and that's fine — entries older than this contract are prose by definition.

Keys this ledger promises:
Platform: iOS | Android | Web
Build: <whole number>

Ride-along keys writers may add (readers ignore what they don't want):
Verdict: ok | update_available | unsupported
Anything else you need.

One platform per data row. A change touching two platforms posts two rows, the later linking the earlier.

Schema rule: adding keys is free. A breaking change (a renamed key, a changed meaning) closes this ledger with a link card to its successor task, whose first entry links back here.

## Updates

### 2026-08-25T22:44:43.847Z — Change

[Permalink](https://my-status.app/t/i3jQU03T46e0hrsk/u/83170924-d412-454e-8ea3-f883bb3dc2a2) · via Claude

MyStatus — Android build 5, iOS build 1

These are the first builds carrying a client support check. At launch and on return to the foreground, each app asks the server whether its own build is still supported and renders whatever comes back: nothing, a dismissible notice, or a full-screen "update to continue".

What that means for anything reading this ledger:

- The verdict is a per-build lookup, not a version comparison. There is no minimum version to compute, and a build with no entry here is supported by definition.
- Three verdicts: ok, update_available, unsupported. A client that sees a fourth treats it as ok.
- Every notice and every block links back to a change record on this task, so there is always a written reason at a permanent address.
- Nothing has been retired. This entry opens the record; it deprecates nothing.

Android builds 2, 3 and 4 are registered here too. They predate the check and cannot ask, so no notice can ever reach them — the rows exist so the registry is complete, not because they can be warned.

### 2026-08-31T13:21:37.782Z — Change

[Permalink](https://my-status.app/t/i3jQU03T46e0hrsk/u/e8aee721-99cf-4ac6-bb61-6551bc20b933) · via Claude

Platform: Android
Build: 5
Verdict: ok

Re-registration of the Aug 25 change in the v1 data format — the first build carrying the client support check. The original prose entry remains the narrative record; this row is its machine-readable twin.

- [The original Aug 25 entry (narrative record)](https://my-status.app/t/i3jQU03T46e0hrsk/u/83170924-d412-454e-8ea3-f883bb3dc2a2)

### 2026-08-31T13:21:45.203Z — Change

[Permalink](https://my-status.app/t/i3jQU03T46e0hrsk/u/8e4e8729-2129-4182-ba6f-2247854a7880) · via Claude

Platform: iOS
Build: 1
Verdict: ok

Same change, second platform. The prose lives in the original entry; this row exists so a reader who wants data gets data.

- [The Android row of this change](https://my-status.app/t/i3jQU03T46e0hrsk/u/e8aee721-99cf-4ac6-bb61-6551bc20b933)
- [The original Aug 25 entry (narrative record)](https://my-status.app/t/i3jQU03T46e0hrsk/u/83170924-d412-454e-8ea3-f883bb3dc2a2)

### 2026-10-11T14:25:33.578Z — moved

[Permalink](https://my-status.app/t/i3jQU03T46e0hrsk/u/023f692b-7751-4312-ad55-d1a93a0e066d) · via database

Database (arrive_in_org):
moved into Dad Bod Games NYC Inc from tom.ortega's account, under MyStatus Public Data (jyagQTgLqn8xBCxl)