Superposition one plan, from requirement to decision Request access

The operating system for engineering teams and agents

Requirements, architecture, schedule, cost, risk and change in one plan. Agents draft changes, people sign off, and every number shows how it was worked out.

Request early access See what it does

We are letting companies in a few at a time. When your turn comes, you get ninety days free with every module. Read why we're building it.

The coffee maker program as a Gantt chart: the design gates across the top, the critical chain running through the moulding tool, and late work marked in red.

One plan, from requirement to decision

A change to a requirement affects the schedule, the budget and the risks. Here they share one plan, so nobody copies numbers between tools to see the effect.

Design

Requirements and architecture

Each requirement lists the parts that meet it, in a table and a diagram, saved as a standard SysML v2 model. Link tasks and risks to the same parts, and you can see what each one is for.

Working Requirements, the architecture diagram, and linking requirements to parts. Next Linking risks to requirements.

Learn more
The coffee maker's six requirements, each with its statement and what satisfies it, the whole appliance in every row, with three satisfied and three not yet checked.

Schedule

Critical path from real dependencies

Link tasks by their dependencies and see the critical path and float. View the plan as a board, a table or a Gantt chart, and see what is left before each milestone.

Shipping

Learn more
Four design gates with progress against each, and a warning that the preliminary design review passed with one task outstanding.

Cost

Earned value from the same plan

Set up control accounts, work packages and a baseline, and measure earned value at the reporting date. Cost and dates come from the same schedule, so there are no two exports to reconcile.

Shipping

See the EVMS mapping
Earned value at the reporting date: schedule performance 0.76, cost performance 0.90, with planned, earned and actual cost against the budget.

Risk

Risks priced in money and days

Each risk has a cost and a delay in days, and the total is compared with your management reserve. A Monte Carlo simulation of the real schedule gives P50 to P90 finish dates.

Working The risk register, total exposure and the Monte Carlo. Next Risk exposure in the estimate at completion.

Learn more
Open risks as dots, placed by likelihood and consequence. Below them, the three risks beyond the program's appetite, each with the reason.

Agents

Agents propose. People decide.

Connect Claude, or any AI assistant that supports MCP, the open standard for connecting AI tools. It reads the schedule, risks and earned value and suggests changes with a reason, and a person accepts or rejects each one.

Shipping Reading the plan, suggesting changes, and a record of each decision. Planned Agents you set to run on a schedule, within rules you choose.

Learn more
The Inbox, holding a new status, a new risk and a new task proposed by @superposition, each with its reason and Accept and Reject buttons.

A part's work, float and milestones

Pick a part to see the work done, in progress and not started, and the float and milestones it affects. A new cost baseline needs a reason and an approver, and the old baseline is kept.

Shipping Work, float, milestones and baselines. Next Impact traced from a requirement, with its cost and the risks it changes.

Learn more

Bring the plan you already have

Import your current schedule and requirements instead of starting over. Each connector moves data in one direction, so the same data is never synced both ways.

Available today

  • Primavera P6 schedules (XER), with their dependencies
  • Microsoft Project schedules (XML), with their dependencies
  • Requirements from IBM DOORS over ReqIF, the standard requirements exchange format, from the command line

In progress and next

  • Teamcenter and Windchill over OSLC
  • Jama Connect over ReqIF, and ReqIF in the browser
  • Microsoft Planner
  • CSV task lists

Planned

  • Excel workbooks and Jira issues
  • SysML v2 models over the standard Systems Modeling API
  • Earned value history from other EVM tools, as IPMDAR cost reports
  • Actuals and rates from Deltek Costpoint, SAP and NetSuite

What each role gets

For program managers

Critical path, earned value and risk exposure come from one plan, so the numbers already agree before the review. The product is mapped to all 32 EVMS guidelines, but not certified.

Read the EVMS mapping

For systems engineering leads

Requirements and architecture live in the same plan as the schedule. Pick a part and see the tasks, float and milestones that depend on it.

Learn more

For chief engineers

See what a change affects before anyone approves it. A baseline changes only with a reason and an approver, and every decision records who made it and when.

What the record keeps

For CTOs and CIOs

Keep your current tools and the AI assistant you already trust. It can suggest changes but not make them, and no AI works out your dates, costs or approvals.

How we handle your data

Built for the audit

Inside your network

You can deploy it inside your own network. Editing, approving and exporting make no connection outside it, and a test checks that on every build.

How we handle your data

Mapped to ANSI/EIA-748

We list all 32 EVMS guidelines, what the product does for each, and where it falls short. Mapped, not certified.

Read the mapping

History that is never rewritten

Every change is added to the history, and nothing is overwritten. To reverse a decision, you record a new one with a reason.

What the record keeps

Certifications we don't hold yet

We don't hold SOC 2, ISO 27001, FedRAMP or CMMC yet. Ask us where each one stands.

Ask us

Join the waiting list

We let companies in a few at a time. When your turn comes, you get ninety days free with every module.

Request early access Talk to us