Skip to content

docs(rfcs): RFC-AI-0008 — the coordinator role (multi-hop relay of security reports) - #1135

Open
ppkarwasz wants to merge 2 commits into
apache:mainfrom
ppkarwasz:rfc/ai-0008-coordinator
Open

docs(rfcs): RFC-AI-0008 — the coordinator role (multi-hop relay of security reports)#1135
ppkarwasz wants to merge 2 commits into
apache:mainfrom
ppkarwasz:rfc/ai-0008-coordinator

Conversation

@ppkarwasz

Copy link
Copy Markdown
Member

What

Adds RFC-AI-0008 (status: Draft): names the coordinator persona of coordinated vulnerability disclosure — the party that receives, triages on behalf of others, and forwards to the owning vendor — and defines:

  • CVD role vocabulary (finder / reporter / coordinator / vendor), with a strictly pairwise relay contract instead of named chain levels;
  • the coordinator profile (functions + termination authority + upstreams + downstream directory);
  • provenance fields carried verbatim across hops (finder credits, append-only reporter chain, origin references, embargo terms);
  • the handling-identifier exchange between hops;
  • bidirectional forwarder adapters (emit templates + detect signatures in one directory, closing the current two-repo drift gap);
  • coordinator-mode skills (security-coordinator-import / -assess) generalized from the ASF Security team's out-of-tree pipeline, which becomes the reference adopter.

Review fallout (second commit)

Cross-reference verification of the RFC against the tree surfaced two pre-existing inconsistencies, fixed here:

  • tools/forwarder-relay/README.md still documented contact_handle: '@raboof' as the shipping default, contradicting the newer org-level security@apache.org in organizations/ASF/organization.md (feat(organizations): introduce Organization-adapter entity + document adapters #622). The shared inbox is now the documented default; an individual liaison's handle remains the override example. The one stale worked example in docs/security/forwarder-routing-policy.md is updated to match.
  • CONTRIBUTING.md's directory-tree comment enumerated "RFC-AI-0002, 0003, 0004" (stale since 0005); it now says "RFC-AI-0002 onward".

Modified paragraphs are reflowed to semantic line breaks per #1108.

🤖 Generated with Claude Code

https://claude.ai/code/session_018SKtoF3YBbXye9jmnZp1Pt

Names the coordinator persona of coordinated vulnerability
disclosure and defines its profile by function and termination
authority, never by chain position: a pairwise relay contract,
provenance fields carried across hops, the handling-identifier
exchange, bidirectional forwarder adapters, and the
coordinator-mode skills generalized from the ASF Security
team's out-of-tree pipeline.

Assisted-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018SKtoF3YBbXye9jmnZp1Pt
Fallout from the RFC-AI-0008 review:

- tools/forwarder-relay/README.md presented '@raboof' as the
  shipping contact_handle default, contradicting the newer
  org-level security@apache.org declared in
  organizations/ASF/organization.md (apache#622). The shared inbox is
  now the documented default; an individual liaison's handle
  stays as the local override example.
- docs/security/forwarder-routing-policy.md worked example
  updated to cite the same default.
- CONTRIBUTING.md directory-tree comment no longer enumerates
  RFC numbers (was stuck at 0002-0004), so it cannot go stale.

Assisted-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018SKtoF3YBbXye9jmnZp1Pt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant