§ Reference

Glossary.

Terms used across the app and these docs.

The vocabulary used by the app and across these docs. Sorted alphabetically.

Address book #

Workspace-scoped list of frequently-invited external contacts. Adding someone here doesn't grant access — it just pre-fills the stakeholder invite form. See Address book.

Amendment #

A formally proposed change to a locked phase. Captured as a queued item, requires owner approval, writes an entry to the audit log when accepted. Use this when material has shifted after lock — a regulatory ruling, a stakeholder pivot, a missed dependency.

Brief (Product Brief) #

The output of phase P-03. A consolidated narrative that fuses the vision and the feature list into one document — the source of truth that downstream phases (design, architecture, etc.) read from.

Conflict check #

The AI pass that runs when you accept a wish. Compares the wish against other open wishes (and the feature list, if accepting on the features phase) and surfaces likely overlaps so a single idea isn't merged twice. Optional tag carried through to the merge step. See Wishes.

CUI #

Controlled Unclassified Information. A federal classification level applied to certain knowledge base entries. CUI entries are gated by per-entry grants, not workspace role.

Department #

The owning function for a phase, and a tag carried by every member, wish, and stakeholder. Departments are per-workspace — owners and admins manage the list under Settings · Departments. The default seed covers the seven phase-owning functions plus system for fully automated phases.

Owner / Admin / Editor / Viewer / Stakeholder #

The five workspace roles. Owner is the immutable safety hatch (cannot be removed, full control). Stakeholder is the read-and-file-wishes role for embedded external reviewers who need an account; ad-hoc external reviewers should use the per-project stakeholder portal instead. See Team & invites for the full permission matrix.

Handoff #

Phase P-08. The automated step that compiles every section into the single spec.md file an agent will read. No human input — it just bundles.

Knowledge Base (KB) #

Workspace-scoped library of reusable spec fragments — finished specs, brownfield captures, or scaffolds. See Knowledge Base.

Lock #

The action that freezes a phase. Downstream phases only trust locked content. Locking is reversible; unlocking triggers regeneration of dependent AI-drafted sections.

Merge into section #

The AI-assisted step that folds an accepted wish into the spec. Renders a field-level diff for review; only writes when you click Apply changes. Distinct from accepting — accepting moves a wish out of the inbox; merging changes the spec. See Wishes.

Phase #

A structured chunk of the spec, owned by one department. SpecGraph has nine phases (P-01 through P-09). See Phases.

Project #

The unit of work. One project produces one spec. See Projects.

Restricted project #

A project whose visibility ignores workspace-wide editor / viewer access — only the project's allowlist can see it. Workspace admins still have access. Used for sensitive engagements.

Spec / spec.md #

The single Markdown file produced by phase P-08, designed to be read once by an AI coding agent.

Stakeholder #

Two distinct things share the name:

  1. The stakeholder workspace role — a member account with read access and the right to submit wishes, but no spec-edit power.
  2. A per-project stakeholder — an external reviewer with a private 14-day portal link and no account. Managed from the project's Share panel.

Context disambiguates: if it's on the team page, it's the role; if it's on the project Share panel, it's the portal.

Tier #

The category of AI use case (interview, enhance, content, file, default). Code asks for a tier; the factory resolves it to a model. See AI & models.

Wish #

A cross-department request — a feature, constraint, or concern — tagged with a phase, a department, and a priority. Filed by org members from the project's wish panel or by stakeholders from their portal. Owners triage with Accept, Defer, or Reject; accepted wishes can be folded into the spec via Merge into section. Wishes don't modify the spec until merged. See Wishes & amendments.

Workspace #

The tenant boundary. URL form: /o/<workspace-id>/.... Has its own team, projects, knowledge base entries, audit log, and AI configuration.