Three running systems. One you can ask a question. One that refuses to answer without a source, and proves the handoff to a human arrived. One ledger that admits a payment it never received, rather than inventing the row.
These are proofs of concept built to test a claim, not client deliverables. Where something is recorded rather than live, it says so.
Knowledge base agent — answers only from your documents
Same knowledge base either way — type to it, or talk to it. The voice agent answers only from a source, and says so when it cannot.
Built with — typing goes through n8n, talking through the Python service; both read one index
Loading the voice agent…
Knowledge base agent — the evidence behind it
Every answer carries its source, or it is not given. Every handoff to a human is confirmed by reading the reply back — never assumed.
Captured from the acceptance runs on 2026-08-29. Real output, recorded rather than live.
What produces this proof
Q: what is the minimum mass of the car?
During Sprint Qualifying and Qualifying the Minimum Mass is 726kg plus the Nominal Tyre Mass. In all other sessions it is 724kg plus the Nominal Tyre Mass.
Answered from a source document, and it names the source out loud.
Q: what is the capital of Peru?
I don't have a sourced answer for that, so I'm passing it to a human who will follow up.
Nothing in the knowledge base covers this, so it refused rather than guessed — and the handoff was confirmed by reading the reply back, not assumed.
Q: how do I cancel my gym membership?
I don't have a sourced answer for that, so I'm passing it to a human who will follow up.
The channel was deliberately broken. The agent still spoke truthfully, but the handoff never arrived — and the console says so instead of staying quiet. A safety net nobody has seen catch anything is not known to work.
Billing event ledger — every payment recorded once, and the misses reported
Every payment recorded once, and only once. What matters is the payment that was never recorded at all — and the fact that nothing anywhere reported it.
Built with — the database decides what is a duplicate, not the code
What happened on 29 August, one step at a time.
A real failure from this system’s own first hour — not a staged demo. Every line of output below is verbatim. Nothing is sent anywhere as you read.
The cause was mundane: a signing secret applied a few minutes after the webhook was switched on. Ordinary setup, ordinary timing, one lost payment.
This ran against Stripe in test mode. The failure works exactly the same way in production — the difference is whose money it is.