The first user confused storage with training in twenty-five seconds.
The regulator's design workshop included LalaLive UX staff, creators, consumer representatives, engineers, Ruth, Marwa, Joel, Amina, and six test users. The goal was not a legal document only a lawyer could understand. The controls had to survive contact with ordinary people.
The first prototype technically had three cards, but storage was blue and training was green with a large `CONTINUE` button. The user tapped both without reading.
Sifa raised her hand. “The color says yes before the words do.”
The UX lead objected. “Green is standard positive action.”
“Positive for whom?”
Marwa said, “If every choice looks dangerous, conversion collapses.”
Ruth answered, “The goal is not to make yes dangerous. The goal is to make no non-punitive.”
Amina ordered a reset. The cards became neutral. Experience described what would happen now. Storage asked whether the anchor could remain for replay. Training asked whether the source could be reused to improve future models. `YES` and `NO` were the same size.
A second test user asked, “If I refuse training, do I lose my discount?”
Marwa admitted the current plan included a training subsidy.
“Then do not call it free consent if no becomes a price penalty,” Sifa said.
Marwa turned to Ruth. “Compute costs money.”
“You may price a service,” Ruth replied. “Do not hide the price inside a data-rights choice.”
Joel added a creator-lineage preview. A user could see contributor codes, license type, and whether a layer was a creator asset or a user-owned anchor without learning another person's identity.
The next users made different choices. One accepted experience and storage but refused training. Another refused both storage and training. A third allowed training for one month.
Average completion time: one minute forty-eight seconds.
“Four times our current onboarding,” Marwa said.
“And now people can explain what they chose,” Sifa replied.
Ruth required comprehension questions. Could a user refuse training and still use the pack? Could storage be revoked without closing the account? Was a creator asset the same thing as a personal anchor? Accuracy rose sharply compared with the first prototype.
Marwa's conversion forecast went red.
“Say the cost out loud,” Amina told her.
“Fourteen percent projected drop.”
Joel answered, “Then creator economics must adapt to users who understand the rights chain.”
The team tested revocation. A user who had accepted training changed the answer to `NO`. The purchased experience had to remain. Storage had to remain because that permission was still active. Only future training reuse would stop.
An engineer read the backend event. “Training source revoked. Existing aggregate model output cannot be unwound, but this raw anchor will not be reused. History preserved.”
Ruth said, “That limitation goes into the user summary. Do not promise to erase model knowledge you cannot technically isolate.”
Then they intentionally broke the connection between the consent service and the training queue. The interface displayed `REVOCATION PENDING` rather than lying with a green success message. If acknowledgement failed beyond the allowed window, support would be alerted.
Sifa approved of that more than any polished screen. “Do not tell me my right was honored before the system knows.”
Joel tested a creator layer at the same time. Its royalty lineage survived the user's training change.
The UX lead saved the approved screen version so later color or placement changes could not quietly restore a dark pattern without a revision record.
After four hours, the architecture was less elegant and more honest. It had pending states, expiry rules, revocation histories, and warnings. It was not one tap. Test users could explain it.
Marwa signed a limited three-day pilot with public metrics for comprehension, conversion, revocation success, and exit safety.
Sifa signed only the user-panel note. She was not a company signatory and would not be used as one.
The engineer refreshed the dashboard.
A feature that had never existed on LalaLive's user interface appeared beneath the three consent cards:
`TRANSFER ANCHORS — READY`.