Kontext Launchpad

Capabilities

Launchpad takes an idea through The Path (ten steps in order), then Phased build you confirm — or an optional one-shot first build. Complete path does not generate code. It is not Talk and not Kontext Docs.

• The Path — ten steps; you cannot skip ahead

• Phased build — confirm or skip each slice, then Product sign-off

• Open Workspace — optional handoff; there is no Business CRM rail

What is Launchpad?

Launchpad (/launchpad) takes an idea through The Path (ten steps you finish in order), then Phased build you confirm, or an optional one-shot first build. Complete path only marks planning done — it does not generate code. The journey stays the source of truth until Product sign-off.

The sidebar

• Start: Launchpad Home, Idea Studio, Guides.
• Build & ship: The Path, Phased build, Launch Readiness, Ship & Announce, Walkthroughs, App Store & Play.

What it is not

It is not the default “generate an app” composer in Workspace. That is a new project from a description on App. It is not an update to an app you already have. That is Workspace. It is not Talk. It is not Kontext Docs. There is no “hand this to Business” rail — Open Workspace is the handoff.

Not yet

Launchpad (/launchpad) guides idea → phased build: structured specs Kontext executes against. Team-visible in the OS catalog. Hand off phases to Workspace or Business when ready.

• Phased capture — intent, milestones, approvals

• Feeds generation/deploy pipelines you control step by step

• Complements ad-hoc Chat when you need a plan first

Launchpad (expanded)

Route: /launchpad

Command layer & OS-native flows (summary)

User journeys

L-01. Start a Launchpad phased build from an idea

Path: /launchpad · OS dock → Launchpad

You do:

1. Open Launchpad from /launchpad or the Kontext OS app catalog entry.
2. Describe your product idea in the first capture step — audience, problem, and rough scope.
3. Read the guided path copy: output is a phased execution spec, not a dead prompt dump.
4. Commit to Start on the path (or equivalent) so Kontext creates or binds a real project before deep steps.
5. Work through early journey steps (intent, constraints, success signals) at your pace.
6. Save drafts between sessions — journey state lives on the bound project.
7. Note the current path step indicator before closing; you can resume later (L-09).

Result: Structured Launchpad journey tied to a Kontext project, ready to compile into phased build work the platform can execute step by step.

L-02. Bind a Launchpad journey to a Kontext project

Path: Launchpad → Start on the path · first committed step

You do:

1. Complete enough idea capture to trigger project bind (first committed start or Step 1 completion per product rules).
2. Confirm the UI shows a linked project name or id in the Launchpad chrome.
3. Open Workspace in another tab and verify the same project appears in the picker.
4. Return to Launchpad — accumulated Launchpad context object should persist on that project.
5. Upload or attach any reference files; they land in project-scoped storage, not orphaned blobs.
6. Continue the path knowing files, specs, and lineage share one system of record.
7. Avoid starting a second parallel Launchpad bind for the same idea unless you intentionally want a new project.

Result: Journey state, context object, uploads, and handoffs all reference one durable Kontext project — nothing is orphaned when you move to Workspace or Business.

L-03. Complete Phase 1 through project generation

Path: Launchpad Phase 1 complete → Generate · handoff to generation pipeline

You do:

1. Finish Launchpad steps that feed Phase 1 — scaffold scope, core features, and acceptance hints.
2. Review the Phase 1 summary panel before triggering generation.
3. Approve Phase 1 execution — it routes into Kontext's existing project-generation pipeline (not a one-shot generate everything).
4. Wait for generation progress in Workspace Chat or the OS overlay if you stayed in Launchpad.
5. Inspect generated files in Workspace side pane — first implementation pass only, per phased model.
6. Mark Phase 1 complete in Launchpad when acceptance criteria are met.
7. Plan Phase 2…N as follow-on passes rather than restarting from scratch (L-04).

Result: Phase 1 ships a scaffold and first implementation pass into the bound project; later phases add features incrementally until MVP scope is done.

L-04. Advance through milestone approvals

Path: Launchpad path stepper → phase gate · Approve & continue

You do:

1. Open your in-progress Launchpad journey and locate the path stepper (active, completed, blocked nodes).
2. Read the current step output — structured fields, not freeform notes only.
3. Edit any step before approving if discovery changed your plan.
4. Click Approve & continue (or equivalent gate) to unlock the next step or phase.
5. Repeat for each gate — intent, milestones, integrations, polish, deployment hardening as defined in your path.
6. Watch completed steps turn emerald in the stepper; active step uses orange brand accent.
7. Do not skip gates that feed the Execution Roadmap compiler (L-08).

Result: Each phase advances only after explicit approval, keeping human control over what Kontext generates or deploys next.

L-05. Hand off Launchpad phase to Workspace

Path: Launchpad phase complete → Open in Workspace · Open in AI Workspace

You do:

