Skip to content

Knowledge Mesh

Every answer comes with its source.

It reads your sources in place, applies the caller’s permissions, decides which passage governs, and answers with the citation.

Book a DemoSee how it runs
  • One layer, every application
  • Permission-filtered
  • Citations that open the source
Story01 / 10

Every source has an answer. Only one of them governs.

The layer itself, then the business case in three scenes: the estate as it stands, the layer that decides what governs, and the applications that share it.

  1. What the layer does

    Reads, filters, decides, then cites.

  2. Finding is not deciding

    Similar articles, different ages.

  3. One layer decides

    Filtered, scoped, ranked, then cited.

  4. One shared layer

    Search, service and agents ask it.

An isometric scene of four source pads, for documents, records, tickets and manuals, cabled into a round mesh ringed with beads, with one answer tile leaving it, all inside a drawn perimeter.
  1. DocumentsPolicies and manuals, read where they already live
  2. The meshDecides which passage governs when sources disagree
  3. Cited answerOpens onto the passage that supports it
  4. Your boundaryDeployed where you decide, with the Voicing runtime

Ask us for a retrieval trace

Illustrative scene, not a product capture

Capability 1 of 4: What the layer does

Sources02 / 10

Each source is selected on its own terms.

Every source is connected on the terms its own system uses.

Knowledge objects

Only named objects.Your conditions select them.

Salesforce

Sites and libraries

Choose sites and libraries.Metadata filters them again.

SharePoint

Service records

Your team writes conditions.That encoded query runs.

ServiceNow

SQL views

Your database team’s views.Read-only, nothing beyond.

Documents

Parsed and scanned pages.Sections, tables kept apart.

Per-connection policy

Its own owner and inclusion.Its own access and refresh.

Knowledge Mesh

Each source keeps its identity, version, address and watermark

How it runs03 / 10

Eligible, applicable, ranked, then one rule decides.

Comprehensive in, salient out: a request is filtered by rights, narrowed, ranked, and settled by the rule that governs when sources disagree; the answer is cited.

Eligible, applicable, ranked, then one rule decides.Comprehensive in, salient out: a request is filtered by rights, narrowed, ranked, and settled by the rule that governs when sources disagree; the answer is cited. The steps, in order: Sources, Access, Scope, Relevance, Authority, Cited answer.SourcesRead in placeAccessRole and policyScopeRegion and datesRelevanceFor the questionAuthorityRule, precedenceCited answerRead in placeNothing is copied outEligible firstRights before relevanceApplicableCurrent and in scopeRelevantUseful is not governingGoverningPrecedence over likenessCitedOpens the source passage

Five decisions04 / 10

Inclusion, access, scope, relevance, authority: kept apart.

Five decisions stay separate, so each one stays reviewable.

An eligible source passes access before it can become a citationSourcesEligibleExcludedAccessCitationSourceVersion
Source records

Source inclusion

Which records may be retrieved at all, by rule.

Eligible passage
Relevant, but inaccessible

Access policy

Who may see a record, filtered at retrieval.

Context and scope

The part of the business this assistant serves.

Relevance ranking

Which eligible record answers the question.

Business authority

Conditions, timing and precedence, declared.

Citation

Cited to source and version, or an honest no.

SourceSectionAddressVersion
Knowledge Mesh

A cited answer or an honest no

Capabilities05 / 10

Every capability, shown on the product.

Eight product captures, one per capability, each a demonstration with sample data and labelled as such, so an evaluator sees the screen and not a diagram of it.

Product demonstration with sample data

Film06 / 10

Watch one question become a cited answer.

One customer question, followed across every connected system, through the rule that settles a disagreement, and on to the passage on screen that supports the answer.

  1. One questionKnowing which guidance to trust
  2. Sources, connectedEach keeps its own identity
  3. Context, preservedPermissions travel with the text
  4. Disagreement, visibleWhere the sources conflict
  5. Authority, explicitThe decision records why
  6. Access, in contextThe caller’s rights, applied
  7. Answer, citedOpen the passage behind it
  8. Delivered, everywhereSearch, service, copilots, voice

Product demonstration with sample data

Snapshots07 / 10

Seven screens, one for each decision.

Each frame is a product demonstration with sample data and answers one evaluation question, from selection at the source to the correction of a wrong one; open any frame at full size with a click.

  • Selecting knowledge with a native query

  • Relationships across systems, shown together

  • Where sources disagree, and which governs

  • Permissions applied before retrieval

  • A grounded answer beside its passage

  • Thin evidence says so instead of answering

  • A correction, reviewed and published

Where it runs08 / 10

One deployment boundary, reviewed once.

Knowledge Mesh is deployed with the Voicing runtime, on-premises, in your cloud or in Voicing Cloud, so the layer, its index and its records fall inside one boundary that procurement reviews once.

  • On-premises

    The retrieval layer, its index and its records run on hardware you operate; connectors reach your systems over your network.

  • Your cloud

    The same deployment in your own tenancy: your keys, your network policy, your logs, and connectors scoped to the sources you name.

  • Voicing Cloud

    A dedicated environment with the same controls, for teams that want the layer run for them while access stays permission-filtered.

Proof09 / 10

Knowledge Mesh

There is no published Knowledge Mesh case study yet; ask us for a demonstration against your own sources.

Talk to an engineer

Closing10 / 10

Bring one call type. Leave with an architecture.

A white suite case opening on six coloured discs, the product surfaces, rising between its lid and its base.
Knowledge Mesh

Comprehensive in, salient and cited out

A working session with an engineer who has deployed inside a bank’s perimeter. We map your telephony, data boundary and handoff rules, and tell you what we would not automate.

Book a Demo