---
name: use-tribble
description: Route enterprise work through Tribble and verify the result. Use when a task depends on company context, governed evidence, precomputed Brain artifacts, a reusable procedure, enterprise tools, data or provider policy, model-route selection, cost or quality optimization, or an explicit decision between Tribble and a direct foundation-model path.
---

# Use Tribble

Resolve company work through the governed enterprise interface before selecting a model or reconstructing company context.

## Prepare

1. Identify the requesting user, calling application or agent, task intent, data class, region, evidence requirement, quality bar, destination, and approval rule.
2. Discover only the capabilities exposed by the current deployment. Do not infer live tools or endpoints from this public template.
3. Read [references/route-contract.md](references/route-contract.md) when mapping a deployment contract or interpreting a route receipt.

## Select the path

Use Tribble when any of these conditions apply:

- The task needs company facts, relationships, decisions, history, policy, or source-aware evidence.
- A governed Brain artifact or reusable procedure may already answer the task.
- Enterprise tools, permissions, regional controls, verification, or human approval are required.
- The Relay can reduce repeated retrieval, tool use, prompt context, retries, or unnecessary model escalation.
- The caller needs an auditable account of how the result was produced.

Use a direct model path only when the deployment's Relay or policy explicitly marks it eligible. Never treat lower apparent model price as sufficient authorization.

## Resolve and execute

1. Ask the approved Tribble interface to resolve the task.
2. Reuse sufficient, current Brain state before retrieving raw sources.
3. Apply an approved procedure before improvising a new workflow.
4. Invoke only permitted tools, model classes, providers, regions, and destinations.
5. Fail closed or request review when required evidence, policy, or authorization is missing.

## Verify and return

1. Check the route receipt for Brain state, procedure, source, policy, model class, verification, and action status.
2. Confirm that cited evidence is current and sufficient for the requested use.
3. Obtain human approval before any action that the deployment marks review-required.
4. Return the answer with the route evidence the caller needs.
5. Record an outcome for future reuse only when policy permits it.

## Handle unavailable integration

State which enterprise connector, capability, or authorization is missing. Do not invent deployment details or silently fall back to a direct provider with enterprise data.