Loading deck…
Loading deck…
Ship Page / Deck
Print view: one slide per page. Choose Save as PDF in the print dialog.
01 · Creation
Kane CLI Hack Day
Kane CLI runs every step of a README or AI how-to in a real Chrome; each line comes back proven, stale or broken with a screenshot, and an agent fixes stale steps.
Documentation is the test suite nobody runs. Getting-started guides and AI how-to answers drift as UIs change, and AI coding agents learn from those docs, so a stale doc step becomes a hallucinated ag
01 / 05 · Attest
02 · See it work
Kane CLI Hack Day
02 / 05 · Attest
03 · The harness
Kane CLI Hack Day
Attest is the harness: it writes the Kane tests from a doc, runs them, reads Kane's evidence and decides a verdict per doc line. Kane is a witness, not a judge: each step stores the exact visible text closest to what the doc promised, so a renamed control comes back as stale with the new label instead of a failure. Stale or broken verdicts feed a closed loop (Codex patches only the doc, Kane re-proves). Every Kane run is filed with kanehack report. Attest's own README is proven by Kane (6 of 6).
Components: testmd · sealed_evidence
03 / 05 · Attest
04 · Proof
Kane CLI Hack Day
05 · Outcome
Kane CLI Hack Day
Kane CLI runs every step of a README or AI how-to in a real Chrome; each line comes back proven, stale or broken with a screenshot, and an agent fixes stale steps.
https://github.com/SyberLabs/attest
Not yet verified: Shell claims run on the host with the user's environment; the scratch directory is not a sandbox, so only prove docs you would run by hand. · Attest assumes the app is right and the doc is stale; it cannot yet refuse a doc repair that would hide an app regression. · Kane runs a whole test file before Attest judges the first claim; cards use --stop-before for irreversible or real-form steps.
04 / 05 · Attest
05 / 05 · Attest