Overview
A content package* in Ottili LD3* is one story, packaged for every channel it touches — without re-authoring it from scratch. From a single verified and approved draft, LD3 groups related assets that share one set of metadata and one approval history.
Content packages are part of the Beta (BETA)* of Ottili LD3. The packaging capability bundles the outputs of the LD3 pipeline (sources → verification → facts → topics → package → review → publishing → analytics) into a multi-channel unit. Everything runs company-scoped: every package belongs to exactly one company (company_id) and is recorded through Ottili Core Audit*.
What is inside a package
From a single approved draft, a package groups related assets that share one set of metadata:
- Article* — the canonical long-form piece; the basis from which every other output is derived.
- Social cutdowns* — short posts for social channels.
- Newsletter blurbs* — recaps for email.
- Shop copy* — product or category page text where relevant.
Every asset points back to the same verified fact base, so claims stay traceable across channels.
Why packages
A package keeps a story consistent across channels. One set of facts, one approval trail, many outputs. Publishing becomes a single action — route the package to its mapped channels instead of posting ten times by hand. When a source or a fact changes, you maintain it once and propagate it to every derived asset.
Status and availability
Content packages carry the maturity status Beta (BETA)*. The LD3 pipeline that produces packages is positioned in the canonical feature-status matrix as follows:
| Capability | Status |
|---|---|
| Source intake | Beta (BETA) |
| Source verification | Beta (BETA) |
| Fact extraction | Beta (BETA) |
| Topic expansion | Beta (BETA) |
| Content packages | Beta (BETA) |
| Human & AI review | Beta (BETA) |
| Multi-channel publishing | Beta (BETA) |
| Analytics | Beta (BETA) |
| Learning loop | Early Access (EARLY_ACCESS) |
| Approval gates (Ottili Core) | Beta (BETA) |
How Ottili ONE labels maturity publicly is explained in [Understand feature-status labels](/docs/understand-feature-status-labels). The beta model of Ottili ONE is described in [What is Ottili ONE?](/docs/what-is-ottili-one) in the context of product maturity.
Package status at a glance
Each item in a package carries a status: *queued*, *in review*, *approved* or *published*. That lets you see, at a glance, where a story stands on every channel — before and during publishing.
Approval and audit
Content packages follow Ottili LD3's draft- and approval-first principle: publications wait for a human confirmation before they go public. Approval gates are held through Ottili Core*; the decision is recorded on the package and logged through Ottili Core Audit*. Every package is therefore auditable and traceable.
Embedded in Ottili ONE
Content packages in LD3 are native to Ottili ONE:
- one login* (One Login)
- one company context* — every package belongs to exactly one company,
company_id - one audit log* (Ottili Core Audit)
- one shared platform*
This means a package always runs inside your company; every action resolves to exactly one company and is logged. LD3 reaches the same connected products as other surfaces — including Ottili AI* (AI review), Ottili Cloud* (infrastructure), Ottili Core* (approval gates, audit) and Ottili HQ* (customer/CRM). The shared platform layer is described in [Platform layer and product layer](/docs/platform-layer-and-product-layer).
Related articles
- [LD3 content automation](/docs/ld3-content)
- [Fact extraction in LD3](/docs/ld3-facts)
- [Human & AI review](/docs/ld3-reviews)
- [Publishing channels](/docs/ld3-channels)
- [Sources in LD3](/docs/ld3-sources)
- [Publishing levels](/docs/ld3-publishing-levels)
- [Understand feature-status labels](/docs/understand-feature-status-labels)
- [What is Ottili ONE?](/docs/what-is-ottili-one)
Was this article helpful?