Answers organized around the mission flow.
These answers are grouped by the way people actually use the product: starting work, tracking progress, continuing context, and governing work at team scale.
Getting started
What should I do the first time I open Kaypal?
Start with New Task. Give the system a real goal, inspect the plan, and then decide whether to move forward.
Why do you keep saying key partner?
Because Kaypal is built around a primary working relationship: you declare the goal and the key partner coordinates execution and returns results.
Planning and execution
Why plan first instead of executing immediately?
The route, risk, and cost should be explicit before the first action so the work never becomes a black box.
Where do I inspect progress?
Use Live Tasks and the task detail page to review stage changes, logs, evidence, and takeover controls.
What happens if runtime or a connector is unavailable?
Kaypal should expose the degraded route explicitly so you can see the fallback instead of silently losing control.
Chat and context
What is the difference between Chat and New Task?
New Task is the formal handoff surface. Chat is where you continue the context, clarify intent, and refine decisions.
Why do some Chat flows ask me to choose a partner first?
Because Chat belongs to an ongoing work relationship rather than an anonymous assistant session.
Enterprise governance
What does enterprise governance manage?
It manages members, credentials, memory continuity, and budget boundaries so work can run safely at team scale.
How do team members join?
They enter the enterprise tenant first and then work inside the same governed collaboration environment.