Skip to content
Get started

Understand Recent Changes

After Castaly updates the Project Spec, the Project Graph marks what changed in that latest update. These markers help you check whether Castaly understood your latest request before you Build.

Recent-change markers are a review aid, not a version history. They are meant for the moment between “Castaly updated the definition” and “you decide whether to Build.”

After a Spec update

Use the markers after Castaly changes the Project definition.

After clarification

Check that your answer changed the right pages, features, or requirements.

Before Build

Confirm the latest structure before approving implementation.

After Preview feedback

When feedback is folded back into the Spec, check what Castaly changed before building again.

A marker sits to the right of a feature’s name:

New

Castaly added this feature in the latest update.

Updated

Castaly changed an existing feature this round.

Removed

Castaly removed this feature from the current structure. The row is shown temporarily so you can see what left, but it is not clickable and has no details.

A Removed row doesn’t count toward your page and feature totals or toward build progress — it’s only there to make the change visible for this round.

Change markers are separate from a node’s build state. They answer “what just changed?”, not “how far along is this?”. A feature can be New and Not started at the same time: newly added to the Spec, but not yet built.

Keep the three layers separate:

  • Change markers answer what changed in the latest Spec update.
  • Node status answers where a page or feature is in the Build.
  • Project status answers what state the whole Project is in.

For node status — Not started, Queued, Building, Testing, Succeeded, Blocked — see Read the Project Graph.

  1. Build if the changes look right

    If the right pages and features changed, continue to Build when the Project definition is ready.

  2. Continue in Chat if something is off

    If something is missing, extra, or changed in the wrong place, tell Castaly before approving implementation.

  3. Open the Spec if wording matters

    If you need exact requirements, rules, or acceptance details, open the Spec and check the source text.

Once a build succeeds, the Graph stops emphasizing the New / Updated / Removed markers for finished work, so the structure reads cleanly again. The detail can still keep a note such as Built in latest preview, so you can trace what landed.

Next: Resolve Spec Conflicts explains what to do when conflicting requirements block Build.