1. Finish a Launchpad phase that generates or edits build work.
2. Click Open in Workspace or Open in AI Workspace from the phase completion panel.
3. Select the bound project if prompted — it should default to the Launchpad-linked id.
4. Confirm Workspace opens with Chat, Context, and files preloaded from Launchpad context — no cold start.
5. Continue generation or manual edits in Chat using accumulated spec context.
6. Use Context tab to review rules Launchpad injected before sending more prompts.
7. Deploy from Workspace when the phase acceptance criteria are satisfied (pair with Gas Station if deploy fails — G-06).

Result: Workspace opens with full project context from Launchpad for generation, edits, and deploy without re-explaining the product from zero.

L-06. Hand off Launchpad plan to Kontext Business

Path: Launchpad → business-oriented phase → Kontext Business · /business

You do:

1. When the phased plan targets a business solution (CRM, automations, owner cockpit), choose the Business handoff target.
2. Review pre-filled intake fields sourced from Launchpad context — offer, audience, operational goals.
3. Confirm handoff opens /business create or solution flow with plan context carried over.
4. Complete any Business-specific fields Launchpad could not infer (phone agent, booking, payment caps).
5. Link the solution to the same underlying workspace project if the UI exposes project lineage.
6. Turn on owner-facing recipes from Business module using the Launchpad spec as north star.
7. Return to Launchpad only if you need to revise upstream phases after Business intake reveals gaps.

Result: /business opens with Launchpad plan context so go-live work starts from structured intake, not a blank business wizard.

L-07. Open Launchpad from Kontext OS

Path: Kontext OS → app catalog · dock → Launchpad

You do:

1. Open Kontext OS (/os) from the module switcher or post-login dock.
2. Locate Launchpad in the OS app catalog alongside Workspace and Documentation.
3. Launch it without leaving OS shell if the overlay supports embedded open; otherwise navigate to /launchpad.
4. Confirm orange-led Launchpad chrome matches OS/marketing DNA (not Messenger-neutral gray).
5. Start a new journey or resume an existing bound project from the OS entry point.
6. Use OS command layer intents ("create app", "phased build") if routed to Launchpad automatically.
7. Hand off back to OS Intelligence or Workspace when a phase completes (L-05, L-10).

Result: Launchpad is a first-class OS destination for idea-to-build journeys, not a hidden standalone URL.

L-08. Review the execution roadmap before handoff

Path: Launchpad Path step 10 · Execution Roadmap · compile panel

You do:

1. Complete prerequisite path steps so the Execution Roadmap compiler unlocks (typically path step 10).
2. Open the compiled Launchpad context object preview — JSON or structured UX summary.
3. Read the phase-ordered execution plan: goals, dependencies, acceptance hints, optional agent tasks per phase.
4. Verify Phase 1 vs Phase 2…N boundaries match what you expect to ship incrementally.
5. Edit upstream steps if the roadmap shows wrong dependencies before any handoff.
6. Choose launch targets: Open in OS, Open in AI Workspace, or Business (L-05, L-06).
7. Export or snapshot the roadmap for stakeholders if the UI offers download.

Result: Machine- and human-actionable phased build plan — not prompts only — ready for approved execution in Workspace, OS, or Business.

L-09. Resume an in-progress Launchpad journey

Path: /launchpad → Continue journey · project-bound entry

You do:

1. Open /launchpad while signed in as the project owner.
2. Select Continue on the in-progress card tied to your bound project (or pick project from list).
3. Confirm the path stepper restores the last saved step and draft fields.
4. Skim prior step outputs for context before editing the current step.
5. Complete or approve the current gate to advance (L-04).
6. Verify uploads and attachments from earlier sessions still appear in project storage.
7. Avoid creating duplicate journeys for the same project unless you intentionally reset.

Result: Journey state, Launchpad context object, and files pick up exactly where you left off on the same Kontext project.

L-10. Query Launchpad state through KESA

Path: KESA-enabled agent → ask about Launchpad · /agents test chat

You do:

1. Enable Kontext Ecosystem on an agent with launchpad module in scope (K-11, K-02).
2. Open test chat on /agents or OS employee with Launchpad access.
3. Ask a read-only question: What Launchpad journeys do I have? or Summarize my active phased build.
4. Confirm the agent uses KESA search and module state before guessing or opening external tools.
5. Request a specific action only if your registry includes Launchpad execute capabilities for your role.
6. Follow any open link in the agent response to jump to /launchpad on the correct journey.
7. Re-test after narrowing module scope to ensure disabled modules stay hidden (K-02).

Result: Launchpad journey status is readable and actionable through KESA like other platform modules — inside Kontext first, Composio second.

How it works

Route /launchpad. Guided phased builder: idea → milestones → specs handed to Workspace or Business. State on user-canister projects; KESA can query Launchpad state.

Benefits

• Turns a vague idea into sequenced build phases.
• Clear handoffs into Workspace or Business without losing the plan.

Who it's for

Primary: founders starting something new who need structure before coding. Not: users mid-flight on an existing Workspace project.