Shared language. Explicit limits.

Working definitionA persistent identity used to refer to the same modeled concept across authored surfaces and versions, instead of representing each mention as an unrelated copy.

How current site copy uses itCurrent site copy uses the term when discussing reuse across documents, diagrams, Runbooks, SLOs, reviews, and exports.

Verify in evaluationVerify the identifier's scope, lifecycle, merge behavior, authorization rules, and behavior after rename, deletion, restore, import, and export. Stability does not by itself establish correctness or currentness.

Working definitionContent or a declaration intentionally created or confirmed by an authorized person in the authoring workflow.

How current site copy uses itCurrent site copy contrasts authored knowledge with suggestions and attributed external context so that human intent and outside observations are not presented as the same state.

Verify in evaluationVerify which actions count as confirmation, who is authorized to perform them, what provenance is recorded, and how corrections or reversals appear. Authored does not mean independently verified operational fact.

Working definitionContext about where an item came from and how it reached its current state, used to help a reader interpret its authority and history.

How current site copy uses itCurrent site copy associates provenance with human declarations, suggestions, external observations, versions, relationships, review, and export.

Verify in evaluationVerify the exact recorded fields, their source, mutability, visibility, retention, and export behavior. The presence of a provenance label does not prove the underlying source is accurate.

Working definitionReview focused on a change in modeled meaning—such as identity, ownership, lifecycle, or a relationship—in addition to edited text or diagram geometry.

How current site copy uses itCurrent site copy uses the term for reviewing material changes through stable identities and explicit relationships rather than relying only on line-level diffs.

Verify in evaluationDemonstrate which change types are detected, how impact is calculated, what reviewers can inspect, and what remains outside the review. Scope may depend on the workflow and configuration.

Working definitionTopoloom's website term for a connection that places attributed external context beside authored declarations for comparison and possible human action.

How current site copy uses itCurrent site copy presents a Living Binding as part of the visible boundary between authored state and observations supplied by an external source.

Verify in evaluationVerify supported sources, refresh behavior, attribution, failure and stale-state labels, permission checks, and the action required before external input becomes authored knowledge.

Working definitionTopoloom's website term for an export intended to carry readable knowledge together with structured context for inspection outside the product.

How current site copy uses itCurrent site copy discusses content, stable identities, versions, relationships, provenance, reviews, and permission mappings as areas to inspect when evaluating portability.

Verify in evaluationRequest an exact inventory of included formats and fields, inspect omissions and transformations, and open the package outside Topoloom. The package name alone is not a completeness guarantee.