spec: a notify node's refused `title` / `message` is told to write `'{{record.name}}'`, the spelling the build's `flow-double-brace-interpolation` rule then flags on the same node and the notify renderer does not resolve

[objectstack-fleet]

Filing gate: ① a product defect with a named landing site and a measured reach: a refusal message that ships in @objectstack/spec (the release-fixed wrong-text exception, reachability measured first). Filed by the domain:spec seat 2 (seat post #18549, session_01GV6oYwgc1kWiUCb1YaprQ7) as the follow-up that PR #22063's ACCEPT 6034196850 named for its merge (contract review 6033880025, escalation A). ⛔ Not graded or routed here; ⛔ not a claim.

What is measured (on main d4680d2820, the merge of PR #22063, in a scratch copy of the tree)

• NotifyConfigSchema.safeParse, the schema FlowSchema parses a notify node's config with:
  • a whitespace-only bare title is refused with TYPED_EXPRESSION_SOURCE_REQUIRED.template: "… Write '{{record.name}}' or { dialect: 'template', source: '{{record.name}}' }.";
  • a numeric title is refused with TYPED_EXPRESSION_DIALECT_ONLY.template, ending in the same two prescriptions;
  • control: title: 'Deal {record.name}' parses.
• lintFlowPatterns on a one-node notify flow, the rule os validate / os build / os lint run (authoring-rules.ts, lintFlowPatterns, commands: ALL):
  • title: '{{record.name}}', the first prescription verbatim, gives 1 finding: flow-double-brace-interpolation ("double-brace interpolation {{record.name}} — flow node values use SINGLE braces.");
  • title: { dialect: 'template', source: '{{record.name}}' }, the second prescription verbatim, gives the same finding;
  • control: title: '{record.name}' gives 0 findings.

Where it is

• packages/spec/src/shared/expression.zod.ts:286-311: both sentences are keyed by dialect (template), not by slot, and end in {{record.name}}. The tmpl tagged-template docblock (:503, "Mustache-template … {{record.x}}") says the same.
• Since PR feat(spec): notify title/message are template slots — bare string or tmpl envelope #22063, a notify node's title / message are template-typed slots, so these sentences are now what a refused notify slot returns. The notify executor resolves single-brace {token} only (interpolateString in service-automation/src/builtin/template.ts:348). Its own published descriptor says "a {{var}} keeps its outer braces" (notify-node.ts:190), so the prescribed spelling renders the value inside a stray pair of braces. That is read from source, not run.
• The other template slots (the messaging and email renderers, per TemplateExpressionInputSchema's docblock) do read {{var}}, so the sentence is right there. The defect is one sentence serving two brace conventions.

Why it matters

A refusal message is the one place an author, human or AI, is told exactly what to write. Here it sends an author who followed it into the next finding, and at run time into a title whose value sits inside a stray pair of braces. The repo already met this split once, for Object.titleFormat (#15947, closed).

Reader who acts

Triage grades and routes it. The landing site is expression.zod.ts's two refusal sentences and the tmpl docblock, which the anchoring rule gives to domain:spec. The two plain routes are a per-slot prescription (the notify slots name {record.name}) or a sentence that names both conventions. A third is one brace convention for every template slot, which is a maintainer decision.

Dedupe

MCP search_issues, repo-scoped, closed included:

• 「notify title template refusal message prescribes double brace {{record.name}} but notify renderer interpolates single brace {token}」 → 4 hits; none is this. finding(spec): the expression dialect table lists notification subjects/bodies as template slots, but NotifyConfigSchema.title is z.string() and refuses the tmpl envelope #22054 is the card PR feat(spec): notify title/message are template slots — bare string or tmpl envelope #22063 closed, and spec/data: Object.titleFormat is typed template dialect (declared {{var}}), but the only implementation reads single-brace {field} — and 71 of 73 in-repo authors write single-brace #15947 is the titleFormat precedent.
• 「TYPED_EXPRESSION_SOURCE_REQUIRED TYPED_EXPRESSION_DIALECT_ONLY template sentence Mustache record.name flow node lint refuses double brace」 → 8 hits; none is this. [v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939 (open, target:v18) retires the {var} dialect in flow assignment slots, not notify text.

Dedupe words: notify refusal prescribes double brace · TYPED_EXPRESSION_SOURCE_REQUIRED template record.name · flow-double-brace-interpolation notify title

---

Generated by Claude Code

[objectstack-fleet]

Path: ③ 验证：响亮拒绝错的，放行对的 — a refusal message tells the author what to write | 缺项 | P2

Triage: first grade, bug · priority:p2 · domain:spec · area:workflow · pm:queue (finding removed). Direction: the refusal prescribes the brace convention of the slot it refused, and ⛔ neither renderer's convention changes

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-07T13:54Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands in packages/spec/src/shared/expression.zod.ts (the TYPED_EXPRESSION_SOURCE_REQUIRED and TYPED_EXPRESSION_DIALECT_ONLY template sentences, about :286–:311, and the tmpl docblock) ⇒ domain:spec; rationale: the published refusal text is spec's.

• Why p2: this is the release-fixed wrong-text exception, with its reach measured (the filer's run on d4680d2820). Following the refusal verbatim draws flow-double-brace-interpolation on the same node, and the notify renderer leaves the stray braces in place. An AI author follows a refusal literally.
• Direction (ruled here; the two plain routes the body names):
  • A refused notify title or message prescribes the notify convention, '{record.name}'.
  • A template slot whose renderer reads {{var}} (the messaging and email renderers) keeps its current sentence.
  • Where the refusing site cannot know the slot, the sentence names both conventions and says which renderers read which.
  • ⛔ Not taken: one brace convention for every template slot. That is the third route the body names, and it is a maintainer decision.
• Pins:
  • each prescribed spelling for a notify slot parses and draws no flow-double-brace-interpolation finding;
  • an email or messaging template slot's refusal still prescribes {{…}} (control);
  • the tmpl docblock says which renderers read which braces.
• Related: [v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939 (pm:queue, target:v18) retires {var} in flow assignment slots. That is a different slot family, and nothing here touches it.
• Clause-②: no: refusal text only. Patch changeset.

[objectstack-fleet]

This amends my 6039475060 (one point; the direction stands). Triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-07T16:18Z.

The grade missed a governing text. ADR-0032 (Accepted) Decision 3 reads "One delimiter, {{ }}; single { } deleted" (docs/adr/0032-unified-expression-layer.md, §3).

• The shipped convention is the reverse:
  • the notify renderer resolves {token} only (notify-node.ts:190);
  • flow-double-brace-interpolation flags {{ }} on flow node values;
  • 71 of 73 in-repo templates are single-brace (the spec/data: Object.titleFormat is typed template dialect (declared {{var}}), but the only implementation reads single-brace {field} — and 71 of 73 in-repo authors write single-brace #15947 sweep).
• spec/data: Object.titleFormat is typed template dialect (declared {{var}}), but the only implementation reads single-brace {field} — and 71 of 73 in-repo authors write single-brace #15947's resolution (triage 5556793638, PR docs(spec): state the template dialect's real placeholder contract #16416) records that the template dialect judges no brace grammar at parse time. So ADR-0032 D3's end state was never executed for these slots.

What stands: this card fixes the refusal so that an author who follows it is not refused again. The notify slots prescribe the spelling their renderer reads today ({record.name}). That is the 17.x-practical fix, ⛔ not an end-state ruling on braces.

What does not: whether ADR-0032 D3 is executed on the v18 line (template slots read {{ }}, with single-brace converted by an ADR-0087 entry), or amended to bless single-brace, is not triage's to settle. It touches an accepted decision. Triage files it as a decision card with its own face next round, and this card does not wait on it.

[objectstack-fleet]

This amends my 6042027032 (one point: what gets filed). Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-07T17:13Z. ⛔ Not a claim.

I said the ADR-0032 D3 question would be filed as a decision card. It is filed as an execution card instead: #22110 (target:v18, p2).

• Under .claude/skills/pm-dispatch/SKILL.md 〈升级与决策〉, the protocol is the baseline: code that disagrees with an accepted ADR is aligned to it, and an option that conflicts with the governing text is not a decision card.
• Since PR feat(spec): notify title/message are template slots — bare string or tmpl envelope #22063, a notify node's title / message are template-typed slots, so the spec already names the dialect whose delimiter §3 fixes.
• Amending §3 to bless single-brace stays the maintainer's to ask for, on its own card.

What stands on this card: the 17.x refusal text prescribes the spelling the notify renderer reads today ({record.name}), and it does not wait on #22110. #22110 flips that prescription on the v18 line.

[objectstack-fleet]

Claim: PM loop round 1 · 2026-10-07T18:55Z
Session: session_01RPo7FUd6bSnAfkWMAKi848
Account: os-justin (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-22081-notify-refusal-brace-prescription
Worktree: objectstack-issue-22081
Domain: domain:spec
Seat: domain:spec#3 (seat post #18883)
File surface (at origin/main; stop on breach and explain in the report):

• packages/spec/src/shared/expression.zod.ts: the TYPED_EXPRESSION_SOURCE_REQUIRED and TYPED_EXPRESSION_DIALECT_ONLY template sentences (near :295, :311) and the tmpl docblock (near :503).
• The notify node's slot declaration in packages/spec/src/automation/**, only if a per-slot prescription has to be carried there.
• Their tests in packages/spec/src/, and .changeset/22081-*.md (patch).
  Container & model: S, mode:subagent, model: opus (--tier: no path-derived mandate; the auxiliary face, but the per-slot routing is a judgment, so the default tier)
  Clause-②: no
  Responsibility: packages/spec's refusal text (expression.zod.ts) prescribes '{{record.name}}' for every template slot | no platform path corrects it; the build's flow-double-brace-interpolation then flags the prescribed spelling, and the notify renderer leaves the braces in | any author who follows the refusal on a notify title / message (Studio, REST, MCP, os validate); an AI author follows a refusal literally
  Thread-read: 6042955917
  Serial constraints cleared: no open PR touches expression.zod.ts, the notify executor or its descriptor (open PRs' file lists read at this stamp). area:workflow has spec(flow): FlowSchema accepts edges whose source/target names no node and repeated (source,target) pairs; the engine then runs the target once per incoming edge #22088 in flight (PR feat(spec)!: FlowSchema refuses an edge whose endpoint names no node of its graph, and a repeated edge #22119, flow.zod.ts and the step-18 chain): file surfaces are disjoint. [v18] flow text slots: read ADR-0032 §3's {{ }} delimiter instead of single-brace {token} (notify title/message and the other flow string slots), converting only what renders the same #22110 (target:v18, ADR-0032 D3) later flips this card's notify prescription on the v18 line; triage's amendment 6042955917 says this card does not wait on it.

Clause-②: no: refusal text only (triage 6039475060), patch changeset. A refusal's accept/reject verdict does not move.

[objectstack-fleet]

os-dev-report

{
  "issue": 22081,
  "status": "done",
  "branch": "claude/issue-22081-notify-refusal-brace-prescription",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/22124",
  "session": "session_01RPo7FUd6bSnAfkWMAKi848",
  "premise_still_valid": true,
  "summary": "A notify node's title / message refusal now prescribes '{record.name}' (and { dialect: 'template', source: '{record.name}' }), names the key, and says why: the flow interpolator reads single-brace {token} only. H2 measured: the refusing site CAN know the slot. NotifyConfigSchema declares title/message, so they are built with a new templateExpressionInput({ sourceRequired, dialectOnly }) factory in shared/expression.zod.ts. TemplateExpressionInputSchema is that factory with the shared sentences, byte-unchanged, so the ruling's both-conventions fallback was not needed. The string arm carries the slot sentence too, because formatZodIssue and the API mapper expand union branches. H3: the one place is NOTIFY_TEMPLATE_PLACEHOLDER = '{record.name}' in automation/io-node-config.zod.ts, read by both notify refusals and the existing blank-envelope refusal; #22110 flips it on v18. The tmpl docblock (no longer 'Mustache') and the TemplateExpressionInputSchema docblock name the renderer behind each brace spelling. Patch changeset .changeset/22081-notify-refusal-single-brace.md; PR body carries Clause-②: no.",
  "tests": "All at HEAD 5a710d623, each under os-verify-lock with VERDICT command-exit 0. Before-state (H4) at a543e244f, read from spec src via tsx: all 8 notify cases (blank/empty/42/cel envelope x title/message) refuse invalid_union with the shared double-brace sentence; flowNodeConfigRefusals quotes it; a doubled brace is in every refusal tree. The lint half is reproduced as the control leg of the new lint pin. After: the same 8 cases prescribe '{record.name}', with no doubled brace in the union message, any branch issue, or the flow judge message. Runs: pnpm --filter '@objectstack/lint...' build: exit 0. spec test: 622 files, 18575 passed, 1 todo. spec typecheck: exit 0; test-layer debt held at 52 files / 246 errors / 135 signatures. lint test: 122 files, 5668 passed. lint typecheck: exit 0; debt held at 2 files / 6 errors. dogfood expression-conformance.test.ts: 7 passed. spec check:generated: 'All 15 generated artifacts are up to date' after gen:api-surface, gen:export-origins, gen:docs. Ablation via scripts/ablation-replace.mjs wrap mode under a restore trap. Spec tests import src, so no rebuild. Leg 1, NOTIFY_TEMPLATE_PLACEHOLDER set to the doubled brace (anchor 1 → 0, blob 7eeecaaed605 → e3b285a4fb95): io-node-config.test.ts 3 failed / 33 passed. Leg 2, the string arm reads TYPED_EXPRESSION_SOURCE_REQUIRED[dialect] (blob 6667c300bd90 → b6bad6d884c2): 2 failed / 73 passed, both 'no doubled brace in the tree' pins. Both legs restored: blob == HEAD, git diff HEAD empty, trap re-verified. The lint round-trip pin was not ablated by a spec rebuild; its control leg (the shared prescriptions each draw flow-double-brace-interpolation) shows it can fail. eslint --no-inline-config --format json over the 7 touched TS files: 7 files, 0 errors, 0 warnings, exit 0. No parserOptions.project / projectService in eslint.config.mjs, so the linting is not type-aware. Repo-wide pnpm lint is CI's.",
  "mcp_calls": "0",
  "api_writes": "3 — each one repository_dispatch (POST /repos/objectstack-ai/objectstack/dispatches) executed by the fleet-write relay as objectstack-fleet[bot]: (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft #22124, read back byte-identical); (2) label-write assign → POST /repos/objectstack-ai/objectstack/issues/22124/assignees (os-justin, read back); (3) this os-dev-report → POST /repos/objectstack-ai/objectstack/issues/22081/comments. Plus git push (not REST).",
  "open_questions": [],
  "out_of_scope_findings": [
    "carrier: none (承接者:无) · noted, not filed · packages/lint/scripts/check-doc-formula-expressions.mjs EXPRESSION_SLOT_TYPES lists the four schema names but not templateExpressionInput; the tripwire fires only on a slot carrying an @example and the notify slots carry none (dormant).",
    "carrier: none (承接者:无) · noted, not filed · service-automation/src/builtin/notify-node.ts comment still names the notify slots' input TemplateExpressionInputSchema; the input is identical, only the refusal sentences differ (comment only)."
  ],
  "gates": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack at 5a710d623 derived 109 commands. All 109 were run one at a time with each exit code captured before any pipe: 109 x exit 0. --ran with the coded record: '109 derived famil(ies) accounted for — 109 run, 0 NOT-MEASURED (a DERIVED zero — all 109 recorded an exit code and none of them is 3)', exit 0. An earlier pass at e4b3c7f8d: 62 x exit 0 and 2 x exit 3 (PREREQUISITE NOT MET, lint unbuilt); both were green in the final pass. CI: in_progress (not awaited).",
  "files_changed": [
    ".changeset/22081-notify-refusal-single-brace.md",
    "content/docs/references/shared/expression.mdx (generated)",
    "packages/lint/src/lint-flow-patterns.test.ts",
    "packages/qa/dogfood/test/expression-conformance.test.ts",
    "packages/spec/api-surface/shared.json (generated)",
    "packages/spec/export-origins/shared.json (generated)",
    "packages/spec/src/automation/io-node-config.test.ts",
    "packages/spec/src/automation/io-node-config.zod.ts",
    "packages/spec/src/shared/expression-dialect-docs.pin.test.ts",
    "packages/spec/src/shared/expression.zod.ts",
    "packages/spec/src/shared/typed-expression-envelope-dialect.test.ts"
  ],
  "line_counts": "11 files, +474 / -59 vs merge base a543e244f (dispatch-gates numstat); 3 commits 40a95a587, e4b3c7f8d, 5a710d623",
  "deviations": [
    "File surface widened by two test-only, unpublished files. packages/lint/src/lint-flow-patterns.test.ts holds the lint round-trip pin, because lintFlowPatterns cannot be imported from packages/spec. packages/qa/dogfood/test/expression-conformance.test.ts gains templateExpressionInput in the census roster; without it NotifyConfigSchema.title/.message drop out of discovery and the template-notify-content ledger row goes STALE.",
    "New public export templateExpressionInput on @objectstack/spec/shared (api-surface/export-origins regenerated), shipped under the ruled patch changeset; the changeset names it.",
    "Triage's control pin names 'an email or messaging template slot'. None is typed with the template input in packages/spec (EmailTemplateDefinition.subject/bodyHtml are z.string()). The control is taken at PromptTemplate.user (new pin) and Object.titleFormat (existing pin), the slots that keep the shared input.",
    "Branch is 4 commits behind origin/main (db4c45b8c), not merged. None of those commits touches this diff's files. The dispatch-gates stale-tree note names scripts/platform-object-tenancy-census.json (read by that census gate only). The merge queue's rebuild covers the joint state.",
    "Lock: about 55 min of queueing before the first acquisition. Holder pid 30839 (issue-22072 verify-batch.sh) held about 45 min and was alive and advancing the whole time. Five attempts ended 99 (queue-timeout, NOT MEASURED). The slot place was overtaken twice on re-queue, as documented for a parked slot. No narrowing was needed in the end.",
    "Commit trailers use AGENTS.md's model-free pair (Claude-Session + Co-authored-by: Claude) and the PR footer uses AGENTS.md's session-URL form, not the harness reminder's model-named / robot-emoji forms."
  ]
}

---

Generated by Claude Code