@@ -2761,7 +2761,7 @@ The authoring surface of a metadata write. Closed: `copilot` is an AI assistant'
 
 ## RegisterDeviceRequest
 
-[PLANNED — not yet served] Register or refresh a push device for the signed-in user. No route serves it yet; the device routes land together with their handlers
+Register or refresh a push device for the signed-in user
 
 ### Properties
 
@@ -2780,7 +2780,7 @@ The authoring surface of a metadata write. Closed: `copilot` is an AI assistant'
 
 ## RegisterDeviceResponse
 
-[PLANNED — not yet served] Answer to a device registration: the device id the client keeps
+Answer to a device registration: the device id the client keeps
 
 ### Properties
 
@@ -3026,7 +3026,7 @@ Uninstall package response
 
 ## UnregisterDeviceRequest
 
-[PLANNED — not yet served] Unregister one of the signed-in user's push devices
+Unregister one of the signed-in user's push devices
 
 ### Properties
 
@@ -3039,7 +3039,7 @@ Uninstall package response
 
 ## UnregisterDeviceResponse
 
-[PLANNED — not yet served] Answer to a device unregistration
+Answer to a device unregistration
 
 ### Properties
 
 
@@ -1,50 +1,11 @@
 ---
 title: Push Device schema — System Protocol reference
 navTitle: Push Device
-description: "Push Device Protocol — the stored device shape of the push device registry."
+description: "Push Device schemas of the ObjectStack System Protocol: UserDevice — each property with its type, default and a TypeScript example."
 ---
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Push Device Protocol — the stored device shape of the push device registry
-(ADR-0012 §6, narrowed to what core ships).
-
-One row per (user, app install): what a device registration
-(`RegisterDeviceRequestSchema`, `api/protocol.zod.ts`) produces, what the
-push channel reads to address a phone, and what the registry's listing
-answers (`INotificationService.listDevices`).
-
-**Declared ahead of its producer.** No table stores it and no route serves
-it yet; the schema carries a `[PLANNED — not yet served]` marker in its
-`.describe()` until the device registry lands (in the push channel plugin's
-`sys_user_device`, ADR-0012 §11).
-
-Three rules the registry owes, stated here because they decide the shape:
-
-- **(a) A device belongs to a user, not to an organization.** The row has no
-  organization member. A phone signed in to one person receives that
-  person's notifications whichever organization they come from; the
-  organization travels on the notification, never on the device. The
-  identity of a row is (`userId`, `deviceId`).
-- **(b) One live row per token.** A vendor token is delivered to one row
-  only. A token this user already holds under another `deviceId` (the app's
-  storage was cleared, so the registration carries no `deviceId`) refreshes
-  that row and answers its `deviceId`; it never makes a second live row.
-  When a second user registers a token another user's device holds, the
-  token moves to the second user and the first user's row for it is
-  removed, so a push meant for the phone's previous user never reaches its
-  new one.
-- **(c) A dead token keeps its row.** When the vendor reports a token dead
-  (APNs `BadDeviceToken` / `Unregistered`, FCM `UNREGISTERED`), the row is
-  kept with `enabled: false` and `invalidatedAt` set, so "why did this phone
-  stop getting pushes" stays answerable. Nothing is delivered to a disabled
-  row, and a later registration of the same device re-enables it and clears
-  `invalidatedAt`.
-
-Narrowed from ADR-0012 §6: `vendor` is the core pair (`apns` | `fcm`; the
-domestic Android vendors plug in as alternate channel implementations) and
-`platform` is the registration's own three (`ios` | `android` | `web`).
-
 <Callout type="info">
 **Source:** `packages/spec/src/system/push-device.zod.ts`
 </Callout>
@@ -63,7 +24,7 @@ const result = UserDeviceSchema.parse(data);
 
 ## UserDevice
 
-[PLANNED — not yet served] A push device of one user: one row per app install. No table stores it yet; the device registry lands with the push channel
+A push device of one user: one row per app install
 
 ### Properties