aswritten.ai · public perspective

PerspectiveDecision Rebrand 2025 › MigrationPlan Rebrand

MigrationPlan Rebrand

5 nodes in this area of the perspective

This hub gathers the coordinated action items for a single rebrand migration to aswritten.ai. The unifying through-line is terminology: across surfaces the plan [replaces storyBASE/witness terms with canonical aswritten.ai language] (MigrationAction_UpdateDocs). The actions fan out by surface — [system prompts and agent instructions] (MigrationAction_UpdatePrompts), [CLI command names] (MigrationAction_UpdateCLI) (e.g. 'remember', 'draft'), [all documentation] (MigrationAction_UpdateDocs), and the [README and public landing page] (MigrationAction_UpdateReadme) carrying new brand positioning — plus an outward step to [communicate the rebrand to users and stakeholders] (MigrationAction_AnnounceRebrand). No dates or sequencing are attached to any child, so the plan reads as a parallel checklist rather than an ordered rollout. All five are framed as terminology/identity alignment work; none records dissent, blockers, or a chosen ordering. If a query concerns rebrand mechanics, scope, or naming choices, support plausibly lives here; if it concerns timeline, rollback, or rationale for the rename, that is not present in these children.

Witness phrases

verbatim
Replace storyBASE/witness terminology with aswritten.ai canonical terms
verbatim
Align command names with new terminology (e.g., 'remember', 'draft')
verbatim
Embed new terminology in system prompts and agent instructions
verbatim
Reflect new brand identity and positioning in public-facing materials
verbatim
Communicate rebrand to users and stakeholders
verbatim
CLI renaming is the only action that changes user-invokable behavior (command names like 'remember'/'draft'), not just descriptive text — a behavior-affecting outlier among otherwise terminology-swap tasks.
verbatim
Announcing the rebrand is the sole outward, communications-facing step; the other four are internal technical/content edits.
verbatim
No child carries dates, ordering, or dependencies, so whether announcement precedes or follows the surface changes is left open rather than concluded.