@@ -0,0 +1,10 @@
+---
+'@objectstack/skills': patch
+---
+
+docs(skills): the objectstack-automation skill names the `save_notice` flow node and points to the save notice's one home
+
+Clause-②: no
+Metadata-protocol: none
+
+`skills/objectstack-automation/SKILL.md` listed no `save_notice` node, so an author designing a "sent for approval" flow from this skill never found it. Its Data Operations table now carries a `save_notice` row that points at `objectstack-data` `rules/lifecycle.md` § Save Notice, which stays the one full teaching. That section gains what the code does and it lacked: a hook's `ctx.notice` message is shown untranslated; a `save_notice` message translates under `flows.<flow>.notices.<node_id>.message` in the saver's locale; the node refuses by name in a `subflow` / `map` child, and a flow with one after a `subflow` / `map` whose child can pause is not armed (`unboundCause: 'notice_after_suspending_subflow'`). `evals/flows-triggers-approvals.json` gains case 16. Growth in both files is paid by same-file deletions of restated text; no ratchet row moves.
@@ -86,14 +86,15 @@ Flows are built from **built-in node types** (plugins register more):
 | `update_record` | Modify existing records |
 | `delete_record` | Remove records |
 | `get_record` | Fetch records with filters — there is **no `query_record`** node (that name has no executor and throws) |
+| `save_notice` | Tell the saver what this create/update started — record create/update trigger only, not after a pause: **objectstack-data** `rules/lifecycle.md` § Save Notice |
 
 #### External Integration
 
 | Node | Purpose |
 |:-----|:--------|
 | `http` | Call an external HTTP API — always set `timeoutMs` (unset = no timeout). `url` and `headers` are served as written with the definition to every member who can read flows — only `signingSecret` and a start node's `secret` are withheld — so never a credential there: a credential means a declared connector called via `connector_action` |
 | `notify` | Send a notification through the messaging service |
