Every component is a vertical tree — goal, objectives, activities — with a budget bubble on each objective that rolls up to the component and the plan. The trees are wired to each other: hover or click any node and the connections light up in every direction, across all four.
Every objective carries its own budget bubble; those add up to each component, and the components add up to the plan. Amounts are working estimates — open any bubble to add, change or remove lines and this table follows. Component 3 lines are per town hall; the calendar schedules three.
Each column is one component. Read down for depth — goal, then objectives, then the activities under each, then what it costs. Read across for dependency — the lines show what feeds what, and every line works in both directions.
Move over any node and its connections appear, with a label saying why they are connected.
Click a node to keep its connections lit and open the connections panel. Click a connection to jump to the other end.
Each objective has a budget bubble. Open it to add or remove line items; the component total and plan total move with it.
Every component has a point of contact. Any cell — component, objective or activity — can carry demographics (who it reaches) and entities (partners, venues, officials) through its pop-up form.
Each tree ends with an Ideas section. Add a thought in one line, move it through New → Under review → Adopted, or park it.
Click any status pill to cycle it. Edits are saved on this device — export them as JSON to keep a copy or fold them into data.js.
The rule from the planning conversation: if a step can't be done with a phone call and a follow-up, it is too heavy for this stage.