> ## Documentation Index > Fetch the complete documentation index at: https://docs.gradial.com/llms.txt > Use this file to discover all available pages before exploring further. # How Gradial Works > The mental model behind Gradial: how agents receive work, execute it across your stack, and get smarter about your organization over time. Gradial's operating model can be summarized in three words: Work comes in from wherever it originates — Gradial's interface, a Jira ticket, a Workfront task, a brief or work request. No change to how you initiate work. Agents read the task, understand the intent, and execute end-to-end across connected systems — without manual handoffs between tools. Every output is checked against brand, accessibility, compliance, and QA rules the organization has defined — on every task, every time. Everything about how Gradial works flows from this model. *** ## The Anatomy of a Task To make this concrete, here is what a single task lifecycle looks like: Via Gradial's interface, a connected ticketing system (Jira, Workfront, Wrike), or a brief or work request document. Work can also be pre-scheduled and queued with dependencies set in advance. Reads the description, identifies the target content, and determines which systems are involved. Pulls relevant assets from the DAM, references brand rules and guidelines, checks templates and content patterns for the relevant page type. Authors, updates, tags, builds, or publishes as specified — navigating connected systems the way a skilled team member would. QA, accessibility (WCAG 2.2 AA), brand, and compliance checks are applied to the output before it reaches a human reviewer. The team reviews at whatever level of oversight is configured — full review, spot-check, or auto-approve for trusted task types. Status updated across connected systems. Audit trail created. Follow-on tasks triggered if needed. This cycle takes minutes for a standard content update. For bulk operations — updating hundreds of pages across a site — the same cycle runs in parallel across all items simultaneously. *** ## Specialized Agents Gradial is not a single general-purpose agent. It is a coordinated system of specialized agents — each built for a distinct category of marketing work — that can be orchestrated together across complex, multi-step jobs. Executes content changes across web pages — from a single field update to bulk operations across hundreds of pages. Understands CMS component structures, authoring rules, and publishing workflows. Builds net-new pages from a reference, brief, Figma file, or prompt. Translates design intent into a fully authored, published page within the existing CMS structure. Manages digital assets — uploading, naming, tagging, applying metadata schemas, retrieving assets for use in other tasks, organizing libraries at scale. Runs quality checks against the organization's defined standards: brand accuracy, accessibility compliance, legal and regulatory requirements, and custom criteria. Authors and builds emails within connected email platforms, creates variants, and applies the same QA and brand checks used for web content. Tracks how the organization's brand appears in AI-generated answers. Surfaces gaps and opportunities, and connects findings to executable optimization tasks. Turns a campaign brief into a structured, actionable set of tasks — broken down by channel, content type, and dependency — ready for execution by the relevant specialized agents. Handles content translation tasks across pages and assets, supporting multi-region and multi-language execution at scale. ### Orchestration in action When a job requires more than one agent, Gradial's orchestration layer coordinates their work automatically — sequencing tasks, passing outputs between agents, managing dependencies. **Example: Launch a localized campaign landing page in three markets** 1. **Brief & Campaign Agent** breaks the brief into tasks: one new page build, three localized variants, QA on all four, assets needed for each 2. **New Page Agent** builds the primary page from the Figma reference 3. **DAM Librarian Agent** retrieves and tags the required assets 4. **Translation Agent** creates the three regional variants 5. **QA Agent** runs brand, accessibility, and compliance checks across all four pages 6. Status is logged back to the work management system; team is notified for review What would typically require coordination across multiple tools, teams, and handoffs is one job in Gradial. *** ## How Gradial Connects to Your Stack Gradial is integration-first by design. A task that requires finding an asset, updating a CMS page, running a QA check, and logging the completion in a ticketing system is **one task** in Gradial — not four separate steps across four separate tools. | Category | Supported platforms | | ------------------------------- | ----------------------------------------------------------------------------------------------------- | | **Content management** | Adobe AEM (6.5 and Cloud), Sitecore | | **Digital asset management** | AEM Assets, Bynder, Content Hub | | **Work management & ticketing** | Jira, Workfront, Wrike, Asana | | **Email platforms** | Marketo, Salesforce Marketing Cloud | | **Design** | Figma | | **Productivity** | SharePoint, Word, Excel | | **Analytics** | Adobe Analytics, GA4 | | **Custom** | Secure MCPs — connect internal knowledge bases, proprietary data systems, or custom AI context layers | Integrations are configured once during implementation. Once in place, they're available to all agents and users in the workspace — no per-task configuration required. [See full integration setup documentation →](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations) *** ## Brand Intelligence — How Gradial Gets Smarter Over Time An agent that can execute work is only as good as its understanding of what *good* looks like for a specific organization. Generic AI outputs are not enterprise outputs. This is the brand intelligence layer: the encoded knowledge of how your brand sounds, how your content is structured, what your compliance requirements actually mean in practice, and how your team operates. Gradial builds this intelligence from the standards you configure and the work agents do — and applies it on every task, automatically. Gradial builds organizational brand intelligence across four areas: Organizations bring their brand guidelines, tone documents, and editorial standards into Gradial. Agents reference these on every content task. Over time, as agents complete more tasks and teams review outputs, the platform develops a working understanding of what on-brand actually means in practice — beyond what a style guide alone can capture. What passes a QA check at a financial services company is different from what passes at a consumer brand. Gradial learns an organization's specific QA criteria — accessibility standards, regulatory language requirements, brand accuracy rules, custom checks — and applies them consistently. As those thresholds evolve, Gradial evolves with them. Organizations develop patterns over time — how pages are structured, how assets are named, how campaigns are briefed. Gradial learns these patterns and applies them, so agents produce outputs that fit naturally into the existing environment rather than requiring extensive post-processing. Some teams prefer agents to draft for review; others want agents to publish directly for certain task types. Some route approvals through specific channels; others use automated sign-off for routine work. Gradial learns these preferences and adjusts how it handles work accordingly. ### The progression most teams follow | Stage | What it looks like | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Early** | Agents execute with frequent human review. The platform is calibrating to the organization's standards. Every review is input. | | **Established** | Agents handle a wider range of tasks with lighter oversight. Outputs consistently meet the bar for common task types. Human review shifts toward edge cases. | | **Advanced** | Agents operate with high autonomy on routine jobs. Teams focus on directing outcomes, not reviewing execution. | The pace of this progression varies. Some teams move through all three stages in weeks; others take longer. The level of autonomy is always in the team's control. *** Ready to go deeper? [Request a demo](https://www.gradial.com/request-demo) to see agents running against your actual CMS and content, or [navigate the platform →](/docs/getting-started/navigating-the-platform) to see how these concepts map to the Gradial interface.