Revisions

Rerun any artifact node with reviewer feedback.

When you review a run's output and want to change a specific artifact, you don't have to rerun the whole pipeline. Revisions let you target a single node — a stakeholder, a requirement, a trade study — and have it re-generated with your feedback as additional context.

How to revise

From the in-browser explorer on the run's Complete page:

  1. Click on the artifact node you want to revise
  2. Click Revise in the side panel
  3. Type your feedback in plain English ("This requirement is too vague; specify the latency target", "Stakeholder is wrong; replace with FAA", etc.)
  4. Click Rerun with feedback

The pipeline regenerates that node (and any downstream nodes that depend on it), preserving everything else unchanged.

What gets re-generated

When you revise a node, the pipeline:

  1. Re-runs the stage that produced that node, with your feedback threaded into the prompt
  2. Re-runs downstream stages on the modified subgraph (e.g., revising a stakeholder triggers re-running affected NGOs, requirements, decomposition allocations)
  3. Leaves untouched anything not affected

The resulting bundle is a new run, with a parent reference back to the original.

Cost

WARNING
Revisions consume CU. The cost depends on how much of the pipeline needs to re-execute. Revising a phase-gate assessment is cheap (< 5 CU); revising a stakeholder can cascade through every downstream stage and approach the cost of a full run.

The estimate is shown before you confirm.

When to use revisions vs a full rerun

Use revisions when:

  • A specific output is wrong but the rest is good
  • You forgot to include something in your original Brief that affects only part of the design
  • A trade study weighted the wrong criterion

Use a full rerun when:

  • The Brief itself needs material changes
  • The pipeline output diverged broadly from your intent
  • You want to try a different configuration (phase, sensitivity, verifier judges)

Revision history

Every revision is tracked. From the run's status page, you can see:

  • The original run
  • Every revision applied to it
  • The diff between successive versions for each affected node

This is the full audit trail — useful for review meetings or when you need to justify a final artifact set to a customer.

Next

Chat with your project →