This canvas keeps only the adopted campaign direction: audience, route, visual system, schedule, operations, team ownership, and deliverables are arranged as editable nodes before they become a document and event site.
Fictional Minora example. Hoshinogawa Summer Night Fireworks Festival is not a real event.
Governed Canvas runtime
A radial campaign map, ready to become docs and a site.
The center holds the event premise. Branches keep decisions close to the outcome they affect, so the campaign can move from conversation to structured output without carrying unused ideas forward.
Drag nodesConnect branchesPan and zoomEdit textHand off to Docs
Core idea
Hoshinogawa Summer Night Fireworks
A fictional riverside summer evening built around lanterns, a slow walk from town to water, food stalls, and a clear 20:00 fireworks moment.
Planner: Aiko Morita
Goal: turn an atmosphere into a complete campaign
Outputs: Canvas, planning doc, event site
01 / World
A believable fictional town
Define the world before writing copy or choosing images.
Town: Hoshinogawa
Tone: lanterns, river wind, black night sky
Rule: always disclose the event is fictional
02 / Audience
Design for three visitor groups
Put needs on the canvas so the final site does not become only a poster.
Families: safety, restrooms, clear exits
Rail travelers: walking time and return route
Design readers: a collectible visual identity
03 / Route
One riverside path
The event site can reuse this path directly instead of inventing a new structure.
Station arrival
Lantern street and food stalls
River viewing lawn and exit split
04 / Visual system
Images the site must generate
Each visual branch can become a hero, section image, or social crop.
Fireworks reflected on water
Food stalls and warm lanterns
A simplified fictional venue map
05 / Operations
Time, safety, and weather decisions
Practical information enters the mind map early, so the public site stays useful.
17:00 open / 18:00 stalls / 20:00 fireworks
Six guide points, two first-aid/lost-child desks
Weather decision at 15:00
06 / Team
Named owners, not vague roles
The same names appear in the planning document so the example feels operational.
Aiko Morita: campaign lead
Ren Sato: site operations
Sho Nakamura: safety
Emily Chen: web production
07 / Handoff
Turn the map into production content
Confirmed branches become the document and event site. Unused ideas stay out of the final plan.
Docs: schedule, staffing, risks, asset list
Site: story, access, program, safety, disclaimer
Review: Aiko Morita approves the direction
Decision record
Adopted scope only
The board keeps confirmed choices and removes backup ideas before they become public content.
This becomes the event-site access and program section.
16:45 station arrival and lantern signs
18:00 stalls open near the river walk
19:30 viewing lawn guidance starts
20:20 split exit route after fireworks
Production checklist
Images and copy to produce
Every asset is tied to a concrete page location, not an unused mood idea.
Hero: fireworks over the Hoshinogawa river
Story: quiet lantern street before dusk
Food: yatai detail image
Access: fictional venue map
Risk rule
What must be stated clearly
These rules prevent the example from reading like a real public announcement.
Weather note is fictional and non-operational
No real train, police, or emergency claims
Disclaimer appears in hero and footer
Docs handoff
Planning document sections
The next page should read like a campaign brief with exact owners and work items.
Objective, audience, route, and visual system
Staff roster with Aiko Morita as planner
Timeline, risks, asset list, review checklist
How this canvas is used
The map keeps planning decisions visible.
Instead of writing a long prompt and hoping the result stays coherent, the canvas gives each decision a place and a relationship. That makes the next pages easier to inspect and revise.
01
Start from the event premise
The center node defines the fictional event, planner, goal, and output scope.
02
Branch into decisions
Audience, route, visuals, operations, and team ownership are separate nodes with semantic connectors.
03
Produce only the adopted plan
The document and event site inherit the accepted structure, so discarded ideas do not become noise.
Next
Now turn the map into a detailed planning document.
MinoraBeta