@@ -0,0 +1,10 @@
+---
+'@objectstack/spec': patch
+---
+
+`record:related_list`'s `parentDataSource` is described as rendered
+
+Clause-②: no (describe and TSDoc text only: `RecordRelatedListProps` accepts exactly what it accepted before, and every refusal keeps its issue `code` and `path`)
+
+- The `parentDataSource` describe no longer opens with `[PLANNED — not yet rendered]`. The console renders the key: a related list reads its parent record from the binding, the first row by its `sort`, and draws a notice in its place when no row answers, never an empty list. Without the key, the record page's record is the parent, as before. The rest of the describe is unchanged.
+- The key's TSDoc names the console's read points in place of the planned note, and no longer calls the `api` data source unrendered.
@@ -1968,7 +1968,7 @@ Sort field and direction pair
 | **objectName** | `string` | ✅ | Related object name (e.g., "task", "opportunity") |
 | **relationshipField** | `string` | ✅ | Field on related object that points to this record (e.g., "account_id") |
 | **relationshipValueField** | `string` | optional (default: `"id"`) | Parent-record field whose value relationshipField stores (default 'id'; e.g. 'name' for name-keyed junctions). |
-| **parentDataSource** | `{ object: string; view?: string; filter?: object[]; sort?: object[]; … }` | optional | [PLANNED — not yet rendered] The PARENT record this related list hangs off, bound by a query of its own: an object binding `{ object, view?, filter?, sort?, limit? }`, the shape `dataSource` takes. Read by the single-record rule: the FIRST row of the bound set by its `sort` is the parent (declare `limit: 1` to say one row is meant), and when no row answers, the block renders a loud absence, never an empty list, which would read as "this record has no related records". `relationshipValueField` is read on that row. When this key is absent, the record page's record context remains the parent. The node-level `dataSource` on this block keeps its published meaning, the CHILD rows the list draws (it fills `objectName`, `columns`, `filter`, `sort` and `limit`), and is never read as the parent. |
+| **parentDataSource** | `{ object: string; view?: string; filter?: object[]; sort?: object[]; … }` | optional | The PARENT record this related list hangs off, bound by a query of its own: an object binding `{ object, view?, filter?, sort?, limit? }`, the shape `dataSource` takes. Read by the single-record rule: the FIRST row of the bound set by its `sort` is the parent (declare `limit: 1` to say one row is meant), and when no row answers, the block renders a loud absence, never an empty list, which would read as "this record has no related records". `relationshipValueField` is read on that row. When this key is absent, the record page's record context remains the parent. The node-level `dataSource` on this block keeps its published meaning, the CHILD rows the list draws (it fills `objectName`, `columns`, `filter`, `sort` and `limit`), and is never read as the parent. |
 | **columns** | `string[] \| { field: string; label?: string \| Record<string, string>; width?: number; align?: Enum<'left' \| 'center' \| 'right'>; … }[]` | optional | Fields to display in the related list — either plain field-name strings, or the same per-column entries a saved list view declares (`ListColumn`: `field`, plus `label`, `width`, `align`, `hidden`, `sortable`, `summary`, …). A view-supplied list may arrive in the `ListColumn` spelling: objectui composes a saved view's `columns` onto this block verbatim, and this key declares the SAME union as `listViews[].columns`. One spelling per list — the two arms are exclusive, so an array mixing strings and column objects is refused. Optional: when omitted, columns derive from the related object's highlightFields / default list columns (a related list is just another surface that lists that object). Override chain: child highlightFields → field-level relatedListColumns (field-name strings only) → this inline list. |
 | **sort** | `string \| { field: string; order: Enum<'asc' \| 'desc'> }[]` | optional | Sort order for related records |
 | **limit** | `integer` | optional (default: `5`) | Number of records to display initially |
 
@@ -18,7 +18,8 @@
 //   D — CONTROL: the node-level `dataSource` on this block is untouched. It is
 //       still the child-row binding (#6953) and parses exactly as it did,
 //       with or without a parent binding beside it.
-//   E — the describe opens with the `[PLANNED — not yet rendered]` marker,
+//   E — the describe carries no planned marker: the console renders the key
+//       (objectui `d81e46043`, at the `.objectui-sha` pin), and a marker is
 //       the one part of the prose a consumer parses (`check-liveness.mts`
 //       `MARKER_RE.planned` reads it as the key's liveness status).
 
@@ -202,10 +203,21 @@ describe('D — CONTROL: the node-level `dataSource` on this block is the child-
   });
 });
 
