Pivot the promise before the infrastructure
If people understand “Story” but not “Library,” change the access/collection logic before adding software.
Venture Universe legacy build · VU-G01-V001-SS01-PL02
Compare edition, access, commission, and guided-use forms without ranking an untested favorite.
Offer variants / pivots
These are prototypes derived from the source’s Minimum Proof wording. None is asserted to be wanted, feasible, profitable, or legally cleared.
| Form | What customer gets | Commitment test | Operating pressure | Key unknown |
|---|---|---|---|---|
| Defined edition | A finite themed story issue/collection with a clear contents promise. | Purchase or prewritten access commitment to one edition. | Curation, production cycle, deadlines, refresh cadence. | Does one edition create a reason to return? |
| Access offer | Defined access to a maintained story catalog or rotating collection. | Paid access, reservation, or another explicit stake. | Catalog maintenance, account/support, cancellation, rights duration. | Does “library” justify ongoing access rather than one-off use? |
| Commission | A story or story-set produced to an agreed brief and scope. | Deposit, signed scope, or paid booking. | Brief quality, revision loops, schedule, rights/usage terms. | Can work stay bounded enough to serve repeatedly? |
| Guided-use session | A facilitated path through selected stories for a defined occasion. | Booking or capped attendance commitment. | Facilitation time, group size, accessibility, host/site/platform. | Is the value in the collection, the guidance, or both? |
If people understand “Story” but not “Library,” change the access/collection logic before adding software.
If a narrowly defined group has no compelling occasion, changing channels does not fix the customer job.
If commissions create uncontrolled revision load, a defined edition or guided format may test the underlying promise with clearer bounds.
ICU / CONNECTED DISCOVERY
This module intentionally uses the existing recommendation node for legacy source ID VU-G01-V001-SS01-PL02, so every dynamic card is grounded in ICU’s current topic or collection relationships rather than title similarity.
Loading public connections…