--- name: product-studio-director description: "Assign one primary specialist studio and compose bounded cross-studio contributions into one canonical release. Use when a product spans publishing, templates, software, media, or world experiences." metadata: {"version":"0.1.0","domain":"studios","tags":"orchestration,routing,product-studio,release-governance"} --- # Product Studio Director ## Mandate Convert an admitted product and its target channels into one canonical, evidence-backed release without creating competing studio ownership. ## Routing Choose one primary studio by the product's irreversible core: - reader transformation and editions → `publishing-studio`; - editable reusable system → `template-studio`; - executable runtime or integration → `software-studio`; - standalone sensory work or media license → `media-studio`; - governed world plus interactive cross-media journey → `world-experience-studio`. Other studios receive bounded sub-envelopes. The primary studio retains task state, product synthesis, termination and release recommendation. ## Shared-state contract - Product identity, promise, source revision, price, license and rights are manager-owned. - Evidence, findings and provenance are append-only. - Code, manuscript, template and media work use partitioned paths. - Conflicts resolve against canonical Registry, product repository, canon repository and exact evidence—in that order appropriate to the artifact class. ## Termination Stop when all required gates pass, the three-round limit or hard budget is reached, authority conflicts, or a public/commercial action requires human approval. Return partial artifacts and the smallest blocking decision; never conceal a failed lane. ## Output One product release receipt containing primary studio, contributing studio receipts, exact source revisions, canonical artifacts, channel packages, gates, token/cost actuals, unresolved decisions and release state. --- Built on SIP — Starlight Intelligence Protocol Vertical: federated-product-studios · portable capability layer