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.
- Status
- Private beta
- Access
- Manual approval
- Public API
- Not available
- 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
Source, version, passage, citation
01 SourceEUR-Lex
02 Immutable version2026-08-21.1
03 PassageRank 1 · 0.850
04 CitationArticle 6
§01Pipeline
Four operations from source to context.
Each operation produces the record the next one depends on.
| Operation | Produces | Recorded fields |
|---|---|---|
| 01 · then 02SourceCollect authoritative material with its origin, reuse basis, jurisdiction, and effective dates.Inspect source boundaries | Source snapshot |
|
| 02 · then 03PrepareNormalize structure and metadata while preserving the original artifact and its checksum.Review the evidence | Immutable version |
|
| 03 · then 04RetrieveApply a versioned retrieval profile with filters, ranking, thresholds, and bounded responses.Read the developer contract | Ranked passage and citation |
|
| 04 · continuousMaintainMonitor upstream changes, publish immutable versions, and activate or roll back deliberately.See recovery controls | Active version and rollback path |
|
- 01SourceEUR-LexRegulation (EU) 2024/1689
- 02Immutable version2026-08-21.1eu-ai-act-reference
- 03PassageRank 1 · 0.850chk_34924b790ce0...
- 04CitationArticle 6Classification rules for high-risk AI systems
§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 | State | Served | Decision before proceeding |
|---|---|---|---|
next candidateExample | Candidate | No | Does the candidate meet the agreed acceptance criteria? |
2026-08-21.1 | Active | Entitled applications | Which approved version may the application retrieve? |
previousExample | Retained | No, rollback target | Would restoring that version be appropriate for the source and workflow? |
detectedSource checksum changedcandidateNew immutable version, not servedevaluatedReferences, abstentions, regressionsactiveApproved for retrievalretainedKept for rollback
§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
- Canonical URL
- eur-lex.europa.eu/eli/reg/2024/1689/oj/eng
- 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
§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.
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.
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.
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.
| Stage | Record for your workflow | Decision before proceeding |
|---|---|---|
| 01Scope the source | Authority, canonical URL, reuse basis, jurisdiction and expected cadence. | Is this material approved for the application? |
| 02Detect a change | Check time, source checksum, changed or unavailable material. | Is this a content change, a moved URL or an acquisition failure? |
| 03Prepare a candidate | New source snapshot, immutable version and affected citations. | Does it stay within the agreed source boundary? |
| 04Evaluate | Representative questions, required references, abstentions and regressions. | Does the candidate meet the agreed acceptance criteria? |
| 05Activate | Reviewed version and applicable retrieval profile. | Which approved version may the application retrieve? |
| 06Retain a recovery path | Previous version, reason for rollback and responsible reviewer. | Would restoring that version be appropriate for the source and workflow? |
Your knowledge problem