Source
Collect authoritative material with its origin, reuse basis, jurisdiction, and effective dates.
Follow this boundary →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 intended product contract. Public access is not yet available.
Prepare
Normalize structure and metadata while preserving the original artifact and its checksum.
Follow this boundary →Retrieve
Apply a versioned retrieval profile with filters, ranking, thresholds, and bounded responses.
Follow this boundary →Maintain
Monitor upstream changes, publish immutable versions, and activate or roll back deliberately.
Follow this boundary →The service boundary
You own the intelligence. We maintain the knowledge.
Source collection, provenance, normalization, versioning, indexing, retrieval quality, updates, and citations.
Models, prompts, agents, application behavior, customer experience, and the decision made from retrieved context.
Source 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.
Reviewed EU AI Act traceSource authority
European Parliament, Council of the European UnionCorpus versioneu-ai-act-reference@2026-08-21.1Document checksumsha256: ced2ae9c...ba859820Verificationverified · publication reviewedInspect the complete Source Trace →Keeping 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.
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.
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.
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.
Maintenance review
Agree what happens after a source changes.
This checklist describes the review process, not a new before-and-after experiment. The EU AI Act beta includes daily checks of the approved source set; check frequency is not a guarantee of immediate activation.
| Stage | Record for your workflow | Decision before proceeding |
|---|---|---|
| Scope the source | Authority, canonical URL, reuse basis, jurisdiction and expected cadence. | Is this material approved for the application? |
| Detect a change | Check time, source checksum, changed or unavailable material. | Is this a content change, a moved URL or an acquisition failure? |
| Prepare a candidate | New source snapshot, immutable version and affected citations. | Does it stay within the agreed source boundary? |
| Evaluate | Representative questions, required references, abstentions and regressions. | Does the candidate meet the agreed acceptance criteria? |
| Activate | Reviewed version and applicable retrieval profile. | Which approved version may the application retrieve? |
| Retain a recovery path | Previous version, reason for rollback and responsible reviewer. | Would restoring that version be appropriate for the source and workflow? |
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.
Inspect the published source trace, use the evaluation worksheet, or compare build and buy responsibilities. The beta offer defines the current commercial scope.
Your knowledge problem