Repository navigation
Conversation
…n plan Vision-aligned end-to-end plan (design + UI/UX) to take the canonical protected-content extraction from trust-core foundation to the full mint->sell->buy->play journey on the ESP substrate. Co-authored-by: Anders <andersalm@users.noreply.github.com>
Collaborator
|
closed this, it have been merged in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A proposal-stage implementation plan to take the canonical protected-content extraction (
feat/protected-content-*) from a trust-core foundation to the full end-to-end user journey — mint → sell → buy → play — with first-class design and UI/UX, coherent withPRINCIPLES.mdand the canonical architecture indocs/PROTECTED_CONTENT.md.Base is set to
feat/protected-content-custody-providerso the diff is just the new doc (docs/PROTECTED_CONTENT_JOURNEY_PLAN.md).Highlights
PRINCIPLES.mdrule (local-first, no ambient authority, one canonical path, fail-closed, UI-is-not-authority, design tokens, human nouns, trust-travels-with-signed-content). If a design choice can't be expressed as one of those, it's out of scope.capsule → Runtime coordinator → rights-provider → custody providers → decrypt-provider, on the existingelastos-protected-content-*crates +custody-provider._shareddesign tokens,home-guicanonical window chrome, one consolidated Store, the Home spend-confirmation dialog ("what is displayed is what is signed"), human-noun IA, and a full states/copy/accessibility pass.RequiredHomeLaunchTokensubject-resolution rewire (PR dKMS/dDRM foundation on the ESP substrate (inspired from flint-5.0) #15's parked gate) into Phase 2 rather than deferring it.docs/PROTECTED_CONTENT.md.dkms_raile2e, plus a merge-gate coherence checklist.Note
This is a planning document only — no code changes. It's written to be reviewed/edited on the protected-content line; open decisions (Store consolidation, product vocabulary, dev-lane vs chain-gated scope for 0.7) are called out in §10.