sitelaunch
Site v2 foundation milestone
The site v2 foundation reframes Yapture around zero-friction starts, portable text, and one truth across clients.
Developers
Ship lists, parsing, and sync without rebuilding them.
Yapture's parser, list engine, and permissioned API are packages you can adopt one at a time. GP.Family built a family-care product on them; the case study shows the seams.
$ 201 Created
{
"ref": "yap-7k2x",
"ownerCode": "yap_oc_••••••••"
} Choose an outcome
Start with what you want to build.
01
Start an agent inbox without sign-up Create a permissioned list, add a task, and hand the capability to an agent.
POST /v1/lists 02 Parse and render Script Turn a line of text into structured fields (priority, due date, assignee) that every client reads the same way.
YaptureNLP.parse(line) 03 Build a goal system Compose goals, recurring tasks, calendar proposals, and local-first lists into a domain app.
GoalEngine.rank(tasks) 04 Add AI-powered task ranking Use your priorities and evidence to rank tasks deterministically. The model is yours to inspect and export.
rankTasks(weights) 05 Extend the ecosystem Add a domain layer without forking the shared task language or the local-first list engine.
yapture.app.json No-account quickstart
Give an agent a readable inbox before you create an account.
Nothing runs on page load. When you make the list live, Yapture returns an owner capability that stays masked until you reveal or copy the handoff.
Interactive / capability-safe
Start here. Sign up later.
Shape a useful list locally, then make it live only when you choose. No account required; the owner capability is still authorization.
LOCAL
- 01local
- 02local
- 03local
Everything here is local
No requests have been made.
No account required. The returned owner capability authorizes clients and agents.
Local sandbox ready. Nothing has been sent.
No request fires on page load. Live creation uses the current preview API. Read the security model
Packages
Choose the smallest useful layer.
These are the same packages GP.Family uses in production. Framework and domain presentation stay with your product.
01
Read the GP.Family case study @yapture/nlp Parse and render Yapture Script in any runtime. import { YaptureNLP } Docs 02 @yapture/script-ui React and Solid components for task badges, compose input, and list rows. <TaskBadges badges={…} /> Docs 03 @yapture/lists Local-first list state, persistence adapters, and sync. import { createList } Docs 04 Yapture AI AI-powered task ranking — the model is yours to inspect and export. rankTasks(weights) Docs 05 REST API Create lists, manage tasks, issue permissions, and connect agents. registerApp(manifest) Docs Principles
How the packages are designed.
- The text you typed stays readable. People can understand a task line without the parser, and every structured field traces back to the original sentence.
- Useful work begins before a network round trip. Lists, parsing, and scoring all run locally first. Sync happens when a connection exists, not as a prerequisite.
- Missing data stays missing. Decision demos and scoring never invent evidence to look complete. A field the user did not write does not appear.
- A score never broadens a permission. Agents and automated clients operate within the scopes you granted. Ranking can suggest; only a person can escalate.
Release ledger
The contracts move in public.
Follow package, client, and API changes from the same release ledger the product site uses.
clirelease
CLI v2 implementation milestone
CLI v2 architecture reached an internal milestone; public packaging and distribution remain verification pending.
One line is enough to begin.
Start with the parser, the API, or the full list engine.