Glossary

Organization, The account that owns projects, members, and the plan. Credits pool across it.

Project, One product you’re building; owns its gates, artifacts, library, and memory.

Project Architect, The orchestrator chat that helps you define your idea, then drafts your gates from it. Available on Trial and Pro.

Conceptualization, The Architect’s opening phase: it asks how defined your project is and, if the idea is still rough, consults with you to sharpen it before drafting the brief.

Gate, One of the ten steps. Produces an artifact and a document; reads from earlier gates.

Artifact, A gate’s structured output (features, schema, risk register, …).

Blueprint, The full set of committed artifacts and documents, your product’s “constitution.”

Feature, Something the product does, from the user’s point of view.

Functionality, A buildable unit of work under a feature; what the CLI tracks to done.

User story, A user-facing description of value, tied to features and functionalities.

Staleness, The flag on a downstream gate when something it read was changed upstream.

Commit gate, The rule that a gate must be complete before it can be committed and unlock the next.

Version, A published, frozen snapshot of the spec (v1, v2, …). Your agent reads a version, never a moving draft.

Amend, The “Update current sprint” flow: batch changes to a published spec, committed atomically as the next version.

Ledger, The local .cubedot/ record of each functionality’s build status.

MCP, Model Context Protocol; how your coding agent reads the blueprint.

PM Hub, The read-only project view of build reality: statuses, verification badges, deviations, field notes.

Devchange, Off-spec work captured via cubedot devchange, tracked without polluting the spec.

Deviation, A recorded, intentional departure from the spec, with its own lifecycle (accepted, resolved, deferred, reopened).

Field note, A small observation written back from the build.

Report, The record of what happened during a chunk of work, written back from the build.

Write-back, Progress, reports, notes, and deviations written from the CLI into the knowledge graph.

Verification, The opt-in pass where a Verifier agent checks built work against its acceptance criteria.

Seat, One accepted org member; the per-month billing unit on Pro.

Credits, The unit usage is measured in (one credit covers 400 AI tokens). Pooled across the org; 5,000 per Pro seat per month.

Top-up pack, A one-time purchase of extra credits (Pro). Spent after the monthly pool; carries over.

Trial, The 30-day plan every new account starts on: 2,500 credits, once, with full feature access for one person.

Comp, An admin-granted free Pro (no charge, no blocking).