Product guide
A clear path
through the work.
A practical guide to the preview and bounded operations workflow. Begin with the mode you are using, then follow the evidence and review trail.
First, know which workspace you are in.
No sign-in required
Available to explorePublic design preview
The workspace contains synthetic tasks, clients and sources. Search, filters, task details and simulated approvals are designed for exploration. No external messages are sent and no real account is connected.
Open the synthetic workspaceConfigured owner only
Bounded implementationAuthenticated operations
Operations requires the configured owner’s credentials. It manages actual core records and requests; it is not a public signup flow. Treat its source text and approvals as real operator work.
Open operations sign-inA five-minute tour of the preview.
Find a task
Browse the task list, use the search field and narrow the view by status. The records are illustrative examples of agency work.
Inspect the detail
Open a task to see its proposed action and activity. Switch to Evidence to inspect the supporting source preview where one is available.
Review the proposal
Check the account, recipient, subject and message together. Approve or reject in the demo to see how the decision changes the simulated state.
Reset and compare
Reset the demo to return to its initial sample state. Try another request or explore the agent, knowledge and connector views; connector descriptions remain a design preview.
The bounded core workflow.
These steps describe the implemented owner-operated core. Public availability and production verification are tracked separately on the status page.
Sign in to operations
Use only the configured operator account. After sign-in, confirm the workspace before adding evidence or submitting work.
Add selected text evidence
Give each source a meaningful title and provide the relevant bounded text. Keep credentials and unrelated sensitive data out of the content. Check the source you intend to use before creating a request.
Submit a specific request
Describe the client and desired draft, select the supporting documents and check the intended recipient/account. The request becomes a durable task.
Watch the actual outcome
Stages and history show the work as it proceeds. A local model can take time. A blocked or failed task is an outcome to inspect, not an instruction to assume success or repeatedly submit the same work.
Review the exact action
Read the draft, commitments and evidence together. Approve only a supported, current proposal. Reject or cancel when the proposed action should not proceed.
Inspect and download the receipt
After a completed internal action, inspect its receipt and download the JSON artifact. It retains the approved action and source hashes. It does not confirm external email delivery.
A status is part of the record.
Queued or running
The task is waiting or being processed. Stage, attempt and history provide context; the request is not yet a completed result.
Awaiting approval
A proposal is ready for a person to inspect. No approved internal action has been committed yet.
Completed
The approved internal draft and commitments have been recorded with a receipt. Read its verification text for the exact outcome.
Blocked, failed or cancelled
The work could not proceed, encountered an error or was stopped. Inspect the reason and history before deciding whether to provide better evidence or create a new request.
Before you approve.
Check the identity
Confirm the client, account and intended recipient. An otherwise useful draft can still be wrong for the person or context it names.
Check the support
Read the cited sources and check names, dates, owners and commitments. Do not fill an evidence gap with an assumption.
Check the scope
Understand that the current core records an internal draft and commitments. Sending or synchronizing externally requires a separately supported connector.
Check the result
Keep the receipt and approved artifact if you need to review or hand off the work. Treat a download as a record, not a claim that every later action has happened.
A considered next step
Learn by inspecting a complete example.
The public demo gives you a safe place to explore the request, evidence and approval flow.