Skip to main content
ACI records content in a versioned ledger with a portable object-storage format. This gives your organization an independently operable copy of its content history without requiring the managed authoring service to use object storage as its live coordination layer.

​
Storage modes

Do not write to the same repository through managed and direct modes at the same time. Coordinate a mode change with your Gradial team to avoid divergent histories.

​
What the portable ledger provides

The portable ledger contains the versioned content state and history required to reconstruct a selected revision. It uses canonical, machine-readable objects protected by content hashes. Use supported ACI export, import, and direct-engine tooling to inspect or operate the ledger. Do not edit storage objects by hand; changing an object outside ACI can break the integrity relationships that make the history verifiable. The portable format supports:
  • independently validating exported content;
  • reconstructing branches and historical revisions;
  • importing the ledger into a compatible ACI deployment; and
  • operating through the direct engine when a repository has been moved to direct mode.

​
Managed-service data

The Gradial-managed service stores the operational ledger and supporting data needed for concurrent workflows. It can also maintain rebuildable views for validation, search, permissions, and publishing. In managed mode, Gradial processes and stores the tenant-isolated data required to provide the service while maintaining the configured portable export.

​
Deployment-specific controls

Storage ownership and cloud topology vary by deployment. During onboarding, confirm:
  • where the managed ledger and portable export are stored;
  • which cloud account and region apply to each store;
  • encryption and key-management responsibilities;
  • retention, backup, and deletion settings;
  • the permissions granted to Gradial; and
  • how export health and recovery are verified.
A customer-owned bucket does not necessarily make every ACI service, database, or delivery resource customer-owned. Use the architecture agreed for your deployment as the source of truth.

​
Recovery planning

A recovery plan should identify the revision you expect to recover and confirm that it is present in the portable export. A typical handoff includes:
  1. verify the export through supported ACI tooling;
  2. stop managed writes;
  3. switch the repository to direct mode;
  4. designate a single writer;
  5. validate the recovered content and references; and
  6. publish through a supported hosting adapter.
Contact your Gradial team before beginning this process so the final managed revision and direct repository start from the same state.
Data ownership and storage location do not by themselves establish compliance with a regulation or standard. Evaluate storage, access, consent, retention, and deletion controls against your organization’s requirements.
Back to What is Gradial ACI?