Skip to content

Clarify approval boundaries and operator conformance - #4

Merged
niejingchuan merged 1 commit into
mainfrom
codex/acc-approval-operator-conformance
Aug 4, 2026
Merged

Clarify approval boundaries and operator conformance#4
niejingchuan merged 1 commit into
mainfrom
codex/acc-approval-operator-conformance

Conversation

@niejingchuan

Copy link
Copy Markdown
Contributor

Summary

  • clarify that approval.when is evaluated per invocation and cannot enforce aggregate or rolling-window limits
  • define portable in, contains, and exists semantics using strict JSON behavior
  • expand the ACC v1 reference corpus from 18 to 26 vectors
  • add read-only CI for repository, conformance, and test checks
  • prepare the compatible ACC v1.0.5 patch release

Compatibility

This change adds no ACC Core field, changes no declaration schema, and requires no declaration migration. Stateful cumulative controls remain in the authoritative business or policy layer.

Validation

  • npm run check
  • git diff --check
  • npm pack --dry-run --json

@niejingchuan
niejingchuan merged commit 2aae4e4 into main Aug 4, 2026
2 checks passed
@niejingchuan
niejingchuan deleted the codex/acc-approval-operator-conformance branch August 4, 2026 05:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant