Knowledge BaseCore Concepts
Core Concepts
This page standardizes the external nouns for MergeSafe. It keeps docs aligned with the audited product model and avoids drifting back into older scanner-first or capability-first language.
Project and Domain
- Project
- The primary boundary for domains, tools, pack versions, analytics, and health. Project creation also generates a project key.
- Domain
- A hostname allowlist entry attached to a project and used for origin-based runtime access control. Multiple domains per project are supported.
Careful claim
Domains should be documented as allowlist entries, not as proof of ownership. The current docs truth does not confirm a formal domain-verification flow.
Tool, Binding, and Pack
- Tool
- The main external noun for something a user creates in MergeSafe. Docs should default to tool rather than capability or legacy tool language.
- Binding
- The execution strategy attached to a tool. The supported publishable families today are HTTP and Hook.
- Pack
- The versioned published release bundle for a project. Use pack as the release-level noun in docs.
Artifact, Version, Active Version, and Current Artifact
- Artifact
- The signed JSON output for a specific pack version. This is the concrete file the runtime downloads.
- Version
- The numeric publish sequence assigned when a new pack is created.
- Active Version
- The currently live version for a project. Runtime pointer resolution follows the active version.
- Current Artifact
- The artifact file belonging to the active version. The UI uses this term even though it is not a separate first-class backend model.
Tool Health, Analytics, Capability, and Verification
- Tool Health
- The rolled-up operational view of tool behavior after publish, including success and failure visibility.
- Analytics
- Raw and rolled-up runtime events used for usage visibility and health reporting.
- Capability
- A richer internal runtime or publish representation derived from tools. Use it carefully in docs and do not make it the main external noun.
- Verification
- A qualified concept. Schema and telemetry-related verification is evident, but docs should avoid overclaiming a separate mature execution-time verification engine for HTTP or Hook runs.