Capabilities and boundaries
Useful capability.
Visible limits.
Explore what the interface demonstrates, what the bounded core implements and where the product is heading.
The foundations of considered operations.
Available means you can explore it in the public preview. Limited means it exists in the owner-operated core and is not an unrestricted public service.
A calm operational workspace
Inspect tasks, sources, agents and approval states through a focused interface. The public workspace makes the workflow explorable with synthetic records.
Try the design previewVersioned text knowledge
The bounded core stores source text with versions and content hashes. Drafts reference the selected evidence so a reviewer can check what informed them.
Durable task history
Requests, attempts, stages and outcomes are recorded in the core. Failure and cancellation remain visible instead of disappearing behind an optimistic success message.
Exact approval envelopes
Approval binds the task, actor, workspace, account, recipient, draft, commitments, source hashes and expiry. The core rejects changes that no longer match the reviewed proposal.
Internal commitments and receipts
Approved internal work records its draft and commitments with a receipt. A downloaded JSON artifact retains the approved action and evidence references.
Three specialist roles
Coordinator, researcher and operator responsibilities run through a bounded Hermes integration. Inference uses a configured local model, with external tools disabled in this implementation.
Connections must earn their place.
Email delivery
Sending from a real mailbox will need scoped authorization, account selection, exact-message approval and a verifiable provider outcome. No external email is sent by the current core.
Connected document libraries
Account-authorized file discovery and ingestion are future work. Current knowledge input is bounded text; a connected-drive logo is not evidence that files are being synchronized.
Messaging and CRM platforms
Third-party channels and CRM writes remain separate integration milestones. Current commitments are internal platform records, not synchronized records in an external CRM.
A roadmap with verification gates.
Richer knowledge retrieval
Document formats, semantic retrieval and knowledge graphs need evaluation before they can extend the evidence boundary. Current source selection should remain understandable.
Measured improvement
Prompt, skill and model changes should beat a measured baseline before promotion. An isolated research environment is part of the direction, not a capability claimed by this preview.
Stronger customer isolation
Independent customer admission requires further identity, execution, credential and recovery controls. Workspace scoping in the bounded core does not establish hostile-tenant isolation.
The questions behind the features.
Can an agent send a message on its own?
No external delivery connector is configured in the bounded core. It can prepare a draft for review and record an approved internal action; a receipt does not claim that an email was delivered.
Is the public workspace connected to real customer data?
The public design preview contains synthetic records and simulated actions. Authenticated operations is a separate interface with its own access boundary.
Does local inference make every answer correct?
No. Model output still needs validation and human judgment. Inspect sources, missing details and the exact proposal before approving work.
A considered next step
Choose a workflow. Inspect every step.
The best way to understand a capability is to see the context and decision around it.