Sourceform technology
Context, found inside a boundary.
Retrieval starts with what this exact deployment is allowed to know. Only then does Sourceform understand the question, combine retrieval routes, and verify the answer against original evidence.
Permission before relevance
Search cannot grant access.
Search infrastructure is a derived, untrusted index. Every result is replaced with its immutable source evidence and checked against the tenant and publication snapshot before a reranker or model can see it.
- 01Authorize deployment
- 02Retrieve candidates
- 03Reauthorize evidence
- 04Allow model egress
Several signals. One evidence set.
The retrieval route is bounded and deterministic. It may expand the search, but it never expands authorization.
Understand the request without widening it.
- DecompositionUp to four explicit subquestions
- Entities and aliasesTenant-scoped; ambiguity stays visible
- Coreference cuesReferences such as “it” or “that policy” are flagged
Multi-hop, but never open-ended.
Concepts, entities, aliases, and relations live in an immutable Semantic Release. Only verified relations with original evidence can contribute context, and traversal stops after two hops.
Atlas 2024SUPERSEDED BYAtlas 2026
Relation evidence returns to the standard authorization path.“Current” is a question, not a pointer.
Years, “latest,” and effective-version language become explicit temporal intent. Answering still reads only the exact Source Versions frozen into the Bot Deployment.
- Source Version
- Immutable
- Publication Snapshot
- Exact
- Mutable current pointer
- Never read
Query routes
Different questions need different context paths.
The route changes. The authorized tenant, bot deployment, publication snapshot, and source versions do not.
Question“What does SKU ATLAS-24 include?”
01 · UnderstandQuoted values and identifiers stay exact.
02 · RouteExact hybridBM25 keeps the identifier; dense retrieval finds explanatory passages.
03 · RejoinRRF combines both rankings before reranking.
The answer can point back to the original.
Normalization creates searchable structure without replacing the original location. Each eligible passage retains its Source Version and the locator appropriate to its format.
Claim-level verification
Generation is a draft, not a decision.
Every atomic claim must cite evidence that survived authorization. Literal facts such as dates and numbers are checked against those passages, then the verifier decides what can be delivered.
Review the trust boundaryMay be deliveredWith authorized citations
Removed or surfaced as conflictNever silently reconciled
Removed from the answerIf nothing remains, Sourceform abstains
Not every question should become an answer.
When verified published sources disagree, Sourceform preserves both citations and asks for resolution instead of choosing.
Supported claims may be delivered while rejected claim text is removed completely.
If eligible evidence is insufficient, the answer says so. An abstention is not billed as a verified answer.
A reproducible answer system
Build your assistant