For knowledge providers

Put your knowledge to work in AI products. Keep control of the source.

CorpusMesh is preparing a controlled distribution layer for publishers, data companies, associations, and expert networks. You define the approved corpus and rights. We operate the versioned retrieval boundary.

Prelaunch
Provider onboarding is manual. CorpusMesh has no announced provider partners yet.

Provider distribution boundary

  1. Provider sourceOwned and maintainedrights · versions · updates
  2. CorpusMeshRetrieval boundaryprovenance · entitlements · metering
  3. Approved customersBounded contextpassages · metadata · citations
The provider remains the editorial authority. Approved customers receive bounded context, not an unrestricted corpus export.

§01Three source routes

Partner is a commercial relationship, not an ingestion shortcut.

Every corpus enters through a declared rights route. The route determines who authorizes processing, who can retrieve, and what happens when access ends.

Source routes and who authorizes them
RouteAuthorized byHow it worksFits
CurateCorpusMesh-ledCorpusMesh selects a public or rights-clean source, documents the reuse basis, and maintains the corpus.For authoritative material that can support a reusable knowledge base.
ConnectCustomer-authorizedA customer authorizes CorpusMesh to process content it owns or validly licenses inside a private scope.For knowledge that must remain isolated to that customer's entitlement.
PartnerProvider routeProvider-controlledA knowledge owner grants bounded processing and retrieval rights under a reviewed commercial agreement.For a maintained corpus that should reach approved AI applications without becoming an unrestricted download.

§02Rights intake

The first deliverable is a precise boundary.

Before a source is processed, both sides establish what may be held, transformed, delivered, measured, and retained. Public availability alone is not permission.

Rights intake questions
FieldQuestion to settle before processing
01AuthorityWho owns the material, and which third-party rights or restrictions travel with it?
02Permitted useDoes the agreement allow normalization, retrieval, citations, and derived artifacts? Training rights are reviewed separately.
03DeliveryWhich source files, feeds, APIs, metadata, identifiers, and update signals are authoritative?
04AudienceWhich customers, products, territories, environments, and use cases may receive retrieved passages?
05Commercial termsWhich usage unit, reporting cadence, review point, and termination rules belong in the agreement?
Discuss a bounded corpus

§03Operating model

Clear ownership at every handoff.

CorpusMesh manages retrieval infrastructure. It does not replace the provider's editorial authority or the customer's application intelligence.

  1. Provider

    Own the source

    Set the editorial authority, approved corpus, update path, attribution, and rights boundary.

  2. CorpusMesh

    Operate the retrieval layer

    Version, normalize, evaluate, index, meter, and serve only within the agreed scope.

  3. Customer

    Use entitled context

    Retrieve bounded passages and citations while keeping its own model, prompts, agents, and application.

§04Provider controls

A distribution agreement should be inspectable in operation.

Source ownership, derived-artifact permissions, attribution, access, metering, and exit behavior become explicit controls rather than assumptions hidden in a pipeline.

  • Source and update ownership
  • Entitlement boundaries
  • Usage and attribution policy
  • Termination sequence
Provider agreement / Control ledgerReviewed before activation
Provider controls, their owner, and their behavior
ControlOwnerBehavior
Source authorityProviderCorpusMesh records the approved corpus, rights basis, and source version.
UpdatesProviderThe provider remains editorial authority and supplies or approves the update path.
Derived artifactsAgreementNormalization, chunks, embeddings, and indexes follow the permissions and retention terms.
Customer accessEntitlementsNamed products, customers, environments, versions, and retrieval scopes are bounded.
UsageMeteredRequests, delivered passages, and agreed commercial units can be reported without exposing customer prompts by default.
AttributionPolicyCitation and attribution requirements travel with the retrieval contract.
WithdrawalControlledNew access can stop, active entitlements can retire, and derived material follows the agreed termination sequence.

§05Withdrawal and termination

An exit path is designed before activation.

The exact sequence is contract-specific. CorpusMesh prepares the technical controls needed to stop distribution without losing the evidence required to account for prior use.

  1. Step 1

    Stop granting new entitlements at the agreed cutoff.

  2. Step 2

    Suspend or expire active customer access according to the contract.

  3. Step 3

    Retire serving projections and derived artifacts under the agreed retention schedule.

  4. Step 4

    Preserve only the audit, usage, and contractual records the agreement or law requires.

§06Reporting and commercial review

Measure the distribution, then review the agreement.

A provider engagement can define reporting around entitled customers, request volume, delivered passages, versions, access events, and agreed commercial units. Reporting scope and economics are reviewed before launch and at contract checkpoints.

Access
Which entitlement used which version
Usage
Agreed retrieval and delivery units
Quality
Evaluation and source-maintenance evidence
Review
Commercial and scope checkpoints
Not launched
Future capabilities, not current product claims: marketplace discovery, self-service publishing, billing, and provider revenue share have not launched. CorpusMesh has no announced provider partners.

§07Provider questions

What the prelaunch model does and does not assume.

Does a Partner agreement include model-training rights?

No. Retrieval, derived-artifact, and model-training rights are separate questions. CorpusMesh only uses the permissions explicitly reviewed and recorded in the agreement.

Who controls source updates?

The provider remains the editorial authority for Partner material. The agreement defines the authoritative delivery path, update cadence, version acceptance, and any emergency withdrawal process.

How are customers allowed to access the corpus?

Entitlements can bound the approved customer, product, environment, corpus version, geography, filters, and retrieval limits. Access is not an unrestricted corpus export.

What commercial model does CorpusMesh offer?

There is no published provider tariff or revenue-share promise. Scope, metering units, reporting, economics, and review points are assessed with each prospective provider.

Provider discovery

Start with one corpus and one honest rights boundary.

Tell us what you maintain, who needs it, how it changes, and which uses you are prepared to review.

Request a provider conversation