Getting started

A 5-minute orientation to the parts of Topolog: the graph, the scheduler, the day view. After this you'll know exactly how to drive the product.

1. Pick a mode

Topolog has three paths to a plan, all arriving at the same dependency graph and scheduler.

• Express: type a single sentence, get a multi-level plan in ~5 minutes. Best for one-off goals.
• Structured: AI breaks the goal into milestones; each breakdown into child nodes (up to seven) asks a few questions. Sign off level by level and drill in on demand. Best for complex, long-running goals.
• Manual: build the graph yourself. Click empty canvas to add a node, drag from one node onto another to connect them, click a node or edge to edit it, press Delete to remove it, or author the plan directly in TOL. No AI, no credits.

2. Edit in the IDE

AI proposes structure; you sign off. The /plan/build IDE has a Graph tab and a Source tab. On the graph: click empty canvas to add a node, drag from one node onto another to draw an edge, click a node or edge to edit it in the inspector pane, press Delete (or the Delete button) to remove the selection, and hit Arrange to re-tidy the layout. Or drop into the Source tab and author the plan as a TOL document. Cycles at the task level are auto-rejected, and every edit is undoable.

3. Set your availability

On the Execute tab, paint blocks onto the weekly grid: sleep blocks are anchors, available blocks are what the scheduler can use. Or choose a preset: Standard, Early Bird, Night Owl.

4. Build the schedule

Once every leaf is an atomic task with an estimate, the scheduler unlocks. It topologically sorts your tasks and packs them into your real calendar windows. Day, Week, and Month views all read from the same blocks.

5. Execute

The Execute Day view shows whatever the scheduler bin-packed for today, ordered by dependency and your availability. Mark things done as you finish them; the graph turns nodes green and the rest of the schedule rebalances.

Where to go next

Once you’ve walked through the five steps above, the rest of the docs are reference. Read them in any order:

• The dependency graph: the node primitives, status propagation, cycle rejection.
• The TOL language: the grammar that backs every plan, with a small canonical example.
• The scheduler: how the graph becomes a calendar.
• The analytical panels: Critical Path, Spectrum, Causal Threads & Parallelism, Money, and Pareto (how budget allocation trades off against your odds of success). Each panel has its own docs page.