How it works

A maintained path from source to context.

CorpusMesh handles the knowledge pipeline your product should not have to rebuild. Every retrieved passage keeps a trace back to the source and corpus version that produced it.

Private beta
The interfaces shown here define the product contract for approved private-beta customers. Access is reviewed manually and public retrieval is not available.
Status
Private beta
Access
Manual approval
Public API
Not available
Ledger entryReviewed EU AI Act trace
trace_id
ret_65f782594371...
knowledge_base
eu-ai-act-reference
version
2026-08-21.1
source
EUR-Lex · Regulation (EU) 2024/1689
passage
rank 1 · score 0.850
citation
Article 6 Classification rules for high-risk AI systems
decision
answer
review
publication-reviewed · 2026-08-21
Open the complete Source Trace

Source, version, passage, citation

  1. 01 SourceEUR-Lex

  2. 02 Immutable version2026-08-21.1

  3. 03 PassageRank 1 · 0.850

  4. 04 CitationArticle 6

One passage from the publication-reviewed EU AI Act Source Trace (2026-08-21), followed from its source to its citation.

§01Pipeline

Four operations from source to context.

Each operation produces the record the next one depends on.

The four pipeline operations and the record each produces
OperationProducesRecorded fields
01 · then 02SourceCollect authoritative material with its origin, reuse basis, jurisdiction, and effective dates.Inspect source boundaries Source snapshot
  • authority
  • canonical URL
  • reuse basis
  • effective date
02 · then 03PrepareNormalize structure and metadata while preserving the original artifact and its checksum.Review the evidence Immutable version
  • normalized document
  • chunk manifest
  • checksums
  • version id
03 · then 04RetrieveApply a versioned retrieval profile with filters, ranking, thresholds, and bounded responses.Read the developer contract Ranked passage and citation
  • allowed filters
  • ranked passages
  • citation anchor
  • retrieval decision
04 · continuousMaintainMonitor upstream changes, publish immutable versions, and activate or roll back deliberately.See recovery controls Active version and rollback path
  • change check
  • candidate version
  • evaluation gate
  • previous version retained
Lineage of one passageeu-ai-act-reference@2026-08-21.1
  1. 01SourceEUR-LexRegulation (EU) 2024/1689snapshot8f0b6563...872d721a
  2. 02Immutable version2026-08-21.1eu-ai-act-referencemanifest2d73f00d...81e74924
  3. 03PassageRank 1 · 0.850chk_34924b790ce0...chunkeeed91ee...b4e4b3d7
  4. 04CitationArticle 6Classification rules for high-risk AI systemsanchor#art_6
Scope
Values from the publication-reviewed EU AI Act Source Trace (2026-08-21). The internal reference corpus is not an available commercial knowledge base.

§02Activation and rollback

Publish immutable versions. Activate or roll back deliberately.

A verified candidate passes review and evaluation before activation, with the prior version retained for rollback.

Version register, illustrated. Only the active version comes from the published trace.
VersionStateServedDecision before proceeding
next candidateExampleCandidateNoDoes the candidate meet the agreed acceptance criteria?
2026-08-21.1ActiveEntitled applicationsWhich approved version may the application retrieve?
previousExampleRetainedNo, rollback targetWould restoring that version be appropriate for the source and workflow?
  1. detectedSource checksum changed
  2. candidateNew immutable version, not served
  3. evaluatedReferences, abstentions, regressions
  4. activeApproved for retrieval
  5. retainedKept for rollback
Limit
The EU AI Act beta includes daily checks of the approved source set; check frequency is not a guarantee of immediate activation.

§03The service boundary

You own the intelligence. We maintain the knowledge.

CorpusMesh owns

  • Source collection
  • Provenance
  • Normalization
  • Versioning
  • Indexing
  • Retrieval quality
  • Updates
  • Citations

Your team owns

  • Models
  • Prompts
  • Agents
  • Application behavior
  • Customer experience
  • The decision made from retrieved context

§04Source trace

A result should be inspectable, not merely plausible.

Each passage is designed to include the source authority, canonical URL, version, effective date where available, document identity, and citation metadata.

Source authority
European Parliament, Council of the European Union
Knowledge base
eu-ai-act-reference
Corpus version
2026-08-21.1
Effective date
2024-08-01
Document checksum
sha256: ced2ae9c...ba859820
Citation
Article 6 Classification rules for high-risk AI systems
Verification
verified · publication reviewed 2026-08-21
Limit
The trace returns source context and does not generate or validate a legal answer.
Inspect the complete Source Trace

§05Keeping external knowledge current

Define freshness from the source to the passage.

A source check, an indexed version and a retrieved passage have different timestamps. Agree which one matters for your workflow before setting an update requirement.

  1. Source age

    Record when the authority published or changed the material and when it was last checked. A successful check does not mean a new version was published.

  2. Index age

    Identify the source snapshots and corpus version used to prepare the retrieval index. Newly detected material remains a candidate until its scope and evaluation are reviewed.

  3. Passage version

    Inspect the version and citation returned to the application. The public EU AI Act trace is pinned to its reviewed artifact and is not a live freshness feed.

§06Maintenance review

Agree what happens after a source changes.

This checklist describes the review process, not a new before-and-after experiment.

Source maintenance worksheet for a bounded workflow
StageRecord for your workflowDecision before proceeding
01Scope the sourceAuthority, canonical URL, reuse basis, jurisdiction and expected cadence.Is this material approved for the application?
02Detect a changeCheck time, source checksum, changed or unavailable material.Is this a content change, a moved URL or an acquisition failure?
03Prepare a candidateNew source snapshot, immutable version and affected citations.Does it stay within the agreed source boundary?
04EvaluateRepresentative questions, required references, abstentions and regressions.Does the candidate meet the agreed acceptance criteria?
05ActivateReviewed version and applicable retrieval profile.Which approved version may the application retrieve?
06Retain a recovery pathPrevious version, reason for rollback and responsible reviewer.Would restoring that version be appropriate for the source and workflow?
Exception
For a missing or withdrawn source, record the exception and review its effect on coverage. Do not treat an unavailable page as unchanged knowledge. Agree who reviews source changes and who validates the resulting application behavior.

Your knowledge problem

Tell us what your application has to keep current.

Discuss a knowledge base