Inference rack — phase 1 · schedule report

Generated by TaskJuggler 3.8.4 — the source is a text file, the output is static HTML. There is no server, no login, no click-to-edit.

$ tj3 plan.tjp → plan.html · gantt.html · report.html

plan.tjp — the whole model

# dependencies are declarative: the scheduler decides dates
project rack "Inference rack — phase 1" 2026-10-26 +30d {
  timezone "Europe/Berlin"

  task power "Power & electrical" {
    task audit   "Site power audit" { effort 3d }
    task breaker "240 V breaker"   { effort 5d; depends !audit }
    task rack    "Rack, PDU"      { effort 2d; depends !breaker }
  }
  task bringup "Node bring-up" {
    task soak "GPU burn-in" { effort 4d
      depends !power.rack, !network.fw }
  }
  task sell "Sell capacity" {
    task listing "Marketplace listing" { effort 3d
      depends !bringup.bench, !paper.contract }
  }
}

What it computes that the others do not: the critical path. A1 → A2 → A3 → E1 → E2 → F1 → F2 has zero slack, so the model can answer “which task, finished today, pulls the launch date forward?” — that is a real dependency queue, not a filter.

Report · tasks in dependency order

id	task	start	end	effort	critical	depends
A · Power & electrical
A1	Site power audit + load calc	26 Oct	28 Oct	3 d	yes	—
A2	240 V breaker + circuit run	30 Oct	3 Nov	5 d	yes	A1
A3	Rack, PDU + cable management	5 Nov	6 Nov	2 d	yes	A2
B · Network
B1	Order fibre uplink (business)	27 Oct	28 Oct	2 d	no	—
B2	Firewall rules + VLAN split	31 Oct	1 Nov	2 d	no	B1
C · Cooling & room
C1	Cooling design (airflow, dB)	28 Oct	31 Oct	4 d	no	—
C2	Ducting + intake install	5 Nov	7 Nov	3 d	no	C1, A2
D · Paperwork
D1	Insurance rider + LLC docs	26 Oct	1 Nov	7 d	no	—
D2	Provider contract review	4 Nov	6 Nov	3 d	no	D1
E · Node bring-up
E1	GPU node burn-in (3× 24 h soak)	8 Nov	11 Nov	4 d	yes	A3, B2
E2	Benchmarks + listing photos	13 Nov	14 Nov	2 d	yes	E1
F · Sell capacity
F1	Marketplace listing application	16 Nov	18 Nov	3 d	yes	E2, D2
F2	First paid workload live	20 Nov	23 Nov	4 d	yes	F1

gantt.html — critical path in red, slack left blank

	October 2026						November 2026
	26	27	28	29	30	31	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19	20	21	22	23	24
A · Power & electrical
A1Site power audit + load calc critical
A2240 V breaker + circuit run critical
A3Rack, PDU + cable management critical
B · Network
B1Order fibre uplink (business)
B2Firewall rules + VLAN split
C · Cooling & room
C1Cooling design (airflow, dB)
C2Ducting + intake install
D · Paperwork
D1Insurance rider + LLC docs
D2Provider contract review
E · Node bring-up
E1GPU node burn-in (3× 24 h soak) critical
E2Benchmarks + listing photos critical
F · Sell capacity
F1Marketplace listing application critical
F2First paid workload live critical

Fit notes for this mock-up

The only tool in this comparison that actually schedules: dependencies resolve, dates propagate, and the critical path is computed rather than typed.
Output is static HTML — a report you regenerate. That means a “blockers today” page is a report definition away, and it can be served from a web root with no server process.
The cost is the input: a DSL file instead of a form. Adding one task means editing text and re-running tj3; there is no drag, no click, and no mobile UI.
For a solo operator who plans in text anyway, this is the most mathematically honest option — and pairs well with obsidian-style plain-file habits.

Stylised concept built from the project's public documentation and screenshots — not a pixel copy of the product, and not connected to any data.