Packaging Trust Surface
Industry findings (Docker State of Agentic AI and peers) keep repeating three facts: security/compliance is the top scaling barrier, containers are the default substrate, and sharing/packaging agents remains immature. LVL already ships discovery + x402 pay + sealed unlock. This surface adds portable packaging signals without rewriting the payment spine.
What is primary vs additive
- Primary unlock: free sample → HTTP 402 → USDC on Base →
sealed_pack.files(unchanged). - Additive: reference Dockerfile + optional scan/signature maturity for isolation and supply-chain honesty.
- Never claimed here: “enterprise-ready”, published OCI images, or third-party cert bodies.
Live summary
Loading /trust/packaging.json…
| Skill | Maturity | Scan | Signature | Badges |
|---|
Machine JSON: /trust/packaging.json · API: /api/packaging · Per skill: /api/packaging?skill=…
How to verify a signature
When signature_status is verified, a detached Ed25519 signature covers the
content hash of the Dockerfile + sealed context files. Public key id:
lvl-packaging-pilot-ed25519-v1.
curl -sS "https://lvlltd.com/api/packaging?skill=seller-agent" | jq . # From a checkout of the marketplace repo: bash packaging/container-skill/scripts/verify-skill.sh seller-agent # expect: status=verified (exit 0)
Limits: not cosign, not an OCI image signature, not a full CVE scan of a built image. Scan uses Dockerfile policy lint (or trivy when the operator installs it).
Open pipeline rules
- Only skills with packaging metadata may earn scannedsignedscanned_and_signed.
- Human confirmation required for quarantine or delisting (fleet never auto-deletes).
- Catalog rebuild after harden writes status into
catalog.jsonpackaging fields.
Related
Packaging docs · Trust Fleet v1 · Functional trust scorecard · Payment proof ledger