On this page
Guided workflows
Prepare a document corpus
Verify extraction before trusting retrieval over non-code material.
Before you start
Choose a small, representative set of documents and a question with a known answer. Include the difficult material: a table, a long document, an unusual encoding or a restricted provider resource. Avoid indexing the whole collection before testing extraction.
Choose the source path
Local files, URLs and providers have different readers and authentication contracts. Confirm that your chosen path supports each format. A file extension alone does not establish support for a scanned PDF, embedded image, email archive or binary attachment.
For an external provider, inspect the configured surface first:
{"name":"ctx_provider","arguments":{"action":"list"}}
Use the provider and resource names returned by your runtime. Credentials must be available to the process launching LeanCTX. Listing a provider does not grant access to its data.
Inspect the extracted material
Compare returned text with the original. Check headings, table cells, source locations and the part containing your known answer. Record unsupported or missing material explicitly.
If an attachment was not read, do not describe the parent document as fully indexed. Decide whether to exclude it, use a supported reader or retain it for manual inspection.
Test a known retrieval
Ask the known question through the intended workflow. Inspect the matching passage and follow its source reference. Then ask a second question whose answer is absent; the workflow should not treat missing evidence as permission to invent it.
Consolidation can make provider results available to retrieval and project knowledge. It does not query every connected provider on every task.
Establish a refresh boundary
Record when the source was retrieved and which project or remote revision it represents. Repeat the test after a relevant source change. Cached provider material is an observation, not a live subscription.
Review retained data and credentials before adding more sources.
Check the result
You have a corpus with known coverage, tested source references and a documented refresh expectation. Expand only after these checks pass for the sample.
See data sources for provider configuration and web and research for URL and Git reads.
Sources & versions
- registry.rsrust/src/core/providers/registry.rsGitHub
- config.rsrust/src/core/providers/config.rsGitHub
- github.rsrust/src/core/providers/github.rsGitHub
- gitlab.rsrust/src/core/providers/gitlab.rsGitHub
- jira.rsrust/src/core/providers/jira.rsGitHub
- postgres.rsrust/src/core/providers/postgres.rsGitHub
- mod.rsrust/src/core/providers/config_provider/mod.rsGitHub
- ctx_provider.rsrust/src/tools/ctx_provider.rsGitHub
- Core checkout
0ce2207ee4- Reviewed runtime
- 3.10.2
- SDK release
- 1.1.0
Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.
Versions & compatibility