-describe('E — the describe carries the liveness marker the ledger reads', () => {
-  it('opens with the planned marker, which `check-liveness` reads as the key status', () => {
+/**
+ * `MARKER_RE.planned` in `scripts/liveness/check-liveness.mts`, copied: the one
+ * reading of the prose a consumer parses (as the key's liveness status).
+ */
+const PLANNED_MARKER = /\[planned|not yet implemented|coming soon/i;
+
+describe('E — the describe carries no planned marker: the console renders the key', () => {
+  it('no planned marker, so `check-liveness` reads no planned status off the describe', () => {
     const key = (RecordRelatedListProps as unknown as { shape: Record<string, { description?: string }> })
       .shape.parentDataSource;
-    expect(key.description?.startsWith('[PLANNED — not yet rendered]')).toBe(true);
+    expect(typeof key.description).toBe('string');
+    expect(PLANNED_MARKER.test(key.description!)).toBe(false);
+  });
+
+  it('DARK: the marker this describe opened with is caught by the same matcher', () => {
+    expect(PLANNED_MARKER.test('[PLANNED — not yet rendered] The PARENT record this related list hangs off')).toBe(true);
   });
 });
@@ -1707,7 +1707,8 @@ export const RecordRelatedListProps = strictObject({
    *    as "this record has no related records", a wrong fact in the silent
    *    direction. The API arm of `dataSource` is not admitted: the card fixes
    *    the shape as the object binding's (object, view, filter, sort, limit),
-   *    the one the sibling blocks read, and that arm is still unrendered.
+   *    the one the sibling blocks read and the one objectui's parent read
+   *    takes (`isElementDataSourceConfig` asks the binding for an `object`).
    *
    * Absent, the parent is the record page's record context, as it always was
    * (objectui `RecordRelatedListBody` reads `useRecordContext()`'s `recordId`
@@ -1734,17 +1735,26 @@ export const RecordRelatedListProps = strictObject({
    * ⛔ No `os validate` consistency finding against a sibling `record:details`
    * binding: the ruling's own exclusion (a new gate defaults to no).
    *
-   * PLANNED, not yet read: no renderer reads this key (measured on objectui;
-   * recorded in the `liveness/page.json` `_note`).
-   * Its reader is the related-list leg of objectui#12294, which lands once a
-   * spec release carrying the key is installable. The liveness record is the
-   * `liveness/page.json` `_note` (a component-level key carries no ledger row:
-   * the walk stops at the undrilled `page/regions` container) and the
-   * `[PLANNED — not yet rendered]` marker the describe opens with; when that
-   * leg lands, the marker leaves and the `_note` sentence is rewritten.
+   * RENDERED by the console. The block hands this key to its parent read
+   * (objectui: packages/plugin-detail/src/renderers/record-related-list.tsx,
+   * whose `RecordRelatedListRenderer` passes `schema.parentDataSource` to
+   * `ParentRecordBinding`; the read itself is
+   * objectui: packages/plugin-detail/src/renderers/recordBinding.tsx). Its
+   * `BoundRecordProvider` asks the page's own adapter, so under the caller's
+   * identity, for one row (`$top: 1`) by the binding's `sort`, and provides
+   * that row as the record context the list body reads. No row, or a read the
+   * server refuses as forbidden, draws the block's loud absence in its place
+   * (`NoParentRecord`), and no child rows are queried. Unbound, the list is
+   * left as it is, so the record page's record stays the parent. Measured at
+   * the console pin (`.objectui-sha` `4016370af3`), which carries the reader
+   * (objectui `d81e46043`, objectui#12407, the related-list leg of
+   * objectui#12294). The liveness record is the `liveness/page.json` `_note`
+   * (a component-level key carries no ledger row: the walk stops at the
+   * undrilled `page/regions` container); the describe carries no liveness
+   * marker.
    */
   parentDataSource: ElementDataSourceSchema.optional().describe(
-    '[PLANNED — not yet rendered] The PARENT record this related list hangs off, bound by a query of its own: an object binding `{ object, view?, filter?, sort?, limit? }`, the shape `dataSource` takes. Read by the single-record rule: the FIRST row of the bound set by its `sort` is the parent (declare `limit: 1` to say one row is meant), and when no row answers, the block renders a loud absence, never an empty list, which would read as "this record has no related records". `relationshipValueField` is read on that row. When this key is absent, the record page\'s record context remains the parent. The node-level `dataSource` on this block keeps its published meaning, the CHILD rows the list draws (it fills `objectName`, `columns`, `filter`, `sort` and `limit`), and is never read as the parent.',
+    'The PARENT record this related list hangs off, bound by a query of its own: an object binding `{ object, view?, filter?, sort?, limit? }`, the shape `dataSource` takes. Read by the single-record rule: the FIRST row of the bound set by its `sort` is the parent (declare `limit: 1` to say one row is meant), and when no row answers, the block renders a loud absence, never an empty list, which would read as "this record has no related records". `relationshipValueField` is read on that row. When this key is absent, the record page\'s record context remains the parent. The node-level `dataSource` on this block keeps its published meaning, the CHILD rows the list draws (it fills `objectName`, `columns`, `filter`, `sort` and `limit`), and is never read as the parent.',
   ),
   /**
    * [#18639] The SAME union `listViews[].columns` declares (`view.zod.ts`) —