Code changes. Promises don't. Wayvian finds the gap.

Connect your live website and your GitHub repo.
Wayvian finds your public promises, checks each one against the code, and keeps the receipt.

Request early accessSee: How a check works
A real check from Wayvian's own codeCurrent

The promise

“Your request is encrypted before it is stored.”

wayvian.com/request-access

The code

lib/db/queries/access-requests.ts

encryptSecret(email)

The verdict

Supported

A regression test checks this path before every release.

Evidence spine

One continuous chain from the promise people read to the behavior your product ships.

A later read can change the verdict. It cannot erase the receipt that explains the earlier one.

  1. 01Read

    Public website + GitHub

  2. 02Locate

    Exact source quote

  3. 03Verify

    Shipped code evidence

  4. 04Resolve

    Honest proof state

  5. 05Remember

    Append-only receipt

Keep public promises tied to the code behind them.

Wayvian saves the exact words customers saw, finds the relevant implementation, explains what the evidence proves, and checks again when either source changes.

Illustrative proof receipt
acme.dev/security

Exact website quote

“Customer data is encrypted at rest.”

Exact quote · pinned to this page version

Pinned to the source version observed on 25 Jul 2026.

src/storage/encryption.ts
example commit · line 42
export const storage = {
  algorithm: "AES-256-GCM",
  keyManagement: "AWS KMS",
  encryptAtRest: true,
}

The citation names the repository, commit, file, and exact line that supports the claim.

Supported

The public promise and current implementation agree. This verdict remains current until either cited source changes.

Receipt
example_rcpt_7f2c
Observed
25 Jul 2026
Freshness
Website + GitHub current
Request early access
Grounded intelligence

An AI operator that can show its work

Meet Ian. Ask what changed, what cannot be proven, and what your team should do next. Every answer is grounded in Wayvian's claim and evidence graph.

Learn more
Follow the evidence pipeline...
◇Website readerEngine
◉GitHub readerEngine
◈Claim extractorEngine
○Code indexerEngine
◎VerifierEngine
○IanEngine

Recommendations grounded in evidence

Ian can propose the next move, but the cited claims and receipts remain visible before anything is accepted.

Evidence IntelligenceIllustrative Ian recommendation
Grounded in
Example claimSecurity promiseExample receipt
Contradicts
Code path
Ian

Why this action was suggested

The security page promises end-to-end encryption, while the pinned repository receipt shows plaintext message storage. Correct the delivery or qualify the public wording.

Alternatives

Fix deliveryCorrect copy
Start with your evidence

A learning loop, not a prompt loop

Accepted, edited, rejected, and outcome-tracked recommendations become workspace-local learning signals.

Recommendation history

Scoped to this workspace and its current evidence

Accepted

Keep the cited security wording

Outcome pending

Edited

Qualify the retention promise

Verified after reread

Rejected

Do not add an unproven compliance badge

Suppressed while evidence is unchanged

New verifier evidence can reopen a previously rejected path.
Continuous product truth

See exactly where product truth breaks

Follow public claims from promise to shipped behavior. See what changed, what went stale, what contradicts the site, and what needs a decision.

30
AUG 3
10
17
AUG 22
24
SEP
Claim extraction
Website read
Code index
Verification pass

Trace a claim end-to-end

Keep the public quote, source version, code evidence, verdict, and history in one durable dossier.

Claim dossier

Verdict
ContradictedEvidence
Evidence
🚩Website quote⚠Code receipt
Lifecycle
Promise locatedEvidence indexedVerdict resolved Current

Honest proof state

See the current conclusion and the evidence boundary behind it. Unproven and contradicted states remain explicit.

Contradicted
Needs proof
Supported

Current evidence supports this promise

Current observation

Keep the full
proof chain intact

Pinned public quote
Located code evidence
Append-only receipt trail
cl1›Proof receipt•••
Inspect the exactproofverifier

Start from the exact wording customers saw, then follow the durable receipt through located codereceipt, the resolved verdict, and every later change without rewriting history.

Public surface

Map the pages and promises customers actually see.

Repository evidence

Locate the code and configuration that prove delivery.

Verdict lifecycle

Keep transitions, reruns, and founder rulings traceable.

Change history

Trace what changed, why the verdict moved, and when.

Evidence workflowsIllustrative examples

Evidence follows
observed source changes

Follow public wording, repository pushes, decisions, and rereads through one append-only evidence history.

Website reader·example read

“End-to-end encrypted by default.” located...

W
Public promiseObserved
◆
Security claimcl1
Evidence queued
📅14:32 UTC

Public surface

Read the promises customers actually see

example changenew revisionexample/source.ts
↗Wayvianlinkedcl3to code...
↗Verifiermarked the prior verdict stale...
↗GitHubdelivered a new source revision...
↗Composerqueued affected claims...

Repository evidence

Match claims to the code that supports them

Inbox

Proof receipts

Preserve the exact source, commit, and verdict

Grounded Ian

Turn evidence gaps into the next honest move

Public website
GitHub repository

Source monitoring

Re-read after the website or repository changes

Decision recorded

Keep the qualified retention wording until implementation changes.

append-only · active

Decision memory

Keep accepted risks and rejected ideas on record

ClaimReceiptReread

Evidence continuity

Keep receipts attached through later rereads

Wayvian on Wayvian

Our own proof comes first.

We are preparing the first public Wayvian-on-Wayvian record. It will appear here when the evidence is ready.

Coming soon.

We will publish the first Wayvian-on-Wayvian record when the evidence is ready.

Say less. Prove more.

Contact salesRequest early access