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
Commit 30ff9f4
Browse filesBrowse the repository at this point in the historyBrowse files
docs(skills): objectstack-data teaches the field permission when and when to pick it over a validation rule
`rules/security.md` gains a section on the row-conditioned edit lock: the
choice rule (a lock for everyone is a validation rule; a lock that depends
on who edits is `when` on that set's field entries, never both), the
contract example, the four boundaries (edit vote only, same object,
pre-image on update, locks and never grants) and the docs pointers.
`SKILL.md`'s `readonlyWhen` line names the per-role alternative inside the
file's headroom. One eval case pins the contract prompt. The two touched
token-ratchet rows are raised by the measured remainder under the
maintainer's ruling quoted beside them.
Claude-Session: https://claude.ai/code/session_01JQwxbakp4nDuCkULsj7Fyr
Co-authored-by: Claude <noreply@anthropic.com>
"prompt": "Finance may edit a contract's legal terms (`governing_law`, `liability_cap`) while it is a draft, but not once it is approved, signing or active. Legal still edits them.",
47
+
"expected_output": "Field permission entries with a row condition on the finance set: `'clm_contract.governing_law': { readable: true, editable: false, when: \"status in ['approved', 'signing', 'active']\" }` and the same for `liability_cap`; the legal set keeps its edit grant. No validation rule and no `readonlyWhen`, which would lock the fields for every user.",
0 commit comments