Skip to content

Whole-site population: manifest import primitive or blessed orchestration contract #49

Description

@jsirish

Context

The agency content pipeline (agency-skills) is moving to content-api + MCP as the primary population path. Full-site population today means client-side orchestration: one compositions/page call per page, plus batch calls for the page tree and assets. That works, but every orchestrator reimplements ordering, error recovery, and idempotency conventions.

Ask

Either (a) a whole-site manifest import primitive, or (b) a blessed, documented client-side orchestration contract. Concretely:

  • Option a: POST compositions/site (or batch extension) accepting a manifest of pages (hierarchy + compositions + asset refs) applied in dependency order with per-page results, resumable on partial failure.
  • Option b: a docs page defining the canonical orchestration loop: create page tree via batch (parents first, ext: ids), upload assets (hash-dedupe makes re-runs cheap), compose per page in tree order, publish recursively from roots, with recommended retry/resume behavior and how to detect and prune leftovers.

Even if (a) is deferred, (b) unblocks consistent agent behavior now and becomes the spec for (a) later.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions