latticesql 1.16.5 → 2.1.0

package/README.md

@@ -24,6 +24,8 @@ Every AI agent session starts cold — no memory of what happened yesterday, wha
 
 Lattice has no opinions about your schema, your agents, or your file format. You define the tables. You control the rendering. Lattice runs the sync loop.
 
+**New in 2.1:** the GUI search box now asks the **assistant** (it answers using a full-text `search` tool) instead of running a plain text match; the assistant gains a **guarded, reversible `delete_entity`** (empty tables go immediately, non-empty tables ask what to do with the data first); new chat threads are named from a short AI summary; ingest failures are surfaced loudly instead of swallowed; and the activity feed, voice-note composer, upload timer, and live counts get a round of fixes. See [docs/assistant.md](docs/assistant.md).
+
 **New in 1.16:** the `.lattice` workspace model + auto-render, full-text search, sources/references, a workspace dashboard, a **multiplayer cloud-editing** experience (live share/de-share, "last edited by", change-flash + counts, and an offline edit queue that replays on reconnect), and a much richer **Data Model editor** in the GUI — a force-directed schema graph, bidirectional many-to-many links, and a soft-delete model where every schema change (create/rename/delete a table, column, or link) is tracked in version history and **reversible** (deletes never destroy data; revert restores it), with session-scoped undo/redo. All with no AI dependency. See [docs/workspaces.md](docs/workspaces.md) and [docs/collaboration.md](docs/collaboration.md). The AI assistant, chat, and ingest summarization are exclusive to the 2.0 line (2.0 = the 1.16 feature set plus that AI layer).
 
 ---
@@ -2277,6 +2279,37 @@ The browser's `EventSource` invalidates the entity cache on every `change` event
 
 ---
 
+## AI assistant & Context Constructor (v2.0+)
+
+`lattice gui` includes an optional **assistant rail**: a Claude-powered chat plus
+a **Context Constructor** that turns dropped files and pasted text into linked
+Lattice objects. It is **GUI-only and inert until you configure a credential** —
+the library API is unchanged and fully backwards-compatible.
+
+- **Connect Claude.** Paste an Anthropic API key in **Settings → User → Assistant**
+  (or set `ANTHROPIC_API_KEY`); it's stored encrypted in the native `secrets`
+  entity. A subscription **Connect** link (PKCE) appears when the `ANTHROPIC_OAUTH_*`
+  values are set (see [`.env.example`](.env.example)).
+- **Drop files / paste text / images / URLs.** Sources become native `files` rows
+  (referenced, not copied) and are extracted — text via the optional `markitdown`
+  CLI, **images via Claude vision**, a pasted **URL crawled** for readable text —
+  then summarized with **Claude Haiku** and classified against your records, and
+  **added, enriched, and linked** automatically, **auto-creating the junction table
+  when none exists** (and a new object when a source fits nothing). All audited and
+  revertible via the version history.
+- **Inference Aggressiveness** slider tunes how much the assistant extrapolates
+  (temperature + link liberality + auto-junction/auto-create gating).
+- Runs on local SQLite and a direct `postgres://` connection; not yet in hosted
+  multiplayer team-cloud mode.
+
+The same intelligence is exposed as a **first-class library API** (inert without an
+LLM client): `organizeSource`, `describeImage`, `crawlUrl`, `enrichKnowledge`, and
+the `summarizeText` / `classifyLinks` primitives — all importable from `latticesql`.
+
+See [docs/assistant.md](docs/assistant.md) for the full guide.
+
+---
+
 ## CLI — `lattice teams` (v1.12+)
 
 Multi-user cloud-shared Lattice databases on your own Postgres. Bring your own Postgres connection; lattice handles identity (bearer tokens, email-bound invitations), the team membership table, and the sync engine (shared objects + row links + change feed + outbox + replay-guard puller).