@mavea/mavea 1.1.0 → 1.2.0

package/CHANGELOG.md

@@ -6,6 +6,89 @@ All notable changes to Mavéa are documented here. The format is based on
 
 ## [Unreleased]
 
+## [1.2.0] - 2026-08-17
+
+### Added
+
+- The daily search budget is adjustable from any dashboard's Settings, under "Every dashboard" —
+  one shared cap across all boards, because what it guards is the total daily spend on your key.
+- **An ordinary answer's figures now prove themselves.** Prove it lists every figure the answer
+  printed and what backs it: grounded ones quote the source's own sentence, and the rest are marked
+  as the model's own rather than left to look measured. The living answer had refused an unbacked
+  number since it shipped; every other answer printed its numbers straight from block props, so the
+  rule held on exactly one surface.
+- **A cause can be opened into its parts**, drawn through the component library rather than a fixed
+  chart — and a part can be opened in turn. A subject whose parts nothing measured is named in a
+  list instead of drawn as a proportion, because a hierarchy figure implies measured shares.
+- The guided walkthrough's living-answer chapter now walks itself, cause by cause. Its line has
+  always promised a narration nobody could trigger on a replay.
+
+### Changed
+
+- The Terms, Privacy Notice, and Disclaimer now cover tracked readings (stored per tracker in
+  IndexedDB, encrypted, deleted with the dashboard) and state plainly that tracked or "live"
+  values are best-effort and depend on the model you pick — a completed search can still surface
+  out-of-date figures, alerts are never guaranteed to arrive, and every check spends on the key
+  you supplied. The dashboards first-use notice says the same in plain words, and the alerts card
+  itself now carries the don't-rely-on-this line. The in-app acceptance version was bumped, so
+  existing users are shown the updated documents once.
+- The default daily search budget is 25 (was 40), sized from the app's own cadence math: hourly ≈
+  up to ~24 checks/day while Mavéa is open, so out of the box the cap covers one always-on hourly
+  board. Running more than that is a deliberate spend choice you make by raising the knob; manual
+  actions like Refresh now were never counted against it.
+
+- **A dashboard check now fetches data, not a rendered card.** Checks used to ask the model to
+  rebuild a finished canvas block — exact component type, exact prop names, nested item shapes —
+  which made it responsible for Mavéa's rendering contract; any drift discarded a grounded search
+  you had already paid for. Data-shaped cards (lists, tables, timelines, charts) now come back in a
+  one-line schema and Mavéa builds the component itself. Cards that carry prose keep the old path.
+- **Readings are kept per tracker in IndexedDB**, encrypted with the same device key as the rest of
+  a dashboard, instead of being folded into the one blob that was rewritten whole on every write.
+- Only one browser tab runs the refresh loop now. Every extra open tab used to run its own
+  scheduler and bill your key again for the same checks.
+- **A living answer is offered on the answer, not the question.** Asking "why" is not the same as
+  getting back something with causes in it, so the offer is judged on what the answer actually
+  contains — no more opening a causal web onto an answer that has none.
+- **The "show only what is sourced" filter is gone.** Measured across every scenario, not one
+  receipt carried a followable link or document anchor, so the control promised a reader something
+  it could never show them.
+
+### Fixed
+
+- **Dashboard checks asked for live data and accepted an answer from memory.** The search tool was
+  offered but never required, so a model could skip it and reply from training data; the reply was
+  correctly discarded, after being billed for. Checks now require the search.
+- Creating a tracker no longer waits on its first check. It used to hold the sheet open for the
+  length of a real web search — routinely 30-60 seconds — with the finished board invisible behind
+  it.
+- **A tracker that cannot complete its first check is kept, not deleted.** A provider hiccup used
+  to make a tracker you had just described disappear. It now stays, marked as waiting, and says
+  what it is waiting on. Nothing unverified is ever shown either way.
+- Each failure now names its own cause — a rate limit, a rejected key, an unreachable provider, a
+  search that grounded nothing — and retries on a schedule that fits it, instead of one message and
+  one five-minute retry for all of them.
+- "What happened on the last check?" on a dashboard shows the steps that check actually took, so a
+  failure can be diagnosed without a network panel.
+- Check all stops after a whole round fails at the provider, instead of spending the rest of your
+  per-minute quota collecting the same error.
+- The dashboards surface scrolls again — content below the fold had become unreachable.
+- An ask-the-user form card can no longer be pinned onto a dashboard; a dashboard's values come
+  from live search.
+- **Three places a living answer could state a figure with nothing behind it.** Source excerpts
+  never reached it, so every figure failed the verbatim check however good the sources were; an
+  arrow's share was drawn without any source stating that share, which sized the ribbons by an
+  unproven number; and a date could place a cause on the timeline unproven, where the position
+  _is_ the claim.
+- A new turn could leave the answer blank instead of drawing it.
+- A pen mark aimed at a collapsed section landed on empty space, next to nothing.
+- Breaking down a cause that had itself come from a breakdown did nothing at all, and the fold-up
+  control on one did nothing either.
+- A cause could be named by a truncated slug ("consumer-switch-to-digit") or, with an invisible
+  label, by nothing at all — leaving a nameless card, a nameless lever, and a sentence with no
+  subject.
+- Long connector labels in a flow diagram were drawn wider than the gap between the shapes and
+  painted over by them, leaving the reader a sliver of each word.
+
 ## [1.1.0] - 2026-08-16
 
 ### Added

