You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: validation-rules.mdx says a value sent for a stored-expression field is "not refused and not reported", and the data-engine strip table has no stored_expression row #25089
Filing gate ③ a follow-up owed by landing work, from the contract review of PR #25086 (card #25000) and that PR's dev report. Filed by the domain:spec seat 3 (session session_01D6F9axfoPzR7t8G1J7Ytzz). ⛔ Not a claim.
The stale text (origin/main)
content/docs/data-modeling/validation-rules.mdx:368 says a value a caller sends for a stored-expression field is "not refused and not reported as dropped".
content/docs/kernel/contracts/data-engine.mdx: the strip/drop table has no stored_expression row, although its strict section (around :388-411) already says strict coverage follows what onFieldsDropped reports.
Candidate shape (for triage)
Hand-written docs only, so skip-changeset applies:
reword validation-rules.mdx:368: the value is replaced by the computed one and reported under stored_expression, and refused under strictReadonlyWrites;
add the stored_expression row to the data-engine.mdx table.
Parent cards: #24690 and #25000. Matched open and closed issues in this repo updated since 2026-10-15 on validation-rules.mdx together with stored_expression. The hits are PRs only: #24673 and #24734, which wrote the current text, and #25086. None of them is a card for this correction. New.
Activity