Glossary
Board
A top-level workspace containing notes, optional Jira work items, and workflow phases. Boards are identified by a unique ID in the URL (/b/{boardId}).
Canvas
The spatial area within a board where note cards are positioned and dragged. The canvas has fixed dimensions (much wider than tall).
Note
A card on the canvas with a title, Markdown body content, position (x/y), colour, and optional metadata (tag, description, relationships, comments, annotations, phase).
Placeholder note
A note with isPlaceholder: true. Rendered with a dashed border and dimmed italic text to indicate suggested but missing content. Editing a placeholder clears the flag automatically.
Overlay
The full-screen editor that opens when you click or open a note. Provides WYSIWYG editing, AI prompts, comments, and version history.
Document-centric editor
The primary editing surface in the board page — a focused writing area for a single note or Jira work item. Provides richer editing than the canvas card.
IndexedDB (IDB)
The browser's built-in database. Used as the primary offline-first local store — all board state is read from IDB; network calls are for sync reconciliation only.
D1
Cloudflare's managed SQLite database. Used as the server-side sync authority. Delta sync uses version counters on all rows.
KV
Cloudflare KV (Key-Value store). Used for sessions, OTP codes, board metadata, billing state, usage counters, and rate-limit counters.
R2
Cloudflare R2 (object storage). Used for board Markdown snapshots and changelog entries — larger payloads that are read infrequently.
Push-on-mutation
Sync model where changes are pushed to the server after local mutations. Pushes are debounced and batched. No continuous polling timer.
Pull-on-focus
Sync model where the client pulls server changes when the browser tab regains focus (Page Visibility API). Rate-limited to avoid rapid tab-switching floods.
Tool-calling
AI technique where the model produces structured function invocations (tools) instead of free-form text. Each tool call is validated with a Zod schema before being applied to the store.
Progressive disclosure
Context strategy where the AI starts with a minimal prompt (just the active note) and uses tools (searchNotes, readNote) to pull in additional context only when its reasoning requires it. Keeps prompts small as boards grow.
Optimistic update
Updating local state immediately on user action, before the server responds. If the server push fails, a retry is scheduled. The UI never blocks on a network round-trip.
Version counter
A monotonically increasing integer column on D1 rows. Used for delta sync: GET /sync?since={version} returns only rows with higher versions than the client's last seen value.
Soft delete
Deleting a record by setting a deletedAt timestamp rather than physically removing the row. Soft-deleted note and Jira item IDs are included in sync responses so all clients can remove them.
Slash command
A /command typed in the note AI prompt bar that triggers a structured artifact generation skill (e.g. /generate-prd, /generate-epic).
Skill (agent skill)
A SKILL.md file defining a slash command's system prompt and metadata. Skills are loaded at build time and looked up by command name at runtime.
Phase
A stage in the PM project lifecycle (e.g. Ideation, Research, Definition, Delivery, Launch). Phases are stored per-board in KV. Notes can be assigned to phases.
Subagent
The dedicated floating AI assistant panel. Has its own conversation state, is phase-aware, and ends each response with 3 suggested next actions.
Annotation
An AI suggestion attached to a section of a note or work item. Rendered as a @subagent blockquote in the TipTap editor with action buttons.
Deferred sync
A sync mode for Jira work item edits where changes are batched in a debounce buffer and flushed to D1 on editor close or after an interval, rather than immediately.
Board owner
The authenticated user who claimed a board. Owners can invite collaborators, manage phases, and are charged for AI operations on their board (including operations by collaborators).
See also
- Architecture Overview — Diagram of how everything connects
- Storage Layers — IDB, D1, KV, R2 roles in detail
- Sync Engine — Push-on-mutation and pull-on-focus explained