Company Identity
The editable identity files every agent writes from — company profile, positioning, voice, terminology, and brand kit, one Markdown file per section.
Company Identity (the Identity item in the sidebar) is where you make the
platform write as your company. Every section is one Markdown file under
documents/identity/ in your workspace, and those files are the identity
source of truth the generating pipelines read — briefings, newsletters,
product covers, video briefs, social drafts, and support email all inherit
their facts, voice, and visual rules from here. Edit a section once and every
agent that writes for you picks it up on its next run.
The product ships with a generic starter in every section. Making it yours is an editing session, not a configuration project: open each section, replace the placeholder facts with your own, save.
The layout
A left rail lists an Overview plus nine sections in two groups; the right pane is a full Markdown editor for the selected section — the same engine as the strategic files: rendered Read mode, a raw Edit mode, Ctrl/⌘+S to save, a stale bar if the file changes on disk while open, and a guard against navigating away with unsaved edits.
Identity — the sections you customize
| Section | What goes in it |
|---|---|
| Company Profile | Legal facts, mission, founding principle, core values, operating model |
| Positioning & Messaging | Differentiation, value propositions, key messages |
| Audiences & Personas | Customer, reader, and buyer personas — plus the email persona replies are written as |
| Brand Voice & Tone | Voice attributes, tone dials, register, exemplars |
| Terminology & Content Rules | The do/don't lexicon, naming standards, what may be disclosed where |
| Visual Identity | Brand colors, typography, logos, music — the brand kit, with a dedicated visual pane |
| Localization (DE/EN) | Language-specific terminology, formality, and content rules |
System — pointer pages
Two further pages index deeper doctrine rather than duplicating it: the Operator-Tool Voice page (how the product's own interface copy speaks) and the AI Writing System page (the writing-quality system agents apply). Both point into the shipped doctrine files on your disk — they are tables of contents, not forks, so the doctrine stays a single source of truth.
The flows
- Edit a section. Select it in the rail, switch to Edit, write, Ctrl/⌘+S. Switching sections with unsaved edits prompts before discarding.
- Open the folder. The rail header's Open folder reveals
documents/identity/in your OS file manager. Because the files live in the documents tree, agents read them directly, external edits reload live, and the folder travels with your workspace. - Reset one section. Each section's Reset returns it to the generic starter. Your current file is moved to the OS trash — recoverable, never deleted in place.
- Restore all defaults. The rail-level Restore resets every section the same way, with the same trash-recoverable safety.
Working with it well
- Start with Profile, Voice, and Terminology. Those three shape the most output; the rest refine it.
- Be concrete. Agents follow exemplars and explicit rules far better than adjectives — the starter files show the intended density.
- Treat it as living. When generated output misses your voice, the fix is usually one edit here rather than re-prompting every pipeline.
Related pages
- Your workspace & documents — why identity is files, and where they live
- Doctrine — the protocol corpus the pointer pages index
- The operator model — editing files as the way you steer agents