Top 20 MVP User Launch Board

Refresh AI Intel Desk, Fit Coach, Loss Reviewer, and Appraisal Desk first because they are the highest-demand public entry tools.

First-Run Steps

12

Sample Proofs

12

Sample Links

4

Acceptance

12

Route Proofs

12

Owner Gated

0

Input Modes

Browser Local, Pasted Input

Tighten Market Command, Industry Lab, PI Planner, and Trade Route proof while private wallet, asset, and provider reads stay excluded.

First-Run Steps

12

Sample Proofs

12

Sample Links

4

Acceptance

12

Route Proofs

12

Owner Gated

0

Input Modes

Public Data, Pasted Input

Recheck route/system risk, public profiles, SRP proof, and fleet/timer operations with public-safe smoke and rollback labels.

First-Run Steps

12

Sample Proofs

12

Sample Links

4

Acceptance

12

Route Proofs

12

Owner Gated

0

Input Modes

Public Data, Manual Workflow

Refresh buyback, mining, recruitment, and access workflows before protected owner review and provider activation.

First-Run Steps

12

Sample Proofs

12

Sample Links

4

Acceptance

12

Route Proofs

12

Owner Gated

0

Input Modes

Manual Workflow

Refresh wormhole, structure, corp/character audit, and support review proof while owner-evidence and provider gates stay closed.

First-Run Steps

12

Sample Proofs

12

Sample Links

4

Acceptance

12

Route Proofs

12

Owner Gated

1

Input Modes

Pasted Input, Manual Workflow

Open /tools/intel-desk, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Gate Camp

Route Proof

3/3

Rollback

Keep provider AI, account save, private scout data, EVE token reads, and database persistence behind feature flags or protected review.

• Try this: Open /tools/intel-desk?sample=gate-camp, run local analysis, and compare the preloaded Gate Camp sample to the expected proof.
• Sample target: Tama gate
• Sample link: /tools/intel-desk?sample=gate-camp
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/intel-desk?sample=gate-camp, review the Gate Camp output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/fit-coach, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Budget Vexor

Route Proof

3/3

Rollback

Keep private skills, implants, hangars, EVE fitting writes, and account sync behind feature-specific consent.

• Try this: Open /tools/fit-coach?sample=budget-vexor, run local analysis, and compare the preloaded Budget Vexor sample to the expected proof.
• Sample target: Lowsec roam
• Sample link: /tools/fit-coach?sample=budget-vexor
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/fit-coach?sample=budget-vexor, review the Budget Vexor output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/loss-reviewer, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Lowsec Bait

Route Proof

3/3

Rollback

Keep private killmails, fleet participation, wallets, SRP decisions, payout actions, and protected queue rows behind owner review.

• Try this: Open /tools/loss-reviewer?sample=lowsec-bait, run local analysis, and compare the preloaded Lowsec Bait sample to the expected proof.
• Sample target: Gate loss
• Sample link: /tools/loss-reviewer?sample=lowsec-bait
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/loss-reviewer?sample=lowsec-bait, review the Lowsec Bait output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/appraisal, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The planning output renders from public, pasted, or local inputs with no wallet, order, contract, or job automation.

First-Run Steps

3

Sample

Loot Stack

Route Proof

3/3

Rollback

Keep private assets, wallets, contracts, market orders, account saves, and trade actions behind consent and protected review.

• Try this: Open /tools/appraisal?sample=loot-stack, run local analysis, and compare the preloaded Loot Stack sample to the expected proof.
• Sample target: Jita estimate
• Sample link: /tools/appraisal?sample=loot-stack
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/appraisal?sample=loot-stack, review the Loot Stack output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/market, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The planning output renders from public, pasted, or local inputs with no wallet, order, contract, or job automation.

First-Run Steps

3

Sample

Hub Check

Route Proof

3/3

Rollback

Keep private wallets, market orders, account ledgers, paid provider feeds, and trade actions behind feature flags or protected review.

• Try this: Open /tools/market?sample=hub-check, run local analysis, and compare the preloaded Hub Check sample to the expected proof.
• Sample target: Jita / Amarr
• Sample link: /tools/market?sample=hub-check
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/market?sample=hub-check, review the Hub Check output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/industry-ops, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The planning output renders from public, pasted, or local inputs with no wallet, order, contract, or job automation.

First-Run Steps

3

Sample

Doctrine Build

Route Proof

3/3

Rollback

Keep private jobs, blueprint ownership, private asset locations, wallet records, corp industry data, and account persistence behind consent and protected review.

• Try this: Open /tools/industry-ops?sample=doctrine-build, run local analysis, and compare the preloaded Doctrine Build sample to the expected proof.
• Sample target: Ferox doctrine batch
• Sample link: /tools/industry-ops?sample=doctrine-build
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/industry-ops?sample=doctrine-build, review the Doctrine Build output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/pi-ops, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The planning output renders from public, pasted, or local inputs with no wallet, order, contract, or job automation.

