Provider listing draft Studio
The private Provider listing Studio is available at stele.monolythium.com/studio. A Browser Wallet-authenticated user can create, edit, preview, and delete durable provider-listing drafts owned by that wallet address.
What the Studio can do
Section titled “What the Studio can do”The Studio prepares canonical service records in private. Draft existence and content remain hidden until the owning wallet signs in. A draft is not published, not discoverable, and not transactable. It remains separate from public catalog projections, and production still has 0 published services.
Saving a provider-listing draft creates durable application state, not on-chain or economic state. Wallet authentication proves control of an address for the session; it does not certify provider identity, credentials, availability, pricing, location, quality, or legal authority. The Studio has no publish, signing, submission, booking, payment, or settlement control.
Deleting a draft removes it from that wallet-owned workspace. It does not affect the public catalog because the record was never published.
Provider publication remains unavailable
Section titled “Provider publication remains unavailable”Before Stele calls provider publication available, a separately released flow must make each boundary explicit:
- The provider authenticates with a supported browser-wallet release.
- Stele distinguishes session authentication from any later signed transaction.
- The provider reviews exactly which fields are public.
- Credentials identify their issuer, jurisdiction, issue date, expiry, and verification method.
- Availability and pricing identify whether they are self-declared, externally sourced, or verified.
- Publishing, bonding, payment, escrow, review, and dispute actions remain separately gated.
Wallet authentication alone must never be presented as KYC, professional accreditation, a background check, or proof of service quality.
Fees and commitments
Section titled “Fees and commitments”There is no current Stele commission, provider fee, bond amount, accepted settlement asset, automatic acceptance rule, or arbiter registry. Any future fee or economic requirement must be published with its network, asset, version, and activation status before users are asked to commit.
Booking-approval drafts and future inquiries
Section titled “Booking-approval drafts and future inquiries”Provider-delivered inquiry handling is not available. The live hosted MCP exposes a different booking-approval draft tool, but production currently has 0 published services, so no successful booking-approval draft can be created. Private provider-listing drafts do not satisfy the tool’s published-listing prerequisite, and MCP cannot list, read, update, delete, or publish an existing draft. Once a real published listing exists, the booking tool still stops at a wallet-owned review page and does not send anything to a provider. Any future delivered inquiry will be nonbinding: providers will remain free to ignore or decline it, and it will not promise delivery, availability, response time, escrow protection, or dispute resolution.
For hosted provider-draft creation, the authenticated tools/list response is authoritative for the hosted inventory. Only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another. If the name is absent, the operation is unavailable. It cannot list, read, update, delete, or publish an existing draft, and it cannot sign, submit, or settle a transaction.
Do not ask prospective customers to upload sensitive files to the public preview. Private messaging, files, and end-to-end encryption are planned rather than available.