[boris-ai-sec]

What changed

Adds Boris Abuzov (@boris-ai-sec) to CONTRIBUTORS.md following substantive ACS specification review and discussion around the boundary between conformance claims and human authorization/oversight.

Which issue does this implement

No issue — contributor attribution only; no behavior, normative text, or code changes.

• This is an editorial correction (typo, grammar, link, formatting) with no change in
  meaning, so it needs no issue

Base branch

• integration, because this touches the specification, schemas, a reference
  implementation, an adapter, tests, or CI
• main, because every changed path is on the documentation lane allowlist in
  CONTRIBUTING.md

Type of change

• Specification change (schema, hooks, events, AgBOM)
• Reference implementation or adapter
• Documentation
• Tooling or CI
• Governance (licensing, security policy, contributor docs)

I tested this

• I synced my branch with the base branch before opening this
• uv run pytest -v passes on my machine
• uv run mkdocs build --strict passes on my machine

Local pytest execution was attempted on Windows: 880 tests passed, but the suite did not complete successfully because of Windows-specific subprocess/environment failures (WinError 1314, environment-variable length limits, and Bash/mock-gh execution). The repository's pull-request CI runs the full guard suite on Ubuntu.

Checklist

• Commits are signed off with git commit -s (required by the DCO)
• Prose follows STYLE.md
• No secrets, tokens, or internal URLs in the diff

Security

• This change has no security impact

[github-actions]

Thanks for this. It is queued rather than ignored.

This pull request does not reference an issue carrying status:accepted, so a maintainer has not looked at it yet and will not until the underlying issue is triaged. Nothing here is rejected. See Current Priority Scope for what the project is working on, and help wanted for work that is already accepted.

If this is an editorial correction, tick that box in the description and this comment stops applying.

[boris-ai-sec]

@rocklambros I’ve updated the PR classification to the editorial-correction path, consistent with the current contributor-attribution pattern. This remains a one-line CONTRIBUTORS.md change with no normative text or code impact. When convenient, could you take a look?

[rocklambros]

Thanks for this, Boris, and for your point on issue #51 about tying an approval to the exact action it approved. It's a good one.

We're closing this PR because CONTRIBUTORS.md lists people for work that reached main: code or specification text, or a significant part in designing it. Comments and issue discussion don't add a name on their own. I've updated the file to say that plainly, since its old wording suggested otherwise.

If you'd like to turn your issue #51 point into a spec change, that would be a great way in, and it would put you on the list once it merges.

[boris-ai-sec]

Thanks Rock, that makes sense. I appreciate the clarification.
I’ll take the exact-action binding point from #51 and develop it as a bounded spec contribution, separate from the authentication/timeout work in #342. I’m happy to proceed through the project’s normal discussion and acceptance path.