Glossary

Terms used in a particular sense here. Where the sense differs from the everyday one, that is noted.

Product

Acceptance criteria — The checkable conditions inside an Intent that would make the work done. What a reviewer maps evidence to.

Active team — The team currently shown in the interface. You may belong to others; one is active. See Companies and teams.

Board column — A status in a team’s workflow. Columns are the status vocabulary, not a grouping over a fixed set. Configured per team.

Company — The top of the hierarchy: teams, members, billing identity. A stronger boundary than a team — crossing it destroys the local replica.

Context bundle — One markdown document holding a task, its confirmed Intent, discussion and eligible linked-document references, with every part’s source named. See Context bundles.

Intent — The approved, versioned agreement about what a piece of work should accomplish. Not a description field. See Intent.

Issue reference — The human-readable identifier, like ENG-42. Scoped to a team, so two teams can each have one.

Non-goal — Something an Intent explicitly does not cover. The part everyone skips and then argues about.

Possibly stale — An advisory signal that the issue has moved since its Intent was approved. Never blocking. false does not prove freshness — it also covers “could not establish”.

Revision — One version of an Intent. Approving stamps a number, an approver and a time. An approval does not follow later revisions.

Saved view — A personal named view within a team, retaining filters and supported display settings; Search views also retain query, scope and sort. See Filters and saved views.

Space — A team-scoped container of Vault pages, with its own membership and roles.

Spotlight — The ⌘K search-and-command box. See Search and Spotlight.

Team — The unit that owns work, and the boundary the sync engine routes on. Stronger than the everyday sense of the word.

Vault — The documentation layer: spaces of pages, co-edited in real time.

Review

Evidence — Material supplied with a change that speaks to a requirement. Not the same as proof — see Evidence and unknowns.

Open question — A specific unresolved matter that can be named. Distinct from an unknown.

Provenance — The record of where a claim came from, and who changed what based on which action.

Source reference — A pointer to material a reader can open. Not an assertion that the material establishes the requirement.

Unknown — Something that could not be established either way. Stated rather than omitted, because silence reads as “checked and fine”.

Platform

Cold start — The path where the client has no usable local data and streams everything from the server.

Conflict resolution — Deciding the result when two clients change the same thing. Per field for issues; per character for Vault text.

Cursor / replay position — The highest change a client has durably applied to its local replica, per team. Not “what a tab saw”.

Local replica — The relational database in your browser holding your company’s data for your teams. Not a backup.

Local-first — Supported work uses a local replica and durable queue before server delivery. The interface can show optimistic changes before local persistence finishes. See How sync works.

Operation log — The durable queue of changes not yet accepted by the server. Survives refresh and restart.

Rebootstrap — Discarding local data for a scope and re-downloading it. Triggered when the replay gap is too large, or the data shape changed.

Replay — Applying the changes a client missed while disconnected, from its recorded position forward.

Sync scope — The boundary events are routed on. In Orneos, the team.

Warm start — The path where local data exists and matches the current shape, so the client replays missed changes instead of re-downloading.

Access

MCP — Model Context Protocol. The standard used for the two read-only agent tools under development. See MCP surface.

Personal access token — Work in progress: a credential identifying a person, with explicit scopes, carrying no company or team of its own. Its separate implementation is not included in this app snapshot. See Personal access tokens.

Scope (on a token) — What a token permits, such as context.read. Checked before any lookup.