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.
Why Gradial ACI
If you’re evaluating content infrastructure, here’s what Agentic Content Infrastructure (ACI) provides and why it exists.What ACI Provides
ACI is the infrastructure layer that handles everything from “content saved” to “content live on your site.”| Capability | How ACI Handles It |
|---|---|
| Content storage | Your cloud storage bucket, in your own account |
| Content validation | Whole-site compilation: every schema, every reference, every route |
| Reference integrity | Compiler-enforced across all documents |
| Publishing | Built-in staging + atomic pointer-swap activation |
| Preview | Instant, any code version + content workspace combination |
| Rollback | Flip a pointer. Sub-second. No rebuild. |
| Data model | A clear, filesystem-inspired structure. Content is JSON files in folders, not scattered across half a dozen APIs and proprietary concepts |
| AI integration | Agents as first-class operators with workspaces and identity |
| Code coordination | Content and code versioned independently, published together |
| Data ownership | Customer-owned cloud storage |
Five Things ACI Gets Right
1. Nothing goes live unvalidated
1. Nothing goes live unvalidated
ACI’s content compiler validates the entire dependency graph before publishing. Every reference must resolve. Every document must match its schema. Every route must map to valid content. If something is broken, the compiler tells you what and where, and the publish doesn’t proceed.This is the difference between “I hope my content is correct” and “I know my content is correct.”
2. You own your data
2. You own your data
ACI stores content as immutable JSON objects in a cloud storage bucket in your own account. Not in Gradial’s database. Not behind a proprietary API.You can inspect it with standard tools, back it up with your existing infrastructure, and query it directly. If you stop using ACI, your content stays exactly where it is, in your bucket, in a standard format.This matters for compliance (data residency requirements), for risk management (no vendor single point of failure), and for peace of mind.
3. Publish is atomic, rollback is instant
3. Publish is atomic, rollback is instant
When ACI publishes, it stages all affected pages into a new release alongside your current live site. Then it flips a pointer. Your users see either the complete old site or the complete new site, never a partial update.Rollback is the inverse: flip the pointer back. No rebuild. No waiting for a deploy pipeline. Sub-second.
4. AI agents are real operators
4. AI agents are real operators
In ACI, agents operate through the same infrastructure as humans. They get draft workspaces, they save changes, they go through validation, and their work is traceable in the audit trail. This makes it possible to run agent workflows at scale (translation, variant generation, SEO optimization, accessibility audits) with the same safety guarantees as human editing.
5. Content and code stay independent, but coordinated
5. Content and code stay independent, but coordinated
ACI versions content and code separately. A developer can ship a new component without rebuilding all content. An editor can update a page without triggering a code deploy.But they never drift out of step. ACI intelligently coordinates them at publish time through the content compiler, validating content against the latest component schemas and rendering through the latest compatible code capsule. No publish bottleneck where content and code changes queue up behind each other.
Where ACI Sits in Your Stack
ACI replaces the “glue” between your content operations and your frontend. It does not replace your editor UI, your design system, or your hosting provider.Who ACI is For
ACI is designed for teams that:- Run content at scale across large page volumes
- Need content operations that are auditable and compliant
- Want to deploy AI agents as real content operators, not just copilots
- Use modern frontend frameworks (Astro, Next.js, SvelteKit)
- Care about data ownership and portability
- Want marketers and content authors to direct updates through natural language rather than navigating CMS menus and configuration screens
Next: Content Versioning →