Conventions

Set shared instructions for how Dawn prepares and presents work.

Conventions are reusable instructions for the agent. Use them for consistent naming, presentation, and working practices across your organisation.

Open Context → Conventions to review existing instructions and add or edit a convention using the available controls.

​

Write an instruction people can check

Too vague	More useful
Make good charts	Label every chart with its units and reporting period.
Clean the data	Report duplicate keys and missing required values before proposing a cleaning rule.
Use our naming convention	Use lowercase snake_case for newly created prepared datasets.
Be concise	Start executive reports with the three most significant changes and supporting figures.

State where the convention applies and any exceptions. Keep one clear instruction per entry where practical.

​

Put business definitions in the right place

Use Catalogue for a metric’s calculation and Data for the location and relationships of source data. Use a convention to say how the agent should work with those definitions, such as “state the metric definition used in each report.” See context types.

​

Check the effect

After saving a convention, try a relevant task and inspect the output. If Dawn does not follow it, check that the wording is specific and that another instruction does not conflict.

Conventions guide agent behaviour. They do not enforce permissions or guarantee that every generated asset satisfies the instruction. Review consequential outputs and use actual access controls for restrictions on data or actions.