SeedSpec marketplace exploration

This project contains an exploratory, local SeedSpec registry/marketplace and the first usable shape of the seedspec-marketplace create scaffolder. It is a reference implementation for learning where portable protocol behavior ends and registry product policy begins. It is not part of SeedSpec package conformance and is not a deployment starter.

The committed prototype/ was generated from the scaffold and contains the existing hubspot-daily-metric reference package as its only listing.

Try the complete path

Run the published experimental scaffolder:

npx @seedspec/marketplace create /tmp/my-marketplace \
  --package ./reference-solutions/packages/hubspot-daily-metric

When running from the parent SeedSpec/ source workspace before publication, use the local package through npm:

npx --yes ./seedspec-marketplace create /tmp/my-marketplace \
  --package ./reference-solutions/packages/hubspot-daily-metric

cd /tmp/my-marketplace
node ./marketplace.mjs list
node ./marketplace.mjs inspect org.seedspec.examples.hubspot-daily-metric \
  --version 0.1.0-alpha.1
node ./marketplace.mjs agent-guide org.seedspec.examples.hubspot-daily-metric \
  --version 0.1.0-alpha.1
node ./marketplace.mjs retrieve \
  org.seedspec.examples.hubspot-daily-metric \
  0.1.0-alpha.1 \
  sha256:8935cc090490ab4411e7a9ca2d40173a5dc7bcab52b252747bb8af29a6df787b \
  /tmp/retrieved-hubspot-daily-metric
seedspec begin /tmp/retrieved-hubspot-daily-metric

If seedspec is not on PATH, set SEEDSPEC_CLI to the compatible CLI. In this workspace:

export SEEDSPEC_CLI="$PWD/seedspec/packages/cli/bin/seedspec.js"

The generated marketplace stores a complete package directory at a canonical digest address. Retrieval copies and validates that directory. Once retrieved, the package requires neither this marketplace nor a network connection.

The generated project declares the compatible @seedspec/cli. Run npm install inside it before later ingestion, retrieval, verification, or rebuild commands when the CLI is not already available on PATH.

Outputs

• docs/experiment-findings.md records what the prototype established and the smallest next implementation.
• docs/protocol-decisions.md classifies current support, required protocol work, proposed conventions, and rejected changes.
• docs/registry-decisions.md defines the local registry and marketplace behavior.
• docs/boundary-table.md assigns ownership of fields and decisions.
• docs/open-questions.md ranks unresolved ecosystem questions.
• proposals/distribution-record.schema.json is a precise detached acquisition-record proposal, intentionally not patched into the protocol alpha yet.

Development

npm test

The tests cover scaffold creation, successful and rejected ingestion, validation, content-addressed storage, exact retrieval, digest verification, tamper detection, registry rebuild, ID/version conflict policy, and use of a retrieved package after the registry has been removed.