Find a term. See how it works.

DefinitionA separate area for people and knowledge with its own access boundary. Each document, diagram, object, and membership belongs to one workspace; every request checks active membership there.

How Topoloom applies itTopoloom uses the workspace as the unit of tenant isolation described on the Trust page. Scope is enforced before retrieval, projection, export, event delivery, or provider access. A denial reveals nothing about whether the item exists.

Validate in your environmentVerify which lookups, searches, autocompletes, and counts are scoped by membership, and what a denied request returns. Then check whether a person with roles in several workspaces can ever see another workspace’s identifiers or titles.

DefinitionThe list of documents and diagrams a person may read in a workspace. It shows each item's type and state and filters results using current access rights.

How Topoloom applies itTopoloom’s Platform page shows the Library in a product capture, where documents and diagrams share one list beside collection navigation and a private drafts view.

Validate in your environmentVerify that the Library re-checks permissions on every page, and that a filtered or empty result reveals nothing about items you may not see. Then check how title search, ordering, and pagination behave when documents and diagrams share one list.

DefinitionAn organizational grouping of documents and diagrams within a workspace. Collections can nest up to five levels; the hierarchy organizes navigation and grants no inherited access from a parent to a child or back.

How Topoloom applies itTopoloom uses collections such as Engineering, Operations, and Team Handbook in its product captures. The Trust page’s permission rules treat a collection as one grant target, not as an authority boundary.

Validate in your environmentVerify what a person sees when they can read a child collection but not its parent. Check whether archiving or deleting cascades, and whether moving a collection ever changes who can read its contents.

DefinitionThe connected model built from what people author in Topoloom. It links documents, diagrams, blocks, declarations, reusable objects, references, relationships, and versions through stable identities.

How Topoloom applies itTopoloom uses Document Graph for the authored model that documents and diagrams contribute to. Any separate graph built downstream may match entities and attach evidence. That graph never changes authored knowledge without a command from an authorized person.

Validate in your environmentVerify which node and relationship kinds the graph exposes through public contracts, how it is rebuilt from PostgreSQL, and whether any provider or search projection can alter it. A graph-shaped model is not a graph database and does not imply canonical operational truth.

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 Topoloom applies itIn Topoloom, a document, a diagram node, a Runbook or SLO link, a review, and an export can all point to the same Payment Service identity. They are not copies that happen to share a name.

Validate in your environmentVerify the identifier’s scope, lifecycle, merge behavior, and authorization rules, then check how it behaves after rename, deletion, restore, import, and export. A stable identity does not by itself make a statement correct or current.

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

How Topoloom applies itTopoloom contrasts authored knowledge with suggestions and attributed external context so that human intent and outside observations are not presented as the same state.

Validate in your environmentVerify 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.

DefinitionA typed statement a person confirms in one document, such as a Service with an owner. It stays anchored to its source block and records identity, author, time, lifecycle, and any declared relationships.

How Topoloom applies itTopoloom shows a declaration as the first formal step in progressive formalization: readable prose gains a declaration without becoming a form. A declaration stays local to its document until an authorized person promotes it to a reusable object or links it to an existing one.

Validate in your environmentVerify how a declaration is created, edited, unlinked, and turned back into ordinary text without losing content. Check what survives collaboration, undo, restore, and export. Confirm that no analysis, import, or provider creates a declaration unless a person accepts it.

DefinitionOne shared, versioned record that documents and diagrams can point to. An authorized person changes its properties by creating a new immutable object version, leaving earlier versions intact.

How Topoloom applies itTopoloom’s Payment Service example is a reusable object. Its owner, criticality, and versions live on its object page, shown in the object capture on the Platform page. Documents and diagrams reference it by identity.

Validate in your environmentVerify that creating an object requires an explicit authorized command, and that two objects sharing a name are never merged. Check that the Used in list shows only the immutable artifact versions you are allowed to read. Ask how restricting or tombstoning an object affects existing references.

DefinitionA pointer from a document block or diagram node to one reusable object, storing the target identity and either a follow-current or a pinned version. It never copies the object’s authoritative properties into document content.

How Topoloom applies itTopoloom’s promise “Reference, don’t recopy” names this mechanism. In the product a reference is marked ↗; edit shared properties on the object page and surrounding wording separately in the document. An object update does not rewrite that wording.

Validate in your environmentVerify the difference between a follow-current and a pinned reference, and what a reader sees when the target becomes unavailable or unauthorized. Confirm that rendering, search, export, and publication re-check permission on the target each time.

DefinitionA view of declared or referenced knowledge within a stated scope. Content and Map are document modes. A Map can also explore selected sources you may read.

How Topoloom applies itTopoloom keeps each Map’s source scope visible. A Map shows knowledge from its sources; it is not a separate authored Diagram.

Validate in your environmentVerify the scope and current access to each source. Check that document Map edits use the normal save and undo path. A Map does not prove what is deployed in production.

DefinitionA standalone diagram artifact whose nodes can reference reusable objects and whose declared edges carry a typed relationship. Freeform connectors remain labeled as not declared; only an explicit semantic edge enters the relationship projection.