-| `connector_action` | Dispatch an action of a declared connector (§ *Integrations are declared, not coded*) or a plugin's. `connectorConfig.input` is a value-slot map like `subflow` `input`: `registerFlow` and `os validate` refuse a `{…}` token at `connectorConfig.input.<key>`. Once evaluated, it is judged against the action's `inputSchema` (`required`, `type`, `properties`, `items`) before dispatch: a breach fails the step `VALIDATION_ERROR` (`fault`-routable), nothing sent; `os validate` does not judge the `inputSchema` fit yet |
+| `connector_action` | Dispatch an action of a declared connector (§ *Integrations are declared, not coded*) or a plugin's. `connectorConfig.input` is a value-slot map like `subflow` `input`. Once evaluated, it is judged against the action's `inputSchema` (`required`, `type`, `properties`, `items`) before dispatch: a breach fails the step `VALIDATION_ERROR` (`fault`-routable), nothing sent; `os validate` does not judge the `inputSchema` fit yet |
 | `script` | Call a **registered** function named by `config.function` (see *Valid-but-silently-wrong* #3) |
 | `screen` | Display a UI form to the user (screen flows only). `config.fields[]`: `{ name, label, type, required, options, defaultValue }`, `type` an open widget hint; `'file'` renders the upload widget and resumes with the `sys_file` id bound to `name` — a later `create_record` / `update_record` writes it into a `file` field, which claims the file: collect first, write after the last screen. `'record_link'` (never `'record'`, an object field type) takes no input — it shows the `reference` record whose id `defaultValue` evaluates to, by display name, as a link to its record page: the result screen of a flow that created records, `{ name: 'account_link', type: 'record_link', reference: 'crm_account', defaultValue: { dialect: 'cel', source: 'account.id' } }` over a `create_record` `outputVariable: 'account'`. Both keys required; `required` / `options` / `placeholder` / `min` / `max` refused; a resume value under its name refused (`400 INVALID_SCREEN_INPUT`). A completed `end` `message` is refused and a markdown link in a screen `description` renders literally. Next / Submit and "Step N of M" are not authored: the engine reads the graph when the screen pauses and serves `progress` (`nextScreen: 'none' | 'possible' | 'certain'`; `step` / `stepCount` only when every path agrees), which alone labels the button and draws the counter. A `decision`, `fault` edge, loop back, non-screen pause (`approval`, `wait`) or `subflow` after a screen answers `possible` — "Next", no count. `progress` in a node `config` is refused; never hand-roll a button label or step counter into `fields` |
 
@@ -328,9 +329,8 @@ for the same people is `approvers: [{ type: 'queue', value: 'crm_support_intake'
 
 ## Triggers — Event-Driven Automation
 
-A `record_change` flow fires on a data event; there is **no standalone trigger
-object and no top-level `trigger` / `event` key** — the binding is the `start`
-node's `config`.
+There is **no standalone trigger
+object and no top-level `trigger` / `event` key**.
 
 ### Prerequisite — declare the capabilities your nodes need
 
 
@@ -277,6 +277,23 @@
           "| label"
         ]
       }
+    },
+    {
+      "id": 16,
+      "prompt": "When a saved `deal` record's `status` is changed to `submitted`, route it to the sales manager for approval, and tell the person who clicked Save \"Sent {{ record.name }} to your manager for approval\" on the save toast, in their own language.",
+      "expected_output": "A flow whose start node binds `objectName: 'deal'` with `triggerType: 'record-after-update'` and the condition `previous.status != 'submitted' && record.status == 'submitted'` (on update `previous` is bound), then a `save_notice` node (`config.message: 'Sent {{ record.name }} to your manager for approval'`) placed BEFORE the approval node (`type: 'approval'`): the run is still inside the write there, while a `save_notice` reachable after the approval (or a `wait`) is refused at parse. The translation lives under `flows.<flow>.notices.<node_id>.message`, read in the saver's locale. Not a `notify` node to the saver (an inbox message, not the save answer), not a page banner component (shown whenever the record's state says so, not for this save), and not in a subflow the trigger flow calls (a child run holds no save, so the node refuses by name).",
+      "files": [],
+      "assertions": {
+        "must_contain": [
+          "save_notice",
+          "triggerType",
+          "notices.",
+          "type: 'approval'"
+        ],
+        "must_not_contain": [
+          "type: 'record:alert'"
+        ]
+      }
     }
   ]
 }
@@ -1,7 +1,7 @@
 # Data Lifecycle & Retention
 
 Guide for declaring how long an object's data lives and how its space is
-reclaimed (ADR-0057 — system data lifecycle & retention). Distinct from
+reclaimed (ADR-0057). Distinct from
 **lifecycle hooks** (`beforeInsert` / `afterUpdate` …), which run logic on
 writes: this page covers the rows' retention, rotation and archival
 — and, at its end, the save notice a hook hands the saver.
@@ -38,7 +38,7 @@ export const ApiCallLog = ObjectSchema.create({
   lifecycle: {
     class: 'telemetry',
     retention: { maxAge: '14d' },                                // reap past 14 days (created_at)
-    storage: { strategy: 'rotation', shards: 14, unit: 'day' },  // O(1) shard DROP on SQLite
+    storage: { strategy: 'rotation', shards: 14, unit: 'day' },
   },
   fields: {
     endpoint: Field.text({}),
@@ -79,7 +79,7 @@ export const AutomationRun = ObjectSchema.create({
     class: 'telemetry',
     retention: {
       maxAge: '30d',
-      onlyWhen: { status: { $in: ['completed', 'failed'] } },  // paused rows never reaped
+      onlyWhen: { status: { $in: ['completed', 'failed'] } },
     },
   },
   fields: {
@@ -88,8 +88,7 @@ export const AutomationRun = ObjectSchema.create({
 });
 ```
 
-Duration literals: `<n>` + `h` / `d` / `w` / `y` — e.g. `'6h'`, `'14d'`,
-`'12w'`, `'7y'`.
+Duration literals: `<n>` + `h` / `d` / `w` / `y`.
 
 ## Validation Rules (rejected at parse time)
 
@@ -117,12 +116,10 @@ lifecycle: {
 
 ## Safety Semantics
 
-- **No `lifecycle` block = today's behavior**: `record` is the implicit default.
 - **Archive-then-delete is atomic-ish and safe by default**: an object
   declaring `archive` is never hot-deleted before the copy to the archive
   datasource succeeded. If no datasource is registered under the `archive.to`
-  name, rows are simply retained — a compliance ledger cannot be destroyed
-  by declaring a lifecycle.
+  name, rows are simply retained.
 - **Rotation** physically time-shards the table on SQLite (writes hit the
   current shard, reads go through a view under the object's name, expired
   shards are DROPped). Other dialects enforce the same window with an
@@ -155,6 +152,11 @@ record's state says so; the notice is for what *this* save started.
   import, a nested write) sets nothing.
 - Not a non-empty string ⇒ the write refuses; a refused write answers its
   error, no notice.
+- A hook's message is untranslated.
 - A flow a record create/update trigger starts sets it with a `save_notice`
   node (`config.message`, `{{ }}` renders); refused in any other flow, and
   after an `approval` / `wait`.
+  Its message translates under `flows.<flow>.notices.<node_id>.message`
+  in the saver's locale.
+  Refused by name in a `subflow` / `map` child; after one whose child can
+  pause, the flow is not armed (`unboundCause: 'notice_after_suspending_subflow'`).
Original file line number	Diff line number	Diff line change
`@@ -277,6 +277,23 @@`
`277`	`277`	`"\| label"`
`278`	`278`	`]`
`279`	`279`	`}`
	`280`	`+ },`
	`281`	`+ {`
	`282`	`+ "id": 16,`
	`283`	+ "prompt": "When a saved `deal` record's `status` is changed to `submitted`, route it to the sales manager for approval, and tell the person who clicked Save \"Sent {{ record.name }} to your manager for approval\" on the save toast, in their own language.",
	`284`	+ "expected_output": "A flow whose start node binds `objectName: 'deal'` with `triggerType: 'record-after-update'` and the condition `previous.status != 'submitted' && record.status == 'submitted'` (on update `previous` is bound), then a `save_notice` node (`config.message: 'Sent {{ record.name }} to your manager for approval'`) placed BEFORE the approval node (`type: 'approval'`): the run is still inside the write there, while a `save_notice` reachable after the approval (or a `wait`) is refused at parse. The translation lives under `flows.<flow>.notices.<node_id>.message`, read in the saver's locale. Not a `notify` node to the saver (an inbox message, not the save answer), not a page banner component (shown whenever the record's state says so, not for this save), and not in a subflow the trigger flow calls (a child run holds no save, so the node refuses by name).",
	`285`	`+ "files": [],`
	`286`	`+ "assertions": {`
	`287`	`+ "must_contain": [`
	`288`	`+ "save_notice",`
	`289`	`+ "triggerType",`
	`290`	`+ "notices.",`
	`291`	`+ "type: 'approval'"`
	`292`	`+ ],`
	`293`	`+ "must_not_contain": [`
	`294`	`+ "type: 'record:alert'"`
	`295`	`+ ]`
	`296`	`+ }`
`280`	`297`	`}`
`281`	`298`	`]`
`282`	`299`	`}`