Use cited evidence in a reviewed outputConnected mail or chat action
ProjectConnected companion
TitleGrounded follow-up
AssigneePriya Mehta
Priority↑ High
Due date8 August
BRAINTRUST INTEGRATION · Available
Eval results, explainable in one question.
Index Braintrust experiments, evaluations and logs so AI product teams get cited answers about quality, regressions and prompt behaviour.
Representative data is enough. No production access required for the first demo.AvailabilityAvailable
ReadsExperiments and evals, Logs
FreshnessScheduled sync through the Linkence indexing pipeline
ScopeAdmin-selected projects
WritesRead only; writes run through connected companions
WHAT ENTERS LINKENCE
Bring the useful context into scope, not the entire system.
Braintrust connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your Braintrust account remains the system of record.
Experiments and evals
Scores, comparisons and summaries
Selected projectsLogs
Trace and span content within scope
Selected projectsHigh-volume logs are sampled per project configurationFind · Prepare · Act
One Braintrust connection, three governed jobs.
BETTER WITH COMPANIONS
Braintrust gets more useful when it knows what happened elsewhere.
Pair Braintrust with Github, Linear, Slack and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
Governed cross-system result Evidence attached
GitHubIssues
Cited in the resultAdmin-selected repositories
LinearIssues
Cited in the resultAdmin-selected teams
SlackChannel messages
Cited in the resultAdmin-selected channels
The failing spans, the diff and the discussion, citedApproval required
SCOPE AND BOUNDARIES
Connection does not mean unrestricted access.
Included when configured
- Admin-selected projects
- Experiments, evals and scoped logs
- Citations to the exact experiment
Not assumed, not included
- Projects outside the connected scope
- Writing back into Braintrust
- Unbounded log ingestion
COMMON WORKFLOWS
Real jobs teams run with Braintrust.
Explain a quality regression
GitHubSlack
The failing spans, the diff and the discussion, cited
RELATED CONNECTORS
Pairs that make Braintrust answers stronger.
ASK IT YOURSELF
Questions Braintrust answers on day one.
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original Braintrust record.
Which evals regressed after the prompt change?
Summarise the scores for the support agent experiment.
Compare the last two summarisation runs.
BRAINTRUST QUESTIONS
Direct answers about Braintrust.
Every answer reflects the verified connector behaviour, never generalised.
What does the Linkence Braintrust integration include?+
Admin-selected projects; Experiments, evals and scoped logs; Citations to the exact experiment.
What is outside the scope of the Braintrust integration?+
Projects outside the connected scope; Writing back into Braintrust; Unbounded log ingestion.
How fresh is Braintrust data in Linkence?+
Scheduled sync through the Linkence indexing pipeline. Scope: Admin-selected projects.
Can Linkence take actions in Braintrust?+
The Braintrust connector is read-focused. Writes happen through connected companions, for example a grounded reply in mail or an approved update in chat, always with approval.
SEE BRAINTRUST IN A REAL WORKFLOW
Bring Braintrust into one governed workflow.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.