Information and actions
Ask a question, open a record or submit a form. Amy presents the information and permitted actions for the task using shared interface components.
Less manual work. Clear responsibilities.
Process Automation
Automate recurring business work with AI. In Space, Amy helps your team find information and take action. Guided procedures connect those actions with your existing systems and the people who review and approve the work.
Shape the intent in Studio. Amy runs supported behavior directly, without a separate application coding and deployment cycle.
How apps and procedures automate work
Apps provide the actions.
Procedures connect the steps.
An app brings information and permitted actions together for a task. A guided procedure carries the process from one step to the next: gather data, prepare an action, request approval and continue in a connected system. Together, they automate routine work while keeping people involved where judgment is needed.
Cases and handoffs
Guide work through declared steps, human decisions and exceptions. Each participant acts within their role and the current case; process history records its progress.
Work with existing systems
Use supported, configured API or tool connections for the capabilities your intent declares. Connection setup, credentials and testing remain part of preparing the work.
Illustrative example · purchasing
A request, an approval, a purchase order.
Capture the request in a native form, retrieve supplier information through a configured connection, ask the responsible manager to decide, then create the order through a supported API operation. A process connects these actions and the human handoff. Each external operation needs an available, tested connection.
Where the team works
Your apps and processes.
One Space.
Space is the shared place where colleagues use the apps and processes assigned to them. Open a task, resume a case needing your role, or ask Amy for help with the work in front of you.
Use what is assigned to you
Find your apps and processes, start permitted work and follow the cases where your role is needed.
Move from a question to an action
Work with conversation, forms, records and observed results. The relevant intent, information and access follow the task.
Keep colleagues within reach
Use the people directory and private one-to-one messages. Everyday participation is separate from permission to author an app or process.
Workspace owners manage invitations, shared model connections and access in Studio. Each person sees the work they are authorized to use.
Shared context covers the relevant intent and authorized information. Private messages stay between the two participants; Amy does not read them.
App and process templates
Explore the work.
Then make it yours.
Try a prepared example without signing in. Inspect its model or try the sample experience, then create a private copy in Studio for your team.
App
Task Planner
See how a member’s tasks connect to priorities, due dates and a focused day.
Look for: the rule that picks up to three tasks for today.
Explore the app model Try the app sample →Use this template →Process
Expense Approval
Follow an expense through submission, a manager’s decision and reimbursement.
Look for: the approval handoff and the path for rejection.
Explore the process model Try the process sample →Use this template →Explore it here
A shared model, visible from every angle.
Select a step to inspect its responsibilities and decisions. These interactive charts show the prepared template; exploring them does not execute business work.
Direct execution
Maintain the rules.
Amy runs the intent.
Amy’s shared runtime uses the intent to guide supported operations and compose the interface. Your team maintains the goals, people, information and rules instead of a separate generated app codebase.
- Configure
- Set up the app or process resources, model connections, participant access and any supported external capabilities.
- Try
- Review the actions and work through test cases before making a process available. Check required providers and the effect of changes to stored data.
- Evolve
- Accepted app changes guide subsequent turns. Released process cases retain their pinned intent so an ongoing case does not silently change underneath its participants.
The shared platform supplies the runtime and interface components; your team keeps the intent current. Read Michael Hasler’s article on running intent directly.
For a standalone website, web application or mobile app, hand the software intent to your coding agent.
From instructions to permitted actions
AI proposes an action.
Amy checks the change.
When an app operation needs interpretation, AI reads the intent and relevant data and proposes what to do. Amy checks supported permissions, data constraints and named outcomes before storing the changes.
- What matters
- Your intent defines
- Amy checks
- Who can act
- The people, roles and operations involved in the work.
- The caller’s access and scope for the requested operation.
- What can change
- The information an operation may create, update or remove.
- Permitted records, field types, required values and references.
- Which outcome
- The decisions and outcomes the operation names.
- Proposed outcomes against the supported contract structure.
- What was recorded
- The operation and the person acting.
- The data change and its activity record. Conflicting or invalid writes are refused.
Keep judgment and approval visible.
Some decisions depend on AI interpreting the meaning of a rule. Structural checks do not prove that interpretation is right. Model the review and approval steps the work needs, and use the recorded outcome to inspect what happened.
Your controls
Decide who acts.
See what happened.
Keep model choices, participant access, human decisions and recorded activity visible as the work grows.
- Access
- Workspace owners assign app and process access and roles. Server-side checks apply the caller’s permissions and, for a process, the current case’s allowed work.
- AI choices
- Owners manage shared model connections. Deployment administrators allow or block models separately for modeling and app use.
- Oversight
- Recorded app activity and process history show outcomes. Deployment administrators can inspect model calls, token usage and estimated costs by user and model.
Plan your first rollout
Start with work you can review.
Choose a focused task, clear responsibilities and a result your team can check. Expand as you learn.
- AI judgment
- Interpretation takes a model call and can be mistaken. Define human review where the decision needs it.
- Usage
- AI calls consume model resources. Review usage and estimated costs alongside your workspace plan and provider charges.
- Connections
- External systems need supported integrations and configuration. Describing a connection does not establish it.
Just need to describe the work or share reusable instructions? Process Modeling is a complete outcome on its own.
Your knowledge. Your rules.