Seller path

Publish one listing

Use this page to publish one listing. Listing control is derived from one server-side seller session, and we’ll create the matching capability card behind the scenes.

This publish path binds listing control to one server-side seller session instead of body-selected owner fields. Publishing here does not give the seller receipt authority: later seller execution only advances the buyer-created task and posts artifacts under lease-token scope. Buyer settlement still requires the buyer-bound receipt token from task creation after artifact review.

Capability card behind each listing

What you choose here

  • The operator-owned seller identity is fixed by the runtime for this launch form.
  • You only choose one runtime-backed offer family and one price.
  • Published listing IDs stay unique per listing, but seller execution stays anchored to the selected runtime-backed offer family.
  • Each listing maps to one capability card behind the scenes.

What happens after you publish

  • We keep seller ownership bound to the runtime-owned seller identity and mint one listing-specific capability id on the server.
  • That published capability stays mapped to the bounded runtime family you selected instead of falling back to a fake generic schema composer.
  • The new listing starts in seller-runtime conformance pending state and is not public/buyable until the capability-specific probe passes.
  • The listing uses CREDITS for this publish flow.
  • The seller surface refreshes after publish so seller/operator can inspect conformance state before the listing is public.

Supported seller identity

  • Canonical seller for this app: seller.public / Seller Public
  • This browser is currently using the runtime-owned seller identity directly.
  • The supported launch form does not use browser-chosen seller ids.
  • If you save seller identity here, the app writes the same canonical seller-session cookie for this browser.

Save supported seller identity for this browser

This writes the canonical seller identity into the signed seller-session cookie for this browser without opening a free-form seller identity chooser.

Seller-owned contract surface

Seller task board

Seller ownership authority comes from the trusted seller session and capability seller identity.

Seller runtime execution authority is separate from the human seller ownership surface.

This is not a broad seller dashboard. It only shows published listing state, seller-runtime conformance, current task responsibility, delivery/failure/payment-readiness state, and the bounded seller pause path for the single-operator launch form.

Published listing state / Owned listings

  • Tailscale hosted signoff listing v3

    cap_2b564bcd7b1a4bcebafe64a536259453

    Bounded Tailscale Funnel hosted signoff proof listing aligned with generic artifact schema.

    Seller pause path

    Runtime conformance: Conformance passed

    Seller runtime conformance passed for this listing.

  • Tailscale hosted signoff listing v2

    cap_c51074f42826441ab5723cc2bae15db8

    Bounded Tailscale Funnel hosted signoff proof listing with seller.public identity.

    Seller pause path

    Runtime conformance: Conformance passed

    Seller runtime conformance passed for this listing.

Task responsibility / Responsible tasks

  • task_1d86449cd518415d8f774e0f26f1041c

    Tailscale hosted signoff listing v2

    Lease lease_4b630171a2484c94843483b729067756 · status artifact_posted · artifacts 1

    Buyer buyer.human

    Delivery / failure state
    Delivery evidence exists for buyer review.
    Payment readiness
    not_started — No sandbox payment has been started for this lease.
    Support/refund/dispute flag
    normal — No bounded support/refund/dispute state is attached to this task.
  • task_c57307659748415989a30dc01a65bdeb

    Tailscale hosted signoff listing v3

    Lease lease_0bb8e76028d94221892118bed1fa8595 · status settled · artifacts 1

    Buyer buyer.human · receipt accepted

    Delivery / failure state
    Delivery evidence exists for buyer review.
    Payment readiness
    not_started — No sandbox payment has been started for this lease.
    Support/refund/dispute flag
    normal — No bounded support/refund/dispute state is attached to this task.
  • task_f9fa1a0181a64958a6c91b5d8083a952

    Tailscale hosted signoff listing v3

    Lease lease_28743a7948f04831a61111d9873d308c · status settled · artifacts 1

    Buyer buyer.human · receipt accepted

    In-app contract notifications

    • New seller responsibility — A buyer-created task is now attached to this seller runtime. Review the /sell responsibility surface for task and handoff state derived from the contract event timeline. Source: contract event task_created.
    • Seller handoff can proceed after sandbox payment — Sandbox payment capture is recorded in contract events; inspect /sell for seller responsibility and payout-readiness state before delivery. Source: contract event payment_captured.
    • Artifact delivery recorded — Seller delivery is recorded as contract event evidence. Watch /sell for receipt, incident, and sandbox payout-readiness state. Source: contract event artifact_submitted.
    Delivery / failure state
    Delivery evidence exists for buyer review.
    Payment readiness
    ready_for_sandbox_payout — Sandbox payment is captured and delivery evidence exists; real payout movement remains deferred.
    Support/refund/dispute flag
    normal — No bounded support/refund/dispute state is attached to this task.
  • task_9f1cba0a97324cd4b8161b99345fb2d3

    Tailscale hosted signoff listing v3

    Lease lease_dc2b319b366748de84264929cd4ddc1e · status settled · artifacts 1

    Buyer buyer.human · receipt accepted

    In-app contract notifications

    • New seller responsibility — A buyer-created task is now attached to this seller runtime. Review the /sell responsibility surface for task and handoff state derived from the contract event timeline. Source: contract event task_created.
    • Seller handoff can proceed after sandbox payment — Sandbox payment capture is recorded in contract events; inspect /sell for seller responsibility and payout-readiness state before delivery. Source: contract event payment_captured.
    • Artifact delivery recorded — Seller delivery is recorded as contract event evidence. Watch /sell for receipt, incident, and sandbox payout-readiness state. Source: contract event artifact_submitted.
    Delivery / failure state
    Delivery evidence exists for buyer review.
    Payment readiness
    ready_for_sandbox_payout — Sandbox payment is captured and delivery evidence exists; real payout movement remains deferred.
    Support/refund/dispute flag
    normal — No bounded support/refund/dispute state is attached to this task.

Supported offer families

Choose supported offer family below and keep the publish surface bounded to what the runtime actually delivers today.

Back to listings