The craft · verification

A number is trustworthy when it ties to the file, not to a guess.

The difference between a certified report and a confident wrong answer is a method. Kymira teaches your agent to find what a file asserts about itself, reconcile every figure to that anchor, and catch anything it cannot prove before it ships.

For the operator who owns the numbers, no data team required.

Get the free skill See it live in the demo

What it does

Find the anchor, reconcile to it

Every computed figure is checked against a total the source file states about itself, not against a recomputation of it. When a file asserts no total to tie to, that is raised, not quietly skipped.

Skills · Anchor discovery

Read every value two ways

Each figure is found two ways that share no logic: once by where it sits, once by the label beside it. Both must agree within a written tolerance, or the agent investigates instead of averaging the difference away.

Skills · Verification practice

Prove the check can fail

Every guard gets a test that feeds it known-bad input and confirms it blocks. A check that cannot fail is a comment with a runtime cost, and more than once one looked green for weeks while being unable to fire.

Skills · Adversarial review

The honest scope

What certified means, and what it does not.

Certified means every figure on the page ties to the source file's own totals, through checks written as plain code you can read and re-run, and that anything the file cannot prove is named on the page or held back rather than shipped as fact.

It does not mean the source file is true, that the vendor's export is complete, or that a business outcome is warranted. The skills' own documentation carries a "what this cannot prove" section for exactly this reason: a method that only lists its wins is the self-grading it exists to refuse. What you get is narrower and stronger than a promise: for a wrong figure to reach your reader, it would have to defeat every check in the net, and the net exists to catch it.

Fail closed and stale, never silent and wrong.

A failed check blocks the update. The last known-good version stays live, marked so a reader knows a newer cut is under review, and a person is told. You can watch this exact behavior in the demo, where two reports are held stale on purpose because their live cut failed a check.

See it in the live demo Read the doctrine