Loading workgroup…
Workgroup
Creating secure, transparent commerce protocols that enable value exchange, micropayments, and economic interactions within the Meta-Layer.
A peek at recent conversation in DP6 - Commerce. Join to read the full history and post.
Join workgroup →Daveed's reply to Joshua Colbert, sent by email:
Hi Joshua,
Thank you for this. The four worked examples were the most useful part for me, especially the two-zone sale and the line that protections stack while charges stay separate. That split is exactly what the chapter is trying to say, and you said it more plainly than we did.
Here is what I've turned into proposals:
In DP6, below the sentence "A common failure mode is asymmetrical friction, where signup is…", I've proposed: "Example: A person joins a learning service. Before they pay, one screen shows the monthly price, the payment fee, any community charge, the renewal date, the data the service needs, the data it would like but does not need, and a cancel link. They can cancel from the same account page they used to join. Their receipt keeps the terms that applied that day, so they have proof if there is a dispute."
In DP6, below the sentence "A zone's economic policy may raise the floor of protection…", I've proposed: "Example: A sale takes place in both a general market and an education zone. The education zone bans gambling offers and requires clear warnings on financial products, so those rules apply to the sale. The education zone also adds a small charge for moderation and access tools, and the bill shows it on its own line with a short reason. Protections stack toward the stronger rule; charges never blend into one total."
In DP6, below the sentence "A critical failure mode is undisclosed optimization, where AI systems…", I've proposed: "Example: An AI assistant helps a person compare repair shops. It says that it is an AI. It says when a shop pays it a referral fee and gives the main reason each result was shown. It can draft a booking, but it cannot spend more than the person's set limit without asking first. The receipt lists the AI's role, the referral fee, the price, the cancellation terms, and who is responsible for doing the work."
In DP6, below the sentence "A primary failure mode is economic lock-in, where value can…", I've proposed: "Interoperable rails also mean keeping the price a person sees separate from the tool they use to pay. A sale can show its price in local money and, where useful, in an optional shared reference or display unit that makes prices, fees and receipts easier to compare across zones. The buyer still pays with any lawful method that works where they live. Before the buyer agrees, the system shows the exchange rate, when it was set, how long it holds, any conversion cost, and the final amount, and it never requires one coin, wallet, or chain."
In DP6, below the sentence "A failure mode is invisible extraction, where value is removed…", I've proposed: "Example: A community market adds a 1% charge to sales in its zone, and the bill shows it before payment. The charge has a cap and a stated purpose. Every three months the community shares a short report on how the money paid for moderation, translated safety guides, accessibility work, and dispute help. Members can read the report, question a choice, vote on the next budget or renewal of the charge, and keep their receipts if they leave."
In DP6, replacing the sentence "Zones and communities attach policy objects directly to transactions. These…", I've proposed: "Zones and communities attach policy objects directly to transactions. In plain terms, a rule that is bound to a sale must be followed when the sale happens. These rules are not advisory; they execute at runtime and shape what is allowed, required, or disallowed in a transaction."
In DP6, below the sentence "Without community economies, the meta-layer reproduces the current arrangement in…", I've proposed: "This connects DP6 to New Economics for Sustainable Development (NESD), which asks that valuable work already being done, often unpaid or unseen, be recognized. In commerce that includes community trust, care work, safety, access, learning, creative work, and the helpful use of attention. A sale should not be judged by price alone: DP6 can show when a low price hides costs that other people carry, such as data tracking, pressure to buy, unpaid community work, or weak safety support. DP6 does not need to solve every social or environmental problem; it focuses on clear costs, real choice, and fair community rules."
Each of these will show up in the chapter's discussion once it is posted, and you can comment on or refine them there.
Some feedback on the feedback. Your bigger structural suggestions (cutting repetition, the seven-part chapter order, a plain-language main text with a builder appendix, and following one sale end to end) are right, but they are a rewrite rather than an edit, and V1 freezes Nov 9. I'm taking them to the workgroup for V2. The worked examples above are my down payment on that. On wording, the chapter doesn't actually say "perfectly fair", so that one is already safe; swapping "opaque" for plainer words is part of the same V2 pass. Your eleven ideas for Section 14 are good material, and since the chapter keeps those as open questions on purpose, I'd like the workgroup to treat them as a test plan rather than settle them in the text now. The one I did pull forward is the display-price idea.
On your follow-up about a shared coin: I see the appeal, but the chapter deliberately does not mandate a single currency, ledger or rail, and your own notes say not to require one coin, wallet or chain. So I've framed it as an optional shared reference or display unit, with the payment method left to the buyer. If you think that undersells the idea, tell me and we can talk it through.
With thanks,
Daveed
Maureen Shea sent these notes on DP6 by email:
I read DP 6
I signed in, but I don’t have any specific changes to make to the texts
Two things that I think are very important is fairness and AI disclosure
I feel like it’s very important to understand when we are navigating to a page that is either completely AI, Or partially AI.
In 6.2 composition across zones
It would be nice to show show some examples - Mock ups.
It really is great work that you’re doing, And I’m excited to watch the next few months unfold
Daveed's reply to Maureen Shea, sent by email:
Hi Maureen,
Thank you for reading DP6. Even without specific text changes, your two points were clear enough to act on.
I've turned them into two proposals, both credited to you:
In DP6, below the sentence "Why this matters: Requires DP11 disclosure and DP13 bounds.", I've proposed: "Participants should always know when a page, listing, or recommendation is wholly or partly generated by AI, before they rely on it to buy or sell."
In DP6, below the sentence "A zone's economic policy may raise the floor of protection for its…", I've proposed: "Example: a buyer in a neighbourhood market zone, which adds a small community surcharge, purchases from a seller in a crafts guild zone that prohibits resale markups. At checkout the buyer sees the item price, the guild's line, and the neighbourhood surcharge as three separate lines, and because the guild's prohibition is stricter, it applies to the sale."
They will show up in the chapter's discussion, and you can comment on or refine them there.
The book has no room for mock-ups, so for 6.2 I wrote a worked example in words instead. If you would like to sketch what it looks like on screen, the DP6 workgroup would welcome it.
With thanks, Daveed
Joshua Colbert sent these notes on DP6 by email:
Yes, my notes indicated alignment with your current framework, but while it's a good idea in theory, I think having one coin is a better idea for a number of reasons such as tracking, refunds, coin stabilization, etc..
Daveed's reply to Joshua Colbert, sent by email:
Hi Josh,
Thanks for pushing back on the coin. Rather than fold it into my softer framing, I've posted it as your own proposal, so the workgroup can weigh it on its merits:
In DP6, below the sentence "A primary failure mode is economic lock-in, where value can…", I've proposed: "A stronger option for the workgroup to weigh is a single shared coin for settlement across zones, which would make payments easier to track, simplify refunds, and keep prices stable."
It will show up in the chapter's discussion, and you can comment on or refine it there.
With thanks, Daveed
Community Chats match workgroup Collab: human messages in the main panel and private Deepi in the right sidebar. Invite people outside the workgroup by email or link. This is separate from Workgroup Chat, which stays inside the member thread.
Start a Community Chat for DP6 - Commerce. You pick who joins. Everyone invited can post in the member chat and use private Deepi in the sidebar. The chat appears in your Deepi sidebar with a Community badge.
Sign in to start a Community Chat from Deepi.
Opens Deepi with the invite flow. Community Chats also appear under My conversations at /agent.