“ENG-428 audit log export: implementation complete; built=true.”
The ticket closed. Its definition of done stops at the merge, not at this customer’s workspace.
THE CUSTOMER REALITY CHECK
Engineering closed the ticket. Can the customer actually use it? Promise Ledger checks every customer promise against customer-specific evidence, shows the gap, and drafts an honest update for you to approve.
No sign-up. Four fictional sample accounts. Live runs are rate-limited; the reference replay is always free.
Powered by NVIDIA Nemotron on Nebius Token Factory
Audit log export
Maya Chen: I will make audit log export available to Northstar by 2026-09-14.Meeting · SRC-01
THE REALITYThe customer-specific audit_export entitlement is disabled. Don’t send the delivery email yet.
Draft for your review. Never sent automatically.
THE PROBLEM
A customer-success manager has to answer one question honestly: can I tell this customer we delivered what we promised? The systems they read each tell a different part of the story.
“ENG-428 audit log export: implementation complete; built=true.”
The ticket closed. Its definition of done stops at the merge, not at this customer’s workspace.
“Audit log export is generally available.”
General availability says nothing about one customer’s plan, entitlement or feature flag.
“The audit export button is still missing in our Northstar workspace.”
Send the “it’s live” email now and you spend trust you can’t easily win back.
THE APPROACH
NVIDIA Nemotron models triage the sources, extract promises and explain disagreements. Every claim cites source text, checked character for character.
Built, enabled and customer-verified are separate facts. A deterministic policy sets every verdict, and no model can change one.
Drafts are editable and approved locally. Export exists; sending does not. A closed ticket never earns a green badge on its own.
HOW IT WORKS
The live agent view streams every step as it happens: the model, latency, tokens, estimated cost, and each cited quote with its exact-match check.
Labels every source and routes conversations to extraction. Delivery records go straight to the rules.
Pulls out commitments, owners and dates, each with an exact quote. Anything it cannot ground is dropped; a failed extraction stops the run.
An ordered policy turns customer-specific built, enabled and verified facts into one of seven conservative verdicts.
Only after the verdict is fixed: why the evidence disagrees, a customer update and a nudge for the owner, each claim cited.
Meeting notes, tickets and availability snapshots. Paste text or drop .txt, .md, .csv or .eml files; you confirm every extracted fact before the rules read it.
Fetches the vendor’s public changelog at runtime and shows it beside the verdict: “Publicly GA ≠ usable by this customer”. It never changes the verdict.
Errors for this customer and feature after acceptance lower “verified” to “needs verification”. A quiet error feed never proves delivery.
GUARDRAILS
POWERED BY
Three open NVIDIA Nemotron models, served by Nebius Token Factory’s inference API, each do one job. The browser never sees a key; every call runs server-side with a strict schema and a budget.
Measured in September 2026 on synthetic data: a four-run pipeline smoke test and a small assistant-authored evaluation of the Super extraction step. Not a real-world accuracy claim.
nvidia/NVIDIA-Nemotron-3-Nano-30B-A3Bnvidia/nemotron-3-super-120b-a12bnvidia/Nemotron-3-Ultra-550b-a55bTRY IT
Every customer, person and document in the samples is fictional, and snapshots are fixed at September 13, 2026. No real CRM, support desk or customer system is connected. Reference mode replays a hand-labelled trace with no AI calls and says so on screen. Evidence you bring stays in your browser until you run a check; a live run sends it to Nebius for inference.