Meaning Governance Glossary

These terms form the canonical working vocabulary of WikiSure Semantic Governance. Canonical concept identity and governed relationships stay unchanged across languages.

Apply glossary concepts in AI consulting

These checklists and templates apply existing concepts. They are not synonyms or additional canonical concepts.

AI advisory by SynsureTech: from strategy and business model to a traceable decision

AI pilot readiness checklist — AI Readiness, Evidence coverage & gaps, Applicability — where this applies
Tools for AI consultants: choosing AI assessment software — WikiSure Case Studio, AI Readiness, Governed decision basis
AI readiness assessment template for client reviews — AI Readiness, Applicability — where this applies, Evidence coverage & gaps, Source provenance & traceability
AI assessment report template: hand over recommendations and evidence — Governed decision basis, Source provenance & traceability, Governance decision & decision trace
Policy and procedure review: examine conflicts before AI implementation — Semantic Drift, Applicability — where this applies, Source provenance & traceability, Governance decision & decision trace

Semantic Governance

The discipline of defining, approving, and maintaining the meaning of business terms so every human, system, and AI agent interprets them in a governed context.

Semantic Governance treats meaning as enterprise infrastructure. It establishes who owns a term, how its definition is approved, how that definition evolves, and how reuse, drift, and contradiction are detected over time. Unlike data governance — which focuses on data quality, lineage, and access — semantic governance focuses on the interpretation layer that sits above data.

Example. When the Claims, Underwriting, and Reinsurance departments each use the word "Coverage," Semantic Governance ensures their distinct meanings are recorded as separate canonical concepts within the same Meaning Space, rather than collapsed into a single ambiguous definition.

Semantic Drift

The unmanaged divergence of a term's meaning across teams, systems, time, or AI models.

Semantic Drift is the silent failure mode of enterprise knowledge. It accumulates whenever a definition is restated, translated, summarized, or interpreted without governance. Left unmanaged, drift causes contradictions in reports, breaks integrations, and produces incoherent AI behavior even when underlying data is correct.

Example. In 2024 a definition of "Customer" is approved as "any party with an active contract." By 2026 marketing uses it for anyone in the CRM, finance uses it for billed parties only, and an AI agent has learned both — producing conflicting answers to the same question.

Meaning Space

A Shared Meaning Space — a bounded, governed context where humans, systems, and AI agents resolve a term to the approved meaning that applies in that context.

A Meaning Space (also called a Shared Meaning Space on first use) is the unit of contextual scope in Semantic Governance. The same surface term can exist as several distinct Canonical Concepts inside one Meaning Space (e.g. Insurance) when it carries different meanings in different sub-contexts (Claims vs Reinsurance). Multiple valid meanings coexist by design — Meaning Spaces make that ambiguity addressable instead of invisible, and give people, systems, and AI agents a shared, governed context to resolve against rather than collapsing every team into a universal definition.

Example. The Insurance Meaning Space contains five distinct canonical concepts for "Coverage": Policy Scope, Claims Limit, Reinsurance Cession, Product Offering, and Regulatory Control Coverage.

Canonical Concept

The single approved, versioned, owner-accountable meaning of a term within one Meaning Space.

A Canonical Concept binds together: a context-disambiguated name (e.g. Coverage (Claims Limit)), a canonical definition, a governance status (proposed, reviewed, approved, deprecated), a confidence score, and a provenance trail. It is the unit that humans approve, systems resolve to, and AI agents cite.

Example. "Coverage (Reinsurance Cession)" — the share of risk transferred from the primary insurer to a reinsurer under a treaty — is one Canonical Concept; "Coverage (Claims Limit)" is a different one.

Source provenance & traceability

In plain language: Source provenance & traceability

Common discovery terms: source provenance, source traceability, evidence traceability

The recorded source, author, and context of every definition that contributes to a Canonical Concept.

Provenance answers: where did this meaning come from? Each ingestion records the raw term, raw definition, submitting department, source document, industry, resolver source (deterministic, context rule, AI, or organizational memory), resolver confidence, and context label. Provenance turns canonical definitions from claims into evidence.

Example. The Canonical Concept "Coverage (Claims Limit)" carries provenance entries from three claims-handling manuals, two regulatory filings, and one internal training document — each with author, date, and confidence.

Governed relationships: informs Governance decision & decision trace

Governance decision & decision trace

In plain language: Governance decision & decision trace

Common discovery terms: governance decision, decision trace, audit trail

An explicit, recorded act by a governance authority that approves, rejects, modifies, or deprecates a Canonical Concept.

Governance Decisions are first-class events. They name the actor, the prior state, the new state, and the rationale. Decisions accumulate into a concept's history and form the audit trail required for regulated industries and AI accountability frameworks.

Example. After a drift event between two definitions of "Coverage (Policy Scope)", the governance authority approves the Underwriting version and deprecates the contradictory submission. Both the decision and the rationale are recorded immutably.

Governed relationships: supported by Source provenance & traceability

Organizational Memory

The append-only history of every governance event, definition change, and learning signal an organization has accumulated about its terminology.

Organizational Memory is what allows an enterprise to answer, years later, how a concept evolved, why it changed, who approved it, and how often it has been reused. It is stored as an immutable event log — not editable records — so the history can never be silently rewritten.

Example. Five years after first ingestion, "Coverage (Reinsurance Cession)" can show its first-seen date, every drift event, every governance decision, and how its confidence evolved from 0.84 to 0.96.

Concept Reuse

The act of resolving a new definition to an existing Canonical Concept instead of creating a new one.

Reuse is the primary learning signal in Semantic Governance. Each reuse strengthens the confidence of the canonical concept, reduces duplication, and builds Organizational Memory. A high reuse rate indicates stable, well-governed meaning; a low rate indicates fragmentation or insufficient context resolution.

