Separate artifact identity from registry coordinates - #2
Closed
jonathanhefner wants to merge 1 commit into
Closed
Conversation
jonathanhefner
force-pushed
the
agent/issue-102-registry-identifier-guidance
branch
from
August 26, 2026 18:56
654207f to
b817b29
Compare
jonathanhefner
commented
Aug 26, 2026
jonathanhefner
force-pushed
the
agent/issue-102-registry-identifier-guidance
branch
from
August 26, 2026 20:28
2e53258 to
2582e64
Compare
Clarify how a registry creates AI Catalog entries for existing artifacts that lack publisher-assigned `urn:air` identifiers. Preserve authorized publisher identifiers when available; otherwise assign and persist a registry-controlled identifier without conflating the registry with the artifact publisher. Keep native registry coordinates in namespaced `extensions`, treat unrecognized schemes as opaque, and defer identifier migration rather than silently changing published identifiers.
jonathanhefner
force-pushed
the
agent/issue-102-registry-identifier-guidance
branch
from
August 26, 2026 21:31
2582e64 to
6d24850
Compare
Owner
Author
|
Submitted upstream as Agent-Card#105. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
urn:airidentifiers as the preferred form when availableextensionsMotivation
This is a proposed resolution for Agent-Card/ai-catalog#102.
The issue presents registry-domain and publisher-domain AIR identifiers as the two choices. This PR separates the artifact identifier, artifact publisher, registry operator, and native registry coordinates instead.
The projection policy is:
A registry does not silently change an identifier after publication. Explicit identifier migration and aliases remain future work.
No new core JSON field is added.
Scope
This draft is intentionally limited to ADR-0021 and the corresponding identifier and registry-projection text in the specification. It does not change Trust Manifest behavior.
Related questions—including OCI/xRegistry mapping corrections, mirror representation, identifier migration and aliases, and AIR namespace registration—are left for separate follow-up work.
Validation
.venv/bin/mkdocs build --strict --site-dir /tmp/ai-catalog-issue-102-site.venv/bin/python tools/build_spec.py specification/ai-catalog.md /tmp/ai-catalog-issue-102-spec.htmlgit diff --check