Glossary supplement

The canonical glossary lives on docs.graftcode.com/glossary. This page defines terms that are missing there today; use it until those entries are published.

For existing terms (Graft, UGM, Hypertube, Virtual Feed, Graft Registry, …), see the Glossary directly.

Project Key

A JWT token issued by the Graftcode Portal when you create or open a project. It authenticates the Gateway to Graftcode Cloud and binds hosted modules to your project.

How to use:

CLI: --projectKey <jwt>
Environment variable: GC_PROJECT_KEY (overrides CLI)

Not the same as: the Registry URL shown on the dashboard (see below).

Project ID (`pid`)

A stable identifier embedded inside the Project Key JWT. The Gateway extracts it at startup and uses it to build the project-scoped Graft Registry path.

Registry URL (Graft Registry address)

The package-manager feed URL where generated Grafts are installed from. Pattern:

http://grft.dev/{projectId}__graftcode

When running GG without a Project Key (local / anonymous mode):

http://grft.dev/{auto-generated-guid}__free

Dashboard vs feed: The Portal shows a stable registry address for your project. The Project Key is the credential; the Registry URL is where npm, NuGet, pip, etc. install Grafts from.

See: Project Key and Registry URL

noVersioning

A Gateway CLI flag (--noVersioning) that disables version-based module identity. Instead, GG appends a hash to the module identity in the Unified Graft Model. Useful when you do not maintain semantic versions on assemblies/packages during development.

See: Module versioning and noVersioning

Stateless execution

Each method call is independent; no server-side object lifetime is retained between calls. Recommended for edge clients and MCP. Can be influenced by interface design (static methods) and by GraftConfig.stateless on the caller side.

See: Stateless vs stateful execution

Stateful execution

Object instances, callbacks, events, and delegates can span multiple calls over a persistent Hypertube session. Required for rich domain models but needs session stickiness when load-balanced.

See: Stateless vs stateful execution

GG_DEBUG

Environment variable. Set to 1 or TRUE to log incoming and outgoing byte traffic on the Gateway console. Used for low-level protocol debugging.

See: Debugging runbook