The web journey
No connected sources are required to describe an outcome. When discovery finds
none, the plan remains a proposal from your brief. External deep search is an
explicit choice with provider cost and limitations; it is never enabled as an
implicit fallback. Draft creation and planning-model use do not prove a run started.
Your progress is saved. If work is waiting on a run or approval, open this
initiative in Mission Control and return later. Retry the saved step when a
save receipt is missing; do not start another journey to recover.
Choose the tool you already use
Verify only tools present in the selected profile and current grant. A narrower
profile cannot acquire missing tools by following a generic prompt. An empty
workspace is a valid result; show the empty state and its next action.
Readiness has several meanings
Browser pairing events only prompt rechecking server state. They cannot prove
readiness or survive as authority across accounts, workspaces, revoked keys, or
stale attempts. A saved portfolio entry is not a started run.
Recovery
Changing the discovery mode, full goal, sources, or workspace creates a new
request identity. Retrying the same request preserves it.
Data and credentials
Before installing, review what changes locally, what data can be sent, the capture mode, and how to remove or revoke access. Show essential boundaries before setup; expand the reference only when needed.
A credential removal is not deletion of hosted records. Capture metadata can
include project names or paths. See security and retention.
Specialized journeys
Team Trail invitations join a specified Trail team and its pooling scope; they do not grant workspace-wide membership or access. Expired or used links need a replacement invitation from the team owner. X-Ray, self-audit, and Workload Doctor begin from their own evidence or workload shape. Workload plan confirmation acknowledges a proposal; account creation and authority grants remain separate. Studio onboarding configures a brand from the supplied URL or brief; its success is a usable Studio configuration, not an accepted organizational work result. Assisted founding-customer onboarding follows the signed agreement. Recording, check-ins, Day-14 brief delivery, refund terms, and next-quarter plans are customer-specific rather than promises of the default web journey.Verification boundaries
Source contract reviewed September 30, 2026: Wizard 0.1.85 (Node 22+), MCP manifest 1.1.5. Source review is not a fresh package install or a deployed OAuth negative control. Record the tested release, host version, workspace, profile, permitted read, denied write, runner probe, and delivered receipt before calling an installation end-to-end verified.onboarding_completed is navigation graduation. It is not accepted first
value. Work milestones must be joined to the workspace, journey, initiative,
run or artifact, and intent; track readback activation separately for status
clients. A receipt marked completed can describe a completed API operation
while its task remains todo.