● Compose-with-provenance · in private preview
Compose your infrastructure-with-policy.
Cite every line.
Vaelith reads your contracts, mandates and Golden Images, composes regional variants in seconds, and refuses to invent a single fact. Every decision traces to the exact line of the source it came from.
0 hallucinations across 247 nightly red-team cases
11s median composition time
BYOK · sources never leave your tenant
THE GRAMMAR
Four states. Nothing else.
Every fact in your workspace carries one of four labels — provenance, not severity. An approver can glance at any screen and know what to look at in two seconds.
✓
STATE EVIDENCED
Evidenced
A specific document, at a specific line. Hashed and re-verified on every read.
~
STATE INFERRED
Inferred
Assembled from related sources. Cannot ship without you signing it — that's how it becomes evidenced.
!
STATE MISSING
Missing
A required fact has no source. Vaelith refuses to invent one. The gap blocks sign-off until resolved.
⚠︎
STATE CONFLICTING
Conflicting
Two sources speak to the same fact and say different things. Vaelith refuses to pick.
01
Cite every line, or don't ship the line.
Click any fact in Vaelith and you land on the exact paragraph of the exact document it came from. Hashed, re-verified, and refused if changed.
Three commitments we won't move on.
02
Two-eyes by default.
Every sign-off requires two distinct approvers. Vaelith records click-through telemetry — if the first reviewer didn't open a single source, the second reviewer sees a yellow flag.
WHY VAELITH
03
Your tenant. Your model. Your data.
BYOK against any frontier model. Sources, embeddings and prompts stay in your VPC. We see metadata only, and the audit log proves it.
How does provenance prevent hallucinations?
Vaelith uses a deterministic retrieval-augmented generation (RAG) architecture. It does not pull from general knowledge; it is restricted to your specific corpus. If a fact cannot be linked to a source hash, it is flagged as 'Missing' instead of generated.
What infrastructure formats are supported?
Vaelith digests everything from legacy PDF manuals and internal wikis to modern Terraform, CloudFormation, and OpenAPI specs. Regional variants are composed based on the intersection of these mandates.
Answering for the AI.
COMMON INQUIRIES
Is our data used to train public models?
Never. By utilizing BYOK (Bring Your Own Key) on your own VPC, prompts and data stay within your tenant. Vaelith serves as an orchestration layer with zero-retention policies for your proprietary architecture documents.
How does the 'Two-Eyes' review work?
Sign-offs are multi-stage. Reviewer 1 validates provenance; Reviewer 2 audits intent. Our telemetry ensures reviewers actually interact with the source links, preventing 'blind approval' of sensitive infrastructure changes.