NoteStore Lab proof boundary
Return to the landing page Open the README contract Open the release feed
Public proof

What you can prove today, what was read back remotely, and what still needs a human click.

Start with the four-command proof path so you can see the workflow shape, the bounded AI layer, and the host boundary before you point the toolkit at a real copied-evidence run. 

notes-recovery demo
notes-recovery ai-review --demo
notes-recovery ask-case --demo --question "What should I inspect first?"
notes-recovery doctor

Read it like a proof ledger

  1. 1
    demo

    Shows the case-root shape without touching live or private evidence.

  2. 2
    ai-review --demo

    Shows AI as a bounded review layer on derived artifacts.

  3. 3
    ask-case --demo

    Shows one evidence-backed question path with citations and uncertainty.

  4. 4
    doctor

    Shows the host boundary and whether to move from demo to a real run.

Layer 1

Repo-side proof

These are the facts the repository can prove on its own, without asking you to trust screenshots, folklore, or platform settings.

notes-recovery demo

Proves the public-safe case-root workflow shape without touching private evidence or a live Notes store.

notes-recovery ai-review --demo

Proves AI exists as a bounded review layer on derived artifacts.

notes-recovery ask-case --demo ...

Proves the repo can answer one bounded question with evidence refs, confidence, and uncertainty.

notes-recovery doctor

Proves the host boundary, optional surfaces, and safest next step are inspectable before a real run.

Layer 2

Remote read-back proof

This layer depends on fresh GitHub read-back. It is stronger than docs claims, but still weaker than repo-owned proof because platform state can drift.

Repository read-back

GitHub repository is public, points at the current Pages landing, and keeps the current product description aligned with the copy-first story.

Release read-back

Release v0.1.0 exists and remains the current published tag tied to the local git tag.

Pages read-back

GitHub Pages is built from main:/, which keeps the landing and proof pages on the repo-owned surface.

Security read-back

Secret scanning alerts are readable and expected to stay at zero. Release readiness continues to audit the same remote truth.

Layer 3

Manual external tail

These items are real, but they live on the GitHub/platform side rather than inside the repo. This page keeps them explicit so they do not get mistaken for repo defects.

GitHub security analysis settings

Dependency graph, dependency review support, and some platform-managed security toggles still depend on GitHub Settings and organization policy.

Storefront checks

Custom social preview still depends on GitHub Settings upload plus REST open_graph_image_url read-back. A generated repository card URL is not the same thing as a confirmed custom upload.

Registry and marketplace listings

Distribution bundles can ship in-repo before any official directory or registry accepts and renders them.

Navigation

Keep going