Product

Tasks, notes, and events that keep their original sentence.

Everything in Yapture starts as a line of text you can read. The app adds structure — priority, dates, people — without ever hiding what you wrote.

Source / Yapture Script Pick up prescription #!high #+alex #@care due:tomorrow
01Chromecapture in context
02GP.Familycoordinate care
03Agentact on structure
04Localavailable offline
The model

Four terms. Everything builds on them.

01
Yap

One line of work.

02
List

A shareable collection of yaps with permissions.

03
Script

The way you type structure: #!high, due:friday, #+alex.

04
Client

Any place a list shows up: web, Chrome, Slack, Discord, desktop, an agent.

Local first

Works on the train. Syncs at the station.

Changes persist on the device and reconcile when connectivity returns. No data leaves your machine until you choose to share the list.

Inspect the list primitives
On your device

Lists work offline. Edits save locally with no round-trip.

Pending sync

When connectivity returns, queued changes reconcile automatically.

Synced

Every connected client sees the same list. Conflicts resolve deterministically.

From outcome to daily work Preview

Build a system around the goal.

A useful goal is more than a label. Connect it to routines, time you actually have, portable tasks, and a policy for choosing what deserves attention today.

  1. 01
    OutcomeThe result and horizon you define.
  2. 02
    PracticeRepeatable behavior, not an opaque streak.
  3. 03
    AvailabilityLocal windows before calendar connection.
  4. 04
    Portable workReadable Script and inspectable structure.

The builder is a local reference recipe. It does not connect a calendar, create account data, or claim a finished routine-management surface.

GOAL SYSTEM / INTERACTIVE RECIPE LOCAL ONLY · PREVIEW
STAGE 01 / 07

Name the outcome.

The goal remains a readable sentence. Yapture adds a stable reference and horizon without replacing your language.

PORTABLE REF#^run-a-comfortable-5k
Run a comfortable 5K · 4 routines · 3 local windows
Personal AI ranking Case study

AI that learns how you work — and stays yours when you leave.

Four visible weights coalesce into one policy for the goal you wrote. A deterministic decision layer explains the recommendation. No schedule, reorder, or agent action is executed here.

Your policy. Fully auditable.

LOCAL DECISION MODEL / MAUT/1 NO NETWORK · NO ACTIONS
TUNE WHAT MATTERS100%
50%
5%
15%
30%
YOUR
POLICY
RECOMMENDED NOW

Complete tempo intervals

Goal impact is the strongest contribution under your policy. Every scored attribute has accepted evidence.

72score96%confidence

Complete tempo intervals is recommended with score 72 and 96 percent confidence.

AI Control Panel

Drag the sliders to change how tasks are ranked. The list re-sorts in real time.

Weights
Learn from my behavior
Ranked tasks
  1. #1
    Review launch blockers
    0.82
  2. #2
    Fix login bug
    0.75
  3. #3
    Draft release notes
    0.62
  4. #4
    Book the launch room
    0.58
  5. #5
    Update API docs
    0.50

This model is stored on your device. Export it as JSON anytime — it works without Yapture.

Powered by AI
Teams

People and agents share one list — with different keys.

Account teams and capability-based lists solve different onboarding problems. Both need visible roles, provenance, and an audit path.

Coming soon Read the capability model
Role Can Access
Owner Create, edit, delete, share, govern Capability or account
Editor Read, create, edit Explicit grant
Agent Read, create within scope Policy + permission
Viewer Read only Read-only token
Release ledger

Product truth has a history.

The changelog records features, fixes, and maturity transitions openly.

sitelaunch

Site v2 foundation milestone

The site v2 foundation reframes Yapture around zero-friction starts, portable text, and one truth across clients.

clirelease

CLI v2 implementation milestone

CLI v2 architecture reached an internal milestone; public packaging and distribution remain verification pending.

View the complete changelog

Keep the meaning. Change the client.

Write one line. Use it in the full app, a browser extension, Slack, Discord, or your own product.