Register did:cha2a method

[wwumit]

Summary

Registers the did:cha2a DID method in the W3C DID Extensions registry.

did:cha2a is a registry-mediated DID method: the prefix ch abbreviates
complianceHub, a2a denotes agent-to-agent. A did:cha2a identifier names a
resource (publisher, authority, agent, skill, MCP server, AI tool, LLM, or the
registry itself) registered in a cha2a Registry. Resolution returns a W3C DID
Document whose verification key is the Registry's Ed25519 signing key and whose
service endpoints expose trust lookup, signed trust proofs, and trust badges.
The resource-type set follows the shared open convention of registry-mediated
methods for interoperability.

Status

• Reference implementation live at https://compliancehub.cn
  (HTTPS; Node on 127.0.0.1 reverse-proxied by nginx on port 443, reusing the
  site's TLS certificate; no public port opened)
• Spec: draft v0.1, Apache-2.0
• Editor: wwumit (complianceHub)

[github-actions]

🤖 AI Preliminary Specification Review

This is an advisory, automated review of the DID Method specification(s) referenced in this pull request, checked against the registration checklist. It does not replace review by the registry editors.

✅ All reviewed submissions passed the preliminary checklist review. A registry editor will still perform the final review.

methods/cha2a.json — method did:cha2a

Specification: https://github.com/wwumit/did-method-cha2a/blob/main/did-method-cha2a.md

Preliminary verdict: ✅ PASS

The did:cha2a specification is a recognizable, well-structured DID Method spec with defined syntax, CRUD operations, and named Security/Privacy Considerations sections; all MUST criteria are satisfied at least plausibly. Full substantiveness of Security/Privacy sections could not be fully verified due to truncation, so those are noted as passing based on visible structure.

	Item	Level	Status	Notes
✅	M1. Specification reachable and is a DID Method spec	MUST	pass
✅	M2. DID Method Syntax defined	MUST	pass
✅	M3. CRUD operations defined	MUST	pass
✅	M4. Security Considerations present and substantive	MUST	pass
✅	M5. Privacy Considerations present and substantive	MUST	pass
✅	M6. Method name indicative and non-generic	MUST	pass
✅	M7. No unreasonable harms	MUST	pass
✅	M8. Human-readable description	MUST	pass
✅	S1. contactEmail present	OPTIONAL	pass
✅	S2. verifiableDataRegistry present	OPTIONAL	pass
✅	S3. Intellectual-property posture clear	SHOULD	pass