The messaging system turns client research into a messaging map and staged copy outputs, with source workflows visible before claiming an approved homepage.
4 source stages; research, messaging map, copy and final-copy workflow exports. Source-defined stages excluding a testing variant. The populated variants/approval frontend has not been recovered.
Start with research and a messaging map
The source family contains market research, messaging-map, copy and final-copy exports. The native backend view here is the twenty-one-node messaging-map component.
Keep variants and approval on their actual evidence
The SOP describes the intended variant and approval handoff. A populated approval inbox or accepted finished homepage was not recovered, so the case does not substitute invented client records.
Inspect the workflow rather than a placeholder dashboard
The backend canvas and its standalone source explorer make the available implementation structure concrete. The original source is shown as a local import, not as proof that the client-facing approval flow is currently live.
Supporting views
About this view
21-node archived source imported locally. Inactive; no credentials or execution.
About this view
Native local source detail. Populated variants and approval frontend have not been recovered.