# suchi

> Document management as one Go binary. SQLite-first, plugin seams, mobile wire-compat.

## Docs

- [Agent surface](https://docs.suchi.page/agents.md): Task-claim/act loop for external processes: LLM runtimes, third-party classifiers, human-in-the-loop workflows.
- [HTTP API](https://docs.suchi.page/api.md): JSON endpoints under /api/ — the surface mobile clients + agents + integrations drive.
- [Approvals](https://docs.suchi.page/approvals.md): State-machine engine for human-in-the-loop review chains, sign-offs, and timeout-driven escalation — driven by durable-outbox jobs.
- [Architecture](https://docs.suchi.page/architecture.md): Layout, data flow, design principles, SQLite discipline, CAS.
- [Automations](https://docs.suchi.page/automations.md): Trigger→conditions→actions rules that fire on document events. When a doc lands, when its metadata changes, or at consumption — one rule, N actions, all data.
- [Backend architecture](https://docs.suchi.page/backend-architecture.md): Onboarding doc for anyone touching the Go server — module boundaries, the SQLite discipline, the durable-outbox pipeline, and the auth/authz split.
- [Backup and restore](https://docs.suchi.page/backup-restore.md): What to back up, when it's safe to copy, and how to bring an instance back from bytes.
- [CLI reference](https://docs.suchi.page/cli.md): Every suchi subcommand: serve, healthcheck, import, gc, taxonomy, doctor, mcp, demo, version.
- [Comparison](https://docs.suchi.page/comparison.md): Honest side-by-side vs Paperless-ngx, Papra, and docspell — features suchi has, features they have, what's on the roadmap, what's out of scope.
- [Configuration](https://docs.suchi.page/config.md): Every knob, its default, its purpose. Env vars + optional config file.
- [Public demo instance — suchi.page](https://docs.suchi.page/demo-instance.md): Plan for hosting a read-only public suchi at suchi.page so people can click before they clone.
- [Supported file types](https://docs.suchi.page/formats.md): Every format suchi ingests, the binary it needs, and where it lands.
- [Getting started](https://docs.suchi.page/getting-started.md): Five-minute quickstart. Docker Compose, bare binary, or NAS.
- [Guides](https://docs.suchi.page/guides.md): Copy-paste walkthroughs — bootstrap, upload, dedup, fs-watch, gc, MCP wiring, external-app tokens. Onboarding kit for operators and contributors.
- [Connect an external app via API token](https://docs.suchi.page/guides/external-app.md): Mint a scoped API token from the UI (or /api/tokens/), attach it to your app, and drive the REST surface end-to-end.
- [Mail ingest via mail-intake](https://docs.suchi.page/guides/mail-intake.md): Run johnnybravo-xyz/mail-intake alongside suchi to pull IMAP attachments straight into your archive.
- [Mail ingest via mbsync](https://docs.suchi.page/guides/mail-mbsync.md): A one-command Docker stack that polls IMAP with mbsync and hands every message to suchi as .eml.
- [Connect an MCP client](https://docs.suchi.page/guides/mcp-connect.md): Wire Claude Desktop, Cursor, or a remote MCP runtime to a running suchi instance via `suchi mcp` or `suchi-mcp`.
- [Importing an export bundle](https://docs.suchi.page/importer.md): suchi import paperless — verbatim metadata, dedup, --map-jd, --auto-jd, --verify.
- [suchi](https://docs.suchi.page/index.md): Document management as one Go binary. SQLite-first, plugin seams, drop-in for existing mobile clients.
- [Johnny.Decimal taxonomy](https://docs.suchi.page/jd.md): The JD opinion, the starter tree, and the invariants that make it a schema — not a suggestion.
- [MCP v2 server](https://docs.suchi.page/mcp.md): Drive suchi from any MCP-capable agent runtime. Thin adapter, same auth.
- [Permissions](https://docs.suchi.page/permissions.md): Groups, per-object ACLs, and the Authorizer interface — Phase 6's answer to "my spouse shouldn't see my personal folder".
- [Writing a plugin](https://docs.suchi.page/plugins.md): The plugin-api surface, worked examples for each interface, and how a private distro registers your plugin at boot.
- [Pre-consume script hook](https://docs.suchi.page/preconsume.md): Operator-defined escape hatch that runs before any built-in ingest logic.
- [Privacy & encryption](https://docs.suchi.page/privacy.md): What leaves the box (nothing, unless you wire it). The encryption ladder. What suchi never logs.
- [Reference architecture](https://docs.suchi.page/reference-architecture.md): Every load-bearing design decision behind suchi, with the reasoning that produced it. Read this before proposing a large refactor.
- [Refile](https://docs.suchi.page/refile.md): The "come back and change your mind" primitive — re-run rules + re-render every live doc after a preset, template, or rule change.
- [Release process](https://docs.suchi.page/release-process.md): How suchi versions ship — commit conventions, changelog, tagging, publishing.
- [SPA architecture](https://docs.suchi.page/spa-architecture.md): Onboarding doc for anyone touching ui/ — layout, build, routing, state, design system, and the guard-rails that keep the frontend small.
- [SPA ↔ backend map](https://docs.suchi.page/spa-backend.md): Every endpoint the shipped Svelte SPA depends on, with its scope + wire shape + status.
- [Wishlist — natural-language Q&A over the archive](https://docs.suchi.page/wishlist/qa-over-archive.md): Plan for a suchi.ask surface that answers questions like "when is my car insurance due?" using the LLM classifier + FTS5 the archive already carries.
- [Wishlist — similar documents via sqlite-vec](https://docs.suchi.page/wishlist/similar-documents.md): Plan for a Detail-page "similar documents" strip + optional semantic search mode, backed by sqlite-vec embeddings.