package/DISCLAIMER.md

@@ -1,12 +1,13 @@
 # Mavéa Disclaimer
 
-Effective: August 11, 2026
+Effective: August 17, 2026
 
 Mavéa uses probabilistic AI systems and can be wrong.
 
 - AI-generated text, citations, calculations, classifications, transcriptions, translations, and visualizations may be inaccurate, incomplete, misleading, offensive, or outdated.
 - A citation, confidence label, validation step, or polished visualization does not guarantee that a claim is correct.
 - Verify important information with authoritative sources and qualified professionals before relying on it.
+- Results depend heavily on the model and provider you choose. Models differ in whether they search the live web at all, whether they can be required to, how reliably they cite what they used, and how current their training data is. A smaller or cheaper model may answer from memory instead of searching, and may not say that it did. Live, tracked, and refreshed values can therefore be stale, incomplete, or wrong, and a shown source does not prove that the figure beside it came from that source or is correct. Even a completed search can surface figures that were already out of date at the source. Scheduled checks may be delayed, skipped, or missed entirely, and alert and notification features are best-effort — a check that does not run, a closed app, or blocked browser notifications means no alert, so never depend on one arriving. Every check runs on the API key you supply, so the refresh cadence you configure is a spending decision with the provider you pay. Do not rely on tracked dashboards or alerts for anything time-critical or consequential.
 - Mavéa does not provide medical, legal, financial, tax, accounting, safety, engineering, mental-health, or other professional advice. Do not use it for emergencies or as the sole basis for high-impact decisions.
 - You are responsible for the prompts, files, audio, accounts, credentials, and actions you provide or authorize.
 - Model, search, speech, hosting, OAuth, media, and connected-action providers are independent third parties. Their terms, privacy practices, availability, and charges apply. All costs are your responsibility.

package/PRIVACY.md

@@ -1,6 +1,6 @@
 # Mavéa Privacy Notice
 
-Effective: August 11, 2026
+Effective: August 17, 2026
 
 This notice describes the current, unmodified local and self-hosted Mavéa software. It does not describe a future hosted service. Local-first does not mean every feature stays on your device: connected features send data through the deployment to third parties you choose. If a person or organization deploys Mavéa for others, that operator must provide any additional privacy notices and controls required for its deployment.
 
@@ -20,6 +20,7 @@ Depending on the features you use, browser storage may contain:
 
 - conversations, saved canvases, bookmarks, memory items, and session history;
 - courses, lessons, flashcards, quiz progress, Ripple analyses, and dashboards;
+- the readings a dashboard has fetched over time, kept per tracked item as its own record so a value's history and the sites it came from survive between checks;
 - preferences such as theme, performance, visual richness, voice, and setup state;
 - drafts, tracked items, presentation settings, and recent feature state;
 - provider and model configuration;
@@ -27,9 +28,9 @@ Depending on the features you use, browser storage may contain:
 - temporary in-progress and finished video-export files in origin-private browser storage until the export is consumed or discarded; and
 - short-lived demo, tour, route, and in-progress session data.
 
