The two-week spreadsheet
A supplier says a tool will be three weeks late. Everybody can see the date move. But to find out what it costs, which milestone it hits and which risk it makes worse, somebody builds a spreadsheet over the next two weeks. By then, the decision has been made without it.
The scheduler, the cost system, the risk register and the design each hold part of the answer. None of them is connected to the others, so someone copies numbers between them by hand, and the copies go out of date.
One plan for all of it
In Superposition, each task is linked to the part it builds, and each risk to the task and the part. Earned value is measured against the same schedule the dates come from. Move a date, and the critical path and the milestones move with it.
Tasks are linked by their dependencies, with critical path, float and working calendars. You can view the plan as a board, a table or a Gantt chart. Cost is measured through control accounts, work packages and a baseline, and the ANSI/EIA-748 mapping says guideline by guideline what it does and where it falls short.
Agents propose. People decide.
Connect Claude, or any AI assistant that supports MCP, the open standard for connecting AI tools. It can read your program's plan, critical path, risks and earned value, and suggest new tasks, dates, statuses and risks. A suggestion doesn't change the plan. It waits in the Inbox with its reason until a person accepts or rejects it, and the record shows who suggested it and who decided.
Scheduling, costing and approvals never use an AI model. If you switch the assistant off, every number stays the same.
What works today
Schedule, cost, risk and change impact work today. Reading from your PLM system is in progress. The capabilities page labels each one, and the roadmap says what comes next.
We are letting companies in a few at a time. While you wait, tell us what you run. The person who reads it is the person building the product.