Provenote

This illustrated overview is a repo-authored summary of the shortest documented path. It is intentionally not presented as a live product recording.

Canonical product path: messy long context -> structured insight -> note / research thread / draft -> inspectable outcome

That is the first door. MCP, starter bundles, distribution pages, and promotion assets are valuable second-ring surfaces, but they should not outrank the product path.

Start Here In 10 Seconds

If you only want the fastest honest map, use this:

| Question | Open this first | Why | | --- | --- | --- | | "Can this help with messy long context?" | Long Context | This is the product center, not a side use case. | | "Can I get one real result quickly?" | Quick Result Path | This is the shortest repo-documented local proof loop. | | "Is this real or just copywriting?" | Public Proof | This is the evidence layer. | | "What is still intentionally unclaimed?" | Project Status | This is the boundary page. |

Judge the workbench before you judge the side doors. MCP pages, starter bundles, distribution packs, and promotion assets matter, but they are second-layer surfaces around the main product path.

Why Provenote Exists

Most AI note tools make it easy to generate words and hard to verify where those words came from.

That gets even worse when the raw material is long and messy: a huge chat log, a copied forum thread, a meeting recap, or a web page pile you do not want to flatten into one more throwaway summary.

Provenote is built for the opposite direction:

• collect notes, documents, audio, and web content in one place
• structure long context before it disappears into another chat turn
• search and ask across that material without losing the source trail
• turn high-value source work into auditabl

... View full README on GitHub