Eight direct capability views and the connected role story are live.
Guided evaluation · Step 4 of 4
Starting brief
Turn the evidence into a five-minute starting brief without recording approval, authorizing a pilot, or creating a live effect.
Earlier steps show sequence, not saved completion. Each proof resets on refresh, and this path creates no live effect.
Phase 2 Decision Room · browser-only
The demo is ready. The next move is six real decisions.
This room connects each unresolved Phoenix decision to evidence Marci can review now. It records no answer, assumes no approval, and authorizes no pilot or live effect.
No form submission. Review, copy, and respond through a channel you already trust. Do not send credentials, card data, or broad raw exports.
From product proof to pilot evidence
No Phoenix answer or approval is inferred from this presentation.
Real clients, money, providers, migration, and outbound effects remain gated.
Five-minute starting brief
Start with four answers—not all six gates.
Choose a first journey, the people needed, the riskiest unknown, and what evidence is available. The brief updates only in this browser tab and remains incomplete by design.
0 of 4starter prompts answered
Local draft
Nothing is sent or saved. Reloading clears these selections.
No form, account, cookie, local storage, database write, analytics event, or submission endpoint is used.Six validation gates
Decide what becomes real—and what stays out.
Each gate names the question, accountable participants, safe evidence to bring, and the bounded outcome needed before pilot design can advance.
Choose the first real journey
Which one real client journey should PTOS validate first—and which variants must stay out of the first pilot?
A thin, real workflow is safer to validate than approving a broad feature list.
- Decision partners
- Marci + a representative coaching/operations owner
- Gate outcome
- One bounded pilot journey, with every excluded variant named.
Bring the safe minimum
- One normal client journey with names and private details removed
- One stalled or exception journey
- One cancellation or offboarding journey
Name the people and promises
Who owns each handoff, exception, override, client message, and coverage decision?
Software cannot safely infer accountability, coverage, or the service level clients are promised.
- Decision partners
- Marci + staff/support owners
- Gate outcome
- A named owner, backup, authority boundary, and response expectation for every pilot handoff.
Bring the safe minimum
- Who owns each handoff and client communication
- Who covers absence or workload overflow
- Who may resolve exceptions or approve overrides
Approve policy and data boundaries
What may PTOS collect, show, retain, send, or change—and who approves each high-impact boundary?
Health-adjacent, payment, coaching, community, and progress data need explicit rules before real use.
- Decision partners
- Marci + applicable policy/business owners
- Gate outcome
- An allowed-data and policy map with named owners, unresolved blockers, and review dates.
Bring the safe minimum
- Approved agreement, payment, health/nutrition, media, privacy, and retention rules
- Identity-verification, export, correction, deletion, and incident procedures
- The accountable legal, financial, privacy, and health-adjacent decision owners
Approve what clients will see
Which brand assets, program names, coaching voice, media, and content are current and licensed for production?
The current direction is intentionally provisional; production must use owned, current, accessible material.
- Decision partners
- Marci + brand/content rights owners
- Gate outcome
- An approved, licensed brand/content pack with replaceable production tokens and copy.
Bring the safe minimum
- Current approved logo and source assets
- Exact colors, fonts, program names, audience, and voice examples
- Content ownership, licenses, captions, and participant/media releases
Choose providers and the transition boundary
Which systems remain, integrate, or exit—and what is the smallest reversible data transition worth testing?
Feature resemblance does not prove export quality, field compatibility, account ownership, or a safe cutover.
- Decision partners
- Account/data owners + technical/operator owner
- Gate outcome
- A source-of-truth map and minimum dry-run migration with reconciliation and rollback criteria.
Bring the safe minimum
- System and provider inventory with owner, purpose, contract, export, and exit terms
- Redacted schemas or synthetic samples—never credentials or broad raw exports
- Which system stays authoritative during a reversible parallel period
Define the pilot decision
What measurable outcome would justify continuing—and what safety or service failure would pause the pilot?
A convincing demo is not a result; the pilot must measure value and safety against an agreed baseline.
- Decision partners
- Marci + all acceptance/support owners
- Gate outcome
- A consented pilot charter with measures, stop rules, support, recovery, export, and rollback ownership.
Bring the safe minimum
- Current baseline for coach time, turnaround, client friction, and missed handoffs
- A small consented cohort, support owner, manual fallback, and incident path
- Numeric success, pause, and stop thresholds recorded before any real data enters
Full six-gate worksheet
Continue only as far as the evidence allows.
The starting brief is enough to schedule a focused review. Use this longer outline only when the applicable decision owners are ready to record evidence gate by gate.
- Replace bracketed prompts with an answer, owner, source, or “not decided.”
- Use synthetic, blank, or explicitly redacted samples.
- Send no password, token, private key, card data, or broad production export.
Nothing is sent or saved from this page.
The honest boundary
Nothing here turns presentation evidence into production approval.
Real Phoenix workflow, content, policy, providers, migration, money, client data, and pilot use remain gated until their accountable owners record the decision and evidence.