From bringing in existing texts to noticing what changed.

The target structure defines where a legal text applies — primarily for a brand, refined by language, market, or commercial variant. Websites are monitored targets for live checks and WebsiteChange.

• Workspaces
• Brands
• Products
• Markets
• Locales
• Site profiles
• Sites
• Domains

Bring your own legal texts: self-authored or externally provided texts are not managed as loose HTML blocks but as structured documents with sections and validated content blocks.

• Bring in existing texts
• No free HTML paste
• Sections and typed blocks
• Stable keys
• Document types
• Search and filter

Variants enable targeted deviations without copying entire documents.

• Base document
• Locale, market, profile variants
• Replace or suppress inherited blocks
• No duplicated full texts

Every approved version remains traceable. Restorations create new drafts rather than overwriting history.

• Immutable snapshots
• Version numbers
• Diffs between versions
• Version pinning on delivery
• Restoration as a new draft
• History is never modified

Approvals are not hidden in informal chats or emails but mapped as an auditable workflow.

• Single reviewer
• Sequential review
• Threshold approval
• Self-review not allowed
• Decisions and notes

Publications target brands, document types, locales, markets, and profiles. Websites remain the context for live checks, drift detection, and WebsiteChange.

• Brand- and context-aware publication
• Asynchronous publishing
• Published artifacts
• Rollback via controlled pipeline

Published content is available via a fast, read-only delivery interface — as HTML, JSON or PDF.

• HTML fragments for websites, apps and emails
• JSON for your own templates and rendering logic
• PDF artifacts for attachments and receipts
• ETags and cache headers
• Version pinning

Deliver legal texts where contracts are created — in order confirmations, contract emails, sign-up flows and checkout steps.

• Embed HTML into transactional emails
• Fetch JSON for your own mail templates
• Attach approved PDF artifacts to mails
• Stable reference to a specific version

Legal content drift happens when the version visible in production no longer matches the approved version. Live drift checks make that gap visible — the verify signal inside Document Intelligence.

• Crawl of public customer sites
• Comparison with approved version
• Drift detection per site, language and market
• Open, assign and triage findings

Legal texts usually age without anyone editing them. Document Intelligence watches three signals — legal changes (LegalChange), website changes (WebsiteChange) and live drift (Legal Content Drift) — assesses what they could mean in the context of brand, language, market and profile, and turns them into review findings. A confirmed finding can become a proposed change. Nothing is adopted or published automatically.

• Legal Change Monitoring (LegalChange): relevant legal changes
• Website Change Monitoring (WebsiteChange) — Beta: changes on monitored websites
• Legal Content Drift: divergence in the version delivered live
• Relevance assessed in brand and target context
• Findings with evidence, status and history
• Proposed changes as an unpublished draft
• No automatic adoption, no automatic publication
• Not a substitute for legal advice

Publication and lifecycle events are integration-ready.

• Publication events
• Signed webhooks
• Replayable deliveries
• Integration with external systems

Operational events remain traceable — failed jobs can be retried under control.

• Workspace event stream
• Retry for failed jobs in the customer app
• Replay for failed webhook deliveries
• No hidden mutation of history