Next: Context Control
Turn evidence into deliberate input.
Choose the detail and context budget for the next model request.
Sources & Retrieval
One question.Connected evidence.
Bring code, documents and business data into the same context flow. LeanCTX finds relevant information across your permitted sources and keeps its origin attached.
The approach
Find the answer across the boundaries.
The implementation lives in a repository. The decision lives in a ticket. The current state lives in a database. LeanCTX brings the relevant evidence together for the task.
Your information
Different sources. One useful view.
Connect a local workspace, a service such as GitLab and a relational database. Each source contributes information through a common contract, with its own permissions and provenance.
- Code & files
- Locate implementations, declarations and exact source lines.
- Service knowledge
- Connect GitHub, GitLab and Jira knowledge; add MCP or configurable HTTP sources for your own services.
- Structured data
- Read bounded records from permitted Postgres tables or views. The model receives scoped results, not unrestricted SQL access.
A cross-source question
What changed in checkout — and which decision explains it?
Retrieve the implementation, the approved change and the relevant record. Keep each source identifiable as the context is compiled.
Task-aware retrieval
Search for relevance. Keep the context.
Combine exact search, indexed retrieval and code relationships. Rank candidates for the question, their available freshness and their source authority. A relevant result must also be permitted.
- Find
- Use text, semantic indexes or symbols to reach the right material.
- Reconcile
- Deduplicate repeated content while retaining its contributing sources.
- Prepare
- Pass selected candidates into a task- and budget-bound context plan.
Source lineage
Every finding. A way back.
Keep source identity, contributing versions and available freshness metadata with the result. When sources disagree or a detail matters, return to the original before making the next decision.
- Origin
- Know which source contributed each piece of evidence.
- Freshness
- Distinguish current material from expired or superseded records.
- Recovery
- Recover retained or current source detail under current permissions; revoked access also blocks cached recovery.
Permitted knowledge
Connected does not mean unrestricted.
Source scope follows the identity and policy behind the request. Revoked access, a forbidden source or an invalid record cannot become authorized merely because it matches the question.
- Identity
- Check the requester’s source permissions before acquisition. A service credential alone does not authorize the user.
- Untrusted content
- Treat retrieved instructions as source data, not permission to act.
- Delivery rules
- Inspect the selected content before it enters model context.
Questions & answers
Your sources, explained.
Does every request query every source?
No. LeanCTX uses the sources, indexes and retrieval path relevant to your task. Credentials, source permissions and refresh settings define the available material.
Can I connect my own data?
Use a supported provider, MCP bridge or the versioned Engine source interface. Preserve source identity and permissions when your application supplies material.
Start with LeanCTX
Connect your first source.
Start with a project you know. Add the sources that explain the decisions around it.
Local-first. Model-agnostic. Your context.