How Topoloom applies itTopoloom uses a semantic diagram for the payment authorization example in the version comparison capture on the Why Topoloom page. Automatic layout, when explicitly invoked, arranges geometry only: arrows, proximity, color, and layout never imply a relationship.

Validate in your environmentVerify which kinds of edge count as declared, and how visual-only connectors are labeled without relying on color. Check what an explicit auto-layout writes, and that a layout or renderer failure leaves the declared relationships unchanged.

DefinitionA way to declare relationships from a document using a form, controlled sentence, table, or tab-separated rows. Topoloom resolves the input by fixed rules and writes the resulting changes together or not at all.

How Topoloom applies itTopoloom offers structured facts beside prose selection as a second path into the same schema. Ambiguous names, stale endpoints, duplicates, and self-edges fail before anything is written; no fuzzy matching or model is involved.

Validate in your environmentDemonstrate three inputs: a batch entered from a table, an ambiguous endpoint, and a duplicate relationship. Verify that the document view shows the resulting fact groups from current state, and that undo removes the whole batch.

DefinitionAn explicitly started analysis of a saved document that proposes declarations and relationships as candidates. The current analysis applies fixed rules without calling an AI model or external provider; this does not imply offline access to the application. Candidates remain suggestions until a person accepts them item by item or in a confirmed batch.

How Topoloom applies itThe Knowledge Review capture on Topoloom’s Trust page shows the Ready, Decisions, and Represented tabs. Acceptance re-derives each candidate against the locked current document and discloses its effect before writing; nothing publishes implicitly.

Validate in your environmentVerify what triggers analysis, and whether any model or provider is called. Check how a candidate is treated when its source text changed underneath it, and that accepting the same suggestions twice creates no duplicates. Suggested is never presented as declared.

DefinitionA saved snapshot of one document or diagram that can be addressed and read without changing it. It includes content, declarations, provenance, source locations, and a content hash. Publication reads this snapshot, not a live draft.

How Topoloom applies itTopoloom’s Version 1 Baseline and Version 2 Current, compared on the Why Topoloom page, are artifact versions. An object version snapshots one shared object’s properties. An artifact version snapshots a document or diagram. Ordinary revision history records editing changes. Creating an artifact version does not itself publish it.

Validate in your environmentVerify that a published version can never be edited or cleared, and that restoring creates a new version instead of rewriting history. Check that every read re-checks the current person’s permissions, and ask how versions, object versions, and revisions differ in your deployment.

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 Topoloom applies itTopoloom records who confirmed each declaration and when. Evidence from an external provider keeps the provider’s name and the time of the check. Provenance also covers suggestions, versions, relationships, reviews, and exports.

Validate in your environmentVerify 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.

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 Topoloom applies itTopoloom compares two saved versions and describes owner, dependency, SLO, and Decision changes in readable language, keyed to stable identities rather than line positions. The comparison capture on the Why Topoloom page reports five semantic changes between two versions of one diagram.

Validate in your environmentDemonstrate 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.

DefinitionA versioned set of rules for governed publication. It combines a template, required and optional structure, validation, ownership, and review policy while allowing ordinary drafts to save.

How Topoloom applies itTopoloom ships one built-in contract, Service Overview v1. It requires a Service name and an OWNED_BY Team before governed publication, and warns when a high-criticality Service has no SLO or Runbook link. Incomplete drafts still save; general contract authoring is a later governance stage.

Validate in your environmentVerify that validation blocks governed publication only, and never an ordinary save. Check that publication evaluates the exact artifact and object versions together with an approved review. Confirm that a waiver requires authority, reason, scope, expiry, and an audit record.

DefinitionAn explicit permission for a person or group to read, edit, or manage a collection, document, or object. Each grant records a reason and an expiry or a deliberate permanent choice; PostgreSQL remains the access authority.

How Topoloom applies itTopoloom’s Trust controls describe permission-aware surfaces; access grants are the mechanism behind them. Timed grants run from five minutes to 365 days, and the database views that authorization reads enforce the expiry. No cache, worker, or browser state can turn an expired grant into an allow.

Validate in your environmentVerify the workspace role ceiling, and what happens to grants when a person is suspended, reactivated, or removed. Check that the last active administrator cannot be removed, and how an expired grant appears to a manager who may renew it.

DefinitionAn explicit mapping from a local declaration to a record identified by an external provider. It lets people compare attributed provider context with authored knowledge; it does not merge the two.

How Topoloom applies itTopoloom uses a Living Binding to keep authored state and observations from an external source visibly separate. Provider evidence keeps the provider’s name and the time of the check. The tested reference workflow uses a simulated provider; confirm any real connector separately.

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

DefinitionA scoped export that carries readable knowledge together with versioned, structured context for inspection outside Topoloom.

How Topoloom applies itTopoloom uses the term for readable content, stable identities, versions, relationships, provenance, reviews, permission mappings, and explicit loss reports that move together. Source-linked Diagram exports use topoloom.package/4; packages in formats /1 to /3 remain readable. The export capture on the Trust page shows a completed export, not the archive’s contents.

Validate in your environmentRequest 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.