Blob

A compressed file in the spec version history, identified by its content hash.

Commit

A snapshot of a spec at a point in time, with a message describing what changed.

Constitution

A document defining the rules, guidelines, and conventions for spec authoring in your organization.

Role

A space member's functional role: Developer, Testing, Product Owner, or UX.

Draft

Captured content from the Chrome extension that has not yet been turned into a spec. Drafts expire after 6 hours.

Epic

A top-level spec type for large, cross-cutting features. Epics cannot have a parent spec.

Organization

Your company's SpecBridge account. On Cloud, each organization gets its own isolated database and its own plan/billing. On a self-hosted Enterprise deployment, there's implicitly exactly one. Not the same as a Tenant — see below.

Project

A delivery unit that tracks work across specs and can link to Git repositories.

Ref

A pointer to the latest commit for a spec, used to track its version history.

Space

An organizational unit within a tenant, like a team or department. Has a short code and a mode (sprint or backlog).

Spec

A specification document with a type (Epic, Story, Task, or Subtask), lifecycle status, version history, and comments.

Staging Area

Where spec files are prepared before committing — lets you choose what goes into the next snapshot.

Story

The default spec type, representing a user story.

Super Admin

(Cloud only) A platform-level operator role that manages SpecBridge Cloud itself — organizations, billing, platform audit log — separate from and outside any single organization's own roles.

Task

A spec type representing work items, typically a child of a story or epic.

Tenant

A workspace inside an organization — a second, nested layer of isolation for splitting up teams or business units. An organization can contain multiple tenants; each tenant has its own isolated users, spaces, projects, and specs.

Tenant Owner

A user with elevated permissions who can manage spaces, members, and sprints within a tenant.

Tree

A structure that maps file paths to content hashes in the version history.

VCS (Version Control System)

The system that tracks spec file history, letting you see what changed, who changed it, and go back to any previous version.