Libraries and marketplaces
Discovery, curation, reputation, licensing, and support can grow around SeedSpec packages without becoming part of the neutral package protocol.
What the protocol provides
SeedSpec defines inspectable packages, identity, semantic roles, relationships, versions, digests, and an agent handoff. Those properties give a marketplace or library a stable object to index and distribute.
The protocol does not define remote search, ranking, payments, licensing enforcement, reviews, publisher reputation, certification, or commercial terms.
What a marketplace can add
Discovery
Search, categories, related solutions, provider adaptations, feature packages, and implementation resources.
Curation
Editorial review, recommended collections, organization policy, known environments, and update requirements.
Trust signals
Publisher identity, reputation, reviews, support commitments, tested claims, limitations, and derivation lineage.
Commerce
Payments, licensing, access, subscriptions, warranties, services, and support outside the neutral package.
Discovery is not activation
A marketplace may return ordinary SeedSpec packages and relevant context. Finding or selecting a package does not authorize its tools, activate its resources, prove compatibility, or override the adopter’s direction.
Discover
The library or marketplace surfaces candidates and explains why they may be relevant.
Acquire and inspect
The adopter obtains the package, validates its structure, reviews provenance, and examines the actual content.
Select deliberately
The adopter confirms fit, configuration, implementation resources, and any adaptation.
Implement under user authority
The agent acts only with the permissions and execution direction supplied in the real environment.
A useful solution graph
A mature registry can relate core intent, derived packages, features, provider adaptations, implementation approaches, tested environments, verification evidence, and known limitations. Agents can retrieve accumulated solution knowledge instead of re-deriving every option from a prompt.
Sales performance solution ├── Native CRM dashboard ├── Embedded CRM extension ├── Standalone web application ├── Regulated-cloud deployment └── Scheduled briefing without a persistent UIThe boundary keeps the ecosystem open
Commercial products can differentiate through discovery, authoring experience, curation, trust, collaboration, support, and accumulated knowledge. The underlying packages remain independently inspectable and validatable.