Capabilities
Capabilities, evidence and limits.
Explore the documented product areas and what remains to be evaluated. Requirements and limitations accompany each entry.
An implemented feature is not proof of reliable behavior. Each entry distinguishes its evidence and limits; public product access is not open.
Current interface truth
Six connected workspaces. Explicit boundaries.
The recorded interface includes Home, Team, Mission, Library, Workspace and Settings. These views help explain the design; their presence does not demonstrate successful tasks.
Browse by category
Explore capabilities by how you work.
Select a category, then open any capability to see its requirements, limitations, evidence date, and Human decision boundary.
Evidence reviewed 2026-09-12. Historical component checks and interface captures do not establish current whole-product qualification. Conversation remains under evaluation. Voice is not included.
Loading capabilities…
Understanding capability
A role, a capability, and authority are different things.
Team shows who exists, which capabilities are registered, and whether a governed assignment is active. Availability never creates authorization.
See the workflowTeam truth remains explicit
Person, role, capability, availability, assignment, and authority are separate states. No state silently promotes another.
Knowledge and context
Know what kind of information you are looking at.
The Library capture separates Knowledge Objects, sources, candidates, registered skills and contextual memory. Its seed counts are demonstration data.