Follow every answer back to evidence.
Citations identify the document, thread, ticket, or conversation behind each material point so the reader can inspect the source.
Search approved mail, files, conversations, tickets, code, and internal systems from one surface. Linkence synthesizes the answer with citations and keeps governed execution behind a visible handoff.
Read-first by design. Sources stay visible. Scope follows the configured workspace and connector model.AI Chat retrieves the configured evidence, reconciles exact identifiers with natural-language context, and returns one answer a user can inspect. Existing systems remain the source of record, and a question never becomes an invisible write.
The answer is split across inboxes, files, tickets, and conversations.
People find different versions and cannot tell which source is current.
A summary without citations is difficult to trust or hand to another team.
Fictional demo for Northstar Services, Atlas Retail, in Project Atlas. No external system is changed.
What did we promise Atlas Retail about the SSO fix, and what is still open?
Northstar committed to a configuration patch by Friday and an implementation note before Monday's review. The patch is linked to ENG-731, while the implementation note still has no owner.
Configuration patch due Friday. Implementation note required before Monday review.
Citations identify the document, thread, ticket, or conversation behind each material point so the reader can inspect the source.
A user can narrow the active source set instead of searching every connected system for every request.
When the next step needs a supported write, the answer and its cited source bundle move into an Actions preview.
Send the verified source bundle into an Actions preview. The exact target and payload stay visible before any supported write can run.
Explore ActionsThe exact gold section appeared in the top ten results for 96.6% of the stratified sample. On all 3,045 valid queries, strict section accuracy@10 was 94.6%. Raw per-query results, manifests, failures, and a verification script are public.
Review methodology and results500 queries · Strict section accuracy@10
3,045 queries · Strict section accuracy@10
Strict section accuracy@10The exact gold document and section appears within the top ten retrieved units.
Retrieval evaluation only. It does not measure answer correctness, workflow execution, production latency, or every customer corpus.
A question about promises and open work
A cited timeline, owners, and unresolved items
Prepare a reviewed follow-up in ActionsA question about the current policy
An answer with the exact source section
A person validates the exception pathA question about a technical decision
A cited decision narrative
An engineer decides the formal workAvailability and connector-specific behavior are stated directly, without universal claims.
No. AI Chat is read-first. A supported write moves into Actions, where the target, payload, and required approval remain visible.
It measures whether the exact gold section appeared in the retrieved top ten. It does not measure answer correctness or every customer corpus.
No. Scope and access behavior differ by connector. Each integration page states the verified model for that system.
Connect the relevant sources and show Linkence the approval rules. See the path from evidence to follow-through on your own data.
Representative data is enough for the first demo. No production access required.