Example. A second upload of a Reinsurance definition resolves to the existing "Coverage (Reinsurance Cession)" concept, raising confidence from 0.95 to 0.97 with no duplicate created.

Semantic Stability

A measure of how consistently a Canonical Concept holds its meaning across ingestions, reviews, and time.

Semantic Stability is derived from the concept's history: ratio of reuses to drift events, confidence trend, frequency of manual review, and time since last contradiction. It is not a marketing score — it is computable evidence that a term is governed well.

Example. "Coverage (Claims Limit)" with 43 reuses, 2 drift events resolved within a week, and rising confidence has higher Semantic Stability than a term with 3 reuses and 5 unresolved drift events.

AI Alignment (Semantic)

The state in which AI agents resolve business terms to the same governed meaning that humans and systems use.

Semantic AI Alignment is a prerequisite for trustworthy enterprise AI. Without it, large language models infer meaning from their training distribution, not from the organization. Semantic Governance provides the missing layer: a canonical, resolvable, evidence-backed meaning per term that an AI agent can cite instead of guessing.

Example. An enterprise assistant asked "what is our reinsurance coverage exposure?" resolves "coverage" to "Coverage (Reinsurance Cession)" via the canonical registry, instead of averaging a generic web-trained meaning.

Governed decision basis

In plain language: Governed decision basis

Common discovery terms: decision basis, governance basis, evidence-based decision

The versioned set of evidence, provenance, scope, authority and applicable meaning on which a governance review or decision is allowed to rely.

A Governed Basis makes the inputs to governance explicit and reviewable. AI may interpret source material, but governance relies on a bounded basis whose evidence, provenance, applicability and authority can be checked independently.

Example. Before a human reviewer records a decision, WikiSure can show which evidence, source versions, activation scope and authority form the governed basis for that review.

Governed relationships: supported by Source provenance & traceability; applies within Applicability — where this applies

Applicability — where this applies

In plain language: Applicability — where this applies

Common discovery terms: applicability, scope of application, where a rule applies

The explicit, versioned boundary that states where a governed proposition is permitted to apply.

Activation Scope is fail-closed: a missing scope is unknown, not universally compatible. Universal applicability requires an explicit versioned unrestricted scope rather than an inference from missing constraints.

Example. A proposition approved for one business process cannot be reused for another process unless its Activation Scope explicitly permits that use.

Governed relationships: governed by Governance decision & decision trace

Evidence coverage & gaps

In plain language: Evidence coverage & gaps

Common discovery terms: evidence coverage, evidence gaps, evidence completeness

The explicit account of which evidence universe and sources were investigated before a governance statement is made.

Evidence Coverage prevents a search result from being overstated. Not finding a conflict in investigated sources is different from proving that no conflict exists in the relevant evidence universe. Stronger absence claims require an explicit Coverage Policy and an Evidence Coverage Receipt.

Example. A review may state that no conflict was found in the investigated policy set; it may only make a stronger absence claim when the applicable coverage policy establishes that the relevant evidence universe was sufficiently covered.

Governed relationships: requires evidence Source provenance & traceability

Evidence Coverage Receipt

A machine-checkable record of the evidence universe, sources, coverage policy and investigation boundary used for a governance statement.

An Evidence Coverage Receipt preserves what was actually investigated and under which coverage policy. It supports later review of whether an absence or completeness statement was justified without converting an incomplete search into a universal claim.

Example. A receipt records the policy corpus, source versions and coverage rule used before the system permits the statement that no relevant conflict was found within that bounded evidence universe.

WikiSure Case Studio

The WikiSure software application for professional case-based review workflows.

Case Studio is the application boundary for professional and consultant workflows. Case Studio Sandbox is its evaluation environment; Solo and Team are commercial tiers or planned tiers of the same product rather than separate decision engines.

Example. A consultant evaluates the workflow in Case Studio Sandbox and can later use an entitled Case Studio tier without moving to a separate governance core.

AI Readiness

A workflow and application profile inside WikiSure Case Studio for preparing evidence-based AI implementation and governance reviews.

AI Readiness is not a separate WikiSure product or governance engine. Public discovery may demonstrate the workflow with synthetic material, while governed case work remains within the Case Studio boundary.

Example. A consultant uses the public AI Readiness walkthrough to understand the workflow, then evaluates the same product boundary through Case Studio Sandbox.

Control Assurance

Evidence-based review of a control's documented, implemented and tested state without turning system output into an automatic effectiveness decision.

Control Assurance is the buyer-facing term for WikiSure's professional control-assurance boundary. A control is linked to an assurance state, evidence references, applicable scope and time, and accountable professional judgment. EFFECTIVENESS_REVIEWED means that a responsible person reviewed effectiveness on that governed basis; it does not mean WikiSure automatically declared the control effective.

Example. A reviewer can see that a control was tested against identified evidence within a stated scope and period, then record a professional effectiveness review without converting the test result into machine-granted assurance.

Exception Management & Risk Acceptance

Governed handling of explicitly scoped, time-bound exceptions with recorded rationale, accepted risk, accountable approval and mandatory reassessment.

Exception Management and Risk Acceptance are established buyer-facing concepts for the boundary WikiSure models internally as a bounded professional exception. An exception must remain tied to its scope, rationale, accepted risk, conditions, accountable review position, expiry and reassessment linkage. Expiry never creates automatic renewal or approval, and persistence or import must not bypass those checks.

Example. A temporary deviation can be recorded for a defined scope until a stated expiry date, with the accepted risk and accountable review captured and a human reassessment required at expiry.