PRODUCT GUIDE
Define the service you want to sell
Prepare a precise service brief before a private Workspace setup.
Product guide · Based on the September 18, 2026 product documentation. Connected proof is reported for specific operations; this guide is not a new live certification. Private work and provider authorization take place in Agent.
What this is for
Prepare the service, buyer, delivery territory and intended next step before setting up a Workspace.
For each service, record what you can deliver, what you exclude and what information a buyer must provide. Keep a service hypothesis separate from a confirmed customer need.
Before you start
Prerequisites
- A clear service scope
- The buyer and decision process
- The territory you can serve
Operating modes and access
Documented modes: ASSIST and AGENT. Modes do not grant access or execution authority.
Relevant roles: OWNER, ADMIN, OPERATOR. A listed role does not imply that every action on the screen is permitted.
Check mode and role boundariesWhat is checked
Review the service scope with the people responsible for delivery. Private setup readiness must be confirmed separately.
Evidence and limits
The source records this setup function, but classifies it for internal use only. This page explains what to prepare; it does not promote the implementation as a verified public capability.
No provider-wide integration claim is made by this capability.
Important limits
- No connected proof is claimed by the current Architecture function registry.
Apply it to your service
Start with the service you deliver. Industry examples are hypotheses to review, not proof of demand or results.
Choose the next step
Explore the public sample, or open Agent to review the relevant setup and permissions for an existing Workspace.
YOUR NEXT MOVE
Start with a clearer
next move.
Explore a Blueprint before deciding how much work to delegate.
Preview available. Paid checkout is not open.