Prism / Release design & governance plan
Unveil the possibility.
Earn the invitation.
A proposed unveiling experience for Prism’s restricted pre-alpha, with a research-led path from interest to approved participation.
Planning edition. This page describes a future release. Applications and product access are not open here. Product capabilities, dates, cohort capacity, and trial criteria must be defined before launch.
One authority. A documented process.
Under this release plan, approval authority is expressly reserved exclusively to The Customer Journey Council. Only its recorded, explicit authorization can grant, extend, or restore Prism participation. Peer panels review and recommend; hosts, commercial teams, sponsors, and administrators cannot substitute their approval.
Eligible participant categories: developers, influencers, celebrities, politicians, and visionaries. Each must be individually approved against published trial criteria. A category, nomination, following, purchase, or affiliation grants no entitlement. Participation is not an endorsement.
This is a proposed operating charter reflecting the requested authority structure. It does not claim the Council has already convened, approved participants, or completed independent research review.
The unveiling page.
What visitors see
- Prism name, one approved product promise, and a clearly labeled demonstration.
- What is being tested, known limits, participant commitments, and what remains undecided.
- The eligible categories and the same evaluation criteria for everyone.
- A visual approval journey, decision states, review expectations, and appeal route.
- “Read participation criteria” and, once operational, “Request consideration.”
A secondary launch path
Primary discovery begins on Aurora’s main page. A direct Prism unveiling URL also supports approved announcements, partner referrals, and invitations. Both lead to the same Council-controlled process.
A direct link never bypasses review. Accepted participants use an authenticated entry point with a current, scoped Council grant. No product payload belongs in the public page.
Main-page popups, with room to decline.
| Moment | Message & action | Behavior |
|---|
| Discovery | “Meet Prism. A restricted pre-alpha is being prepared.” → Read the release plan. | Explicit visitor click first. If later approved for automatic display, once per session after engagement; no repeat after dismissal. |
| Consideration | “Interest is the first step. Council approval is required.” → Read criteria / request consideration when intake is enabled. | Explain purpose and data handling before collecting anything. No implied acceptance. |
| Return visit | “Already participating?” → Secure sign-in. | Only show private status after authentication. Never display acceptance based on a browser flag. |
Use a roomy rainbow-edged dialog, visible close button, Escape dismissal, focus containment and return, reduced-motion support, and a closing animation. No background blur. The current home-page button opens a planning preview only.
Research → review → trial → decision.
- Protocol: define the product, question, participant criteria, measures, data handling, stop conditions, and trial duration. Independent peers critique it; the Council authorizes the protocol.
- Intake: verify eligibility and willingness, disclose conflicts, and collect only required information. Keep research participation separate from publicity permission.
- Trial authorization: peers assess suitability and accommodations. The Council expressly approves limited trial access before anyone enters the product.
- Bounded trial: run the authorized scope, gather agreed evidence, log incidents, and allow withdrawal. Review results against the protocol.
- Decision: peers submit reasoned recommendations. The Council records approve, defer, decline, or veto, with scope and expiry for each grant.
- Renewal: re-review changed scope, incidents, or expiry. Revoke or suspend access when the authorization ceases to be valid.
“Peer-reviewed” describes the planned review process, not an existing scientific validation claim. Use independent qualified reviewers and any required institutional review before commencing relevant research.
Try a lottery-and-vote peer process.
Proposed for every stage—protocol, intake, trial, final decision, and renewal—subject to Council ratification. Random selection and democratic election are distinct mechanisms; combine them transparently rather than treating a lottery as a vote.
- Publish eligibility, nomination, conflicts, term length, and replacement rules for the peer pool.
- Freeze the eligible roster; document its version, consent, exclusions, and an independently witnessed random draw.
- Publish an auditable draw record with privacy-preserving identifiers. Select reviewers and alternates; record recusals and redraws.
- Let eligible peers elect panel officers and vote on stage recommendations using a predeclared quorum and threshold. Log abstentions, dissent, and ties.
- Send the complete record to the Council. Peer outcomes inform the decision; they never confer Prism access.
Panel size, voting method, quorum, thresholds, observer role, and tie rule remain adoption decisions. Ratify them before recruiting, rather than changing them to favor an outcome.
A veto gate that leaves a record.
At each stage, reviewers can raise an evidence-backed hold request. Only the Council issues a formal admission veto. An operational incident owner may temporarily suspend access for containment under a Council-approved policy; suspension is not approval authority.
Each veto records its basis, affected scope, evidence, conflicts, decision-maker authorization, notice, and review date. A veto blocks issuance or renewal. Participants can correct factual errors and request reconsideration by unconflicted reviewers; only the Council can lift the veto or reauthorize access. No silent expiry into acceptance.
Separate offers. Separate governance.
Explore the separate concept store ↗
The fashion brand and expert offers run in parallel to Prism with their own owners, budgets, approval records, audiences, and delivery promises. Their commercial decisions do not grant Council powers or influence admission. Fashion-brand sales are also distinct from Aurora’s editorial fashion treatment.
| Framework | Fashion workstream: proposed adaptation | Expert-offer workstream: proposed adaptation |
|---|
| Attraction | A useful styling guide leading to one clearly priced capsule item. | A practical diagnostic leading to a scoped workshop or advisory engagement. |
| Upsell / menu | Optional complementary pieces or a styling session matched to customer needs. | Optional implementation support, training, or production services with separate scope. |
| Feature downsell | A smaller bundle with plainly stated differences. | A workshop or self-serve toolkit instead of a larger implementation engagement. |
| Continuity | Only if recurring styling value and fulfillment capacity are demonstrated. | An optional ongoing review service with defined deliverables and cancellation terms. |
Build and test one reliable offer before layering the rest. Measure delivery cost, contribution, customer outcomes, refunds, and retention separately for each workstream. Prices, performance claims, and launch dates remain unapproved.
Source: Alex Hormozi, $100M Money Models: How To Make Money, supplied EPUB; “The Four Types of Offers That Make Money Models,” “Menu Upsell,” “Feature Downsells,” “Continuity Offers,” and “Make Your Money Model.” These are original applications of the book’s offer-sequencing concepts, not copied offers, revenue guarantees, or an endorsement. The supplied book is distinct from $100M Offers.
Release gates before real invitations.
- Council charter adopted; authorized decision-makers and peer rules documented.
- Product promise, trial protocol, eligibility rubric, and capacity approved.
- Secure intake, identity verification, scoped access, expiry, revocation, and audit records implemented and tested.
- Access-denial checks pass for anonymous, unapproved, expired, revoked, and vetoed accounts—including direct URLs and APIs.
- Withdrawal, incident, appeal, and participant-support routes staffed.
- Public copy and any secondary launch materials approved; internal records excluded from publication.
Required future access rule: authenticated identity + explicit active Council grant + permitted scope + no active veto or suspension. Otherwise deny. The current static Aurora site implements none of that product access infrastructure.