Castaly can only build reliably when the Spec points to one clear product definition.
Resolve Spec Conflicts
Castaly builds from the Project Spec. Before implementation starts, it checks whether the Spec contradicts itself. If it finds a conflict, Build stops before code changes and Castaly asks you to clarify the right direction.
This is not a failure state. It is a safety check that keeps Castaly from building against requirements that disagree with each other.
Why Spec conflicts matter
Section titled “Why Spec conflicts matter”When possible, Castaly stops before implementation starts, so nothing half-built is left behind.
Castaly explains the conflict and offers suggested resolutions so you usually only need to choose or clarify.
Resolving a conflict updates the Spec and Graph, but Build still waits for you to press Build again.
When conflict check happens
Section titled “When conflict check happens”You press Build
Build starts with a check against the current Project Spec, not code generation.
Castaly checks the Spec
Castaly looks for requirements that contradict each other, such as two sections describing different login rules.
Conflicts block Build if found
If conflicts exist, the Project enters Build blocked and Castaly shows a Conflict Card in Chat.
A clean Spec continues to Build Plan
If no conflicts are found, Castaly generates the Build Plan for you to review and accept.
If Castaly discovers a Spec conflict while a Build is already running, it uses the same resolution flow: the Project becomes Build blocked, Chat becomes available again, and the affected Graph nodes show Blocked.
What a conflict looks like
Section titled “What a conflict looks like”A Conflict Card appears in Chat with the title Build is blocked by spec conflicts. One card can contain one or more conflicts.
A short name for the contradiction Castaly found.
A plain-language summary of why the requirements disagree.
Three AI-suggested options, labeled A, B, and C.
A field for your own resolution when none of the suggested options is quite right.
An expandable source list showing the Spec files and line references that created the conflict.
The card header shows how many conflicts have been answered, such as 1 / 3 answered.
When there are only one or two conflicts, they are expanded by default. With three or more, Castaly opens the first one and keeps the others collapsed so the card stays readable.
How to resolve conflicts
Section titled “How to resolve conflicts”Read the explanation
Start with the conflict title and short explanation to understand what Castaly needs you to decide.
View sources if needed
Open View sources when you want to see the Spec files and lines behind the conflict.
Choose or write a resolution
Pick A, B, or C, or write a Custom answer if you want a different rule.
Resolve every conflict item
Each conflict needs an answer before Apply resolutions becomes available.
Apply the resolutions
Click Apply resolutions to let Castaly update the Spec and Graph from your choices.
You can also use Use recommended answers to select Castaly’s recommended option for each open conflict. It only selects the answers; it does not apply them until you confirm.
Keep editing instead
Section titled “Keep editing instead”Use Keep editing when you are not ready to apply the full card.
- If you answered some conflicts, Castaly applies those selected resolutions and returns you to Chat.
- If you have not answered anything, Castaly simply returns you to Chat so you can clarify in your own words.
- The card becomes part of the Chat history, so its state is preserved when you return later.
What happens after applying resolutions
Section titled “What happens after applying resolutions”Castaly updates the Spec
Your selected or custom answers are written into the Project Spec.
The Graph updates
Affected Graph nodes update from the revised Spec, and resolved conflict state is reflected in the workspace.
The Conflict Card is saved
The card stays in Chat history and shows the final answers you applied.
You press Build again
Castaly does not automatically restart Build. Press Build again when the updated Spec and Graph look right.
How it appears in the workspace
Section titled “How it appears in the workspace”| Surface | What you see |
|---|---|
| Project status | Build blocked |
| Chat | A Conflict Card titled Build is blocked by spec conflicts |
| Graph | Affected nodes show Blocked |
| Build Plan | Not generated until the Spec conflict check passes |
What Spec conflict is not
Section titled “What Spec conflict is not”Build failed means implementation, tests, or deployment broke after execution started.
Preview failed means Castaly could not prepare the running preview.
Configuration required means a runtime secret is missing. It does not block Build or Preview.
A Spec conflict is a requirements problem. Castaly needs a clearer definition before it can safely build.
Next: Start a Build explains how a clean Spec becomes a Build Plan.