Do we have to rebuild our existing templates?
No. Kestral reads the markup syntax your templates already use. On import it reports anything in a template that needs attention, naming the specific construct behind each finding rather than failing silently.
Do we have to build the intake form separately?
No — that is the point. Kestral drafts the form from the document's own markup, and you adjust it from there. You do not build the same structure twice.
Can clauses be reused across templates?
Yes. Clauses live in their own library with their own versions and history, and can be inserted or appended into any template.
Can we see what a change will affect before making it?
Yes. Every artifact shows its reach — the templates and clauses that include it — so you can see where an edit will land before you publish it.
What happens to earlier versions of a template?
Nothing is lost. Each artifact keeps its drafts, its published versions and a full history, and any earlier version can be restored.
Can Kestral run inside our own product?
Yes. The designer, intake and assembly are all built to be delivered as services, including their interfaces, with branding and access handled as configuration rather than per-partner code.