-Saved content is encrypted in browser storage only where the relevant feature and browser support it. Course data, mastery and progress, some Ripple data and analysis caches, preferences, metadata, and fallback content can be stored in ordinary local storage or IndexedDB. Anyone who can use your unlocked device or browser profile, and malicious extensions or same-origin code, may be able to access browser data.
+Saved content is encrypted in browser storage only where the relevant feature and browser support it. Dashboards and the readings they fetch are encrypted with the same device key, the readings in IndexedDB with only their routing details — which tracked item, and when — left readable so they can be looked up. Course data, mastery and progress, some Ripple data and analysis caches, preferences, metadata, and fallback content can be stored in ordinary local storage or IndexedDB. Anyone who can use your unlocked device or browser profile, and malicious extensions or same-origin code, may be able to access browser data.
 
-Because this browser data is encrypted to this specific browser, it does not carry over to a different browser, an incognito window, or another device. You can export a backup file of your dashboards, memory, flashcards, saved canvases, map, and courses, and import it elsewhere to move that data. The backup is plain, unencrypted JSON under your control, so store and share it carefully; it deliberately excludes your provider and search keys. Importing a backup merges into existing data and never deletes it, and importing a file you did not create can add content from that file — import only backups you trust.
+Because this browser data is encrypted to this specific browser, it does not carry over to a different browser, an incognito window, or another device. You can export a backup file of your dashboards, memory, flashcards, saved canvases, map, and courses, and import it elsewhere to move that data. A backup carries a dashboard's definition and its latest values, not its fetched reading history, so moving to another browser starts that history fresh. The backup is plain, unencrypted JSON under your control, so store and share it carefully; it deliberately excludes your provider and search keys. Importing a backup merges into existing data and never deletes it, and importing a file you did not create can add content from that file — import only backups you trust.
 
 Browser and operating-system caches may retain application assets and optional voice models. The actions gateway may store connected-service credentials and configuration on the deployment operator's machine.
 
@@ -88,7 +89,7 @@ The unmodified project does not sell personal information or use it for cross-co
 
 ## 8. Retention and deletion
 
-Memory-only values disappear on reload. Session storage generally remains until the tab or browser session ends. Local storage and IndexedDB remain until a feature removes the item, you use an available clear, forget, or reset control, you clear site data, or the browser evicts it. Some session history is capped and expires, but many course, progress, dashboard, memory, and Ripple records have no automatic expiration. Clearing all browser site data is the broadest local deletion control. Removing browser data does not delete copies already sent elsewhere.
+Memory-only values disappear on reload. Session storage generally remains until the tab or browser session ends. Local storage and IndexedDB remain until a feature removes the item, you use an available clear, forget, or reset control, you clear site data, or the browser evicts it. Some session history is capped and expires, but many course, progress, dashboard, memory, and Ripple records have no automatic expiration. A dashboard's fetched reading history is capped per tracked item, and deleting a dashboard deletes its readings and its record of recent checks with it. Clearing all browser site data is the broadest local deletion control. Removing browser data does not delete copies already sent elsewhere.
 
 Gateway tokens remain until disconnected or removed by the gateway operator. Server, proxy, infrastructure, and provider retention depends on the relevant operator, logs, backups, account settings, and third-party policy. Contact those parties for deletion of data they control and revoke credentials at the issuing service.
 

package/README.md

@@ -77,11 +77,12 @@ A few specific things worth trying:
   surface from what you actually said — never fixed buckets — with the tensions between them.
 - **The Blank Space.** When an answer needs a number only you have, Mavéa leaves a hole to fill —
   by voice, type, or a dragged card — instead of quietly guessing.
-- **View any "why" as a world.** The answer opens into the causal web behind it: press
+- **View any "why" as a living answer.** The answer opens into the causal web behind it: press
   _Walk me through it_ and the camera flies cause to cause while Mavéa narrates, or read the same
-  web as contribution ribbons, a timeline, or a chart. Every figure on it can prove itself, every
-  arrow says what it does _not_ claim, and pulling a what-if lever re-weights the world in words —
-  never in invented numbers.
+  web as contribution ribbons, a timeline, or a chart. Break a cause open and its parts are drawn by
+  whichever component the library has for that shape — or simply named, where nothing measured them.
+  Every figure on it can prove itself, every arrow says what it does _not_ claim, and pulling a
+  what-if lever re-weights the world in words — never in invented numbers.
 
 The full tour — Atlas, the Rehearsal, living dashboards, Ripple, selective Conversation video,
 Mavéa Reels, and ~30 more —