First-Run Steps

3

Sample

P2 Factory Chain

Route Proof

3/3

Rollback

Keep private colonies, character planet data, tax records, EVE writes, and account-saved PI plans behind feature-specific consent.

• Try this: Open /tools/pi-ops?sample=p2-factory-chain, run local analysis, and compare the preloaded P2 Factory Chain sample to the expected proof.
• Sample target: Coolant chain review
• Sample link: /tools/pi-ops?sample=p2-factory-chain
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/pi-ops?sample=p2-factory-chain, review the P2 Factory Chain output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /trade-route, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The planning output renders from public, pasted, or local inputs with no wallet, order, contract, or job automation.

First-Run Steps

3

Sample

Hub Check

Route Proof

3/3

Rollback

Keep private hauling routes, wallet exposure, market order actions, route-history records, and paid data providers behind protected review.

• Try this: Open /tools/market?sample=hub-check, run local analysis, and compare the preloaded Hub Check sample to the expected proof.
• Sample target: Jita / Amarr
• Sample link: /tools/market?sample=hub-check
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/market?sample=hub-check, review the Hub Check output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/hauling-ops, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Uedama Route Risk

Route Proof

3/3

Rollback

Keep private locations, fleet movement, route history, character location reads, and route decision automation behind feature flags or protected review.

• Try this: Open /tools/hauling-ops, use the Uedama Route Risk public-safe sample, and confirm the page shows the expected proof without private account access.
• Sample target: Jita to Amarr
• Sample link: /tools/hauling-ops
• Expected proof: Public data or lookup output renders with no private character, wallet, fleet, location, or corporation reads.
• Acceptance prompt: Open /tools/hauling-ops, review the Uedama Route Risk output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /profiles, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Public Character Lookup

Route Proof

3/3

Rollback

Keep private member lists, standings, contacts, mail, account exports, and token-backed character data behind consent and protected review.

• Try this: Open /profiles, use the Public Character Lookup public-safe sample, and confirm the page shows the expected proof without private account access.
• Sample target: Public profile card
• Sample link: /profiles
• Expected proof: Public data or lookup output renders with no private character, wallet, fleet, location, or corporation reads.
• Acceptance prompt: Open /profiles, review the Public Character Lookup output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/srp-ops, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Doctrine Loss

Route Proof

3/3

Rollback

Keep wallet reads, payout approval, ISK movement, protected reviewer packet contents, account saves, and SRP queue mutation behind owner review.

• Try this: Open /tools/srp-ops?sample=doctrine-loss, run local analysis, and compare the preloaded Doctrine Loss sample to the expected proof.
• Sample target: Armor HAC timer
• Sample link: /tools/srp-ops?sample=doctrine-loss
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/srp-ops?sample=doctrine-loss, review the Doctrine Loss output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/fleet-ops, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Armor Timer

Route Proof

3/3

Rollback

Keep fleet membership, calendar writes, Discord command registration, EVE fleet writes, structure timers, and protected ops updates behind owner review.

• Try this: Open /tools/fleet-ops?sample=armor-timer, run local analysis, and compare the preloaded Armor Timer sample to the expected proof.
• Sample target: Armor timer
• Sample link: /tools/fleet-ops?sample=armor-timer
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/fleet-ops?sample=armor-timer, review the Armor Timer output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/appraisal, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Loot Stack

Route Proof

3/3

Rollback

Keep private asset details, contract creation, wallet movement, payout approval, protected queue mutation, and account saves behind owner review.

• Try this: Open /tools/appraisal?sample=loot-stack, run local analysis, and compare the preloaded Loot Stack sample to the expected proof.
• Sample target: Jita estimate
• Sample link: /tools/appraisal?sample=loot-stack
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/appraisal?sample=loot-stack, review the Loot Stack output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/mining-ops, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Moon Pull

Route Proof

3/3

Rollback

Keep private ore ledgers, fleet participation, payout decisions, wallet reads, protected reviewer notes, and mining queue mutation behind owner review.

• Try this: Open /tools/mining-ops?sample=moon-pull, run local analysis, and compare the preloaded Moon Pull sample to the expected proof.
• Sample target: Athanor split
• Sample link: /tools/mining-ops?sample=moon-pull
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/mining-ops?sample=moon-pull, review the Moon Pull output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/recruiting-ops, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Line Member

Route Proof

3/3

Rollback

Keep applicant notes, private contacts, standings, Discord role sync, EVE corp actions, messages, and protected recruiter decisions behind owner review.

