Glossary
Canary
Canary is gloria.dev’s first shipping tool for dependency monitoring. It discovers dependencies, checks them on a schedule, and notifies the owner when something changes; see Canary.
Check run
A check run records the result of one coding standard check on a change or file set. It gives teams a quick pass or fail signal; see Coding Standards.
Coding Standard
A coding standard defines one expected way to write code or content. It groups related rules and checks in one place; see Coding Standards.
Cost evaluation
Cost evaluation is the derived state that shows when a dependency’s cost moves above expectation. It is based on check results and expected cost behavior, not manual input; see Concepts.
Dependency
A dependency is an internal system or external SaaS service that a project relies on to operate. It is the core unit Canary documents, checks, and notifies on; see Concepts.
Doc Holiday
Doc Holiday is the documentation layer of gloria.dev. It organizes publications and conversations around requested documentation work; see Overview and Concepts.
Drift ledger
A drift ledger records where current behavior drifts from the intended standard. It gives the team a running view of gaps to close; see Coding Standards.
External SaaS
An external SaaS is a dependency kind for a vendor service a project relies on. It is one of the two kinds described in Concepts.
Feature
A feature is a named capability in a project’s feature map. It helps teams track what the product offers; see Features.
Feature Map
A feature map lists a project’s features in one place. It helps teams review the current set of capabilities; see Features.
Health check
A health check is a defined check registered for a dependency, not a free-form note about its condition. It can be an HTTP probe or an authenticated service-specific check; see Health Checks.
Internal System
An internal system is a dependency kind for a system the project owns or runs itself. It is one of the two kinds described in Concepts.
Marketplace
A marketplace is a source of skills. gloria.dev supports official system skills, organization-authored skills, and external marketplaces; see Skill Library and Concepts.
MCP server
The MCP server is the bridge between the coding agent and gloria.dev’s hosted services. It carries structured results into the platform and keeps the shared record current; see Skills and MCP.
Project
A project is the unit of registration and authentication context for dependency, document, and health check work. It owns the dependency inventory, documents, health checks, and settings; see Concepts.
Rule
A rule is one expectation inside a coding standard. It gives the team a clear yes or no check; see Coding Standards.
Skill
A skill is a versioned, shareable coding-agent instruction collected in the Skill Library. Skills run inside the agent and turn source into structured findings; see Skills and MCP.
Snippet
A snippet is a short reusable example that shows the right pattern to follow. It gives teams a quick reference for applying a rule; see Coding Standards.
Status evaluation
Status evaluation is the derived state that comes from dependency checks and results, not a manual setting. gloria.dev compares current behavior against expected behavior to decide whether a dependency is down, degraded, or otherwise out of line; see Concepts.