Product truth
Product truth answers one question: what is this project allowed to say it does?
It is derived, never authored. There is no form to fill in and no list to maintain, because a fact you can type is a fact nobody checked. Everything in it happened.
What it is made of
Section titled “What it is made of”Open the marketing home for a project and choose the product truth view.
| Source | What lands in the pack |
|---|---|
| Shipped work | Every task in the project that reached done, newest first, with its description |
| Meeting summaries | The running summary of each recent meeting on the project |
| Project intent | The objectives, functional requirements, and agreed scope from the project’s intent model |
| Repositories | The repositories connected to the project, by name |
How truth constrains a claim
Section titled “How truth constrains a claim”Two things read this pack.
Agents, before they write. The drafting step of a workflow digests product truth first, so an agent asked to announce the launch already knows what shipped and does not have to be briefed.
The brand-safety lint, before anything publishes. The lint runs a deterministic pass over your profile’s banned phrases and prohibited claims, which is a hard gate at every autonomy level, and a judgment pass that flags capability claims which do not trace back to a product-truth item. Findings from the judgment pass are warnings attached to the publish for you to decide on, not blocks.
So the honest summary is this: product truth is what makes “announce what we shipped” answerable without a briefing, and it is what a reviewer checks an unexpected claim against.
Keep it current
Section titled “Keep it current”The pack is cached briefly and reassembled on the next read after it expires, so a task you finish now is quotable within minutes. The timestamp under the list says when the version on screen was read.
Market from the project that builds the thing
Section titled “Market from the project that builds the thing”Because the pack is assembled per project, its contents depend on which project you market from.
Alpenglow Labs splits its work: Summitline App builds the product and Summitline Launch carries the launch. Product truth for the App project is thirteen shipped features and a repository. Product truth for the Launch project is the launch chores that shipped, which is honest but is not what a hiker wants to read about.
The practical rule: keep the marketing on the project whose shipped work you want to talk about. A separate launch project is a fine place for launch tasks, and a poor place to ask an agent what the product does.
Next steps
Section titled “Next steps”- Work with content assets: what a grounded draft becomes.
- Constraints and agent guidance: the other half of the lint, in your profile.
- Set the project’s intent: one of the four sources.