Umbrella: make adcp-go a first-class SDK and seller framework

Open
  • Is something wrong?
#352 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, backend

Research direction

Start by reading the linked workstreams, including issues #348, #344, #153, and #286, to understand the framework, reference seller, generator, and helper tasks. Then review the Go SDK's existing protocol and seller implementation; the goal is to complete the listed workstreams and meet the definition of done, including 3.0 and 3.1 support and adopter documentation.

Written by the indexing model from the issue text.

Description

claude-triaged enhancement go-first-class sdk

Goal

Track the work required for adcp-go to be a first-class AdCP SDK and seller framework alongside the Python and TypeScript SDKs.

This is the post-2.0 roadmap for turning the current protocol/router/reference implementation into a practical seller integration platform: generated schema-faithful types, validation, task handling, auth/account context, transport parity, high-quality examples, and adopter documentation.

Definition of Done

  • Protocol typing is schema-faithful, generated where practical, and avoids hand-invented fields.
  • Server responses have a clear projection/wire-safety layer instead of ad hoc ext flattening.
  • Optional values, enums, additionalProperties, and inline schemas have documented policies and lint coverage.
  • Seller implementations get first-class framework hooks for auth, account resolution, tenant routing, async tasks, validation, and testing.
  • The Go reference seller is production-shaped and comparable in clarity to the Python/TypeScript examples.
  • Go supports 3.0 and 3.1 clients/servers with version-selected schemas and validation.
  • Docs include a minimal hello seller, a production fork checklist, and migration/adopter guidance.

Workstreams

Framework and runtime
  • #348
  • #345
  • #347
  • #67
  • #69
  • #70
  • #350
Reference sellers and conformance
  • #344
  • #349
  • #351
  • #140
  • #97
  • #196
  • #141
Generator and protocol typing
  • #153
  • #145
  • #176
  • #259
  • #260
  • #162
  • #139
  • #271
  • #191
  • #225
  • #226
  • #291
  • #341
  • #343
Product/feed helpers
  • #286

Non-goals

  • Do not make root or TEE-bound modules depend on heavy frameworks.
  • Do not add protocol fields that are not in the schema.
  • Do not block the adcp 2.0 release on this roadmap.
Dominant language
Go
Stars
4
Forks
2
Avg merge
1d 10h
Merged PRs (30d)
29

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adcontextprotocol/adcp-go

All issues in adcontextprotocol/adcp-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.