Writing a brief the engine can ground

Give it the question, not the topic

The brief is the single field that decides whether you get something useful. A good brief works like the instructions you would hand a freelance writer you will never meet: tell them the exact question to answer or the claim to make, because anything you leave vague they will fill with something generic. Ask for "a report" and you get a generic report. Ask for "a board update that explains why Q3 spend rose 40 percent and what it bought" and you get the document you actually had in mind.

The context filter decides what it reads

Below the brief is a context filter with six settings: Full audit, Brand, Research, Strategy, Performance, and Creative. This is where you tell the engine which project facts to pull in before it writes. A positioning document wants Brand and Strategy. A performance report wants Performance. Full audit lets it read everything you have. Narrow it when you want the document to stay on one subject and not wander.

Grounding and live web research

Leave "Use this project's details" on and the engine reads your brand, research, and strategy first, so the writing comes out in your voice and uses your real numbers. Separately, a Live web research toggle runs a search pass before writing and cites the source URLs inline. Turn it on for anything that leans on outside facts, like a market scan. Leave it off when the document should reflect only what the project already knows.

Tone, length, and the extras

The same form carries tone, audience, length, an optional executive summary, and a citations switch. They all have sensible defaults, so you can ignore them and still get a complete document. Reach for them when the output has to match a house style or land on a fixed length.