Canonical names for governance primitives across multi-issuer agent ecosystems.
Precedent: IANA JWT claim registry, JSON-LD @context. Each system keeps its internal code. This repo provides shared reference + per-system crosswalks.
v0.1 draft. Open for Working Group review. Co-authored:
- @aeoess - APS
- @QueBallSharken - descriptor dimensions, BBIS-aligned distinctions
- @douglasborthwick-crypto - InsumerAPI / SkyeProfile, scope layering
- @MoltyCel - MolTrust / AAE, typed schema discipline
- WG members invited
Three layers, distinct altitudes, cross-reference via this repo:
vocabulary.yaml- canonical names for abstract governance primitives (signal types, descriptor dimensions, match semantics)MULTI-ATTESTATION-SPEC.md(lives in insumer-examples) - canonical envelopetypefield values for multi-issuer verificationcrosswalk/<system>.yaml- per-system mappings between internal names and canonical names
Renaming live signed envelope type values is explicitly out of scope - canonical aligns with what is already in production.
Open a PR adding crosswalk/<your-system>.yaml. Use the match types from vocabulary.yaml > crosswalk_match_types. Partial match and non-equivalent-similar-label are encouraged - this layer exists to clarify differences, not hide them.
Committed contributors so far:
crosswalk/insumerapi.yaml- @douglasborthwick-cryptocrosswalk/satp/behavioral-trust.yaml- SATP / @aeoesscrosswalk/aps.yaml- @aeoess (this week)crosswalk/rfc-category-taxonomy.yaml- reverse crosswalk mapping the ten MULTI-ATTESTATION-SPEC signal_types to the (proposed) A2A RFC trust evidence category taxonomy. Drafted on @douglasborthwick-crypto's offer per A2A Discussion #1734 (@AlexanderLawson17). Eight of ten rows currently need per-issuer field-set confirmation; see the file'sreview_requiredblock for the tag list.
Apache-2.0.