@@ -89,7 +90,7 @@ is in [docs/FEATURES.md](docs/FEATURES.md). In the app, press **⌘K**.
 
 ## What it looks like
 
-Ten moments from the walkthrough and the recorded sessions. Every one replays with no key via
+Twelve moments from the walkthrough and the recorded sessions. Every one replays with no key via
 `npx @mavea/mavea` — except the thought map, whose threads need a live model to draw.
 
 <!-- Generated, never hand-captured: `pnpm gen:media` re-shoots these against the current build
@@ -99,18 +100,22 @@ Ten moments from the walkthrough and the recorded sessions. Every one replays wi
      it is the only markup GitHub and npm both keep on one row. -->
 <table>
   <tr>
-    <td width="20%" valign="top"><img width="168" src="docs/media/answer-ink.jpg" alt="A token-exchange request on the canvas, underlined and highlighted by Mavéa's pen as it narrates" /><br /><sub><b>It marks what it's saying.</b> The pen lands on the exact line as the sentence is spoken.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/canvas-view.jpg" alt="The same answer opened as a spatial canvas, cards connected by drawn links" /><br /><sub><b>The same answer as a board.</b> Laid out in space, with the relationships drawn between them.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/trip-plan.jpg" alt="A day trip drawn as a route map with numbered stops beside an hour-by-hour plan" /><br /><sub><b>It picks the right form.</b> A route becomes a map; a day becomes an hour-by-hour plan.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/think-map.jpg" alt="Thoughts spoken out loud, sorted into themes and threads with the tension between two of them named" /><br /><sub><b>Think out loud first.</b> A ramble sorts itself into themes — and it names the tension you missed.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/voice-scrub.jpg" alt="A settled answer with its spoken track drawn as a waveform, above the card being narrated" /><br /><sub><b>Scrub the voice.</b> Drag the spoken track and the canvas un-builds to what had been said.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/answer-ink.jpg" alt="A token-exchange request on the canvas, underlined and highlighted by Mavéa's pen as it narrates" /><br /><sub><b>It marks what it's saying.</b> The pen lands on the exact line as the sentence is spoken.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/canvas-view.jpg" alt="The same answer opened as a spatial canvas, cards connected by drawn links" /><br /><sub><b>The same answer as a board.</b> Laid out in space, with the relationships drawn between them.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/think-map.jpg" alt="Thoughts spoken out loud, sorted into themes and threads with the tension between two of them named" /><br /><sub><b>Think out loud first.</b> A ramble sorts itself into themes — and it names the tension you missed.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/voice-scrub.jpg" alt="A settled answer with its spoken track drawn as a waveform, above the card being narrated" /><br /><sub><b>Scrub the voice.</b> Drag the spoken track and the canvas un-builds to what had been said.</sub></td>
   </tr>
   <tr>
-    <td width="20%" valign="top"><img width="168" src="docs/media/doc-prism.jpg" alt="A NASA technical report read claim by claim, each finding highlighted on the real scanned page" /><br /><sub><b>A document, claim by claim.</b> Every finding highlighted on the real page it came from.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/repo-course.jpg" alt="A GitHub repository turned into a beginner-to-expert curriculum with lessons, files to read and a checkpoint" /><br /><sub><b>A repository, taught.</b> Beginner to expert, built from the code, with real files.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/deep-zoom.jpg" alt="Deep Zoom descending through a leaf, from the whole plant down toward a photon" /><br /><sub><b>A topic, in powers of ten.</b> Telescope from the big picture to the finest mechanism.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/deck-export.jpg" alt="The export studio previewing a generated slide, with PDF and PPTX downloads" /><br /><sub><b>Out as a deck.</b> Ten skins, a live preview, PDF or PowerPoint.</sub></td>
-    <td width="20%" valign="top"><img width="168" src="docs/media/doc-export.jpg" alt="The export studio previewing a generated document page in an editorial template" /><br /><sub><b>Or as a document.</b> The same answer set as a paper, ready to print or send.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/living-answer.jpg" alt="A causal web explaining why the 2008 financial crisis happened, nodes connected by weighted arrows showing what led to what" /><br /><sub><b>Walk the why.</b> A "why" answer opens into the causal web behind it — every cause traceable to a real quote.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/course-lesson.jpg" alt="A course lesson titled 'The learning loop', showing lesson 1 of 5 with learning objectives, a checkpoint, and a diagram of a neural network's training cycle" /><br /><sub><b>It builds you a course.</b> Ask to master something and get real lessons — objectives, a checkpoint, next steps.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/deep-zoom.jpg" alt="Deep Zoom descending through a leaf, from the whole plant down toward a photon" /><br /><sub><b>A topic, in powers of ten.</b> Telescope from the big picture to the finest mechanism.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/doc-prism.jpg" alt="A NASA technical report read claim by claim, each finding highlighted on the real scanned page" /><br /><sub><b>A document, claim by claim.</b> Every finding highlighted on the real page it came from.</sub></td>
+  </tr>
+  <tr>
+    <td width="25%" valign="top"><img width="168" src="docs/media/trip-plan.jpg" alt="A day trip drawn as a route map with numbered stops beside an hour-by-hour plan" /><br /><sub><b>It picks the right form.</b> A route becomes a map; a day becomes an hour-by-hour plan.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/repo-course.jpg" alt="A GitHub repository turned into a beginner-to-expert curriculum with lessons, files to read and a checkpoint" /><br /><sub><b>A repository, taught.</b> Beginner to expert, built from the code, with real files.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/deck-export.jpg" alt="The export studio previewing a generated slide, with PDF and PPTX downloads" /><br /><sub><b>Out as a deck.</b> Ten skins, a live preview, PDF or PowerPoint.</sub></td>
+    <td width="25%" valign="top"><img width="168" src="docs/media/doc-export.jpg" alt="The export studio previewing a generated document page in an editorial template" /><br /><sub><b>Or as a document.</b> The same answer set as a paper, ready to print or send.</sub></td>
   </tr>
 </table>
 

