reference · platform overviewPublicVersion current

ClearPoint glossary

Use these definitions to interpret ClearPoint documentation consistently and to understand the limits attached to evidence, policy, and verification language.

Scope

This glossary defines the preferred terms used across ClearPoint Docs. Product behavior, access, and proof state still come from each page's approved source.

Reference

action path

The exact route from an authority decision through a policy-enforcement point to an observed target effect or non-effect.

Usage: Bind claims to one named path; evidence from one route does not cover another route.

agent

A software system that can use a model and tools to perform work toward a defined objective.

Usage: Do not imply autonomy, certification, or enforcement unless the source evidence supports it.

agent owner

The person or team accountable for an agent's purpose, access, operation, and retirement.

Usage: Use a role name instead of user when accountability matters.

Agent Passport

A Meridian-owned workforce record of an agent's identity, declared capabilities, policy attachments, certification status, and available runtime posture.

Usage: A passport is evidence to review, not a safety or compliance conclusion; do not confuse it with an Anchor-signed artifact envelope.

audience

The reader tier allowed to discover and read a documentation page.

Usage: The supported values are public, customer, developer, internal, and partner. Publication stays fail-closed when a tier cannot be enforced.

audit evidence bundle

A scoped package of evidence prepared for review against a defined question, time range, and subject set.

Usage: Do not describe a bundle as proof of compliance by itself.

check

A bounded action that compares an observed result with an expected result.

Usage: Name the condition being checked and the expected result.

ClearPoint Docs

The ClearPoint Logic documentation portal.

Usage: Use this reader-facing name. Use Docs Portal only when discussing the implementation surface.

ClearPoint Logic

The company and parent brand.

Usage: Use the full name on first meaningful reference. Use ClearPoint afterward when the meaning is unambiguous.

enforcement confidence state

The evidence-bounded confidence label for one action path: enforced, gateway-enforced, telemetry-verified, attested, or unverified.

Abbreviation: ECS

Usage: Use exactly one of the five labels and never promote above the current claim ceiling.

evidence

A record or artifact that supports a bounded statement about an action, state, or control.

Usage: Name the scope, source, time, and proof state when they matter.

identity provider

A system that authenticates people and supplies identity information to a service provider.

Abbreviation: IdP

Usage: Write identity provider (IdP) on first use in general-audience prose.

implementation classification

The current delivery classification for a claim: verified implementation, fixture-only proof, documented capability, target architecture, or unsupported claim.

Usage: State the classification separately from the proof state and block publication of unsupported claims.

interface path

The ordered controls or destinations a person uses to reach a result in an interface.

Usage: Name exact interface labels when the path is part of a supported procedure.

mandatory policy-enforcement point

A separately authorized control that every in-scope invocation must traverse before the target action can occur.

Abbreviation: PEP

Usage: Do not call a point mandatory until alternate routes are closed or proven unable to create the same effect.

policy envelope

A versioned set of boundaries for an agent, including data scope, action scope, approval requirements, and output handling.

Usage: Distinguish configured policy from runtime enforcement evidence.

proof state

The bounded maturity statement supported by current evidence for a claim or workflow.

Usage: Keep proof state distinct from implementation classification, ECS, and a release status.

source anchor

A durable reference from a portal page to the source that owns the documented fact or behavior.

Usage: Expose it through page metadata, not as internal process narration in reader prose.

tenant

A customer's isolated ClearPoint data and access boundary.

Usage: Use workspace for the reader-facing place where people work. Use tenant when the isolation boundary is the subject.

user

A person who interacts with a ClearPoint product or service.

Usage: Prefer a specific role name when the person's permissions or responsibilities matter.

verification

A check that presented evidence or state matches a defined rule or source.

Usage: State exactly what was verified. Do not turn a verification result into a broader conclusion.

workspace

The customer-facing ClearPoint environment where members access their organization's product surfaces.

Usage: Prefer workspace in instructions unless the tenant boundary is technically relevant.

Constraints

These definitions do not establish product behavior, entitlement, control effectiveness, certification, or compliance. Each documentation page remains bounded by its source and stated evidence.

Examples

The usage note under each definition shows how to apply the preferred term without broadening its meaning.