[Implementer track] Independent ACC v1 parser or policy component

[niejingchuan]

Objective

Validate that ACC v1 can be implemented independently of BailingHub and of any particular gateway, agent framework, or business system.

This is intentionally split into small tracks. A contributor does not need to build a complete runtime.

Track A: OpenAPI Binding Parser

Build a parser in any language that:

1. reads x-agent-capability from OpenAPI operations;
2. validates declarations against the ACC v1 schema;
3. exposes normalized operation-level declarations;
4. reports its result against the Binding Parser profile and published conformance vectors.

Track B: Binding Generator

Build a generator or authoring helper that:

1. emits ACC v1 declarations without inventing runtime policy;
2. preserves the separation between capability reach and final business authority;
3. validates its generated output;
4. publishes at least one non-trivial multi-operation example.

Track C: Policy Component

Add a bounded ACC-aware component to an existing gateway or runtime that consumes one or more portable declarations, for example:

• enabled and operation exposure;
• scope matching;
• subject.required enforcement at the trusted runtime boundary;
• approval intent and exact-argument binding.

The component must not claim to replace the business system's final authorization decision.

Minimum public evidence

A candidate implementation should publish:

• source code in a repository independent of BailingHub;
• the ACC profile it implements;
• a completed self-assessment;
• reproducible test or conformance output;
• known limitations.

Useful starting points:

• Quick start
• Implementer guide
• Implementation profiles
• Order-service example
• CLI: npx agent-capability-contract your-openapi.yaml

What this issue is not

• It is not a request to adopt BailingHub.
• It is not a certification promise or endorsement.
• It is not a request to replace OPA, API gateway policy, IAM, or business authorization.

Maintainers can use this issue to declare a track, ask a semantics question, or link an independent implementation. Once public code and reproducible evidence exist, the implementation can be reviewed for inclusion in IMPLEMENTATIONS.md under the same neutral criteria as any other implementation.