Context is the shared source of truth

ContextContextWhat GrowthOS knows about your company: what you do, the market you sit in, the buyers you write for, and how you sound. Held on 8 screens, and every agent reads context before it does anything., what GrowthOS knows about your company, is not documentation that sits to one side of the work. It is the input every agentAgentAn automated worker inside GrowthOS. Agents research your market, propose opportunities, write drafts, and score the pages you already have. Every agent stops at a proposal: nothing publishes and nothing moves forward until you review it and decide. (the automated workers that research, draft and score) 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 opportunitiesOpportunityA page worth writing or rewriting, proposed by an agent with the reasoning attached. Opportunities wait for your triage: accepting one is what starts production. (the pages an agent proposes writing or rewriting), vague briefsBriefThe plan for one page: the research, structure, and targeting a draft is written from. (the plans drafts are written from), 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 outright wrong.

The prose is what agents read. Not the labels, not the field names. A personaPersonaA buyer your content speaks to, and what that buyer is trying to find out. (a buyer your content speaks to) written as 3 bullet points and a job title gives an agent almost nothing to work with. The same applies to taxonomyTaxonomyYour own categories for classifying content, such as funnel stage or product line., your own categories for classifying content: 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 build and which you correct matters here, because the fix for a thin Context is different in each case.

• Yours to build. Personas, Taxonomy, Competitors and the Writing ProfileWriting profileThe compiled version of how you sound. Every draft starts from it, and it is the only place annotations become voice: pending feedback folds in when **Update profile** is clicked., the compiled version of how you sound. These are the judgement calls, and no research run produces them.
• Yours to correct. Company Overview, Ecosystem, Product & Features and Ideal Customer are drafted by agents on Foundation. When one is thin or wrong, open it, type over the wrong claim, and click Done to save. When one is wrong throughout, ask your strategistStrategistYour GrowthX contact: the person who configures your workspace, runs the parts of the product that sit outside it, and takes the corrections only you can catch. (your GrowthX contact) to regenerate it.

Correcting isn't the lesser job. Those 4 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. An AI Visibility SegmentAI Visibility SegmentA slice of your market that GrowthOS watches inside AI answer engines: where you are cited, and who is cited instead. is a slice of your market GrowthOS watches inside AI answer engines.

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

Topics is a bridge, not a voice input

Topics, the map of what your market asks about, 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 clusterClusterA group of related opportunities built around one topic, worked as a set. Deleting a cluster removes the territory itself (its topics and their questions); opportunities it already produced survive, losing only the cluster link. (a group of related opportunities worked as a set) 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 only 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.