store

Using the store

store is one server holding several collections — separate lists, each with its own fields. The collections are todos, things, bookmarks, reading, and watch, plus — for tracking my work across projects — projects and initiatives. More can be added without changing these tools.

There are six tools, and they never change no matter how many collections exist:

Tool	Use it to
store_guide()	Read this guide. Call it first, before anything else.
store_describe(collection)	See a collection's exact fields, types, and allowed values.
store_add(collection, data)	Add one record. data is an object of field → value.
store_update(collection, id, patch)	Change fields on an existing record.
store_remove(collection, id)	Delete a record (soft — recoverable).
store_query(collection, search, all, limit)	Read records.

The one rule that matters most

Do not guess field names. Each collection has a fixed set of fields. If you are unsure what a collection accepts, call store_describe(collection) — it is cheaper than a failed write. Sending a field that doesn't exist (e.g. a made-up priority or urgent) will be rejected; when that happens, read the error, it names the valid fields, and retry once with a correct field. Do not loop.

Don't smuggle an unsupported concept into another field. If the user asks for something a collection simply doesn't model — a todo's priority, importance, or urgency — do NOT write the word into notes (or any other field) to fake it. That silently corrupts the data. Instead tell the user plainly that this list doesn't track that. A todo has no priority concept; its only states are open and done.

Which collection?

Every request maps to one collection. Route by what the user wants to do:

• Something small to get done, remember, or act on → todos.
• A physical object and where it's stored → things.
• A link or item to read / watch / keep → the distractor triple below.
• A larger thread of work on a project — building a feature, writing an article, a research effort, a hardware build — or when I ask what I'm working on, my backlog, priorities, or focus → initiatives (with projects as the list of projects they belong to). The line vs todos: a todo is one small task; an initiative is a bigger body of work with its own lifecycle and a home project. "Call the dentist" is a todo; "Add offline mode to the mobile app" is an initiative.