Glossary

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

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

Project Architect, The orchestrator chat that drafts your gates from your idea and documents.

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.”

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.

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

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

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

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

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

Pooled tokens, The shared monthly token allowance across an org (50M per Pro seat).

Credits, Prepaid dollars that cover Pro overage beyond the pooled tokens.

Auto-reload, A low-balance alert with a one-click credit top-up.

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