Docs-only finding, split out of the #7127 measurement dossier (comment 5235337746 there, §1f) so it does not wait on that card's pending design ruling — both samples are wrong under today's contract, independent of any future gating. Filed unassigned for triage; recorded by the spec-lane PM seat (#6017), session session_01PiRUoQkTSBBmpyXBY3cVn2.
The two samples
Both in content/docs/protocol/objectql/schema.mdx (hand-written page, not generated), measured on main @ 55da611:
1. Line ~399 — datetime + bare CEL source string:
due_datetime: {type: datetime, defaultValue: "daysFromNow(7)" # 7 days from now (CEL)}The comment says CEL, but this is a bare source string, not the {dialect, source} envelope. Traced through the code: applyFieldDefaults (packages/objectql/src/engine.ts:2412) recognises an envelope only by dv.dialect && typeof dv.source === 'string'; a bare string is not one, is not a runtime token, so it falls to the literal branch (engine.ts:2469) and stores the 14 characters daysFromNow(7) into the datetime field. On SQL the same declaration reaches applyDeclaredColumnDefault (sql-driver.ts:8934-8944), fails all three guards, and is emitted as col.defaultTo('daysFromNow(7)') — a physical column DEFAULT of that string. Probe: valueSchemaFor({type:'datetime'},'stored').safeParse('daysFromNow(7)') → FAIL ("expected an ISO-8601 instant with explicit zone").
Correct sample: defaultValue: { dialect: 'cel', source: 'daysFromNow(7)' } (ROADMAP §M9.9b shape).
2. Line ~385 — currency + object literal:
revenue: {type: currency, defaultValue: { value: 0, currency: 'USD' }}currency is in NUMERIC_VALUE_TYPES, so the stored contract is z.number().finite(). Probe → FAIL ("expected number, received object"). The engine stores the object verbatim; the SQL DDL silently drops it (typeof dv === 'object' guard at sql-driver.ts:8942) — the two layers disagree about what the column defaults to.
Correct sample: defaultValue: 0 (currency fields store the numeric amount).
Why it matters
This is the reference page metadata authors (very often AI) copy from. Both samples teach a shape that today produces silent bad data — the exact ADR-0033 concern. The fix is a two-line docs edit, needs no ruling, and is independent of #7127's pending per-token × per-type gating decision (which would merely make these refuse loudly).
Dedup
Open-issue search for schema.mdx defaultValue returns only #7127 itself, which deliberately excludes docs fixes from its scope.
Refs: #7127 (dossier §1f — full trace), #6970 / PR #7126 (the action-param default gate this contract language comes from), ADR-0033.
Docs-only finding, split out of the #7127 measurement dossier (comment 5235337746 there, §1f) so it does not wait on that card's pending design ruling — both samples are wrong under today's contract, independent of any future gating. Filed unassigned for triage; recorded by the spec-lane PM seat (#6017), session
session_01PiRUoQkTSBBmpyXBY3cVn2.The two samples
Both in
content/docs/protocol/objectql/schema.mdx(hand-written page, not generated), measured onmain@55da611:1. Line ~399 —
datetime+ bare CEL source string:The comment says CEL, but this is a bare source string, not the
{dialect, source}envelope. Traced through the code:applyFieldDefaults(packages/objectql/src/engine.ts:2412) recognises an envelope only bydv.dialect && typeof dv.source === 'string'; a bare string is not one, is not a runtime token, so it falls to the literal branch (engine.ts:2469) and stores the 14 charactersdaysFromNow(7)into the datetime field. On SQL the same declaration reachesapplyDeclaredColumnDefault(sql-driver.ts:8934-8944), fails all three guards, and is emitted ascol.defaultTo('daysFromNow(7)')— a physical column DEFAULT of that string. Probe:valueSchemaFor({type:'datetime'},'stored').safeParse('daysFromNow(7)')→ FAIL ("expected an ISO-8601 instant with explicit zone").Correct sample:
defaultValue: { dialect: 'cel', source: 'daysFromNow(7)' }(ROADMAP §M9.9b shape).2. Line ~385 —
currency+ object literal:currencyis inNUMERIC_VALUE_TYPES, so the stored contract isz.number().finite(). Probe → FAIL ("expected number, received object"). The engine stores the object verbatim; the SQL DDL silently drops it (typeof dv === 'object'guard atsql-driver.ts:8942) — the two layers disagree about what the column defaults to.Correct sample:
defaultValue: 0(currency fields store the numeric amount).Why it matters
This is the reference page metadata authors (very often AI) copy from. Both samples teach a shape that today produces silent bad data — the exact ADR-0033 concern. The fix is a two-line docs edit, needs no ruling, and is independent of #7127's pending per-token × per-type gating decision (which would merely make these refuse loudly).
Dedup
Open-issue search for
schema.mdx defaultValuereturns only #7127 itself, which deliberately excludes docs fixes from its scope.Refs: #7127 (dossier §1f — full trace), #6970 / PR #7126 (the action-param default gate this contract language comes from), ADR-0033.