FAQS
An agent reads a document, decides what it is, and takes the next step itself rather than waiting for a person to trigger each stage. In TeamSync the actions it may take are declared in business rules and enforced at the platform layer, so autonomy is bounded by configuration, not by prompt wording.
A rule fires on a fixed condition you defined in advance. An agent classifies ambiguous input and chooses a path, then hands anything above your defined thresholds to a person. The rules do not disappear - they become the boundary the agent operates inside.
That depends on your use case, not on the platform. Where a deployment does fall in scope, every agent action and refusal is anchored to the audit chain and human-oversight evidence is generated from it, so the required documentation is a query rather than a project.
Agent actions are versioned like any other change, so a document or workflow state can be restored to the point before the agent acted, and the audit chain records the inputs, the rule that fired and the outcome.
Agents are configured in the workflow designer from document types, metadata and rules you already have. Custom code is optional rather than required, so the constraint is usually how quickly your rules can be agreed, not build time.