Knowledge, content, channels, and publishing
Brand knowledge
Knowledge sources and entries hold approved facts, claims, source URLs, ownership, confidence and validity. Answer assessments compare observed answers with approved knowledge to identify missing, conflicting or unsupported claims.
Content Studio
Create briefs, pages, FAQs, product copy, campaign copy, social content, structured data and machine-readable artifacts from approved facts and evidence. Content items have versions, parent relationships, target, topic, channel, format, goal, source entries, measurement window, owner and approval status.
llms.txt, JSON-LD, feeds and similar artifacts are outputs, not universal ranking guarantees. Publish only artifacts appropriate for the destination and verify that they remain reachable and valid.
Planning
Activation plans connect a recommendation to content, channel, owner, approval, schedule, expected lift and verification window. Use one plan when changes share a common outcome; use separate plans when risk, owner or rollback differs.
Channel connections
Supported capability families include WordPress, Contentful, Sanity, Strapi, Webflow, Shopify, AEM, generic REST CMS, GitHub/GitLab, object storage, sitemap, robots/llms.txt, feeds, LinkedIn, Meta, X, TikTok, YouTube, Google Ads, CRM/e-mail and generic webhook.
A connection defines destination, capability, HTTPS endpoint, secret reference, allowlist, configuration, status and policy. Availability depends on the configured adapter and third-party API access; naming a channel does not imply that credentials or external API approval already exist.
Publishing lifecycle
Preview → approve → schedule → publish → verify → measure. Every publication links content, target, channel and destination and records approval, result, verification and rollback. Retries must be idempotent. Failed work enters a visible retry/dead-letter path rather than being marked published.
Capability versus availability
| State | Meaning |
|---|---|
| Modeled | The channel type exists in the connection contract |
| Configured | Workspace destination and non-secret configuration exist |
| Authorized | Required credential/OAuth scopes resolve successfully |
| Preview-ready | Adapter can generate a destination-specific diff without mutation |
| Publish-ready | Policy, approval, idempotency and rollback prerequisites pass |
| Verified | The expected destination state was read back successfully |
Documentation of a channel family does not imply that a third-party account, OAuth application review or production scope has already been granted.
Safe configuration
- Store credentials in encrypted storage or secret references such as
env://GEO_CMS_TOKEN. - Prefer HTTPS and explicit host allowlists.
- Use least-privilege channel credentials.
- Preview diffs before mutation.
- Require approval for high-risk or public changes.
- Define verification and rollback before publishing.