A profile is the identity record
This article is about organisation, not the mechanics of achieving consistency in one clip. A useful character profile records the reusable identity, approved source, rights boundary and neutral traits that should survive across projects. Campaign wardrobe, location and offer belong in separate layers.
Use a naming pattern
- Brand or client code.
- Character name or role.
- Identity version.
- Reference status: neutral, campaign or retired.
- Example: AZ-Guide-v2-neutral.
Keep a neutral master
Build one approved neutral profile that is not tied to a seasonal outfit or campaign environment. Create campaign-specific prompt and wardrobe notes around it instead of overwriting the master every time. This makes rollback possible when an experimental look fails.
Store worlds separately
Use afterSora Worlds for environment, palette, tone and prohibited scene elements. A product launch, tutorial series and seasonal campaign may use the same character but different worlds. The separation prevents a location or campaign prop from becoming an accidental identity feature.
Record rights and review state
- Owner of the source material and permitted commercial use.
- Consent or verification status for real-person likeness.
- Approved markets, duration and campaign limitations where relevant.
- Last reviewer and last successful model test.
- Retirement date when a profile must no longer be used.
Link profiles to projects deliberately
Use a project for each campaign and document which profile version it uses. Do not silently replace the identity halfway through a production. If the master changes, test the new version in a separate project before adopting it across active work.
Run a quarterly cleanup
- Archive duplicates and profiles with unclear rights.
- Promote the strongest neutral reference to the master.
- Separate campaign wardrobe from identity notes.
- Retest important characters on current model routes.
- Update the prompt library with continuity language that actually worked.
