A product direction you keep moving forward. Each Project has its own Chat, Spec, Graph, Preview, and Project Versions.
How Castaly Works
Castaly turns product intent into a controlled build loop. Chat captures what you want, the Spec becomes the source of truth, the Graph makes that structure visible, and Build keeps code changes deliberate.
The working model
Section titled “The working model”You start in Chat
Describe the product, change, or question in plain language. You can also add screenshots, documents, or references when they help explain the intent.
Castaly forms an understanding
Castaly interprets the request, asks clarifying questions when needed, and turns rough input into a structured view of goals, pages, flows, and features.
The Spec becomes the source of truth
Once the direction is clear, Castaly writes it into the Project Spec. The Spec is the durable definition of what should be built.
Build controls execution
When you press Build, Castaly validates the Spec and proposes a Build Plan. Code changes only start after you approve that plan.
Preview and Publish close the loop
The build produces a running Preview you can test. When it matches your intent, Publish creates a stable public Project Version.
Core objects
Section titled “Core objects”The process layer where you describe intent, answer questions, refine decisions, and track what Castaly is doing.
The Markdown source of truth for the Project. Castaly writes it from Chat, and every Build reads from it.
The visual layer over the Spec. It shows pages, feature groups, and features so you can review structure without reading Markdown.
The proposed execution plan created from the current Spec. It lets you review what will be built before code changes begin.
Preview is the running version you test. Publish turns a reviewed Preview into a stable public Project Version.
Process layer and result layer
Section titled “Process layer and result layer”Castaly separates the workspace into two layers so you always know what you are looking at.
- Chat is the process layer: understanding, questions, decisions, progress, and change requests happen here.
- Graph, Spec, and Preview are the result layer: they show the structured product, the source of truth, and the running application.
This separation keeps the workflow clear. You steer the work in Chat, review the structure in Graph and Spec, then test the result in Preview.
Why approval matters
Section titled “Why approval matters”Castaly can update understanding and the Spec through conversation, but code does not change as a side effect of a message. Build is the boundary between defining the product and executing it.
What to explore next
Section titled “What to explore next”- Try the full loop in Quickstart.
- Learn how the source of truth works in Understand the Project Spec.
- See what happens before code changes in Start a Build.