Context is the shared source of truth

Every agent in GrowthOS starts from Context. A vague Company Overview produces vague opportunities, vague briefs and generic drafts.

Context is not documentation about your company that sits to one side of the work. It is the input every other agent starts from.

That is the whole reason it exists as its own area rather than a settings page, and the reason a thin Context is expensive in ways that are hard to trace back.

Vague in, vague out

A vague Company Overview produces vague opportunities, vague briefs, and drafts that could describe any vendor in your category.

The damage is diffuse. Nothing breaks visibly. You get content that competes on the wrong axis, which is much harder to notice than content that is simply wrong.

The prose is what agents read. Not the labels, not the field names. A persona written as three bullet points and a job title gives an agent almost nothing to work with. The same applies to taxonomy: agents classify against the description rather than the name, so a category called "Funnel Stage" with a thin description produces tagging that looks plausible and sorts badly. Write them as if briefing a new hire.

Two kinds of Context surface

Which surfaces you write and which you read matters here, because the fix for a thin Context is different in each case.

Yours to write. Personas, Taxonomy, Competitors and the Writing Profile. These are the judgement calls, and no research run produces them.
Yours to review. Company Overview, Product Features, Ecosystem Map and ICP are agent-generated and read-only in your workspace. When one is thin or wrong, tell your GrowthX team; they make the change.

Reviewing isn't the lesser job. Those four are the documents everything else reads from, so a correction there is worth more than any single page edit.

Personas and AI Visibility Segments are not the same thing

This is the distinction most worth holding onto, because the two sit next to each other in the sidebar and do unrelated jobs.

	Personas	AI Visibility Segments
What it is	A person you write for	A slice of the market you want to be cited in
What it shapes	Angle, depth, vocabulary	Nothing about the draft
Can you tag work to it	Yes	No

Conflating them produces content aimed at a query pattern rather than a reader.

Topics is a bridge, not a voice input

Topics feeds Page Creation. It has nothing to do with how you sound; that is the Writing Profile.

It sits in Context because it is part of the model of your market, not because it shapes drafts. It is also the layer strategic territories are built on: a cluster owns topics, and a topic's questions are what its coverage is measured against.

Taxonomy is the axis nobody else can give you

Health, Quality and momentum are computed. Funnel stage, product line and industry are judgement calls about your business.

Taxonomy is where that judgement gets recorded so it can be used at scale. No amount of research produces it, which is why it is worth the time it costs.

Competitors works the same way. The roster shapes reports, gap analysis, and the framing of opportunities, not just comparison pages. Research answers "who ranks near you"; only you can answer "who shows up in deals".

Where this shows up

Every screen under Context & voice is an input to this. Foundation is the one to get right first, because the rest read from it.