package/TERMS.md

@@ -1,6 +1,6 @@
 # Mavéa Terms of Use
 
-Effective: August 11, 2026
+Effective: August 17, 2026
 
 These Terms of Use (the **Terms**) govern your use of the Mavéa application, command-line package, demos, documentation, and related materials (collectively, the **Service**). **Licensor** means each applicable copyright holder offering software under the PolyForm license. **Maintainers** means the people who publish or contribute to Mavéa; a Maintainer is not necessarily a Licensor. **Deployment operator** means the person or organization hosting the copy you use. **Responsible Party** means the applicable Licensor, Maintainer, or deployment operator responsible for a statement, obligation, service, or claim. In these Terms, **we**, **us**, or **our** means the relevant Responsible Party or Parties in context. A separately operated deployment remains independent from the Licensors and Maintainers unless the same person or organization serves both roles.
 
@@ -30,6 +30,8 @@ You are responsible for selecting, configuring, operating, and securing your dev
 
 The Service uses probabilistic artificial-intelligence systems. Outputs, citations, calculations, classifications, summaries, transcriptions, translations, confidence labels, and visualizations may be false, fabricated, inaccurate, incomplete, misleading, biased, offensive, unsafe, or outdated. A polished presentation, citation, calculation, validation check, or natural voice does not guarantee accuracy, originality, legality, quality, or fitness for a particular purpose.
 
+Output quality depends on the model, provider, and settings you select, and those are your choices. Models differ in whether they retrieve live information at all, whether the Service can compel them to, whether they disclose what they used, and how current their training data is; a smaller or cheaper model may answer from memory rather than searching, and may not say so. Features that display tracked, refreshed, or "live" values are therefore best-effort only: a value may be stale, incomplete, absent, or wrong, a check may be delayed, skipped, or silently unsuccessful, a figure obtained from a genuine live search may already be out of date at its source, and a source shown beside a figure does not establish that the figure came from that source or is accurate. Alert and notification features are likewise best-effort; no alert is guaranteed to fire or to be delivered. Scheduled checks run on credentials you supply and can incur third-party charges at whatever cadence you configure. Do not treat any displayed value as real-time, authoritative, monitored, or verified, and do not rely on tracking or alerts as your means of watching anything consequential.
+
 You must independently review and verify important output against qualified professionals and original sources before relying on, publishing, sharing, or acting on it. The Service is not a substitute for qualified professional judgment and does not provide medical, legal, financial, tax, accounting, safety, engineering, mental-health, or other professional advice. Do not use it for emergencies or as the sole basis for decisions that may affect a person's rights, health, safety, finances, employment, education, housing, insurance, or access to essential services. You remain responsible for deciding whether and how to use every output.
 
 ## 5. Third-party services, credentials, and costs