• Try this: Open /tools/recruiting-ops?sample=line-member, run local analysis, and compare the preloaded Line Member sample to the expected proof.
• Sample target: Nullsec corporation
• Sample link: /tools/recruiting-ops?sample=line-member
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/recruiting-ops?sample=line-member, review the Line Member output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/alliance-ops, use the manual intake or browser-local packet builder, and keep protected review decisions gated.

Success Signal

The workflow creates review-ready public or local proof while protected reviewer decisions remain manual.

First-Run Steps

3

Sample

Access / SRP

Route Proof

3/3

Rollback

Keep access grants, expiry changes, Discord role sync, private scope prompts, protected access queue mutation, and approval actions behind owner review.

• Try this: Open /tools/alliance-ops?sample=access-srp, run local analysis, and compare the preloaded Access / SRP sample to the expected proof.
• Sample target: Member rules
• Sample link: /tools/alliance-ops?sample=access-srp
• Expected proof: A review-ready manual workflow packet appears while protected reviewer decisions remain owner-gated.
• Acceptance prompt: Open /tools/alliance-ops?sample=access-srp, review the Access / SRP output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/wormhole-ops, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Chain Review

Route Proof

3/3

Rollback

Keep private chains, bookmarks, mapper provider sync, scout contacts, shared route state, and protected wormhole notes behind owner review.

• Try this: Open /tools/wormhole-ops?sample=chain-review, run local analysis, and compare the preloaded Chain Review sample to the expected proof.
• Sample target: C5 chain review
• Sample link: /tools/wormhole-ops?sample=chain-review
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/wormhole-ops?sample=chain-review, review the Chain Review output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /tools/structure-ops, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Armor Timer

Route Proof

3/3

Rollback

Keep private structure names, ACL records, fuel bay details, timer secrets, calendar writes, and protected ops updates behind owner review.

• Try this: Open /tools/structure-ops?sample=armor-timer, run local analysis, and compare the preloaded Armor Timer sample to the expected proof.
• Sample target: Astrahus defense
• Sample link: /tools/structure-ops?sample=armor-timer
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/structure-ops?sample=armor-timer, review the Armor Timer output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open /corp-audit, use public or pasted inputs, and review the output without connecting private EVE or provider accounts.

Success Signal

The tool renders useful public or browser-local output and keeps private EVE data, provider actions, and secrets excluded.

First-Run Steps

3

Sample

Line Member

Route Proof

3/3

Rollback

Keep private member data, wallet data, roles, standings, contacts, account exports, and token-backed audits behind consent and protected review.

• Try this: Open /tools/recruiting-ops?sample=line-member, run local analysis, and compare the preloaded Line Member sample to the expected proof.
• Sample target: Nullsec corporation
• Sample link: /tools/recruiting-ops?sample=line-member
• Expected proof: Advisory tool output renders from pasted, public, or browser-local sample input with no live external action.
• Acceptance prompt: Open /tools/recruiting-ops?sample=line-member, review the Line Member output, and confirm it is useful enough for a first public MVP review.
• Pass criteria: The public tool opens with the intended sample context, renders advisory output or a safe public workflow, and does not request private EVE or provider access.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

Open the public support route and keep replies, account decisions, payment links, and provider sends owner-review gated.

Success Signal

Support intake is visible, protected review stays gated, and no email, payment, or account action fires.

First-Run Steps

3

Sample

Support Intake Review

Route Proof

3/3

Rollback

Keep support message bodies, private contacts, email sends, payment links, provider console actions, protected reviewer notes, and account saves behind owner review.

• Try this: Open /support, use the Support Intake Review public-safe sample, and confirm the page shows the expected proof without private account access.
• Sample target: Support queue
• Sample link: /support
• Expected proof: Support intake or support guidance is visible while email sends, payment actions, and protected replies stay gated.
• Acceptance prompt: Open the support sample route and confirm protected reply, payment, and email actions remain owner-review gated.
• Pass criteria: Support guidance is visible, the route does not expose protected queue contents, and no email, payment, or account action runs.
• Acceptance rollback: Keep the lane in public preview and update the sample before live activation if this acceptance check fails.
• Step 1: Open the public tool route.
• Step 2: Use pasted, manual, public, or browser-local inputs only.
• Step 3: Check the readiness route and rollback label before treating the output as launch evidence.

uses only public top-20 tool labels, public routes, readiness routes, API smoke labels, first-run instructions, and public-safe input mode labels

keeps owner evidence values, protected packet bodies, support message bodies, account records, private EVE data, provider console details, private logs, tokens, credentials, and separate-project details excluded

does not start OAuth, call EVE or CCP, call providers, write database rows, save account reports, send email, create payment links, register Discord commands, load ads, flip feature flags, or mutate external services

treats nineteen public MVP lanes as usable public previews and keeps the support/protected-ops lane owner-review gated

keeps every launch action reversible through public route proof, readiness proof, API smoke proof, local/manual input labels, and rollback text