Skip to content

feat(registry): agent asset catalog on AgentCore — provisioning, port/adapter, API, CLI (#246) - #3

Draft
Kalindi-Dev wants to merge 1 commit into
mainfrom
feat/246-registry-catalog
Draft

feat(registry): agent asset catalog on AgentCore — provisioning, port/adapter, API, CLI (#246)#3
Kalindi-Dev wants to merge 1 commit into
mainfrom
feat/246-registry-catalog

Conversation

@Kalindi-Dev

Copy link
Copy Markdown
Owner

Summary

Read-side catalog for the central agent asset registry on AWS Agent Registry (Bedrock AgentCore). Nothing upstream imports the AWS SDK directly.

  • Provisioning: AgentRegistryStack (NestedStack) creates the registry via a custom resource (async CreateRegistry, no L2 in preview); bootstrap IAM + resource-action-map + golden DEPLOYMENT_ROLES.md in sync.
  • Ports & adapters: RegistryClient port (TS + Py), one AgentCoreRegistryClient adapter per language. Native descriptors — MCP server.json + _meta, AGENT_SKILLS markdown frontmatter, CUSTOM verbatim.
  • Grammar: registry://kind/namespace/name@constraint with mandatory semver pin, mirrored byte-for-byte across ref.ts/ref.py and enforced by the contracts/registry-resolution/ parity corpus.
  • API: publish/resolve/list/show on TaskApi, gated by Cognito groups (RegistryPublisher/RegistryApprover); bgagent registry CLI.
  • Wire types: resolved-asset triple stamped on TaskRecord/Detail/Summary for audit.

Integration (orchestrator resolve-step, agent loaders, blueprint pins) lands in the follow-up PR that builds on this catalog.

Test plan

  • mise run build green (2583 CDK tests + agent quality)
  • TS↔Py resolution parity corpus passes
  • Deploy to dev; confirm registry reaches READY and publish/resolve/list/show work end-to-end

…/adapter, API, CLI (aws-samples#246)

Introduces the read-side catalog for the central agent asset registry built
on AWS Agent Registry (Bedrock AgentCore), with nothing upstream importing the
AWS SDK directly:

- Provisioning: `AgentRegistryStack` (NestedStack) creates the registry via a
  custom resource (async CreateRegistry, no L2 in preview); bootstrap IAM +
  resource-action-map updated (states, cognito group, cloudformation nested
  stack) with the golden DEPLOYMENT_ROLES.md kept in sync.
- Ports & adapters: `RegistryClient` port (TS + Py) with a single
  `AgentCoreRegistryClient` adapter per language. Native descriptor storage —
  MCP server.json + `_meta`, AGENT_SKILLS markdown frontmatter, CUSTOM verbatim.
- Grammar: `registry://kind/namespace/name@constraint` with mandatory semver
  pin, mirrored byte-for-byte across ref.ts / ref.py and enforced by the
  `contracts/registry-resolution/` parity corpus.
- API: publish / resolve / list / show routes on TaskApi, gated by two Cognito
  groups (RegistryPublisher / RegistryApprover); `bgagent registry` CLI.
- Wire types (shared/types.ts + cli/types.ts): resolved-asset triple stamped on
  TaskRecord/TaskDetail/TaskSummary for audit.

Integration (orchestrator resolve-step, agent loaders, blueprint asset pins)
lands in the follow-up PR that builds on this catalog.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant