Product Surfaces

Vision Map

Map company vision as a top-down tree, then attach reality, milestones, tasks, and evidence to each branch.

What Vision Map is

Vision Map is the founder-facing source of truth for what the company is supposed to become.

It is not another health dashboard. Analytics tells you whether the company is healthy. Vision Map tells you whether the work being done is still attached to the founder's intent.

Use it to lay out the company as a top-down tree:

Company vision at the root.
Product, operational, collaboration, compliance, and venture goals underneath.
Reality notes beside the desired vision.
Milestones and optional deadlines where timing matters.
Board task links and evidence where work proves progress.

Why it exists

Pulse is meant to make concurrent ventures real. A founder should be able to set up a company, leave it running, and return because they are excited to see progress, not because they had to babysit execution.

Vision Map gives agents a shared target. Instead of doing plausible work in isolation, agents can connect tasks, evidence, and reviews back to the specific part of the company vision they advanced.

Core workflow

Open Vision Map from the Pulse navigation. It sits immediately beside Workforce because both surfaces use the same canvas-style thinking: the company is represented as connected nodes, not as a flat table.
Use the plus handle on a node to create a child branch directly on the canvas.
Type into the new node immediately. Draft nodes show type anything, and your first text replaces the placeholder.
Use the selected-node controls to add a child, sibling, parent, milestone, open details, or delete the selected branch without leaving the map.
Open details when you need to edit type, reality state, vision text, reality notes, task IDs, evidence, and milestones.
Use milestones for optional deadlines or required-by-date commitments.
Link board tasks to the node they advance.
Use evidence links or notes to capture proof that reality is catching up to the vision.

Node types

Vision Map supports these node types:

company: the root company or venture.
feature: product capability or user-facing functionality.
operational: operating model, quality, cost, or execution goal.
collaboration: partnership, ecosystem, or model-provider strategy.
compliance: legal, privacy, security, or trust requirement.
venture: a company, workspace, family workspace, or major business line.
milestone: a dated or staged outcome.

Reality states

Each node has a reality state:

empty: vision exists, but reality has not started.
partial: some foundation exists, but the branch is not fully true.
in-progress: active work is moving this branch forward.
done: current reality satisfies the node.

Import and export

Vision Map stores its canonical data in .pulse/vision-map.json.

Use export when you want to review, back up, or migrate a company vision. Use import when you want to replace the current map with a prepared JSON structure.

Source data model

Each node stores:

id, parentId, title, type, and order for the tree.
vision, reality, and realityNotes for vision-versus-reality tracking.
taskIds and taskLinks for board work tied to the branch.
evidence for proof, reviews, checks, or deliverables.
milestones for staged outcomes.
deadline for an optional target date.
requiredBy for required-by-date commitments.

taskIds is the current UI editing field. taskLinks is kept as a compatibility alias so agents and future surfaces can use the clearer name without losing the existing contract.

Agent access through MCP

Pulse agents can use Vision Map through MCP tools:

vision_map_get
vision_map_node_create
vision_map_node_update
vision_map_node_delete
vision_map_node_move
vision_map_seed_company
vision_map_export
vision_map_import
vision_map_validate
vision_map_task_link

That means agents can inspect the company vision before creating work, link tasks to the right branch, and validate that the map still has the required structure.

Seeding is intentionally agent-driven. The Seed with agent action does not blindly reset the map with canned content; it dispatches an agent to draft or refine a company-specific vision from workspace context.