@scribed/cli 0.1.19 → 0.1.21

package/README.md

@@ -503,6 +503,57 @@ Async work (meeting/YouTube transcriptions, automation runs) returns an id immed
 
 Four internal chat helpers are excluded from the CLI and MCP: `web_search`, `attachment_list`, `attachment_save_to_vault`, and `tool_discover`. External clients use `tools list` for discovery and the shared `agent_session_attachments_list` / `agent_session_attachment_save_to_vault` tools with an explicit session id.
 
+## Financial evidence and tax preparation
+
+The `connected-apps` category includes `financial_connections_status`,
+`financial_read`, `financial_read_export`, `financial_write` and
+`financial_disconnect`. Connect Brex, QuickBooks, Puzzle or Stripe in Scribed's
+Settings → Integrations first; provider credentials never belong in a CLI
+argument or chat. Stripe financial reads use your own restricted or secret API
+key independently of the workspace's Stripe Connect payment tools.
+
+Read status to discover the actual supported actions and current
+`connectionVersion`, then use `scribed tools show financial_read` for filters.
+Stripe supports account, balance, balance transactions, charges, refunds and
+payouts. List windows use Unix seconds with `createdGte` inclusive and
+`createdLt` exclusive; `startingAfter` is the last returned item ID when
+`has_more` is true. Creation dates need separate reconciliation to bank posting
+and payout arrival dates.
+
+`financial_read_export` uses the same arguments plus a new private Vault
+`.json` path. It saves one raw provider page and source metadata server-side,
+returns its SHA-256 and pagination, and never overwrites a file. It requires
+write scope because it creates a file; `financial_read` remains read-only.
+Keep every page and a coverage manifest before deriving annual or quarterly
+schedules. The shared agent/MCP guidance separates card settlements and Stripe
+payouts from expenses and sales, keeps unresolved reimbursements and loan
+allocations visible, and maps supporting schedules to a supplied draft form.
+An accountant package does not file a return or share private records with a
+workspace. All financial tools are interactive and unavailable to Runs.
+
+Shared financial records belong in the workspace's **Financials** table. Discover
+it through `objects_sources_list` and `objects_types_list` (`source: financials`),
+then use `financials_entries_list`, `financials_entries_import` and
+`financials_entry_review`. Imports require an explicit workspace and authorized
+sharing scope, with evidence already copied to that workspace's Drive. Drive
+files follow the Drive audience independently of manager-only Financials access;
+this path does not provide manager-only evidence storage. Preserve the source
+identity, exact original amount/units and review status. Generic collection writes
+cannot edit Financials, and tax preparation must not create a parallel ledger.
+Read one entry with `financials_entry_get` before an authorized
+`financials_entry_correct`; corrections preserve source identity, require the
+current version and retain history in `financials_entry_events`. Statement and
+reconciliation inputs have typed periods, basis and exact decimal metrics;
+computed closing balances and differences remain unknown when inputs are missing.
+
+Derive CSV, Excel and PDF snapshots from saved, reviewed Financials records:
+`objects_records_export` exports the authorized slice, `vault_office_create`
+creates a real XLSX that `vault_office_read/edit` can verify and update, and
+Documents tools draft, save and export the exact accepted revision to PDF/DOCX.
+Use Financials saved views with workspace page block tools for live page tables.
+Report period, basis, currency, source IDs, exclusions and missing coverage in
+each output. Generated files do not replace Financials as the source of truth.
+
 ## Agent integrations
 
 Use Scribed in **Claude Code, Codex, and Cursor**. Choose any combination; each
@@ -700,3 +751,29 @@ behavior. The command has fixture tests; running it against a chosen deployment
 is a separate verification step.
 
 For large Personal Notes boards, use `account_notes_list` and `account_note_get`; received shares use `account_notes_shared_list` and `account_note_shared_get`. Confirmed `account_note_create`, `account_note_update` and `account_note_delete` carry the exact board revision and preserve unrelated notes on the server. Never send a partial or truncated board to `account_notes_set`.
+
+
+### Living knowledge
+
+The shared `knowledge_base_*` tools read and manage the account's personal base
+or one explicitly selected workspace. They are available in the default MCP
+catalog and through `scribed call`:
+
+```sh
+scribed call knowledge_base_status scope=account
+scribed call knowledge_base_manifest scope=workspace workspaceId=<workspace-id> audience=private
+scribed call knowledge_base_search scope=account query="current priorities"
+scribed call knowledge_base_file scope=account revision=3 path=README.md
+```
+
+Copy the returned revision and cursor/offset for subsequent pages. File reads
+return Markdown chunks; exports return paginated JSON containing complete
+Markdown files and metadata. Preserve partial coverage and original source
+permissions. Knowledge settings, updates, corrections, cancellation and rollback
+require explicit confirmation; updates may incur the configured AI usage cost.
+A million-token output budget is spread across many steps and files.
+
+Brain Build's local computer knowledge is separate. External AI can query its
+native local MCP server; the Scribed private device relay is not exposed through
+this CLI or hosted MCP. Connecting a device requires approval in Settings and in
+the native Brain Build app.