Ivy.

System

Capture from iPhone one Shortcut

Build a voice-first Capture to Ivy Shortcut. The same Shortcut can accept Share Sheet input; if you prefer typing, swap its dictation action for Ask for Text.

  1. Choose the input. In Shortcut Details, enable Show in Share Sheet and receive Text and URLs; set If There's No Input to Continue. Add an If action: when Shortcut Input has a value, set variable Capture Text to it. Otherwise use Dictate Text with Stop Listening set to After Pause, then set Capture Text to the result; if no text is returned, fall back to Ask for Text. For a typed-first variant, use Ask for Text instead of Dictate Text.
  2. Add Get Contents of URL with method POST and these values.
    URL
    /api/capture
    Authorization header value
    Not set

    Header name: Authorization. The token hides after 30 seconds, when this section leaves view, or when the page is hidden.

    Content-Typeapplication/json

    Request body · JSON fields

    textCapture Text magic variable
    sourceshortcut
  3. Check the response. Get the id dictionary value from Get Contents of URL. If it has a value, show “Captured in Ivy.” Otherwise show an alert: “Ivy did not save this — open the app”. Keep Shortcuts' own network error visible too.

Check this connection

Makes one authenticated read. It does not create a capture or run the interpreter.

Run the Shortcut once; your words appear at the top of the Ledger.

Captures typed in the app are saved on this device first and sent when Ivy is reachable. If Ivy rejects an entry as invalid (HTTP 422), the app removes it from the waiting list and shows the error instead of retrying.

On iPhone, install Ivy to the Home Screen for the safer PWA path; Safari may evict website storage for a site that is not installed.

Shortcut captures are saved only if Ivy responds with an id. If it fails, re-send the words or type them in the app.

This device has no captures waiting to send.

kill condition measured, not vibes

measuring_

derived on read from capture, reshape, version, and revert history

consent & activity closed policy state

Google Calendar

read-only · titles are fetched live, not stored

a connection is not consent; request-bound reads and standing grants are logged separately

notifications web push

…

schemas layer 2 — data, not code

schema changes are additive-only — nothing renamed, nothing dropped

ledger the audit path
open the ledger →

every capture in arrival order — raw text is preserved, always

export ivy-export-v1

every observation, record, schema, view, note — the exit promise.