Challenge
Cross-brand timeline publishing and automation rules need a central orchestration layer that Ace9 and marketing sites can call without embedding LLM or worker logic in every app.
OrchestrationConcept
Agent9 Platform
Automation and intelligence layer for timeline publishing, ingest workers, and cross-brand operations — orchestration source lives outside this monorepo.
Concept case study — core orchestration code is maintained in a separate Agent9 Platform repository.
Approach
Agent9 Platform (separate repository) exposes ingest webhooks and content builders; ace9-admin accepts signed ingest posts and surfaces pending_approval events for human review before publish.
- POST /api/timeline/ingest with Bearer + HMAC hardening
- @a9/timeline-drafts package for dedupeKey and suggest scripts
- Ingest worker script for dry-run and live platform runs
Outcomes
Marketing sites consume published feeds only; operators approve timeline items in Ace9. Auto-blogger LLM refinement stays deferred while webhook and worker paths are production-documented.
Key highlights
- Timeline ingest webhooks with HMAC verification and rate limiting
- Agent9 content builder for deduplicated auto-blogging workflows
- Bot member attribution and structured ingest logging
- Integration boundaries documented for Ace9 and connected ventures
More case studies