Skip to main content

Glossary

SABLE​

The agency operating agent and app: project memory, scoped answers, meeting extraction, approvals, and connector automation.

Spine​

The owned project data model in Supabase: orgs, clients, projects, people, sources, decisions, promises, tasks, documents, approvals, feedback, and audit.

Source​

A provenance record for a meeting, email, document, or manual input. Fathom meeting transcripts are stored in sources.body; metadata lives in sources.metadata.

Approval​

A proposed action waiting for human review. Approvals live in the approvals table and can move from pending to approved, executing, executed, failed, or rejected.

Act Layer​

The propose-approve-act loop. In v1 it turns Fathom-derived action items into pending Asana task proposals, then executes approved proposals through a gated Edge Function.

Cockpit​

Portfolio-level view for status, hours, promises, and delivery risk.

Project Hub​

Project-level view for a client/project: decisions, promises, tasks, docs, people, and source context.

Ask SABLE​

Scoped chat over the spine and retrieved document excerpts. It is read-only and should answer only from data the signed-in user may see.

Outcome Engine​

The pricing/scoping surface. The current slice uses Supabase project metadata and Toggl hours to produce comparable-hour estimates and scope signals.

CMA​

Claude Managed Agents. The original demo uses CMA memory stores and agents to render the board, draft responses, and show the "board lands without a laptop" flow.

Edge Function​

A Supabase-hosted function under sable-agents-demo/supabase/functions. These run connector logic and hold server-side secrets.

Operator Switch​

An environment secret that must be set before a write path can run. Example: ASANA_ACT_WRITES_ENABLED=true.

Model Role​

A named function (chat, extract, board, embed, rerank, ...) that resolves to a specific model id, rather than a hardcoded model id at every call site. Rolling a model to a new version is then an environment-variable change (SABLE_MODEL_<ROLE>), not a code deploy. See AI Providers Reference.

Prompt Owner​

The SABLE_PROMPT_OWNER allowlist (currently Lindsey Cutts and Kirk Orrick) that alone may promote or roll back the live agent prompt and approve prompt/skill-update approvals — so the app never runs two competing prompts. Set identically on Vercel and Supabase Edge; a mismatch defeats the control. See Security Posture.

Learned Rule​

A standing behavioral instruction folded into the live agent prompt's "Learned Rules" block after approval, as a flat, dated bullet with no nesting. Distinct from a fact about a specific client (which belongs in Active Projects data) or a log entry (which belongs in a project note) — see Prompt Control's three-tier test for routing a candidate rule.

Watchdog​

A scheduled Trigger.dev task (sable.report.watchdog.morning/.eod) that independently verifies a board actually delivered, by reading board_runs directly rather than trusting the report pipeline's own success signal. Exists because of the July 15–21 outage, when boards silently failed to deliver for six days. See Incident Response.

Drain Loop​

The pattern behind sable.fathom.reconcile and sable.email.drain: keep invoking a connector sync while it reports more work remaining, bounded by both a per-pass and a run-wide time budget, instead of one invocation per scheduled tick. Fixed Fathom's chronic staleness, which turned out to be a drain-rate problem, not a data problem. See Connector Tasks.

Paused By Decision​

A connector status distinct from broken or degraded: the code works and is tested, but a product decision turned its automatic schedule off (Drive, as of #217). Reported as a healthy run that ingested nothing, with the reason recorded in metadata — not as an unhealthy connector.

Gap-Filler Connector​

A connector, like Granola, that only contributes data when the primary source (Fathom) didn't capture it — enforced by skipping any note that overlaps an existing non-Granola meeting source within a time window, so the primary source's record always wins when both exist.

Env Manifest​

A env-manifests/*.json file tracking which environment variables a runtime needs, where, and why — names and metadata only, never values. See Env Manager Guide.

Deliverable​

A client-facing artifact (SOW draft, client readout, scope summary) that goes through drafting, QA, approval, and a separate Release action before becoming client-visible — distinct from a weekly update or scope-change memo, which publishes directly after approval with no separate release step. See Draft Workbench.

Spine Scope​

The server-derived boundary (org, then project/client membership) that determines what a given signed-in person can see. Always resolved from the verified JWT, never from a client-supplied parameter — a lead's as override still resolves through the same server-side check. See Security Posture.