Tapeo

Using the workspace

Change files and rerun

Edit a file a stage used, rerun only what is affected, review what the AI changed, and go back if needed.

Each tab has one job. Code is your design. Workflow builds it: every tool run, every result, and the signoff checklist, with Setup for the process, running a single tool, and the files tools need. Goals tells you whether the design does what it must.

Change something after a run#

  1. 1
    Find the file
    Select a stage on the Workflow map. Inputs used and Outputs list each file with who last changed it: You, AI, or Tool. Click a file name to open it in Code.
  2. 2
    Edit it
    Your edit is saved automatically and protects the file: automatic AI repairs will only suggest changes to it, never apply them. Use the lock button in a stage panel, or Protect from AI in Code, to change this.
  3. 3
    Rerun
    • Workflow shows a banner such as “You changed constraints/top.sdc after Pre-route timing ran” with Run from Pre-route timing.
    • In any stage panel: Run this stage (one stage) or Run from here → (that stage and every later one).
    • Goals measured by the rerun stages get new results automatically, so Goals stays up to date; your goal list is never changed.
    • Tick Let the Architect repair failures if you want automatic repairs of unprotected files.
  4. 4
    Review what the AI changed
    The run report lists files the Architect changed, with View change and Revert, and suggested changes to protected files, with Review and Decide in chat: the run leaves them, and a failed formal proof, in the Architect chat as a card to apply or fix.
  5. 5
    Go back if needed
    Project history (Workflow header, or the history icon above the file tree) lists checkpoints by You, the Architect, or Tool, shows what each changed, and restores a file to its earlier or later content. Your edits get their own checkpoint when a workflow run starts.
  6. 6
    Check your goals
    Goals already shows the results from your rerun. A result is marked stale only when one of its inputs changed and no rerun stage measured it; rerun that stage, or use Verify in Goals. If place and route fails, the run skips ERC and LVS instead of checking the earlier layout, and those results are marked out of date.