How Brand memory affects creation
What changes in the projects you create after Brand memory is set up, and why projects you already made keep the look they were created with.
Once Brand memory is set up, Layerpath consults it every time it generates. This page explains what that changes in each creation path, and why the projects you already made stay as they are.
What each creation path uses
Both creation paths read Brand memory. What differs is which parts of the project each one generates.
| Path | What Brand memory shapes |
|---|---|
| Create a project with Agent | Titles and body copy in the plan Layerpath drafts from your prompt, then the callouts, step titles, connecting prose, and voiceover script generated as the tour is built out |
| Record your screen | The callouts on each step, the step titles, the connecting prose, and the voiceover script written after Layerpath analyzes your recording |
Both paths also take your visual identity, so the colors, logo, and fonts are applied to the project as it is created.
Your voice varies by situation
Brand memory does not hold one single writing style. It holds several, and the one Layerpath uses depends on what the project is for.
The project category, such as a product walkthrough, a sales demo, customer onboarding, or internal training, selects which part of your voice applies. The same Brand memory produces a different register for a sales demo than for internal training, which is what the Position and Enable cards on the Voice tab describe.
What Brand memory does not do
- It does not rewrite projects you already created.
- It does not change voiceover audio that has already been generated. Existing audio is a finished file.
- It is not used at all until you choose Use brand voice on the Voice tab. Before that, generation runs on Layerpath's defaults.
- It guides generation. It does not guarantee that every generated element follows it, which is why reviewing the result in the editor still matters.
Why projects you already made do not change
When Layerpath creates a project, it records your visual identity as it stands at that moment and keeps that record with the project. The project renders from its own copy afterwards, in the editor, in the player, on a shared link, and in an exported video.
Setting up Brand memory later, or changing it, does not reach back into that copy.
So if you create two projects and then set up Brand memory:
| Project | How it looks |
|---|---|
| The two you created first | Layerpath's default branding, unchanged |
| Everything you create afterwards | Your own brand |
This is deliberate. Finished work that has been shared with customers stays as it was when you shared it.
The watermark is the exception
The watermark setting follows your workspace as it stands now rather than being recorded with each project. Turning the watermark off removes it from projects you already created as well as new ones.
Language and voiceover voice settings behave the same way. A billing entitlement or a workspace-wide preference should not be frozen into work you already finished.
Check the result
Brand memory changes what Layerpath generates, so review these in the editor before sharing:
- Step titles and callout wording read the way your company writes.
- Preferred words from Language rules are used, and words you asked Layerpath to avoid are absent.
- The voiceover script matches your intended register for this kind of project.
- Colors, logo, and fonts are the ones you set on the Identity tab.
- The register suits the audience, whether you are positioning to a prospect or guiding an existing user.
When wording is wrong across several projects rather than in one place, correct the voice itself on Review your brand voice instead of editing each project.