Change names of NormAction#62
Merged
Merged
Conversation
…ss pipeline NormAction's vendor-surface field is now `source` (was `channel`), and the normalizer-extracted-field namespace is `parameter`/`parameters` (was `entity`/`entities`). Touches every layer: types, DSL schemas, packs, audit chain, UI labels, tests, and docs. Highlights: - File rename: `eval/entity.rs` → `eval/parameter.rs` - Pack file renames: `_channel.yaml` → `_source.yaml` (gmail / outlook / template packs) - Test fixes: pack_snapshot expected JSON reordered alphabetically; pack_integration switched test input from `entity.*` to `parameter.*`; cli_tests scaffold filename + `Channel:` substring assertion updated. - UI relabel: dashboard audit table distinguishes `Source` (vendor) from `Decision Source` (origin of the decision); JS render now reads `r.decision_source` for the second column. - Bootstrap LLM prompt + mock response retaught with the new key names. - Docs: README, docs/taxonomy.md, docs/installation.md. - Pack lockfile regenerated. Note: existing Postgres deployments need a separate `channel` → `source` column rename on `audit_entries` and `pending_approvals`. Not bundled. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Both `apply_calibration` and `await_ui_wait_approval` previously wrote to policy_cache after a human verdict, so a one-time human approval silently whitelisted the same norm_hash for the cache TTL. For high-risk Medium+ tier actions this is the wrong default — every HITL-routed call must re-prompt the reviewer. Remove both post-resolution cache writes. The engine itself already skips caching when permission is HITL (engine.rs:329); this matches that policy at the post-resolution sites too. Operational note: deployments with existing policy_cache rows should TRUNCATE policy_cache so previously-approved norm_hashes don't keep short-circuiting. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ings, packs, and clients Completes the rename started in a16760f. The earlier commit covered the Rust pipeline + UI; this one sweeps: - OpenClaw TS integration: Decision interface + Permit0Client validator + 5 fixture JSONs + 6 test files. Splits the old `source` field into `source` (vendor surface) and `decision_source` (decision origin) to match CheckResponse exactly. - Python client SDK: Decision dataclass, check_action/guard signatures, wire payload keys, and tests. Old `source` field becomes `decision_source` to avoid collision with the renamed vendor `source`. Breaking for SDK consumers: `channel=`→`source=`, `entities=`→`parameters=`. - Bindings: permit0-node/index.d.ts NormAction shape; permit0-py test accessors (.channel → .source). - Packs/docs: CLAUDE.md, gmail/outlook normalizer comments, _template normalizer + risk_rules, tests/shared README + fixture, corpora calibration comment, plus a stray comment in permit0-cli and permit0-dsl. pack.lock.yaml regenerated. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
fafaisland
approved these changes
May 26, 2026
The rsa Marvin Attack advisory only reaches us through sqlx-mysql in Cargo.lock. sqlx is built with default-features=false and the postgres feature only, so the mysql driver never compiles — confirmed via cargo tree -e normal. Matches the existing pattern for RUSTSEC-2026-0097. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix #61